Search Results cmt_creation_date




Overview
Explore in AI Chat

Overview

PA_ACCUM_CMT_TXNS_V is an APPS-owned database view in the Oracle E-Business Suite Projects (PA) module. It presents project-, task-, and resource-level commitment transaction data in a single consolidated result set, including commitment-line attributes such as vendor, commitment type, amounts, dates, and outstanding quantities. The object is defined in both Oracle EBS 12.1.1 and 12.2.2 and carries a status of VALID, exposing it as a supported read-only interface for reporting and integration.

Commitments in Oracle Projects represent externally sourced obligations, typically purchase orders and requisitions originating in Oracle Purchasing, that are associated with a project, task, or resource. This view consolidates accumulated commitment transactions so that cost and financial reporting can retrieve commitment information without querying multiple base views individually. Its principal role is as a reporting and data-extraction layer; because the view is defined with a UNION of three underlying base views, it returns the union of project-level, task-level, and resource-level commitment records.

Underlying Base Objects

The documented definition of PA_ACCUM_CMT_TXNS_V is a UNION of three base views in the APPS schema, each expressed through an identical column list:

The documented metadata also lists HR_GENERAL (PACKAGE) and HR_SECURITY (PACKAGE) among the referenced base objects. This indicates that the view's access path is subject to Oracle HR security, so row visibility is filtered according to the operating user's organization and responsibility security profile as resolved through the HR security packages. The view therefore inherits Projects commitment accumulation logic while enforcing organizational security at query time.

Key Columns

Because all three base views expose an identical column list, the columns returned by PA_ACCUM_CMT_TXNS_V are consistent regardless of the source level.

Common Use Cases and Queries

Typical scenarios include project commitment reporting, reconciliation of commitments against expenditures, and feeds into project cost or funds-availability reporting. Because row-level access is governed by HR security, queries should be executed under an appropriately privileged responsibility and, where required, with MO security context initialized.

A representative query listing outstanding commitments by project and task:

  • SELECT project_id, task_id, vendor_name, cmt_number, cmt_line_number, tot_cmt_raw_cost, tot_cmt_burdened_cost, quantity_outstanding, cmt_approved_flag FROM pa_accum_cmt_txns_v WHERE project_id = :p_project_id ORDER BY cmt_creation_date;
  • SELECT transaction_source, transaction_source_m, COUNT(*) FROM pa_accum_cmt_txns_v GROUP BY transaction_source, transaction_source_m;
  • SELECT vendor_name, SUM(tot_cmt_burdened_cost) FROM pa_accum_cmt_txns_v WHERE cmt_approved_flag = 'Y' GROUP BY vendor_name;

The view should be treated as read-only; commitment data is maintained through Oracle Projects and Oracle Purchasing processes, not through this view.