Search Results destination_context




Overview
Explore in AI Chat

Overview

PO_DISTRIBUTIONS_MRC_V is a Multi-Reporting-Currency (MRC) view in the Oracle E-Business Suite Purchasing (PO) module. It exposes purchasing distribution records alongside their reporting-set-of-books currency conversions, drawing on the corresponding MRC columns grouped by SET_OF_BOOKS_ID. Because Oracle EBS allows multiple reporting currencies to be maintained within a single ledger environment, an MRC view such as this presents the same underlying distribution data repeated once per reporting set of books, with converted amounts carried in the MC-prefixed columns.

The view is documented in ETRM 12.2.2 with the description "- Retrofitted" and is noted as "Not implemented in this database." The "Retrofitted" designation indicates the object was retrofitted into the MRC dictionary during an upgrade, and the "Not implemented" note means it may not exist in every environment. Its principal role is reporting and integration: it allows a single SQL statement to retrieve distribution-level purchasing amounts expressed in multiple reporting currencies without manually joining to the reporting ledger tables.

Underlying Base Objects

The ETRM metadata documents no base objects for this view; the view text itself references aliases PRIMARY and MC. In standard EBS design these map to the primary-ledger purchasing distribution table (PO_DISTRIBUTIONS_ALL) and its MRC counterpart (PO_DISTRIBUTIONS_MC), with SET_OF_BOOKS_ID driving the relationship. The MC alias supplies the reporting-currency columns (RATE_DATE, RATE, ENCUMBERED_AMOUNT, UNENCUMBERED_AMOUNT, MRC_RATE_DATE, MRC_RATE, MRC_ENCUMBERED_AMOUNT, MRC_UNENCUMBERED_AMOUNT, and related fields), while PRIMARY supplies the operational distribution attributes. Because the documented base-object list is empty, the exact join conditions cannot be confirmed from the metadata alone; the view should be treated as an MRC wrapper over the distribution tables.

Key Columns

The projection includes a broad set of identifiers and financial attributes. Operational keys include PO_DISTRIBUTION_ID, PO_HEADER_ID, PO_LINE_ID, LINE_LOCATION_ID, PO_RELEASE_ID, REQ_DISTRIBUTION_ID, CODE_COMBINATION_ID, ORG_ID, and PROJECT_ID. Financial columns cover AMOUNT_BILLED, AMOUNT_ORDERED, QUANTITY_ORDERED, QUANTITY_DELIVERED, QUANTITY_BILLED, QUANTITY_CANCELLED, and the encumbrance/unencumbrance flags and amounts. Currency-conversion columns carry the MC prefix or are grouped with the reporting books.

The column most relevant to the user's search, WIP_REPETITIVE_SCHEDULE_ID, links a purchasing distribution to a Work in Process repetitive schedule. It appears alongside WIP_ENTITY_ID, WIP_OPERATION_SEQ_NUM, WIP_RESOURCE_SEQ_NUM, WIP_LINE_ID, and BOM_RESOURCE_ID, forming the WIP-reference portion of the distribution. These columns are populated when the purchase order is associated with WIP activity, enabling reconciliation between procurement and manufacturing. Tax, award, and contract columns (RECOVERABLE_TAX, NONRECOVERABLE_TAX, TAX_RECOVERY_OVERRIDE_FLAG, AWARD_ID, OKE_CONTRACT_DELIVERABLE_ID) and descriptive Attributes 1–15 are also exposed.

Common Use Cases and Queries

A frequent scenario is reporting purchasing commitment and accrual amounts in a reporting currency, or tracing which distributions reference a given WIP repetitive schedule. The following query retrieves distributions tied to a repetitive schedule while showing reporting-currency amounts:

  • SELECT po_distribution_id, wip_repetitive_schedule_id, wip_entity_id, set_of_books_id, mrc_encumbered_amount, mrc_unencumbered_amount FROM po_distributions_mrc_v WHERE wip_repetitive_schedule_id IS NOT NULL;
  • Filter by SET_OF_BOOKS_ID to isolate a specific reporting ledger.
  • Join to PO_HEADERS_ALL or PO_LINES_ALL via the exposed IDs for descriptive reporting.

Consultants should confirm the view's presence in each environment, since the metadata flags it as not implemented, and verify the actual base tables and join logic against the live data dictionary before relying on it in custom reports.