Search Results pa_accum_task_cmt_txns_base_v




Overview

PA_ACCUM_TASK_CMT_TXNS_BASE_V is an Oracle EBS Projects (PA) reporting view owned by the APPS schema. It presents project-task level commitment transactions, combining commitment header and line attributes held in PA_COMMITMENT_TXNS with the transaction accumulation context stored in PA_TXN_ACCUM_DETAILS. The view is described in ETRM as a "Retrofitted" object, meaning it was introduced or re-pointed to support the commitment accumulation model used by Project Resource Management and Cost Collection processes.

The view serves as a denormalized base layer for commitment-related reporting, integrating descriptive lookups, task identification, expenditure organization details, and transaction source meanings into a single row per commitment line joined to an accumulation detail record. It is typically consumed by Oracle Projects commitment reports, Project Status Inquiry style inquiries, and custom extracts that must reconcile commitments against actual and budgeted costs at the lowest project-task-expenditure-type granularity.

Underlying Base Objects

Per the documented metadata the view is defined over the following objects:

  • PA_COMMITMENT_TXNS (synonym) — the source of commitment line data, including vendor, commitment number and line, raw and burdened cost, dates, expenditure type, organization, approved flag, quantity, and unit of measure.
  • PA_TXN_ACCUM_DETAILS (synonym) — provides TXN_ACCUM_ID and the accumulation line type; the view restricts to TAD.LINE_TYPE = 'M' and joins on CMT_LINE_ID.
  • PA_LOOKUPS (view) — joined twice: once with LOOKUP_TYPE = 'COMMITMENT LINE TYPE' for the line type meaning, and once with LOOKUP_TYPE = 'COMMITMENT TXN SOURCE' for the transaction source meaning.
  • PA_TASKS (synonym) — supplies TASK_NUMBER and TASK_NAME.
  • HR_ORGANIZATION_UNITS (view) — provides the expenditure organization name via ORGANIZATION_ID.
  • HR_GENERAL and HR_SECURITY (packages) — supporting PL/SQL packages referenced for security and organization access.

Key Columns

Common Use Cases and Queries

Typical usage includes commitment-to-actual reconciliation, expenditure type analysis, and organization-level commitment reporting. A representative query:

  • SELECT project_id, task_number, expenditure_type, cmt_number, vendor_name, tot_cmt_burdened_cost FROM pa_accum_task_cmt_txns_base_v WHERE project_id = :p_project_id ORDER BY task_number, expenditure_type;
  • Commitment detail by vendor and approval status: SELECT vendor_name, SUM(tot_cmt_burdened_cost) FROM pa_accum_task_cmt_txns_base_v WHERE cmt_approved_flag = 'Y' GROUP BY vendor_name;
  • Transaction source drill-down: SELECT cmt_number, transaction_source_m, amount_delivered FROM pa_accum_task_cmt_txns_base_v WHERE transaction_source = :p_source;

Because the view joins commitment transactions to accumulation details, it is best suited for reporting rather than high-volume transactional processing, and custom org-security logic should respect the HR_SECURITY package conventions used by the underlying PA objects.