Search Results rcv_mc_shipment_headers_pk

Overview

RCV_MC_SHIPMENT_HEADERS is the Multiple Reporting Currencies (MRC) sub-table of RCV_SHIPMENT_HEADERS, owned by the PO schema and classified under the PO - Purchasing product. It stores the reporting set-of-books equivalents of receiving shipment header records so that a single shipment can be reported in more than one functional currency. In Oracle EBS 12.1.1 and 12.2.2 the base transaction is captured once in RCV_SHIPMENT_HEADERS in the primary set of books, and MRC propagates a converted row into this table for every enabled reporting set of books. The object has a documented status of VALID and is listed in the ETRM 12.2.2 physical schema with five columns.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. Treated as a modeling suggestion, this indicates that RCV_MC_SHIPMENT_HEADERS does not act as a classic hub or link in the mined relationship graph: its PK is a composite of the business discriminator plus the reporting set of books, with no outgoing FK relationships recorded in the documentation. In dimensional or Data Vault terms it behaves most like a currency-specific satellite that shadows the shipment header entity rather than an independent transaction entity.

Key Information Stored

The documented physical schema contains exactly five columns. The columns of greatest analytical importance are:

• SHIPMENT_HEADER_ID — the identifier of the receiving shipment header being reported. It ties the MRC row back to the source transaction in the primary books.
• SET_OF_BOOKS_ID — the reporting set of books for which the converted row was generated. Together with SHIPMENT_HEADER_ID this is the principal discriminator.
• CONVERSION_RATE_TYPE — the rate type (for example Corporate, Spot, or User-defined) used to convert the base amount into the reporting currency.
• CONVERSION_DATE — the effective date on which the conversion rate was applied.
• CONVERSION_RATE — the multiplier applied to translate the primary set-of-books value into the reporting set-of-books value.

The surrogate primary key is RCV_MC_SHIPMENT_HEADERS_PK, defined on the composite of SET_OF_BOOKS_ID and SHIPMENT_HEADER_ID. A second documented unique index, RCV_MC_SHIPMENT_HEADERS_U1, covers the same two columns in the reverse sequence (SHIPMENT_HEADER_ID, SET_OF_BOOKS_ID). Because the two constraints share the identical column set, the PK and U1 are not independent business-key candidates; SHIPMENT_HEADER_ID is effectively the source-business key, and SET_OF_BOOKS_ID is the MRC partitioning attribute that makes the row unique per reporting ledger.

Common Use Cases and Queries

Typical use cases include audit and reconciliation of receiving activity by reporting ledger, verification of the rate type and rate used for a particular shipment, and multi-currency receiving reports that must present shipments in a reporting currency rather than the primary functional currency.

A representative reconciliation query joins the MRC row back to its base shipment header by the source ID and filters to one reporting set of books:

• SELECT m.shipment_header_id, m.set_of_books_id, m.conversion_rate_type, m.conversion_date, m.conversion_rate FROM po.rcv_mc_shipment_headers m WHERE m.set_of_books_id = :reporting_sob AND m.shipment_header_id = :header_id;
• SELECT set_of_books_id, COUNT(*) FROM po.rcv_mc_shipment_headers GROUP BY set_of_books_id; — used to confirm that MRC rows exist for each enabled reporting set of books.
• SELECT conversion_rate_type, conversion_date, COUNT(*) FROM po.rcv_mc_shipment_headers GROUP BY conversion_rate_type, conversion_date ORDER BY conversion_date; — used to profile rate sources in effect over a period.

Because the table holds only conversion metadata, amount-based reporting still requires joining to the base shipment header and its lines.

Related Objects

The most significant related objects are:

• RCV_SHIPMENT_HEADERS — the primary set-of-books parent of this MRC sub-table; joined on SHIPMENT_HEADER_ID. This is the source transaction that MRC conversion shadows.
• RCV_SHIPMENT_HEADERS_PK — the primary key of the base table, providing the source key that this table carries forward per reporting set of books.
• RCV_TRANSACTIONS — receiving transactions linked to the shipment header, used when converted receiving values must be reported.
• RCV_SHIPMENT_LINES — line-level detail beneath the shipment header, the usual companion table for MRC receiving extracts.
• GL_SETS_OF_BOOKS — the ledger definition table; joined on SET_OF_BOOKS_ID to resolve the reporting set of books name and currency.
• GL_CURRENCIES — resolves the reporting currency associated with the set of books and the conversion applied.
• PO_HEADERS and PO_LINES — purchasing documents linked to the receiving shipment, frequently included in multi-currency procurement reporting.
• FND_CURRENCIES — the currency-code reference used alongside CONVERSION_RATE_TYPE and CONVERSION_RATE.

Because MRC propagation is driven by the base transaction, no application programming interface writes to RCV_MC_SHIPMENT_HEADERS directly; rows are populated by the MRC concurrent programs that process RCV_SHIPMENT_HEADERS.