Search Results po_mc_headers




Overview
Explore in AI Chat

Overview

PO_MC_HEADERS is a Multiple Reporting Currencies (MRC) sub-table owned by the PO schema within the Oracle Purchasing module. It functions as the currency-specific companion to the base PO_HEADERS table, storing the reporting-currency representation of purchasing document header information. In an MRC-enabled E-Business Suite instance, transactions are captured in the functional (primary) currency and simultaneously converted into one or more reporting currencies, allowing subsidiaries, statutory reporting, and global consolidation requirements to be satisfied without altering the underlying transactional record. PO_MC_HEADERS holds the reporting set-of-books view of that conversion for purchase order headers.

The object is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its documented physical schema in 12.2.2 comprises five columns. Based on the mined foreign-key structure, the metadata suggests a Data Vault classification of standalone, meaning the table does not participate in a classic hub-and-link dependency pattern and is best modelled as an independent, reference-oriented structure rather than a conventional satellite attached to a single parent hub.

Key Information Stored

The table stores converted header-level amounts and the currency attributes used to derive them. The documented columns are:

  • SET_OF_BOOKS_ID — Identifies the reporting set of books (ledger) for which the reporting-currency conversion was performed. This column forms part of the composite primary key.
  • PO_HEADER_ID — The foreign key back to the base PO_HEADERS record. This is the business-key candidate that links the reporting-currency row to its source transaction.
  • RATE_TYPE — The Oracle GL rate type (for example, Corporate or Spot) applied when converting the functional-currency value into the reporting currency.
  • RATE_DATE — The effective date of the exchange rate used for the conversion.
  • RATE — The actual exchange rate applied.

The documented primary key is PO_MC_HEADERS_PK, defined on the composite of SET_OF_BOOKS_ID and PO_HEADER_ID. A separate unique index, PO_MC_HEADERS_U1, is defined on PO_HEADER_ID and SET_OF_BOOKS_ID — a reversed ordering of the same two columns. Because both constraints cover the identical column pair, the primary key and the unique index are functionally equivalent in their uniqueness enforcement; the U1 index provides an alternate access path optimizing lookups by PO_HEADER_ID first.

Common Use Cases and Queries

PO_MC_HEADERS is consumed primarily by MRC-aware reporting and by the Purchasing forms and concurrent programs that render reporting-currency values. A typical join returns the reporting-currency rate context for a given purchase order:

  • Reporting-currency purchase order inquiries filtered by ledger: SELECT po_header_id, set_of_books_id, rate_type, rate_date, rate FROM po_mc_headers WHERE po_header_id = :p_id AND set_of_books_id = :sob_id;
  • Exchange-rate audit and revaluation analysis, comparing RATE and RATE_DATE against GL daily rates for the same period.
  • Global consolidation extracts that pull reporting-currency header data across multiple sets of books for a single PO_HEADER_ID.
  • Data validation routines confirming that every MRC-enabled PO_HEADERS row has a corresponding PO_MC_HEADERS row for each defined reporting ledger.

Because the table carries no amount columns in the documented schema, it should be joined to its parent for monetary reporting rather than treated as a self-contained financial source.

Related Objects

The following objects are most significant in relation to PO_MC_HEADERS:

  • PO_HEADERS — joined on PO_HEADER_ID; the functional-currency source record.
  • PO_MC_LINES — the MRC companion to PO_LINES, providing reporting-currency line detail beneath the same header.
  • PO_MC_DISTRIBUTIONS — MRC distributions aligned to the reporting-currency header.
  • PO_HEADERS_ALL / PO_LINES_ALL — the multi-org base tables underlying the _ALL views consumed by forms and reports.
  • GL_DAILY_RATES — joined on RATE_TYPE and RATE_DATE to validate or reproduce the stored conversion rate.
  • FND_CURRENCIES and GL_SETS_OF_BOOKS — reference tables for the reporting currency and ledger context.

Foreign-key and validation logic is typically enforced through the Purchasing MRC APIs rather than through declarative database constraints, so integrators should treat PO_MC_HEADERS as a derived table maintained by the application layer.