Results for “burden_sum_source_run_id”

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

Overview

PA_AUD_COST_DIST_LINES is a Projects (PA) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. Its documented purpose is to store audit information for summarized burden expenditure items. In practice, the table acts as an audit and reconciliation trail that records how summarized burden cost distribution lines were generated, retaining the identifiers of the source compilation, the burden summary run, and the concurrent program that produced the rows.

The table is owned by the PA schema and holds nine documented columns. It does not participate in the transactional flow of project costing directly; rather, it supplements the summarized burden expenditure data so that cost distribution results can be traced back to the run, request, and compiled set that generated them. This makes the table valuable for troubleshooting, audit compliance, and re-processing scenarios.

Based on the documented foreign key linkage to PA_EXPENDITURE_ITEMS_ALL, the heuristic Data Vault classification for this table is satellite-leaning. In modeling terms, it is best treated as a descriptive satellite attached to the expenditure item hub, carrying audit and run-context attributes rather than defining new business entities or relationships.

Key Information Stored

The nine documented columns fall into keys, audit context, and run-context attributes:

• EXPENDITURE_ITEM_ID — Foreign key to PA_EXPENDITURE_ITEMS_ALL. This is the primary business-key candidate that ties each audit row back to the expenditure item being burdened.
• LINE_NUM — Sequence number identifying the individual summarized burden cost distribution line within the expenditure item.
• IND_COMPILED_SET_ID — Identifier of the indirect compiled set used during burden compilation, anchoring the audit row to the costing configuration in force at the time.
• BURDEN_SUM_SOURCE_RUN_ID — Identifier of the burden summarization source run, allowing reconstruction of the run that produced the summarized burden amounts.
• CREATED_BY, CREATION_DATE — Standard Oracle who/when audit columns recording the creating user and timestamp.
• PROGRAM_ID, PROGRAM_APPLICATION_ID, REQUEST_ID — Concurrent program and request context, identifying the program and concurrent request that inserted the audit rows.

No surrogate single-column primary key is documented; the effective business key is the combination of EXPENDITURE_ITEM_ID and LINE_NUM. Uniqueness of that combination is implied by the summarization granularity rather than a documented unique index.

Common Use Cases and Queries

Typical scenarios include auditing a burdened expenditure item, tracing summary results to the originating run, and investigating summarization errors. A representative query joins the audit rows back to the expenditure item:

SELECT a.EXPENDITURE_ITEM_ID, a.LINE_NUM, a.IND_COMPILED_SET_ID, a.BURDEN_SUM_SOURCE_RUN_ID, a.REQUEST_ID FROM PA.PA_AUD_COST_DIST_LINES a WHERE a.EXPENDITURE_ITEM_ID = :expenditure_item_id ORDER BY a.LINE_NUM;

Reporting queries commonly aggregate by IND_COMPILED_SET_ID or BURDEN_SUM_SOURCE_RUN_ID to identify which compiled sets and runs contributed to summarized burden amounts, and by REQUEST_ID to correlate results with the concurrent request log. Audit and SOX-oriented extracts select CREATED_BY and CREATION_DATE to establish who generated a given distribution.

Related Objects

The documented foreign key defines the principal relationship:

• PA_EXPENDITURE_ITEMS_ALL — Joined via PA_AUD_COST_DIST_LINES.EXPENDITURE_ITEM_ID = PA_EXPENDITURE_ITEMS_ALL.EXPENDITURE_ITEM_ID; the master expenditure item record.
• PA_EXPENDITURE_ITEMS — The operational synonym typically queried alongside the audit lines for the current operating unit.
• PA_COST_DISTRIBUTION_LINES_ALL — Holds the resulting cost distribution lines for the associated expenditure items.
• PA_IND_COMPILED_SETS — Source of IND_COMPILED_SET_ID, defining the indirect cost configuration applied.
• FND_CONCURRENT_REQUESTS — Joined via REQUEST_ID to resolve the concurrent program run context.
• FND_USER — Joined via CREATED_BY to resolve the creating user.

Together these relationships position PA_AUD_COST_DIST_LINES as a supporting audit satellite to the project costing expenditure and distribution data model.