Results for “pa_expenditure_items_mrc_v”

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

Overview

PA_EXPENDITURE_ITEMS_MRC_V is a reporting view within the Oracle Projects (PA) module of Oracle E-Business Suite, documented for releases 12.1.1 and 12.2.2. Its description identifies it as a "Single-org, single currency view," which indicates that it presents project expenditure item data scoped to a single operating organization and expressed in a single currency, rather than aggregating across multiple organizations or reporting currencies.

The view exposes expenditure item records together with their associated cost, revenue, billing, and adjustment attributes. In the Projects architecture, expenditure items are the transactional foundation for cost collection, burdening, revenue accrual, and customer invoicing. This view provides a consolidated read interface over those attributes, making it useful for reporting, reconciliation, and integration scenarios where a flattened, single-currency perspective of expenditure item activity is required.

The ETRM metadata notes that the view is "Not implemented in this database," and no base objects are documented. This indicates that the view definition exists in the reference catalogue but is not necessarily deployed in every environment, and that implementers should verify its presence before relying on it.

Underlying Base Objects

The ETRM documentation lists no referenced base objects for this view, and the provided view text is truncated before the FROM clause is fully resolved. However, the column prefixes in the SELECT list reveal the underlying structure. Columns prefixed with MC. are drawn from a multiple reporting currency source, while columns prefixed with PA1. originate from the primary expenditure items table, PA_EXPENDITURE_ITEMS_ALL.

The presence of the MRC (Multiple Reporting Currency) prefix is consistent with the view name and with the single-currency description: the view joins the base expenditure item row to its MRC counterpart, selecting a consistent set of both primary and reporting-currency measures. Because the metadata documents no base objects and states the view is not implemented, the join condition and the precise MRC table reference should be confirmed against the actual database definition in any given instance.

Key Columns

• EXPENDITURE_ITEM_ID, EXPENDITURE_ID, TASK_ID, PROJECT_ID — primary keys and foreign keys identifying the expenditure item and its project and task context.
• RAW_COST, RAW_COST_RATE, BURDEN_COST, BURDEN_COST_RATE — cost and burden amounts and their associated rates.
• RAW_REVENUE, BILL_RATE, ACCRUED_REVENUE, ACCRUAL_RATE, ADJUSTED_REVENUE, ADJUSTED_RATE — revenue accrual and billing amounts and rates.
• BILL_AMOUNT, BILL_TRANS_BILL_AMOUNT, PROJECT_BILL_AMOUNT — billing measures, appearing from both sources.
• EXPENDITURE_ITEM_DATE, EXPENDITURE_TYPE, QUANTITY, NON_LABOR_RESOURCE, ORGANIZATION_ID, JOB_ID — descriptive expenditure attributes.
• COST_DISTRIBUTED_FLAG, REVENUE_DISTRIBUTED_FLAG, BILLABLE_FLAG, BILL_HOLD_FLAG, COST_BURDEN_DISTRIBUTED_FLAG — processing status indicators.
• COST_DIST_REJECTION_CODE, REV_DIST_REJECTION_CODE, IND_COST_DIST_REJECTION_CODE — distribution rejection reasons.
• RECEIPT_CURRENCY_AMOUNT, RECEIPT_CURRENCY_CODE, RECEIPT_EXCHANGE_RATE, DENOM_CURRENCY_CODE, DENOM_RAW_COST, DENOM_BURDENED_COST — currency and denomination attributes.
• ORG_ID, ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE10 — organization and descriptive flexfield columns.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID — standard audit and concurrent program columns.

Common Use Cases and Queries

Typical uses include expenditure item reporting, cost and revenue reconciliation, and constructing integration extracts. A representative query retrieves billable expenditure items for a project within a date range:

• SELECT expenditure_item_id, project_id, task_id, expenditure_item_date, expenditure_type, raw_cost, burden_cost, bill_amount, billable_flag FROM pa_expenditure_items_mrc_v WHERE project_id = :project_id AND expenditure_item_date BETWEEN :start_date AND :end_date AND billable_flag = 'Y';
• SELECT organization_id, expenditure_type, SUM(burden_cost), SUM(accrued_revenue) FROM pa_expenditure_items_mrc_v GROUP BY organization_id, expenditure_type;

Because the view is documented as single-org and single-currency, queries should apply organization and currency filters where required, and implementers should verify the view's deployment status before use.