Results for “act_raw_cost”

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

Overview

PJI_XBS_PLANS_PRJ_V is a read-only Oracle EBS view owned by the APPS schema and shipped as part of the PJI (Project Intelligence) product family. It presents a consolidated, project-level projection of cross-business-plan (XBS) financial and workplan accumulations. The view aggregates fact data captured in the PJI cross-business-plan accumulation table and joins it to the WBS header to expose plan-level rolled-up effort, cost, and revenue measures for each project element.

A distinguishing characteristic of the view is the STRUCTURE_TYPE column, which is derived via DECODE(HEAD.WP_FLAG, 'Y', 'WORKPLAN', 'FINANCIAL'). This allows consumers to distinguish records that originate from a Workplan structure versus a Financial structure without querying the header directly, making the view suitable for mixed-purpose reporting in Project Intelligence and downstream analytics.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

• PJI_FP_XBS_ACCUM_F — the primary fact table, aliased as FACT. It supplies the project, plan version, project element, and the full set of effort, cost, and revenue measures.
• PJI_PJP_WBS_HEADER — the WBS/plan header, aliased as HEAD. It contributes WBS_VERSION_ID and the WP_FLAG used to classify the structure type.

The two objects are joined on PROJECT_ID and PLAN_VERSION_ID. The fact side is tightly filtered to a single reporting slice: CALENDAR_TYPE = 'A', PERIOD_TYPE_ID = 2048, TIME_ID = -1, PRG_ROLLUP_FLAG = 'N', RBS_AGGR_LEVEL = 'T', PLAN_VERSION_ID > 0, and BITAND(CURR_RECORD_TYPE_ID, 8) = 8. Results are grouped by project, plan version, WBS version, project element, and the workplan/financial classification.

Key Columns

• PROJECT_ID, PLAN_VERSION_ID, WBS_VERSION_ID — the composite plan context for each row.
• PROJECT_ELEMENT_ID — the WBS or project element being summarized.
• STRUCTURE_TYPE — derived value indicating WORKPLAN or FINANCIAL structure.
• LABOR_EFFORT, EQUIPMENT_EFFORT, EQUIPMENT_HOURS — planned effort quantities.
• RAW_COST, BRDN_COST, REVENUE, and their labor-specific counterparts (LABOR_RAW_COST, LABOR_BRDN_COST, LABOR_REVENUE) — planned amounts.
• Actual measures: ACT_LABOR_HRS, ACT_EQUIP_HRS, ACT_LABOR_BRDN_COST, ACT_EQUIP_BRDN_COST, ACT_BRDN_COST, ACT_RAW_COST, ACT_REVENUE.
• Estimate-to-complete measures: ETC_LABOR_HRS, ETC_EQUIP_HRS, ETC_LABOR_BRDN_COST, ETC_EQUIP_BRDN_COST, ETC_BRDN_COST, ETC_RAW_COST.

Note that the documented column list uses canonical aliases such as STRUCTURE_VERSION_ID and PROJ_ELEMENT_ID, while the underlying SQL selects HEAD.WBS_VERSION_ID and FACT.PROJECT_ELEMENT_ID. All measure columns are wrapped in SUM(NVL(..., 0)), so consumers can rely on non-null numeric output.

Common Use Cases and Queries

Typical usage centers on plan-versus-actual and estimate-to-complete reporting at the project element level, across both Workplan and Financial structures.

• Comparing planned, actual, and ETC values for a given project and plan version.
• Separating results by STRUCTURE_TYPE to reconcile Workplan-driven versus Financial-driven plans.
• Feeding BI Publisher or OBIEE dashboards that report effort, cost, and revenue by WBS element.

A representative query:

SELECT PROJECT_ID, PLAN_VERSION_ID, PROJ_ELEMENT_ID, STRUCTURE_TYPE,
  LABOR_EFFORT, RAW_COST, BRDN_COST, REVENUE,
  ACT_LABOR_HRS, ACT_RAW_COST, ETC_RAW_COST
FROM APPS.PJI_XBS_PLANS_PRJ_V
WHERE PROJECT_ID = :p_project_id
  AND PLAN_VERSION_ID = :p_plan_version_id
ORDER BY PROJ_ELEMENT_ID;

Because the view is aggregation-based and internally filtered to a fixed slice of the accumulation table, it should be treated strictly as a reporting object; no DML is supported, and heavy ad-hoc queries should be constrained by project and plan version to avoid full scans.