Search Results pte_reference




Overview
Explore in AI Chat

Overview

PA_EXPENDITURES_MRC_V2 is a reporting view in the Oracle E-Business Suite Projects (PA) module that presents project expenditure transaction data filtered to a single operating unit and a single ledger/accounting currency context. In Oracle EBS 12.1.1 and 12.2.2, the "MRC" designation refers to Multi-Reporting Currency, the architecture by which Oracle Projects stores and exposes transaction distributions across multiple reporting currencies. This view is the "single-org, single currency" variant, meaning it resolves the organization (ORG_ID) context dynamically and returns rows as they are recorded in the ledger currency rather than presenting one row per reporting currency.

The view is defined as a projection over PA_EXPENDITURES_ALL, restricted by the predicate ORG_ID = MO_GLOBAL.GET_CURRENT_ORG_ID. This means the view honors the current operating unit set by the MO (Multi-Org) security layer at runtime, automatically returning only the expenditure rows belonging to the session's active organization. For reporting and integration purposes, this is the reason the view is frequently used in concurrent programs, BI Publisher reports, and inbound/outbound interfaces where data must be scoped to the current operating unit rather than the full multi-org population.

Underlying Base Objects

Per the ETRM metadata, no additional referenced base objects are documented beyond PA_EXPENDITURES_ALL, which serves as the single underlying table. PA_EXPENDITURES_ALL is the primary transactional store for project expenditures — raw cost transactions in Oracle Projects — and is itself an _ALL table that carries ORG_ID for multi-organization partitioning. PA_EXPENDITURES_MRC_V2 does not join other tables in its documented text; it is a column-restricted and row-filtered select from PA_EXPENDITURES_ALL.

Because the only restriction is an equality predicate on ORG_ID evaluated through MO_GLOBAL.GET_CURRENT_ORG_ID, the view behaves as a "current operating unit" wrapper. Two behavioral consequences follow: (1) the view returns no rows when no current org is initialized in the session, and (2) results differ per operating unit even though the underlying table is shared. This is consistent with the "single-org" characterization in the title.

Key Columns

The view exposes a broad column set drawn from PA_EXPENDITURES_ALL. The most commonly referenced columns include:

Common Use Cases and Queries

Typical uses include current-org expenditure extracts for cost reporting, reconciliation of incurred-by organization spend, and integration payloads feeding downstream cost collection. The following query filters by the searched column within the current operating unit:

  • Expediture detail for an incurring organization: 
    SELECT expenditure_id,
       incurred_by_organization_id,
       incurred_by_person_id,
       expenditure_class_code,
       expenditure_status_code,
       acct_currency_code
FROM   pa_expenditures_mrc_v2
WHERE  incurred_by_organization_id = :org_id
AND    expenditure_ending_date >= :start_date;
  • Aggregated spend by incurred organization: 
    SELECT incurred_by_organization_id, COUNT(*)
FROM   pa_expenditures_mrc_v2
WHERE  expenditure_status_code = 'APPROVED'
GROUP BY incurred_by_organization_id;
  • Audit-oriented extract including WHO and descriptive flexfield columns: 
    SELECT expenditure_id, org_id, last_update_date, last_updated_by,
       attribute1, attribute_category
FROM   pa_expenditures_mrc_v2;

Because ORG_ID is implicitly bound through MO_GLOBAL.GET_CURRENT_ORG_ID, no explicit ORG_ID predicate is required in these queries; the calling environment must have the correct operating unit initialized. For cross-organization reporting, a direct query against PA_EXPENDITURES_ALL with an explicit ORG_ID or a multi-org reporting view is generally preferred over this single-org view.