Search Results pa_cost_dist_lines_all_mrc_v2




Overview

PA_COST_DIST_LINES_ALL_MRC_V2 is a Projects (PA) module view in Oracle EBS 12.1.1 and 12.2.2 that exposes multi-reporting-currency (MRC) cost distribution lines. Per the ETRM metadata, this object is formally described as a "Multi-org, single currency view." This description reflects its design intent: it is one member of the family of MRC-related views generated by Oracle's Multiple Reporting Currencies architecture, in which a base transactional table is mirrored for each additional reporting currency set defined at the ledger level. The "_V2" suffix indicates a versioned variant of the view, typically introduced to align the view definition with later table structures or to expose additional columns.

The view is used primarily for reporting and enquiry against project cost distribution data expressed in a reporting currency, rather than the functional currency of the operating unit. It joins MRC-specific distribution columns (prefixed MC.) with the primary cost distribution columns (prefixed PA.), producing a consolidated projection that supports cross-currency cost analysis without requiring the caller to join the MRC shadow table manually.

Underlying Base Objects

The ETRM record states that this view is "Not implemented in this database" and documents no referenced base objects. The view text, however, shows a clear join pattern between two logical sources: an MRC side aliased MC and a primary Projects cost distribution side aliased PA. Column naming conventions strongly indicate that PA corresponds to PA_COST_DIST_LINES_ALL (or its transactional counterpart, PA_COST_DISTRIBUTIONS_ALL / EXPENDITURE_ITEMS_ALL lineage), while MC corresponds to the MRC-enabled variant of the same distribution table for a reporting currency. The two are correlated on expenditure item identity and line number, with the MRC side supplying currency, conversion and transfer attributes and the primary side supplying cost, burden, code combination and period attributes.

Because the ETRM documentation records no base objects, DBAs should confirm the actual underlying objects in their instance by querying DBA_VIEWS / DBA_DEPENDENCIES, as view composition can differ between 12.1.1 and 12.2.2 and depends on whether MRC is enabled for the operating unit's ledger.

Key Columns

Common Use Cases and Queries

Typical uses include reconciling functional and reporting currency cost distributions, investigating rejected MRC transfers, and feeding custom reporting or reconciliation extracts where the reporting-currency view is required.

Sample query to list MRC distribution lines for a project:

  • SELECT expenditure_item_id, line_num, currency_code, amount, burdened_cost, transfer_status_code, gl_date, pa_period_name FROM pa_cost_dist_lines_all_mrc_v2 WHERE project_id = :project_id;

Sample query to identify rejected transfers in a reporting currency:

  • SELECT expenditure_item_id, line_num, currency_code, transfer_rejection_reason, transferred_date FROM pa_cost_dist_lines_all_mrc_v2 WHERE transfer_status_code = 'R' AND org_id = :org_id;

Because the view is documented as not implemented in the reference database, availability and column presence should be validated against the target instance before use in concurrent programs, OBIEE extracts or integrations.