Results for “pa_project_exp_item_accum”

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

Overview

PA_PROJECT_EXP_ITEM_ACCUM is a Projects (PA) module table in the Oracle E-Business Suite database, owned by the PA schema. It stores accumulated revenue, cost, and quantity balances derived from project expenditure items, aggregated by project, task, expenditure type, expenditure organization, and both the project accounting period and general ledger period. Its defining characteristic is that it is populated and consumed only when the Projects application operates in Dual Accumulation Mode, in which expenditure is accumulated along two parallel accounting dimensions rather than a single one. In standard installations that do not use Dual Accumulation Mode, this table remains effectively dormant.

From a dimensional modeling perspective, the mined metadata suggests a link classification under Data Vault heuristics. This is a reasonable modeling suggestion: the table sits at the intersection of several independent business entities — projects, tasks, expenditure types, expenditure categories, and organizations — and its composite key resolves that many-to-many intersection. It is not a descriptive satellite in the Data Vault sense, since it carries measures (revenue, cost, quantity amounts) rather than pure descriptive attributes of a single parent key.

Key Information Stored

The table is keyed by a composite primary key, PA_PROJECT_EXP_ITEM_ACCUM_PK, covering PROJECT_ID, PA_PERIOD, GL_PERIOD, EXPENDITURE_TYPE, TASK_ID, and EXPENDITURE_ORGANIZATION_ID. A unique index, PA_PROJECT_EXP_ITEM_ACCUM_U1, mirrors essentially the same business-key column set (PROJECT_ID, TASK_ID, PA_PERIOD, GL_PERIOD, EXPENDITURE_TYPE, EXPENDITURE_ORGANIZATION_ID), confirming that this combination is the natural business key. There is no single-column surrogate identifier; the composite key itself functions as the identity of each row.

The most operationally significant columns fall into three groups:

• Dimensional keys: PROJECT_ID, TASK_ID, EXPENDITURE_TYPE, EXPENDITURE_ORGANIZATION_ID, PA_PERIOD, GL_PERIOD, EXPENDITURE_CATEGORY, and REVENUE_CATEGORY define the grain at which amounts are accumulated.
• Cumulative balances: TOTAL_REVENUE, TOTAL_RAW_COST, TOTAL_BURDEN_COST, and TOTAL_QUANTITY hold running totals, while BILLABLE_RAW_COST, BILLABLE_BURDEN_COST, and BILLABLE_QUANTITY isolate the billable portion of those balances.
• Incremental amounts: the INC_-prefixed columns (INC_TOTAL_REVENUE, INC_TOTAL_RAW_COST, INC_TOTAL_BURDEN_COST, INC_TOTAL_QUANTITY, and their billable counterparts) capture period-to-period deltas applied since the last accumulation run.

Audit and control columns include CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and the concurrent program fields REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE. A ROLLUP_FLAG supports hierarchical aggregation logic.

Common Use Cases and Queries

This table primarily supports reconciliation and reporting in Dual Accumulation Mode environments, where project and GL period views of the same expenditure must be compared. A typical query reconciles the incremental movement against cumulative balances for a given period:

• Period accumulation reporting: filter by PA_PERIOD or GL_PERIOD and group by EXPENDITURE_TYPE to review total versus billable cost by period.
• Dual-dimension reconciliation: compare PA_PERIOD-based totals with GL_PERIOD-based totals to detect timing differences between accounting views.
• Balance validation: verify that TOTAL amounts equal the sum of prior cumulative values plus current INC_ amounts, using ROLLUP_FLAG to isolate rollup rows.
• Program traceability: join REQUEST_ID to concurrent program request tables to audit which accumulation run populated or refreshed a given row.

Related Objects

The documented foreign keys establish the primary relationships:

• PA_PROJECTS_ALL, joined on PROJECT_ID.
• PA_TASKS, joined on TASK_ID.
• PA_EXPENDITURE_TYPES, joined on EXPENDITURE_TYPE.
• PA_EXPENDITURE_CATEGORIES, joined on EXPENDITURE_CATEGORY.

These parent tables supply the descriptive context for every accumulated row. Related PA accumulation and reporting logic interacts with this table alongside expenditure item and project summary structures that share the same project, task, and period grain.