Results for “pa_expenditure_items_mrc_v2”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_EXPENDITURE_ITEMS_MRC_V2 is a reporting view within the Oracle Projects (PA) module of Oracle E-Business Suite. Its documented description identifies it as a "single-org, single currency view." This designation reflects the view's role as a components-available source that exposes expenditure item data — raw cost, burdened cost, revenue, billing amounts, and associated attributes — from the Multi-Report Currency (MRC) context. In releases 12.1.1 and 12.2.2, MRC views were traditionally used to present the same transactional data in multiple reporting currencies derived from the functional currency base. The "_V2" suffix signals a revised version of the view, typically introduced to harmonize column definitions or correct structural issues relative to an earlier iteration.

The view is relevant to reporting and integration scenarios where a single set of expenditure item records must be presented without org or currency multiplication, allowing downstream reports, extracts, or interfaces to consume a consistent grain. It is not, however, an interface table or a base transactional table; it is a read-oriented construct intended for query and reporting.

Underlying Base Objects

The ETRM documentation excerpt for this view does not enumerate referenced base objects ("Referenced base objects: none documented"), and the metadata additionally states "Not implemented in this database." This means the view may not be deployed in the environment from which the metadata was harvested, and its dependency catalog is therefore not captured. Absent a documented dependency list, the conventional derivation for an MRC expenditure items view is from the base tables PA_EXPENDITURE_ITEMS (aliased in the view text as PA1) joined to an MRC counterpart table (aliased as MC), keyed on EXPENDITURE_ITEM_ID. The base PA_EXPENDITURE_ITEMS table supplies the functional-currency cost and burden amounts, while the MRC alias supplies converted or reporting-currency revenue, bill rate, and forecast revenue values. Because the view is described as single-org and single-currency, it does not fan out across multiple orgs or currencies in the manner of a full MRC expansion; instead it presents one row per expenditure item.

Key Columns

The view text exposes a broad set of expenditure item columns, which can be grouped as follows:

• Identifiers and keys: EXPENDITURE_ITEM_ID, EXPENDITURE_ID, SOURCE_EXPENDITURE_ITEM_ID, ORIG_TRANSACTION_REFERENCE, ADJUSTED_EXPENDITURE_ITEM_ID.
• Cost amounts: RAW_COST, RAW_COST_RATE, BURDEN_COST, BURDEN_COST_RATE, DENOM_RAW_COST, DENOM_BURDENED_COST.
• Revenue and billing: RAW_REVENUE, BILL_RATE, ACCRUED_REVENUE, ACCRUAL_RATE, ADJUSTED_REVENUE, ADJUSTED_RATE, BILL_AMOUNT, PROJECT_BILL_AMOUNT, BILL_TRANS_BILL_AMOUNT, FORECAST_REVENUE.
• Flags and status: COST_DISTRIBUTED_FLAG, REVENUE_DISTRIBUTED_FLAG, BILLABLE_FLAG, BILL_HOLD_FLAG, COST_BURDEN_DISTRIBUTED_FLAG, NET_ZERO_ADJUSTMENT_FLAG, CONVERTED_FLAG.
• Project and organization context: PROJECT_ID, TASK_ID, ORGANIZATION_ID, OVERRIDE_TO_ORGANIZATION_ID, ORG_ID.
• Descriptor and date fields: EXPENDITURE_ITEM_DATE, EXPENDITURE_TYPE, QUANTITY, NON_LABOR_RESOURCE, JOB_ID, and the standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY).
• Multiplier and compiled set references: LABOR_COST_MULTIPLIER_NAME, BILL_RATE_MULTIPLIER, COST_IND_COMPILED_SET_ID, REV_IND_COMPILED_SET_ID, INV_IND_COMPILED_SET_ID.

Common Use Cases and Queries

The view is suited to expenditure item extracts, cost and revenue reconciliation reports, and integrations requiring a flattened, single-currency projection of project expenditures. A representative query returning cost and revenue for a given project might be:

SELECT expenditure_item_id, project_id, task_id, expenditure_type, raw_cost, burden_cost, raw_revenue, bill_amount, billable_flag FROM pa_expenditure_items_mrc_v2 WHERE project_id = :p_project_id AND expenditure_item_date BETWEEN :p_start AND :p_end;

Because dependency metadata is not documented and the view may be absent from a given database, implementers should verify existence in ALL_VIEWS and confirm the actual view text in ALL_VIEWS before relying on it in custom code, extracts, or interfaces. Where the view is unavailable, equivalent logic should be built directly against PA_EXPENDITURE_ITEMS and its MRC counterparts.