Results for “burdened_cost”

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

Overview

PJI_ACCUM_WBS_ACT_V is an Oracle E-Business Suite view owned by the APPS schema and shipped as part of the PJI (Project Intelligence) product family. It presents accumulated project actuals at the project and task level, consolidating raw cost, burdened cost, and revenue amounts on an inception-to-date (ITD) basis. Its primary role is to expose project performance data in a form consumable by Project Intelligence dashboards, Oracle Business Intelligence (OBIEE) subject areas, and custom reporting against the Projects module. The view is registered with a status of VALID and is documented in ETRM for releases 12.1.1 and 12.2.2.

The view is significant because it applies a source-flag-driven selection strategy. Rather than being a simple projection over a single base object, it merges two distinct data paths, which allows Project Intelligence to reconcile standard accumulated actuals with amounts derived from an alternate source used during the accumulation process.

Underlying Base Objects

The documented dependencies of PJI_ACCUM_WBS_ACT_V include PA_ACCUM_WBS_ACT_V (VIEW), PA_PROJECTS_ALL (SYNONYM), and PJI_FM_XBS_ACCUM_TMP1 (SYNONYM). Additional referenced objects recorded in the metadata are HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages, which are inherited through the dependency chain (notably via PA_PROJECTS_ALL and security-related logic in the underlying views).

Structurally, the view text joins PA_ACCUM_WBS_ACT_V to PA_PROJECTS_ALL on PROJECT_ID where PJI_SOURCE_FLAG is null, and unions that result with a second branch joining PJI_FM_XBS_ACCUM_TMP1 to PA_PROJECTS_ALL on PROJECT_ID where PJI_SOURCE_FLAG = 'Y'. The PJI_FM_XBS_ACCUM_TMP1 object acts as a temporary accumulation store for the alternate source path, while PA_ACCUM_WBS_ACT_V supplies the standard inception-to-date accumulated actuals. The union all preserves duplicates intentionally, since the two branches represent mutually exclusive source populations distinguished by the source flag.

Key Columns

• PROJECT_ID — The project identifier, sourced from ACT.PROJECT_ID in the first branch and TMP.PROJECT_ID in the second. It is the principal join key to PA_PROJECTS_ALL.
• TASK_ID — The task or project element identifier. In the first branch it maps to ACT.TASK_ID; in the second it maps to TMP.PROJECT_ELEMENT_ID, aliased to TASK_ID so the union is column-compatible.
• RAW_COST — Inception-to-date raw cost, taken from ACT.RAW_COST_ITD or TMP.POU_RAW_COST depending on the source flag.
• BURDENED_COST — Inception-to-date burdened cost, from ACT.BURDENED_COST_ITD or TMP.POU_BRDN_COST.
• REVENUE — Inception-to-date revenue, from ACT.REVENUE_ITD or TMP.POU_REVENUE.

All amount columns are cumulative from project inception rather than period-specific, which is characteristic of the PA_ACCUM family of views.

Common Use Cases and Queries

The view is typically used to feed project cost and revenue summaries into Project Intelligence reporting, to reconcile burdened versus raw cost at the task level, and to validate alternate-source accumulation results before posting. Because it excludes projects handled by the alternate source path when the flag is null, queries against it return a coherent, de-duplicated population.

A representative query retrieving accumulated actuals for a project is:

• SELECT project_id, task_id, raw_cost, burdened_cost, revenue FROM apps.pji_accum_wbs_act_v WHERE project_id = :p_project_id;
• SELECT project_id, SUM(raw_cost) raw_cost, SUM(burdened_cost) burdened_cost, SUM(revenue) revenue FROM apps.pji_accum_wbs_act_v GROUP BY project_id;
• SELECT a.project_id, a.task_id, a.burdened_cost FROM apps.pji_accum_wbs_act_v a, apps.pa_projects_all p WHERE a.project_id = p.project_id AND p.project_number = :p_number;

Because the object is a view rather than a table, no DML should be issued against it, and query performance depends on the underlying accumulation and temporary tables.