Results for “oth_committed_cost”

50+ results




Overview
Explore in AI Chat

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

Overview

PJI_PRD_ACT_CMT_BY_RSRC_V is a Project Intelligence (PJI) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents periodic actual cost, commitment, and revenue totals aggregated by project task and by resource breakdown structure (RBS) element. The view consolidates data across both Oracle Projects (PA) and General Ledger (GL) calendar periods, making it suitable for cross-module cost and commitment reporting.

The documented description notes that the view displays budget cost and revenue totals for PA and GL periods by task and resources, and that it is mainly used by external project management systems that import actuals from Oracle Projects. The view name itself (ACT_CMT) indicates its emphasis on actuals and commitments by resource, while the underlying aggregation supports both cost and revenue rollups. In practice this view serves as a denormalized, integration-ready dataset for external systems, Oracle Business Intelligence (OBIEE/OBIA), and ad-hoc reporting where a resource-level, period-by-period cost and commitment picture is required.

Underlying Base Objects

The view is defined over three documented base objects:

  • PJI_FP_XBS_ACCUM_F (SYNONYM) — the primary fact table, aliased FACT. It stores accumulated cost, revenue, quantity, and commitment amounts by project, task, resource, and time period. All measure columns in the view are aggregated from this table.
  • PJI_TIME_CAL_PERIOD_V (VIEW) — aliased TIME, supplying period attributes such as calendar type, calendar identifier, period name, start date, and end date. The join is FACT.TIME_ID = TIME.CAL_PERIOD_ID.
  • PA_PROJECTS_ALL (SYNONYM) — aliased PPA, the Oracle Projects project master, providing the project-level filter that restricts the fact data to valid projects.

The view restricts the fact rows with FACT.PERIOD_TYPE_ID = 32, which limits the aggregation to a specific period type (typically the PA/GL period type relevant to actual cost and commitment accumulation). All measure columns are wrapped in SUM() and grouped by project, task, calendar type, calendar, period name/dates, and RBS element/version, producing a compact periodic rollup.

Key Columns

Common Use Cases and Queries

Typical use cases include resource-level cost and commitment reconciliation, external project management system integration, and periodic variance reporting across PA and GL calendars. A representative query filters by project and period and selects the key cost, commitment, and revenue measures:

  • Resource cost and commitment by period: SELECT project_id, task_id, period_name, rbs_element_id, raw_cost, burdened_cost, cmt_burdened_cost, revenue FROM pji_prd_act_cmt_by_rsrc_v WHERE project_id = :p_project_id ORDER BY period_start_date.
  • Commitment exposure by task: aggregate cmt_burdened_cost and its component columns (SUP_INV_COMMITTED_COST, PO_COMMITTED_COST, PR_COMMITTED_COST, OTH_COMMITTED_COST) grouped by task_id to identify unspent committed amounts.
  • External system extraction: a full or incremental extract joined back to PA_PROJECTS_ALL via project_id for downstream import of actuals and commitments into third-party project management tools.

Because the view already performs the aggregation, query predicates on project_id, task_id, or period_name are essential to limit data volume. Note that the underlying documentation text references the related view name PJI_PRD_PLN_BY_RSRC_V in its description, but the object analyzed here is PJI_PRD_ACT_CMT_BY_RSRC_V, whose column set is oriented toward actuals and commitments rather than plan.