Search Results cmt_raw_cost




Overview
Explore in AI Chat

Overview

APPS.PA_RPT_PRJ_CMT_SUMMARY is a public Oracle E-Business Suite view in the Projects (PA) schema that exposes project-level commitment cost summarization data. It is registered under the application design data as PA.PA_RPT_PRJ_CMT_SUMMARY and carries a VALID status in the ETRM repository for both 12.1.1 and 12.2.2. The view is documented as a reporting-oriented object intended primarily to support Oracle Discoverer workbooks, though it is equally available for custom reporting and integration requirements that need aggregated commitment balances by project.

Commitments in Oracle Projects represent encumbered or anticipated costs arising from purchasing, requisitioning, or other feeder transactions, accumulated into the project cost structure. The view does not capture transactional detail; instead, it surfaces the summarized accumulated commitment positions already persisted in the underlying accumulation tables. Because of this, it is best understood as a convenient read-only access layer over pre-aggregated project commitment data rather than a live computation of commitment activity.

A documented prerequisite governs its use: all Reporting Profiles must be configured at the site level of the application for the view to return correct results. Without proper reporting profile configuration, the project identifiers and accumulation periods returned may not align with the expected reporting hierarchy, and the summarized amounts may be incomplete or misattributed.

Underlying Base Objects

The view is defined over three base objects, all referenced via APPS synonyms: PA_PROJECTS, PA_PROJECT_ACCUM_COMMITMENTS, and PA_PROJECT_ACCUM_HEADERS. Each serves a distinct purpose in composition of the result set:

  • PA_PROJECTS — supplies the project master definition, including the project number, name, and organizational attributes needed to join the accumulated commitment rows to the correct project.
  • PA_PROJECT_ACCUM_HEADERS — provides the accumulation period context, allowing each summarized row to be tied to the GL or PA period in which the commitment figures were last accumulated.
  • PA_PROJECT_ACCUM_COMMITMENTS — the principal fact source, holding the raw and burdened commitment cost amounts at the project accumulation level.

These tables are joined to produce one row per project accumulation record. The view sits downstream of these objects and does not modify them, making it safe for read-only reporting workloads. It is itself referenced by APPS.PA_RPT_PRJ_SUMMARY_BASE_V, indicating that it forms part of a broader reporting view chain used by the Projects reporting layer.

Key Columns

  • PROJECT_ACCUM_ID (NUMBER(15)) — the unique identifier for the accumulated actual and budget line; this is the primary correlation key back to the accumulation tables.
  • ACCUM_PERIOD (VARCHAR2(20)) — the last accumulation GL or PA period, determined by the installed implementation option; establishes the reporting period context.
  • CMT_RAW_COST (NUMBER) — the commitment raw cost for the project, i.e., commitment amounts expressed before burden or indirect cost application.
  • CMT_BURDENED_COST (NUMBER) — the commitment burdened cost, reflecting raw cost plus applied burden/indirect components.
  • PROJECT_ID (NUMBER(15)) — the identifier of the project to which the summarized commitment amounts apply; the join key to PA_PROJECTS.

The user query term cmt_raw_cost corresponds directly to the CMT_RAW_COST column, which is the raw commitment cost measure central to this view.

Common Use Cases and Queries

Typical uses include project commitment cost reporting, raw-versus-burdened commitment analysis, and feeds into custom Discoverer or BI workbooks. A representative query retrieving raw and burdened commitment costs for a specific project is shown below.

  • Project-level commitment summary: select PROJECT_ID, ACCUM_PERIOD, CMT_RAW_COST, CMT_BURDENED_COST from the view filtered by PROJECT_ID.
  • Raw-cost reconciliation: compare CMT_RAW_COST against CMT_BURDENED_COST to derive the burden component for a given accumulation period.
  • Period-batch extraction: query all rows at the latest ACCUM_PERIOD to support period-end reporting.
SELECT PROJECT_ID,
       ACCUM_PERIOD,
       CMT_RAW_COST,
       CMT_BURDENED_COST
FROM   APPS.PA_RPT_PRJ_CMT_SUMMARY
WHERE  PROJECT_ID = :p_project_id
ORDER  BY ACCUM_PERIOD;

Because the view is read-only and exposes only summarized figures, consumers requiring transactional commitment detail must query the underlying commitment tables directly. When embedded in custom reports, callers should confirm site-level Reporting Profile setup to guarantee accurate project and period attribution.