Results for “contract_exchange_rate”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PO_BPOS_HDR_EFC is a shadow table owned by the GML schema (Process Manufacturing Logistics) in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to serve as a shadow copy of PO_BPOS_HDR for EFC (Enterprise Financial Consolidation / E-Business Financials Consolidation) migration. The table carries a status of VALID in the ETRM repository and, per the documented physical schema for 12.2.2, contains only three columns: BPO_ID, CONTRACT_EXCHANGE_RATE, and SET_OF_BOOKS_ID.

The object exists primarily to support data migration and consolidation processing rather than day-to-day transactional activity. Because it shadows a base purchasing document header, it is best understood as an auxiliary staging or mirror structure that allows the migration process to preserve header-level attributes without directly modifying the live PO_BPOS_HDR table. The heuristic Data Vault classification mined from the foreign-key structure is standalone; from a modeling standpoint this suggests the table behaves as an independent satellite-like construct rather than a true hub or link, since the only documented referential relationship is a self-referencing FK back to PO_BPOS_HDR.

Key Information Stored

The documented column list for PO_BPOS_HDR_EFC is narrow and purpose-built. The most important columns are:

• BPO_ID — The identifier that links the shadow record back to the corresponding row in PO_BPOS_HDR. This is the only documented foreign key, defined as PO_BPOS_HDR_EFC.BPO_ID → PO_BPOS_HDR. As a result, BPO_ID acts as the effective join key and business-key candidate for the shadow row, rather than a column unique to the shadow table itself.
• CONTRACT_EXCHANGE_RATE — The exchange rate associated with the contract/blanket purchase order at the header level. This is a migrated financial attribute that consolidation processing requires alongside the base purchasing document data.
• SET_OF_BOOKS_ID — The identifier of the set of books (ledger) to which the migrated record pertains. This is essential for EFC migration because consolidation is performed per set of books, and the value determines ledger context for the shadowed header.

No surrogate primary key unique to PO_BPOS_HDR_EFC is documented; the table inherits its row identity from the parent PO_BPOS_HDR via BPO_ID. The physical schema lists exactly three columns, so there are no additional business-key columns to enumerate beyond those above.

Common Use Cases and Queries

Typical use cases center on consolidation migration validation, reconciliation between the live header and its shadow copy, and financial reporting that requires contract exchange-rate and ledger context.

A reconciliation query joining the shadow table to the base header might resemble:

• SELECT h.bpo_id, h.contract_exchange_rate, h.set_of_books_id FROM gml.po_bpos_hdr_efc h WHERE h.set_of_books_id = :ledger_id;
• SELECT e.bpo_id, e.contract_exchange_rate, e.set_of_books_id FROM gml.po_bpos_hdr_efc e JOIN po.po_bpos_hdr p ON p.bpo_id = e.bpo_id WHERE e.contract_exchange_rate IS NULL; — used to detect migration gaps.
• Aggregate checks grouped by SET_OF_BOOKS_ID to confirm that all headers expected for a given ledger have been shadowed before consolidation runs.

Reporting use cases include validating exchange-rate population for contract-based purchasing documents and comparing source-to-shadow record counts per ledger prior to EFC load.

Related Objects

The documented relationship data identifies the following significant related objects:

• PO_BPOS_HDR — The parent header table and the sole documented referent, joined on PO_BPOS_HDR_EFC.BPO_ID → PO_BPOS_HDR.BPO_ID. This is the primary dependency for both reconciliation and any query that enriches shadow rows with full header detail.

Because the metadata documents only one foreign key and classifies the table as standalone, other related objects such as sets-of-books/ledger definitions (referenced conceptually through SET_OF_BOOKS_ID) and EFC consolidation migration programs operate on this table indirectly rather than through documented FK constraints. Analysis should therefore treat PO_BPOS_HDR as the authoritative join partner and use SET_OF_BOOKS_ID to constrain results to the appropriate ledger context.