Search Results tot_cmt_burdened_cost




Overview

APPS.PA_ACCUM_CMT_TXNS_V is a consolidated Oracle EBS Projects (PA) reporting view that exposes commitment transaction accumulations across three organizational grains: project, task, and resource list member. In Oracle EBS 12.1.1 and 12.2.2 it serves as the canonical read interface for committed cost (CMT) balances, presenting summarized commitment transactions with both raw and burdened cost amounts, vendor details, and lifecycle dates. Because it unifies three base views through a UNION, it allows reporting tools, Oracle Business Intelligence (OBIEE), Oracle Project Financial Management, and custom extensions to retrieve commitment accumulations without knowing the internal grain-specific storage model. The column the user searched on, TOT_CMT_RAW_COST, is the raw (unburdened) committed cost total and is the principal measure consumed by commitment-versus-budget and commitment-versus-actual reporting.

Underlying Base Objects

The ETRM metadata documents the referenced base objects as three views and two packages. The row data is sourced from:

Each of the three SELECT statements projects an identical column list, and the results are combined with UNION to produce a single, uniformly shaped result set distinguished by the grain of the identifier columns (PROJECT_ID, TASK_ID, RESOURCE_LIST_MEMBER_ID). The view also references the packages HR_GENERAL and HR_SECURITY, which are leveraged for organizational and security (MOAC / responsibility-level access) processing consistent with HR security policies.

Key Columns

Common Use Cases and Queries

Typical uses include commitment-versus-budget analysis, funds checking, and commitment ledger reconciliation. A common query aggregates raw committed cost by project to compare commitments against budgets:

  • SELECT project_id, SUM(tot_cmt_raw_cost) FROM apps.pa_accum_cmt_txns_v GROUP BY project_id;
  • Filtering on cmt_approved_flag = 'Y' to report only approved commitments.
  • Joining to PA_PROJECTS_ALL on project_id to obtain project names and numbers.
  • Restricting by transaction_source to isolate purchase order versus requisition commitments.

Because the view is secured through HR_SECURITY, results are automatically constrained by the responsibility's organization access. As a UNION of accumulations, callers should apply the grain filter explicitly when a specific level (project, task, or resource) is required, and should expect raw cost to be populated independently from burdened cost. TOT_CMT_RAW_COST remains the most frequently referenced column for commit-versus-actual reporting.