Results for “cmt_distribution_id”

50+ results




Overview
Explore in AI Chat

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

Overview

PA_ACCUM_PROJ_CMT_TXNS_BASE_V is an Oracle E-Business Suite view owned by the APPS schema within the Projects (PA) module. Its purpose is to retrieve project-level commitment transactions, exposing commitment header and line attributes together with associated accumulator context. The view is documented as returning project level commitments, including commitment-line attributes such as commitment type and transaction source, with reference to retrofitted behavior introduced through Release 12 Accounts Payable line uptake.

In the EBS reporting and integration layer, this object functions as a denormalized, presentation-oriented view rather than a transactional base table. It joins commitment transactions to their accumulator detail rows, resolves lookup meanings for commitment line type and transaction source, and resolves the expenditure organization name. This design makes it suitable for feeder programs, project commitment inquiries, and custom reports that require commitment amounts, quantities, and classification without directly navigating the underlying PA commitment schema.

Underlying Base Objects

The view definition references several documented base objects:

  • PA_COMMITMENT_TXNS (synonym) — the primary source of commitment transaction rows, supplying project, task, vendor, commitment number, amounts, dates, and flags.
  • PA_TXN_ACCUM_DETAILS (synonym) — joined on CMT_LINE_ID to provide accumulator detail identity where the line type is 'M'.
  • PA_LOOKUPS (view) — joined twice; once for lookup type 'COMMITMENT LINE TYPE' and once for 'COMMITMENT TXN SOURCE', to resolve descriptive meanings.
  • HR_ORGANIZATION_UNITS (view) — joined on ORGANIZATION_ID to obtain the expenditure organization name.
  • HR_GENERAL and HR_SECURITY (packages) — supporting objects referenced in the dependency chain for organization and security context.

The join predicates restrict the view to commitment accumulator records, linking CT.TASK_ID to zero and mapping each commitment line to its accumulator detail and lookup descriptions.

Key Columns

Common Use Cases and Queries

Typical uses include commitment reporting by project and task, reconciliation of approved versus outstanding commitment amounts, and analysis of commitment transaction sources for Release 12 AP line uptake. A representative query aggregates commitments by project:

  • SELECT project_id, SUM(tot_cmt_raw_cost), SUM(tot_cmt_burdened_cost) FROM pa_accum_proj_cmt_txns_base_v GROUP BY project_id;
  • SELECT cmt_number, cmt_line_number, vendor_name, transaction_source_m, tot_cmt_burdened_cost FROM pa_accum_proj_cmt_txns_base_v WHERE project_id = :p_project_id ORDER BY cmt_number;
  • SELECT cmt_type_code_m, amount_delivered, quantity_outstanding, unit_of_measure FROM pa_accum_proj_cmt_txns_base_v WHERE cmt_approved_flag = 'Y';

Because the view applies lookup and organization joins, consumers should filter on PROJECT_ID or TASK_ID to constrain result sets and avoid scanning the full commitment population.