Results for “prg_level”

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

Overview

The PJI_FP_AGGR_PJP1_T table resides in the PJI schema and belongs to the Project Intelligence product family (PJI), which Oracle classifies as obsolete in release 12.1.1 and 12.2.2. Per the ETRM documentation, the table is described as "a mirror of PJI_FP_XBS_ACCUM_FROM used during summarization." This indicates the table serves as an intermediate or staging structure populated by the Project Intelligence summarization engine, which aggregates cost, revenue, commitment, and forecast data from Project Accounting and related subledgers into a form suitable for project performance reporting and analysis.

The object contains 79 documented columns and references PA_RBS_ELEMENTS via RBS_ELEMENT_ID and PA_RBS_VERSIONS_B via RBS_VERSION_ID, meaning the summarization process operates at the resource breakdown structure (RBS) level and is version aware. Because the table has no documented primary key and the FK mining classified it as standalone, a Data Vault modeling suggestion would treat it as a satellite-like or staging object rather than a true hub or link. Practitioners should recognize that Project Intelligence is a legacy component; Oracle's strategic replacement is the Oracle Project Portfolio Management (PPM) analytics stack and its associated data model.

Key Information Stored

The table's most important columns fall into several functional groups:

• Work unit and level: WORKER_ID, RECORD_TYPE, PRG_LEVEL, CURR_RECORD_TYPE_ID, LINE_TYPE, and PLAN_TYPE_CODE identify the aggregation context and the worker process that produced each summarization row.
• Project and RBS dimensions: PROJECT_ID, PROJECT_ORG_ID, PROJECT_ORGANIZATION_ID, PROJECT_ELEMENT_ID, RBS_ELEMENT_ID, RBS_VERSION_ID, PLAN_VERSION_ID, and PLAN_TYPE_ID define the project, organization, resource, and plan context. The columns RBS_ELEMENT_ID and RBS_VERSION_ID carry the documented foreign keys.
• Time and calendar dimensions: TIME_ID, PERIOD_TYPE_ID, CALENDAR_TYPE, START_DATE, and END_DATE specify the reporting period.
• Currency and rollup flags: CURRENCY_CODE, RBS_AGGR_LEVEL, WBS_ROLLUP_FLAG, and PRG_ROLLUP_FLAG.
• Financial measures: RAW_COST, BRDN_COST, REVENUE, BILL_RAW_COST, BILL_BRDN_COST, and the labor and equipment variants such as LABOR_RAW_COST, LABOR_BRDN_COST, EQUIPMENT_RAW_COST, and BILL_LABOR_HRS.
• Commitment measures: SUP_INV_COMMITTED_COST, PO_COMMITTED_COST, PR_COMMITTED_COST, and OTH_COMMITTED_COST.
• Actual versus estimate-to-complete: ACT_RAW_COST, ACT_BRDN_COST, ACT_REVENUE, ETC_RAW_COST, and ETC_BRDN_COST.
• Descriptive and qualifier columns: CUSTOM1 through CUSTOM15, RATE_DANGLING_FLAG, and TIME_DANGLING_FLAG, the latter two flagging rows whose rates or time dimensions did not resolve cleanly during summarization.

No surrogate primary key or unique business key index is documented, so the combination of worker, project, RBS, plan, and time columns behaves as the de facto grain.

Common Use Cases and Queries

Typical usage focuses on reconstructing aggregated project cost and revenue views. Analysts can filter on RECORD_TYPE, PROJECT_ID, and TIME_ID to isolate periods, then aggregate ACT_BRDN_COST and ETC_BRDN_COST to assess cost performance. A simple pattern:

• Select PROJECT_ID, RBS_ELEMENT_ID, and TIME_ID with summed RAW_COST, BRDN_COST, and REVENUE grouped by project and period.
• Join to PA_RBS_ELEMENTS on RBS_ELEMENT_ID to obtain resource names, and to PA_RBS_VERSIONS_B on RBS_VERSION_ID to resolve the version in force.
• Compare ACT_LABOR_HRS and ETC_LABOR_HRS to detect effort overruns, and inspect RATE_DANGLING_FLAG or TIME_DANGLING_FLAG to identify rows requiring correction before downstream reporting.
• Query the CUSTOM1–CUSTOM15 columns to surface descriptive attributes configured for the PJI summarization process.

Related Objects

• PJI_FP_XBS_ACCUM_FROM — the source table from which this table is mirrored during summarization.
• PA_RBS_ELEMENTS — joined on RBS_ELEMENT_ID, supplying resource breakdown structure element definitions.
• PA_RBS_VERSIONS_B — joined on RBS_VERSION_ID, supplying the RBS version context.
• PA_PROJECTS_ALL — joined on PROJECT_ID for project attributes and naming.
• PA_PROJECT_ELEMENTS — joined on PROJECT_ELEMENT_ID for WBS/work breakdown context.
• PA_PERIODS_ALL / period tables — joined on TIME_ID for calendar alignment.
• Oracle Project Intelligence reporting views and concurrent programs that consume this staging table during summarization runs.

Because PJI is obsolete, dependencies in this area should be reviewed carefully before any upgrade or reimplementation involving release 12.1.1 or 12.2.2.