Search Results po_mc_headers_u1

Overview

PO.PO_MC_HEADERS is the Multiple Reporting Currencies (MRC) sub-table that shadows PO_HEADERS_ALL in the Oracle Purchasing module. For each purchase order header that exists in the transactional set of books, the MRC architecture permits one additional row in PO_MC_HEADERS for every reporting set of books assigned to the operating unit. In Oracle EBS 12.1.1 and 12.2.2 this object therefore carries the reporting-currency view of purchasing documents — the amounts and conversion attributes required to present the same purchase order in a set of books other than the one in which it was entered.

From a Data Vault modeling perspective, PO_MC_HEADERS is classified heuristically as a standalone construct — that is, a satellite-like table whose grain is one row per parent document per reporting set of books, but which has no formally declared foreign keys in the data dictionary. The unique index PO_MC_HEADERS_U1, which the user searched for under the name po_mc_headers_u1, is the object that instantiates this grain and is the object most frequently interrogated by DBAs and developers.

Key Information Stored

The table is compact, with five documented columns. Each column has a specific role in the MRC conversion process:

• SET_OF_BOOKS_ID (NUMBER(15), mandatory) — identifies the reporting set of books for which this shadow row exists. It is part of the primary key PO_MC_HEADERS_PK.
• PO_HEADER_ID (NUMBER) — the document header identifier that links back to the parent record in PO_HEADERS_ALL. It is also part of the primary key.
• RATE_TYPE (VARCHAR2(30)) — the conversion type (for example, a corporate or spot rate) used when translating the transactional currency amount into the reporting currency.
• RATE_DATE (DATE) — the effective date of the exchange rate, typically the document date or the accounting date, depending on the rate type definition.
• RATE (NUMBER) — the actual multiplier applied to convert transactional currency into the reporting currency.

The primary key is PO_MC_HEADERS_PK (SET_OF_BOOKS_ID, PO_HEADER_ID), which reflects the natural grain of the MRC model. The unique index PO_MC_HEADERS_U1 is defined on (PO_HEADER_ID, SET_OF_BOOKS_ID) in the APPS_TS_TX_IDX tablespace. Note that the column order differs from the primary key — the index is led by PO_HEADER_ID, which is the more selective access path for single-document lookups. The table itself resides in APPS_TS_TX_DATA with PCT Free 10.

No surrogate key is documented. The business keys for identification are the combination of PO_HEADER_ID and SET_OF_BOOKS_ID, which in MRC terms is the natural identifier of a converted document line.

Common Use Cases and Queries

Reporting requirements in a multi-set-of-books environment typically retrieve the converted amounts alongside the transactional amounts. The following join pattern is the canonical access path:

SELECT h.segment1        AS po_number,
       m.set_of_books_id,
       m.rate_type,
       m.rate_date,
       m.rate
  FROM po.po_headers_all h,
       po.po_mc_headers  m
 WHERE h.po_header_id  = m.po_header_id
   AND m.set_of_books_id = :p_reporting_sobid;

Because PO_MC_HEADERS_U1 is led by PO_HEADER_ID, this query benefits from an index range scan on that index when the reporting set of books is supplied as a predicate. A second common pattern enumerates all reporting set of books for a single document, which relies on the leading column of the unique index. Reconciliation reports comparing converted totals against converted requisition or invoice figures frequently drive from the same index.

Related Objects

The most significant objects adjacent to PO_MC_HEADERS are:

• PO.PO_HEADERS_ALL — the parent transactional table, joined on PO_HEADER_ID.
• PO.PO_HEADERS_ALL_MC — the MRC view that exposes converted header columns for reporting.
• PO.PO_LINES_ALL and PO.PO_LINES_ALL_MC — the line-level counterparts, joined on PO_HEADER_ID.
• APPS.PO_MC_HEADERS — the APPS-layer synonym that most application code references.
• GL.GL_SETS_OF_BOOKS — resolved on SET_OF_BOOKS_ID to obtain the reporting currency.
• AP.FND_CURRENCIES and GL.GL_DAILY_CONVERSION_TYPES — used to interpret RATE_TYPE and RATE.