Search Results gms_burden_components

Overview

PA_EXPENDITURE_ITEMS_ALL is the core transactional table in the Oracle Projects (PA) module, residing in the PA schema. It stores the smallest units of expenditure charged to projects and tasks — each row represents a single, individually tracked expenditure item that flows through the Oracle E-Business Suite project costing, billing, and accounting engines. Every labor hour, expense report line, requisition, purchase order receipt, or usage transaction that is charged to a project ultimately materializes as a row in this table, making it the granular foundation upon which project cost collection, burdening, revenue accrual, invoicing, and asset capitalization are built.

From a Data Vault modeling perspective, the metadata's heuristic classification describes PA_EXPENDITURE_ITEMS_ALL as satellite-leaning. This reflects its role as a descriptive, transactional record that hangs off the stronger business hubs and links elsewhere in the model — most notably the parent expenditure hub and the project/task link — rather than acting as an independent hub itself. The 205-column width and the heavy concentration of descriptive, currency, rate, and status attributes reinforce this satellite interpretation.

The primary key is PA_EXPENDITURE_ITEMS_PK, defined on EXPENDITURE_ITEM_ID, the surrogate identifier generated by the Projects system for each expenditure item. A secondary unique constraint, PA_EXPENDITURE_ITEMS_U1, exists on the combination of EXPENDITURE_ITEM_ID and BILL_HOLD_FLAG.

Key Information Stored

The table's columns fall into several functional groups. The most important include:

• EXPENDITURE_ITEM_ID — the surrogate primary key uniquely identifying each expenditure item.
• EXPENDITURE_ID — foreign key to PA_EXPENDITURES_ALL, grouping items under a parent expenditure transaction.
• PROJECT_ID and TASK_ID — the project and task to which the cost is charged (PA_PROJECTS_ALL and PA_TASKS respectively).
• EXPENDITURE_TYPE — the classification of the cost (for example, labor, expense, or usage), referencing PA_EXPENDITURE_TYPES.
• EXPENDITURE_ITEM_DATE — the accounting date of the item.
• QUANTITY and RAW_COST / BURDEN_COST — the quantities and the unburdened and burdened cost amounts.
• BILLABLE_FLAG and BILL_HOLD_FLAG — govern whether the item can be invoiced and whether it is currently held from billing.
• COST_DISTRIBUTED_FLAG and REVENUE_DISTRIBUTED_FLAG — indicate whether costing and revenue distribution have completed.
• TRANSACTION_SOURCE and SYSTEM_LINKAGE_FUNCTION — identify the originating subsystem and linkage.
• ADJUSTED_EXPENDITURE_ITEM_ID, TRANSFERRED_FROM_EXP_ITEM_ID, and SOURCE_EXPENDITURE_ITEM_ID — self-referencing columns supporting adjustments, transfers, and reversals.
• Labor and utilization attributes such as ASSIGNMENT_ID, JOB_ID, and WORK_TYPE_ID.
• Multi-currency columns including PROJECT_CURRENCY_CODE, ACCT_CURRENCY_CODE, DENOM_CURRENCY_CODE, and their associated exchange rates.

Common Use Cases and Queries

Because this table is the transactional heart of project costing and billing, it supports a wide range of reporting and integration scenarios. Typical uses include cost reports by project and task, burden analysis, unbilled receivable reconciliation, and billing hold investigations.

A representative query to retrieve the latest expenditure items for a project might read:

• SELECT expenditure_item_id, expenditure_item_date, expenditure_type, raw_cost, burden_cost, billable_flag FROM pa_expenditure_items_all WHERE project_id = :project_id AND cost_distributed_flag = 'Y';

Analysts frequently join to PA_PROJECTS_ALL and PA_TASKS to resolve project and task names, and to PA_EXPENDITURE_TYPES to label the item type. Because the table is denormalized across currencies, reporting can read the account or project currency amounts directly without currency conversion logic. Interfaces such as PA_TRANSACTION_INTERFACE_ALL feed new items here, and downstream processes such as cost distribution, revenue generation, and asset capitalization read items from this table.

Related Objects

PA_EXPENDITURE_ITEMS_ALL sits at the center of a large relational network. The most significant related objects include:

• PA_EXPENDITURES_ALL — parent expenditure, joined on EXPENDITURE_ID.
• PA_PROJECTS_ALL and PA_TASKS — joined on PROJECT_ID and TASK_ID to identify the charging destination.
• PA_COST_DISTRIBUTION_LINES_ALL and PA_CC_DIST_LINES_ALL — costing and cross-charge distribution lines referencing EXPENDITURE_ITEM_ID.
• PA_CUST_REV_DIST_LINES_ALL and PA_DRAFT_INVOICE_DETAILS_ALL — revenue and invoicing detail rows that reference the item.
• PA_TRANSACTION_INTERFACE_ALL — the interface table that imports transactions forming new items.
• PA_PROJECT_ASSET_LINE_DETAILS — links items to capitalized project assets.
• PA_EXPENDITURE_COMMENTS and PA_EXPEND_ITEM_ADJ_ACTIVITIES — comments and adjustment activity for items.