Results for “pji_xbs_plans_v”

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

Overview

PJI_XBS_PLANS_V is a reporting view owned by the APPS schema in Oracle EBS 12.1.1 and 12.2.2. It belongs to the PJI – Project Intelligence product family, which Oracle has since marked obsolete in favor of the Oracle Project Portfolio Management (PPM) and Oracle Fusion Project Performance reporting stack. The view exposes aggregated effort, cost, and revenue plan data across both workplan and financial plan structures, resolved at the resource breakdown structure (RBS) level. Its purpose is to give downstream reporting, extraction, and integration processes a single denormalized source for plan-versus-actual-versus-estimate-to-complete (ETC) quantities.

The view is of particular interest to consumers searching for labor_effort, since the LABOR_EFFORT column is computed directly from cumulative labor hours in the underlying fact table. The view therefore serves as a convenient access point for labor effort reporting without requiring direct joins against the Project Intelligence accumulators.

Underlying Base Objects

The view is defined over two synonyms:

• PJI_FP_XBS_ACCUM_F — the Project Intelligence accumulation fact table holding per-period, per-resource plan, actual, and ETC balances.
• PJI_PJP_WBS_HEADER — the workplan/financial plan header table carrying the WBS version and the workplan flag (WP_FLAG).

The two are joined on PROJECT_ID and PLAN_VERSION_ID. The view filters the fact table to calendar type 'A', period type 2048, TIME_ID = -1 (the summary/total bucket), and CURR_RECORD_TYPE_ID with bit 8 set, and requires RBS_AGGR_LEVEL = 'T' with PLAN_VERSION_ID greater than zero. Grouping is performed by project, plan version, WBS version, project element, and a decoded structure type.

Key Columns

• PROJECT_ID, PLAN_VERSION_ID, STRUCTURE_VERSION_ID, PROJ_ELEMENT_ID — Project and plan identifiers, plus the WBS version and the project element (task) that the aggregated row pertains to.
• STRUCTURE_TYPE — Derived from WP_FLAG; returns 'WORKPLAN' when the flag is 'Y', otherwise 'FINANCIAL'.
• LABOR_EFFORT — Summed labor hours (NVL of LABOR_HRS), the primary labor effort measure.
• EQUIPMENT_EFFORT / EQUIPMENT_HOURS — Summed equipment hours.
• RAW_COST, BRDN_COST, REVENUE — Total planned raw cost, burdened cost, and revenue.
• LABOR_RAW_COST, LABOR_BRDN_COST, LABOR_REVENUE — Labor-specific cost and revenue plan components.
• ACT_* columns — Actual labor hours, equipment hours, raw cost, burdened cost, and revenue.
• ETC_* columns — Estimate-to-complete labor hours, equipment hours, and cost components.

Common Use Cases and Queries

Typical usage includes labor effort rollups for project performance dashboards, variance analysis between WORKPLAN and FINANCIAL structures, and extraction feeds into external cost or earned-value systems. Because the view already filters to summary time and top-level RBS aggregation, queries generally only need to add project, plan, or element predicates.

A representative query for labor effort by task is:

SELECT project_id, plan_version_id, proj_element_id, structure_type, labor_effort, act_labor_hrs, etc_labor_hrs
FROM apps.pji_xbs_plans_v
WHERE project_id = :p_project_id
ORDER BY proj_element_id;

For plan-versus-actual labor variance, aggregate LABOR_EFFORT against ACT_LABOR_HRS and ETC_LABOR_HRS within the same query. Analysts should note the view’s obsolete status in PJI and confirm whether a supported PPM reporting view is preferred in later releases.