Search Results historical_flag

Overview

The view PA_EXPENDITURE_ITEMS_ALL_MRC_V is a multi-organization, single-currency reporting view owned by the APPS schema in Oracle E-Business Suite. It is part of the PA (Projects) product family and exposes expenditure item data alongside corresponding multi-reporting-currency (MRC) revenue amounts. The "MRC" designation indicates that this view consolidates each expenditure item record with its reporting-currency and multiple-currency counterparts, allowing consumers to retrieve a single logical row per expenditure item while still accessing the denormalized reporting set columns.

Its principal role is to support Project Accounting reporting and integration interfaces that must reconcile cost side data (labor and non-labor burdened costs) with revenue side data (billing rates, accrued and adjusted revenue) across organizational units. Because the view is defined as a UNION-style composition of the base synonym PA_EXPENDITURE_ITEMS_ALL and the multi-currency synonym PA_MC_EXP_ITEMS_ALL, it presents the combined item master attributes from the first synonym prefixed through the alias PA1 and the MRC-specific amount columns through the alias MC.

In both EBS 12.1.1 and 12.2.2 the object is validated and remains available for querying directly from PL/SQL packages, Oracle Reports, OBIEE extraction, and APPS standard concurrent programs. It is not a table and carries no storage of its own; it is a pure read construct whose behavior depends on the session's organization context and reporting currency settings.

Underlying Base Objects

The view text selects from two underlying documented objects, both referenced as synonyms within the APPS schema:

• PA_EXPENDITURE_ITEMS_ALL (SYNONYM) — the primary expenditure item store, aliased PA1 in the view definition. It supplies the vast majority of columns, including cost, burden, quantity, task, organization, program, and descriptive flexfield attribute columns.
• PA_MC_EXP_ITEMS_ALL (SYNONYM) — the multi-currency expenditure items object, aliased MC. It supplies the reporting-currency revenue and billing amount columns such as RAW_REVENUE, BILL_RATE, ACCRUED_REVENUE, ACCRUAL_RATE, ADJUSTED_REVENUE, ADJUSTED_RATE, and FORECAST_REVENUE.

Joining the two synonyms on EXPENDITURE_ITEM_ID yields the combined projection. The view also passes through ROWID from MC and the audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY) from PA1, preserving standard WHO columns for downstream change tracking.

Key Columns

Among the most significant columns exposed are the cost and revenue amount pairs that allow reconciliation across currency contexts:

• EXPENDITURE_ITEM_ID — the unique identifier for the expenditure item; the join key between cost and MRC revenue records.
• RAW_COST, RAW_COST_RATE, BURDEN_COST, BURDEN_COST_RATE — the raw and burdened cost amounts and rates sourced from PA1.
• RAW_REVENUE, BILL_RATE, ACCRUED_REVENUE, ACCRUAL_RATE, ADJUSTED_REVENUE, ADJUSTED_RATE, FORECAST_REVENUE — reporting-currency revenue and rate columns sourced from MC (multi-currency).
• BILL_AMOUNT and BILL_TRANS_BILL_AMOUNT/PROJECT_BILL_AMOUNT — billing amounts appearing from both sides, useful for validating the cost-to-bill relationship.
• REVENUE_DISTRIBUTED_FLAG, COST_DISTRIBUTED_FLAG, COST_BURDEN_DISTRIBUTED_FLAG — distribution status flags controlling accounting and revenue generation.
• BILLABLE_FLAG, BILL_HOLD_FLAG, NET_ZERO_ADJUSTMENT_FLAG, CONVERTED_FLAG — lifecycle and eligibility indicators.
• ORG_ID, ORGANIZATION_ID, OVERRIDE_TO_ORGANIZATION_ID — multi-org and organization assignment columns.
• RECEIPT_CURRENCY_AMOUNT, RECEIPT_CURRENCY_CODE, RECEIPT_EXCHANGE_RATE, DENOM_CURRENCY_CODE, DENOM_RAW_COST — receipt and denominated currency conversion columns relevant to MRC reporting.
• TRANSACTION_SOURCE, ORIG_TRANSACTION_REFERENCE, EVENT_NUM — transaction provenance and event linkage.
• Descriptive flexfield columns ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE10.

Note that no column named HISTORICAL_FLAG appears in the documented view text. Callers searching for "historical_flag" against this view should confirm whether they intend the DFF attribute columns or an audit/date-based derivation such as LAST_UPDATE_DATE rather than a literal flag column. If a historical flag is required, it is typically derived from expenditure item dates or from the converted/net-zero adjustment indicators rather than stored directly on this object.

Common Use Cases and Queries

Typical consumers include revenue and cost reconciliation reports, MRC extraction programs, and interfaces that must obtain both the functional-currency cost and the reporting-currency revenue for each item. A representative query joining expenditure context to task and project is shown below.

SELECT ei.expenditure_item_id,
       ei.expenditure_item_date,
       ei.project_id,
       ei.task_id,
       ei.raw_cost,
       ei.burden_cost,
       ei.raw_revenue,
       ei.adjusted_revenue,
       ei.bill_rate,
       ei.billable_flag,
       ei.org_id
  FROM appspa_expenditure_items_all_mrc_v ei
 WHERE ei.org_id = :p_org_id
   AND ei.expenditure_item_date BETWEEN :p_from_date AND :p_to_date;

To locate items still pending revenue distribution, filtered to a specific organization, the view is commonly queried as follows:

SELECT ei.expenditure_item_id,
       ei.expenditure_id,
       ei.project_id,
       ei.revenue_distributed_flag,
       ei.billable_flag
  FROM appspa_expenditure_items_all_mrc_v ei
 WHERE ei.revenue_distributed_flag = 'N'
   AND ei.billable_flag = 'Y'
   AND ei.org_id = :p_org_id;

Because the view is organization-sensitive, callers should always constrain on ORG_ID (or rely on the MOAC security profile) to prevent cross-organization leakage. When trending "historical" item activity, aggregate by EXPENDITURE_ITEM_DATE and compare DENOM_RAW_COST against RAW_COST to assess currency effects, rather than expecting a dedicated HISTORICAL_FLAG column, which the view does not expose.