Search Results cmt_rejection_code




Overview
Explore in AI Chat

Overview

APPS.PA_STATUS_CMT_BASE_V is a reporting and integration view within the Oracle E-Business Suite Projects (PA) module. It consolidates commitment (CMT) transaction information across project, task, and resource-level hierarchies into a single, uniformly structured result set. The view functions as the base consolidation layer for commitment status reporting, presenting purchasing commitments such as purchase orders and purchase requisitions in a form suitable for Project Status Inquiry, cost and commitment analysis, and downstream reporting or interface extraction.

The view is defined as a UNION ALL of three component views — PA_STATUS_PROJ_CMT_BASE_V, PA_STATUS_TASK_CMT_BASE_V, and PA_STATUS_RSRC_CMT_BASE_V — each of which exposes commitment data at a different level of project detail. Because the union preserves all rows without duplicate elimination, a commitment appears at the granularity supplied by whichever component view contributes it. The column list is identical across all branches, guaranteeing a stable projection for consumers. The identifier most frequently used to locate a specific commitment is CMT_NUMBER, which carries the source document number (for example, a purchase order or requisition number) and is typically paired with CMT_LINE_NUMBER to identify the exact commitment line.

Underlying Base Objects

The ETRM metadata documents the following referenced objects: HR_GENERAL (PACKAGE), HR_SECURITY (PACKAGE), PA_STATUS (PACKAGE), PA_STATUS_PROJ_CMT_BASE_V (VIEW), PA_STATUS_RSRC_CMT_BASE_V (VIEW), and PA_STATUS_TASK_CMT_BASE_V (VIEW). The three PA_STATUS_*_CMT_BASE_V views are the direct sources combined by UNION ALL. The remaining objects are referenced indirectly through those component views or through security and status resolution logic.

  • PA_STATUS_PROJ_CMT_BASE_V — supplies project-level commitment rows.
  • PA_STATUS_TASK_CMT_BASE_V — supplies task-level commitment rows.
  • PA_STATUS_RSRC_CMT_BASE_V — supplies resource-list-member-level commitment rows.
  • PA_STATUS (PACKAGE) — provides status derivation logic used to determine the state of a commitment or project.
  • HR_SECURITY (PACKAGE) and HR_GENERAL (PACKAGE) — support organizational and person-level security and name resolution applied within the underlying views.

Because the view depends on these packages and views, its runtime behavior inherits any security filtering and status logic implemented in the component views.

Key Columns

The projection is consistent across all branches of the union. The columns most relevant to typical reporting are:

Common Use Cases and Queries

A frequent requirement is to retrieve all commitments for a given document number. The following query returns commitment details across all levels:

  • SELECT project_id, task_id, cmt_number, cmt_line_number, vendor_name, tot_cmt_raw_cost, tot_cmt_burdened_cost, cmt_approved_flag FROM apps.pa_status_cmt_base_v WHERE cmt_number = :p_cmt_number;

Reporting by project and task is equally common, aggregating burdened commitment amounts:

  • SELECT project_id, task_id, SUM(tot_cmt_burdened_cost) tot_burdened FROM apps.pa_status_cmt_base_v WHERE project_id = :p_project_id GROUP BY project_id, task_id;

Commitments pending approval or with outstanding quantities are typically isolated using the approval flag and quantity column:

  • SELECT cmt_number, cmt_line_number, vendor_name, quantity_outstanding, unit_of_measure FROM apps.pa_status_cmt_base_v WHERE cmt_approved_flag = 'N' AND quantity_outstanding > 0;

Because the view unions project-, task-, and resource-level rows, results should be filtered or aggregated according to the desired reporting grain to avoid double counting when the same commitment is represented at more than one level.