Search Results cmt_quantity




Overview
Explore in AI Chat

Overview

APPS.PJI_ACT_CMT_BY_PERIOD_V is a reporting view in the Oracle EBS Projects (PJI) schema that consolidates actual cost and commitment balances at the project, task, and accounting period grain. It is defined as a thin projection over a single underlying view, PJI_PRD_ACT_CMT_BY_RSRC_V, and exposes a horizontally consistent column set covering revenue, raw cost, burdened cost, capital cost, quantities, labor and equipment hours, and committed costs across multiple commitment sources.

The view is designed for period-based reporting and integration scenarios in Oracle EBS 12.1.1 and 12.2.2. Because it aggregates activity on a period basis while retaining resource breakdown structure (RBS) identifiers, it supports both summarized project performance summaries and drill-down diagnostics by resource element and resource version. The presence of CMT_QUANTITY and the family of committed cost columns makes it particularly relevant for procurement and commitment reporting workflows where users need to compare incurred actuals to open commitments within the same period window.

Underlying Base Objects

The documented base object for this view is a single view: PJI_PRD_ACT_CMT_BY_RSRC_V. The columns exposed by the source text are a direct, one-to-one selection from that view, with no joins, unions, aggregations, or filters applied in this layer. The aliasing convention (PABR) confirms that PJI_ACT_CMT_BY_PERIOD_V functions as a stable presentation layer, insulating consumers from the internal naming and logic of the underlying resource-based view.

Practically, this means the row count, filtering behavior, and refresh characteristics of APPS.PJI_ACT_CMT_BY_PERIOD_V are entirely inherited from PJI_PRD_ACT_CMT_BY_RSRC_V. Any performance tuning, index usage, or execution plan considerations must be evaluated against the underlying view rather than this projection. The view is a read-only reporting construct and should not be treated as an updatable entity for DML operations.

Key Columns

Common Use Cases and Queries

Typical uses include period commitment reporting, project cost-to-complete analysis, resource-level utilization reporting, and reconciliation of actuals against commitments. A basic period query filtering by project and period is shown below, demonstrating retrieval of the CMT_QUANTITY measure alongside committed costs.

  • Period commitment lookup: select project, task, period, CMT_QUANTITY, and the PO/PR committed cost columns for a given period name.
  • Actual versus commitment comparison: compare BURDENED_COST with CMT_BURDENED_COST per project and period.
  • Resource-level drill-down: group by RBS_ELEMENT_ID and RBS_VERSION_ID to analyze quantity and cost distribution.

Sample SQL:

SELECT PROJECT_ID, TASK_ID, PERIOD_NAME, QUANTITY, CMT_QUANTITY, PO_COMMITTED_COST, PR_COMMITTED_COST, CMT_BURDENED_COST FROM APPS.PJI_ACT_CMT_BY_PERIOD_V WHERE PERIOD_NAME = 'JAN-24' AND PROJECT_ID = :p_project_id;