Search Results act_prj_burdened_cost

Overview

The table PJI_FM_EXTR_PLAN_LINES resides in the PJI schema and belongs to the Project Intelligence (PJI) product family, which Oracle classifies as Obsolete in Oracle E-Business Suite 12.1.1 and 12.2.2. As documented in the ETRM repository, this table stores the changes to financial plan data. It functions as a staging and delta-capture structure within the Project Intelligence extraction and reporting framework, holding plan line records that have been captured from the source financial planning model for downstream analytical processing.

The heuristic Data Vault classification derived from the foreign key structure is link. This designation reflects the table's role as an associative construct: it resolves relationships between PA_BUDGET_VERSIONS, PA_PROJECTS_ALL, PA_PROJ_ELEMENTS, PA_RBS_ELEMENTS, and PA_RBS_VERSIONS_B. In a dimensional modeling exercise, this object is therefore best treated as a link (or fact-like association table) rather than a hub or satellite, since it primarily carries the intersection of project, element, and version identifiers alongside measures.

Key Information Stored

The documented physical schema contains 47 columns. The most significant identifiers and measures include:

PROJECT_ID – Foreign key to PA_PROJECTS_ALL; identifies the project whose plan is being captured.
PROJECT_ELEMENT_ID – Foreign key to PA_PROJ_ELEMENTS; the work breakdown or cost element context.
PLAN_VERSION_ID – Foreign key to PA_BUDGET_VERSIONS; identifies the specific plan/budget version.
RBS_ELEMENT_ID and RBS_VERSION_ID – Reference the resource breakdown structure element and version (PA_RBS_ELEMENTS, PA_RBS_VERSIONS_B).
PERIOD_NAME, START_DATE, END_DATE, CALENDAR_TYPE – Provide the temporal grain of the plan line.
CBS_ELEMENT_ID – Links the line to a cost breakdown structure element.
RESOURCE_CLASS_CODE and RATE_BASED_FLAG – Describe the type of resource planned and whether rate-based costing applies.
TXN_RAW_COST, PRJ_RAW_COST, PFC_RAW_COST, and their burdened and revenue counterparts – Carry transactional, project, and project functional currency amounts.
QUANTITY, ACT_QUANTITY, and ETC_QUANTITY – Represent planned, actual, and estimate-to-complete quantities; matching ACT_* and ETC_* cost and revenue columns support variance and forecasting.

The metadata does not document a single surrogate primary key column; PROJ

ECT_ID combined with PROJECT_ELEMENT_ID, PLAN_VERSION_ID, RBS_ELEMENT_ID, RBS_VERSION_ID, and PERIOD_NAME constitutes the probable composite business key.

Common Use Cases and Queries

Typical usage centres on comparing planned, actual, and estimate-to-complete financials across projects and RBS elements. A representative query joins to the master tables on the documented keys:

Plan-versus-actual variance analysis: select PRJ_BURDENED_COST and ACT_PRJ_BURDENED_COST, grouping by PROJECT_ID, PLAN_VERSION_ID, and PERIOD_NAME.
ETC forecasting: aggregate ETC_QUANTITY, ETC_TXN_RAW_COST, and ETC_PFC_BURDENED_COST by RESOURCE_CLASS_CODE.
Currency-translation reporting: reconcile TXN_*, PRJ_*, and PFC_* amounts using TXN_CURRENCY_CODE, PRJ_CURRENCY_CODE, and PFC_CURRENCY_CODE.

Joins to PA_PROJECTS_ALL and PA_BUDGET_VERSIONS are essential to resolve project names and version labels in any report.

Related Objects

PA_PROJECTS_ALL – joined on PROJECT_ID.
PA_BUDGET_VERSIONS – joined on PLAN_VERSION_ID.
PA_PROJ_ELEMENTS – joined on PROJECT_ELEMENT_ID.
PA_RBS_ELEMENTS – joined on RBS_ELEMENT_ID.
PA_RBS_VERSIONS_B – joined on RBS_VERSION_ID.

These five relationships constitute the complete documented dependency set for this obsolete Project Intelligence extraction table.

Table: PJI_FM_EXTR_PLAN_LINES 12.2.2
owner:PJI, object_type:TABLE, fnd_design_data:PJI.PJI_FM_EXTR_PLAN_LINES, object_name:PJI_FM_EXTR_PLAN_LINES, status:VALID, product: PJI - Project Intelligence(Obsolete) , description: This table stores the changes to financial plan data , implementation_dba_data: PJI.PJI_FM_EXTR_PLAN_LINES ,
Table: PJI_FM_EXTR_PLAN_LINES 12.1.1
owner:PJI, object_type:TABLE, fnd_design_data:PJI.PJI_FM_EXTR_PLAN_LINES, object_name:PJI_FM_EXTR_PLAN_LINES, status:VALID, product: PJI - Project Intelligence , description: This table stores the changes to financial plan data , implementation_dba_data: PJI.PJI_FM_EXTR_PLAN_LINES ,
Table: PJI_FM_EXTR_PLAN_LINES_DEBUG 12.2.2
owner:PJI, object_type:TABLE, fnd_design_data:PJI.PJI_FM_EXTR_PLAN_LINES_DEBUG, object_name:PJI_FM_EXTR_PLAN_LINES_DEBUG, status:VALID, product: PJI - Project Intelligence(Obsolete) , description: This table stores the changes to financial plan data , implementation_dba_data: PJI.PJI_FM_EXTR_PLAN_LINES_DEBUG ,
Table: PJI_FM_EXTR_PLAN_LINES_DEBUG 12.1.1
owner:PJI, object_type:TABLE, fnd_design_data:PJI.PJI_FM_EXTR_PLAN_LINES_DEBUG, object_name:PJI_FM_EXTR_PLAN_LINES_DEBUG, status:VALID, product: PJI - Project Intelligence , description: This table stores the changes to financial plan data , implementation_dba_data: PJI.PJI_FM_EXTR_PLAN_LINES_DEBUG ,
VIEW: PJI.PJI_FM_EXTR_PLAN_LINES# 12.2.2
VIEW: PJI.PJI_FM_EXTR_PLAN_LINES_DEBUG# 12.2.2
VIEW: PJI.PJI_FM_EXTR_PLAN_LINES_DEBUG# 12.2.2
owner:PJI, object_type:VIEW, object_name:PJI_FM_EXTR_PLAN_LINES_DEBUG#, status:VALID,
VIEW: PJI.PJI_FM_EXTR_PLAN_LINES# 12.2.2
owner:PJI, object_type:VIEW, object_name:PJI_FM_EXTR_PLAN_LINES#, status:VALID,
TABLE: PJI.PJI_FM_EXTR_PLAN_LINES 12.1.1
owner:PJI, object_type:TABLE, fnd_design_data:PJI.PJI_FM_EXTR_PLAN_LINES, object_name:PJI_FM_EXTR_PLAN_LINES, status:VALID,
TABLE: PJI.PJI_FM_EXTR_PLAN_LINES_DEBUG 12.1.1
owner:PJI, object_type:TABLE, fnd_design_data:PJI.PJI_FM_EXTR_PLAN_LINES_DEBUG, object_name:PJI_FM_EXTR_PLAN_LINES_DEBUG, status:VALID,
TABLE: PJI.PJI_FM_EXTR_PLAN_LINES_DEBUG 12.2.2
owner:PJI, object_type:TABLE, fnd_design_data:PJI.PJI_FM_EXTR_PLAN_LINES_DEBUG, object_name:PJI_FM_EXTR_PLAN_LINES_DEBUG, status:VALID,
TABLE: PJI.PJI_FM_EXTR_PLAN_LINES 12.2.2
owner:PJI, object_type:TABLE, fnd_design_data:PJI.PJI_FM_EXTR_PLAN_LINES, object_name:PJI_FM_EXTR_PLAN_LINES, status:VALID,
APPS.PJI_FM_XBS_ACCUM_MAINT SQL Statements 12.1.1
APPS.PJI_FM_XBS_ACCUM_MAINT SQL Statements 12.2.2
APPS.PA_FP_PJI_INTG_PKG SQL Statements 12.1.1
APPS.PA_FP_PJI_INTG_PKG SQL Statements 12.2.2
APPS.PJI_FM_XBS_ACCUM_MAINT dependencies on PJI_FM_EXTR_PLAN_LINES 12.1.1
PACKAGE BODY: APPS.PA_FP_PJI_INTG_PKG 12.1.1
PACKAGE BODY: APPS.PA_FP_PJI_INTG_PKG 12.2.2
APPS.PJI_FM_XBS_ACCUM_MAINT dependencies on PJI_FM_EXTR_PLAN_LINES 12.2.2
PACKAGE BODY: APPS.PJI_FM_XBS_ACCUM_MAINT 12.1.1
PACKAGE BODY: APPS.PJI_FM_XBS_ACCUM_MAINT 12.2.2
eTRM - PJI Tables and Views 12.2.2
description: This is an temporary table that is used to store XBS denorm data by the Refresh/Update Project Performance Data. This is a global temporary table. ,
eTRM - PJI Tables and Views 12.1.1