Results for “pa_expenditure_items”

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

Overview

PA_EXPENDITURE_ITEMS is a single-organization view in the Oracle Projects (PA) module of Oracle E-Business Suite, catalogued in ETRM for releases 12.1.1 and 12.2.2. It presents expenditure item detail — the transaction-level records produced when labor, usage, expense, and other costs are charged against a project or task. Each row represents one expenditure item belonging to a parent expenditure, carrying the distributed and billable amounts, burdened cost figures, revenue accrual values, and the associated currency conversions. The view is the primary access point for reporting and integration logic that requires transactional project cost and revenue data without querying the large multi-organization base table directly.

Because the view is defined as single-org (exposed through the ORG_ID column), it filters or projects data relative to a single operating unit context. In ETRM, the implementation note records that PA_EXPENDITURE_ITEMS is "Not implemented in this database," which means the view definition exists as reference metadata; the corresponding object is created in customer instances where Oracle Projects is installed.

Underlying Base Objects

The ETRM documentation does not enumerate any referenced base objects for this view. Functionally, PA_EXPENDITURE_ITEMS is the single-org layer over the multi-org table PA_EXPENDITURE_ITEMS_ALL, the core table that stores every expenditure item. The view filters on the organization identifier so that queries return only the records associated with the current operating unit, consistent with the multi-org security model used throughout Oracle Projects and Oracle Subledger Accounting. No other base tables are documented as referenced, so all columns derive from the expenditure item record itself and its distribution attributes.

Key Columns

The view exposes a broad set of cost, revenue, billing, and currency attributes. The most significant include:

• EXPENDITURE_ITEM_ID — Primary key uniquely identifying the expenditure item; referenced by adjustment, cross-charge, and distribution records.
• EXPENDITURE_ID, TASK_ID, PROJECT_ID — Parent expenditure, task, and project keys linking the item to its project structure.
• EXPENDITURE_TYPE, EXPENDITURE_ITEM_DATE — Classification and accounting date of the item.
• RAW_COST, BURDEN_COST, RAW_COST_RATE, BURDEN_COST_RATE — Unburdened and burdened cost amounts and rates.
• COST_DISTRIBUTED_FLAG, REVENUE_DISTRIBUTED_FLAG, COST_BURDEN_DISTRIBUTED_FLAG — Indicators of whether cost, revenue, and burden distribution have been processed.
• BILLABLE_FLAG, BILL_HOLD_FLAG, BILL_AMOUNT, BILL_RATE — Billing eligibility and amount attributes.
• RAW_REVENUE, ACCRUED_REVENUE, ADJUSTED_REVENUE, ACCRUAL_RATE, ADJUSTED_RATE — Revenue accrual and adjustment values.
• QUANTITY, NON_LABOR_RESOURCE, ORGANIZATION_ID, JOB_ID, ORG_ID — Quantity and resource/organization context.
• DENOM_*, ACCT_*, PROJECT_* currency columns — Amounts and exchange rates in denominated, accounting, and project currencies.
• TRANSACTION_SOURCE, ORIG_TRANSACTION_REFERENCE, SYSTEM_LINKAGE_FUNCTION — Source and linkage metadata for integration.
• CC_CROSS_CHARGE_CODE, CC_PRVDR_ORGANIZATION_ID, CC_RECVR_ORGANIZATION_ID — Cross-charge processing attributes.

Common Use Cases and Queries

Typical uses include cost and revenue reconciliation, billing review, burden analysis, and feeds into Oracle Subledger Accounting, Oracle Payables, and Oracle Receivables. Project accountants query the view to identify undistributed items or bill holds, while integrators extract items for external reporting.

A representative query lists billable labor items for a project:

• SELECT expenditure_item_id, task_id, expenditure_item_date, expenditure_type, raw_cost, burden_cost, bill_amount, billable_flag, bill_hold_flag FROM pa_expenditure_items WHERE project_id = :project_id AND billable_flag = 'Y' ORDER BY expenditure_item_date;

A second query identifies items pending cost distribution:

• SELECT expenditure_item_id, expenditure_id, raw_cost, cost_distributed_flag FROM pa_expenditure_items WHERE cost_distributed_flag = 'N';

Because the view is single-org, all queries implicitly return only the current organization's data, ensuring multi-org security without additional predicates.