Results for “pa_commitment_txns”

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

Overview

PA_COMMITMENT_TXNS is a Projects (PA) module table that stores commitment transactions used to hold summarized project summary commitment amounts. In Oracle EBS 12.1.1 and 12.2.2, commitments represent anticipated costs arising from purchase orders, requisitions, and other purchasing documents that have not yet been transformed into actual expenditures. This table consolidates those anticipated amounts at the project and task level, enabling project managers and cost analysts to compare budgeted, committed, and actual costs within the same reporting framework.

Each row in the table captures a single commitment line, keyed by a surrogate primary key, CMT_LINE_ID, enforced through the PA_COMMITMENT_TXNS_PK constraint. A separate unique index, PA_COMMITMENT_TXNS_U1, also covers CMT_LINE_ID, reinforcing its role as the natural business identifier for the commitment line. From a Data Vault modeling perspective, the heuristic classification for this object is hub-leaning, since CMT_LINE_ID functions as a stable, unique business key around which descriptive attributes and transactional measures are organized.

Key Information Stored

The table contains 95 documented columns, but the most functionally significant ones fall into several categories:

• Identity and relationships: CMT_LINE_ID (surrogate primary key, also the unique business-key candidate), PROJECT_ID, TASK_ID, CMT_NUMBER, CMT_LINE_NUMBER, CMT_HEADER_ID, CMT_DISTRIBUTION_ID.
• Commitment detail: TRANSACTION_SOURCE, LINE_TYPE, DESCRIPTION, EXPENDITURE_ITEM_DATE, PA_PERIOD, GL_PERIOD, EXPENDITURE_TYPE, EXPENDITURE_CATEGORY, VENDOR_ID, VENDOR_NAME, UNIT_OF_MEASURE, UNIT_PRICE.
• Financial and quantity measures: TOT_CMT_RAW_COST, TOT_CMT_BURDENED_COST, TOT_CMT_QUANTITY, QUANTITY_ORDERED, AMOUNT_ORDERED, QUANTITY_DELIVERED, AMOUNT_DELIVERED, QUANTITY_INVOICED, AMOUNT_INVOICED, QUANTITY_CANCELLED, AMOUNT_CANCELLED, and the corresponding outstanding and overbilled amounts.
• Currency conversions: DENOM_CURRENCY_CODE, ACCT_CURRENCY_CODE, PROJECT_CURRENCY_CODE, and their associated exchange rates, rate dates, and rate types.
• Audit and provenance: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID.

Common Use Cases and Queries

Typical reporting scenarios include reconciling commitments against actual expenditures, tracking outstanding deliveries or invoices on purchasing documents linked to projects, and analyzing commitment trends by period, task, or vendor. A representative query for outstanding commitment amounts by project might be:

SELECT p.project_number, SUM(c.TOT_CMT_RAW_COST) commitment_cost
FROM   pa_commitment_txns c, pa_projects_all p
WHERE  c.project_id = p.project_id
AND    c.pa_period = :period
GROUP  BY p.project_number;

Analysts also use the quantity-based columns to measure purchase order fulfillment, comparing QUANTITY_ORDERED with QUANTITY_DELIVERED and QUANTITY_INVOICED to identify overdue supply. Since the table supports multiple currency representations, reporting can be performed in project, accounting, or transaction denominations without re-deriving rates.

Related Objects

The strongest dependency is documented through the foreign key PA_TXN_ACCUM_DETAILS.CMT_LINE_ID, which references PA_COMMITMENT_TXNS.CMT_LINE_ID. This relationship places the accumulation detail records downstream of the commitment line, aligning summarized commitments with the transactions that accumulate against them. The tables PA_COMMITMENT_TXNS_EFC and PA_TXN_ACCUM_DETAILS_AR likewise reference CMT_LINE_ID, reflecting cross-application and receivables-related accumulation paths.

In addition, joining PROJECT_ID to PA_PROJECTS_ALL and TASK_ID to PA_TASKS provides the project and task context required for most project-level reporting. These relationships make PA_COMMITMENT_TXNS a central holding object for commitment reporting within the Oracle Projects data model.