Results for “cmt_line_id”

50+ results




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

Overview

PA_TXN_ACCUM_DETAILS is a transaction detail table in the Oracle Projects (PA) module of Oracle E-Business Suite, owned by the PA schema. It serves as a drilldown bridge between summary-level transaction accumulator records in PA_TXN_ACCUM and the underlying source transactions that contributed to them. Specifically, it links accumulated project transaction figures to cost distribution lines, revenue distribution lines, customer event revenue distribution lines, and commitment transactions. This allows Oracle Projects to reconcile aggregated cost, revenue, and commitment amounts back to their originating detail rows for reporting, audit, and unbilled receivable processing.

Because every row in this table exists solely to associate two or more existing entities (an accumulator record and one or more source distribution lines), the heuristic Data Vault classification for this object is a link. In a Data Vault model this table would be modeled as a link table capturing the many-to-many relationship between accumulator records and their constituent source transactions, with the foreign key columns forming the link's composite business key.

Key Information Stored

PA_TXN_ACCUM_DETAILS contains 17 documented columns. The most significant are:

The metadata does not document an explicit single-column surrogate primary key or unique index; the effective business key is the composite of TXN_ACCUM_ID together with the relevant source identifiers (EXPENDITURE_ITEM_ID, LINE_NUM, PROJECT_ID, TASK_ID, EVENT_NUM, or CMT_LINE_ID, depending on LINE_TYPE).

Common Use Cases and Queries

Typical uses include reconciling accumulated project balances to source transactions, auditing which expenditure items or commitments contributed to a given accumulator, and building drilldown reports from summary cost/revenue figures to their detail lines.

A common pattern joins the detail table back to its accumulator and project context:

  • SELECT d.txn_accum_id, d.line_type, d.expenditure_item_id, d.project_id, d.task_id FROM pa.pa_txn_accum_details d WHERE d.txn_accum_id = :accum_id;
  • Joining to PA_TXN_ACCUM on TXN_ACCUM_ID to retrieve the summary amount while listing the contributing detail rows.
  • Joining to PA_PROJECTS_ALL and PA_TASKS on PROJECT_ID and TASK_ID to report by project and task.
  • Joining to PA_COST_DISTRIBUTION_LINES_ALL on EXPENDITURE_ITEM_ID and LINE_NUM for cost drilldown.
  • Joining to PA_CUST_REV_DIST_LINES_ALL for revenue drilldown, and to PA_COMMITMENT_TXNS on CMT_LINE_ID for commitment analysis.

Related Objects

The following objects are referenced by or relate to PA_TXN_ACCUM_DETAILS through documented foreign keys:

  • PA_TXN_ACCUM — joined on TXN_ACCUM_DETAILS.TXN_ACCUM_ID; the parent accumulator table.
  • PA_COST_DISTRIBUTION_LINES_ALL — joined on EXPENDITURE_ITEM_ID and LINE_NUM; cost drilldown source.
  • PA_CUST_REV_DIST_LINES_ALL — joined on EXPENDITURE_ITEM_ID and LINE_NUM; revenue drilldown source.
  • PA_CUST_EVENT_RDL_ALL — joined on PROJECT_ID, TASK_ID, EVENT_NUM, and LINE_NUM; event revenue source.
  • PA_COMMITMENT_TXNS — joined on CMT_LINE_ID; commitment transaction source.
  • PA_PROJECTS_ALL — joined on PROJECT_ID; project master reference.
  • PA_TASKS — joined on TASK_ID; task master reference.