Results for “project_accum_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_RPT_PRJ_CMT_SUMMARY is an APPS-owned reporting view within the Oracle E-Business Suite Projects (PA) module. Its stated purpose is to display project-level commitments in a form suitable for reporting and downstream integration. The view consolidates commitment cost data that Oracle Projects stores in its accumulation tables, flattening the data to a single row per project accumulation period so that it can be queried directly by reports, extracts, and custom programs without requiring the caller to reconstruct the joins between the accumulation header and commitment detail tables.

Because the view persists in a VALID status and is shipped in the APPS schema, it is available to any responsibility or concurrent program with appropriate grants. It is an internal reporting object rather than a transactional entry point: no inserts, updates, or deletes are expected, and consumers should treat the columns as read-only snapshots of accumulated commitment cost for a given period. The view is documented in ETRM and is present across the 12.1.1 and 12.2.2 releases, where it serves the same role. The reference to cmt_burdened_cost in the underlying commitment table aligns with the view's exposure of CMT_BURDENED_COST, making it the natural target for users seeking burdened commitment amounts at the project level.

Underlying Base Objects

The view is defined over three documented base objects, exposed through APPS synonyms: PA_PROJECT_ACCUM_HEADERS, PA_PROJECT_ACCUM_COMMITMENTS, and PA_PROJECTS. The join logic is straightforward:

• PA_PROJECT_ACCUM_COMMITMENTS is joined to PA_PROJECT_ACCUM_HEADERS on PROJECT_ACCUM_ID, linking each commitment accumulation row to its parent header row.
• PA_PROJECT_ACCUM_HEADERS is joined to PA_PROJECTS on PROJECT_ID, attaching project master attributes and ensuring the result set is scoped to valid project definitions.

Two filters constrain the result set to the project-level, non-task, non-resource granularity: PAH.TASK_ID = 0 and PAH.RESOURCE_LIST_MEMBER_ID = 0. In Oracle Projects accumulation data, a TASK_ID of zero denotes the project-level rollup rather than a specific task, and a RESOURCE_LIST_MEMBER_ID of zero denotes the total across the resource list rather than an individual expenditure category or resource. Consequently, the view does not expose task-level or resource-level detail; it deliberately reports the fully rolled-up commitment figure for the project and period. The burdened commitment value surfaced by the view originates from CMT_BURDENED_COST_PTD in PA_PROJECT_ACCUM_COMMITMENTS.

Key Columns

• PROJECT_ACCUM_ID — Identifier of the accumulation header record that anchors the row; the primary join key between the header and commitment accumulation tables.
• ACCUM_PERIOD — The accumulation period (PA period) to which the commitment balances belong, used to select period-to-date reporting windows.
• CMT_RAW_COST — The raw (unburdened) commitment cost period-to-date. In the view text this maps to CMT_RAW_COST_PTD in the commitment accumulation table.
• CMT_BURDENED_COST — The burdened commitment cost period-to-date, derived from CMT_BURDENED_COST_PTD. This is the column most commonly sought when users search on "cmt_burdened_cost," as it reflects committed amounts inclusive of burden/overhead.
• PROJECT_ID — The project identifier from the accumulation header, joinable to PA_PROJECTS and to other project-keyed reporting objects.

Common Use Cases and Queries

Typical scenarios include project commitment reporting, reconciliation of burdened versus raw committed cost, feeding project cost dashboards, and extracting period-to-date commitment balances into external reporting tools. The following query retrieves burdened and raw commitment cost for a specific project across periods:

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;

To compare burdened and raw commitments and derive the burden component for the latest accumulation period:

SELECT project_id, accum_period,
       cmt_raw_cost, cmt_burdened_cost,
       (cmt_burdened_cost - cmt_raw_cost) AS burden_amount
FROM   apps.pa_rpt_prj_cmt_summary
WHERE  accum_period = :p_period
ORDER BY cmt_burdened_cost DESC;

Because the view is restricted to TASK_ID = 0 and RESOURCE_LIST_MEMBER_ID = 0, it should not be used where task-level or resource-level commitment detail is required; for those needs, query PA_PROJECT_ACCUM_COMMITMENTS joined to PA_PROJECT_ACCUM_HEADERS directly without the project-level filters.