Search Results pji_ac_pln_by_task_v




Overview
Explore in AI Chat

Overview

PJI_AC_PLN_BY_TASK_V is an APPS-owned database view in the Oracle E-Business Suite Project Intelligence (PJI) module. It exposes budgeted cost and revenue amounts at the task level, aggregated across both Oracle Projects (PA) and General Ledger (GL) accounting periods. The view is intended primarily for external project management or planning systems that import financial data from Oracle Projects, allowing those systems to reconcile plan-versus-actual figures without querying the underlying fact tables directly. Because it presents a single denormalized row per project/task/plan type/plan version combination, it simplifies downstream extraction and reporting for tools that require labor hours, cost, revenue, and commitment metrics in one query. The view is marked VALID in the ETRM metadata for release 12.2.2 and applies equally to 12.1.1 deployments where the PJI schema is present.

Underlying Base Objects

The documented referenced base objects are PA_PROJECTS_ALL (referenced through a synonym) and PJI_FP_XBS_ACCUM_F (also accessed through a synonym). PJI_FP_XBS_ACCUM_F is the Project Intelligence financial plan cross-business-structure accumulation fact table, which stores the pre-aggregated plan amounts (cost, revenue, quantities, commitments) that the view later rolls up. PA_PROJECTS_ALL supplies project header context, ensuring that only valid projects are represented. The view text groups the fact records by PROJECT_ID, PROJECT_ELEMENT_ID (task), PLAN_TYPE_ID, and PLAN_VERSION_ID, and applies SUM aggregation across the measure columns. This design means the view returns a consolidated plan-by-task dataset rather than the granular rows held in the fact table.

Key Columns

Common Use Cases and Queries

Typical usage centers on extracting budget/plan data for external systems, reporting labor hour consumption, and reconciling plan versus actual. A representative query retrieves planned and ETC labor hours per task:

  • SELECT project_id, task_id, plan_type_id, plan_version_id, labor_hrs, etc_labor_hrs, revenue, burdened_cost FROM apps.pji_ac_pln_by_task_v WHERE project_id = :project_id;

For plan-versus-actual analysis, consumers select both the plan columns and the ACT_ columns in the same row. For commitment reporting, the CMT_BURDENED_COST and the four committed-cost columns supply a pre-summed commitment figure. Because all measures are already aggregated by the view, external integrations can apply filters on project, task, or plan version and load results directly, avoiding joins to the underlying PJI_FP_XBS_ACCUM_F fact table.