Results for “rbs_element_id”

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

Overview

PJI_FP_CUST_PJP0 is a table owned by the PJI schema (Project Intelligence) in Oracle E-Business Suite, present and valid in both 12.1.1 and 12.2.2. Project Intelligence is the analytical and reporting layer that sits on top of Oracle Projects and Oracle Project Resource Management, and it provides the reporting structures consumed by Project Management reporting, Oracle Business Intelligence Applications, and custom project analytics. The PJI_FP_CUST_PJP0 table is a customer-extensible fact table used by the Project Intelligence fact programming infrastructure. The "FP" prefix denotes fact programming, "CUST" indicates customer/customization scope, and "PJP0" identifies the specific fact population program and its associated fact set. It is designed to hold derived, aggregated fact metrics organized along Project Intelligence reporting dimensions and supplemented by fifteen generic CUSTOMn columns for client-specific extensions.

The ETRM heuristic Data Vault classification for this object is standalone, indicating that the mined foreign-key structure does not resolve to a clean hub, link, or satellite pattern. This should be treated as a modeling suggestion rather than a definitive designation; the table functionally behaves as a fact/dimension hybrid rather than a canonical Data Vault construct.

Key Information Stored

The documented physical schema carries 33 columns. The most significant include:

• WORKER_ID – identifies the project resource or worker associated with the fact record.
• PROJECT_ID, PROJECT_ORG_ID, PROJECT_ORGANIZATION_ID, PROJECT_ELEMENT_ID – project and project element business context.
• TIME_ID – the time dimension key for period-based fact accumulation.
• PERIOD_TYPE_ID, CALENDAR_TYPE – the reporting calendar and period granularity.
• RBS_ELEMENT_ID, RBS_VERSION_ID – foreign keys into the Resource Breakdown Structure (see Related Objects).
• RBS_AGGR_LEVEL, WBS_ROLLUP_FLAG, PRG_ROLLUP_FLAG – control flags governing aggregation and roll-up behavior.
• PLAN_VERSION_ID, PLAN_TYPE_ID – plan context for budgeting/forecasting facts.
• CURRENCY_CODE – the transactional/functional currency for monetary facts.
• CUSTOM1 through CUSTOM15 – fifteen client-defined extension columns.
• TXN_ACCUM_HEADER_ID – link to the accumulation header driving the fact population.

No surrogate primary-key column is documented in the metadata; WORKER_ID and TXN_ACCUM_HEADER_ID are the strongest candidates for composite business-key uniqueness, but this should be verified against the actual unique indexes at the site.

Common Use Cases and Queries

Typical scenarios include custom Project Intelligence fact reporting, resource utilization and cost roll-ups, plan-versus-actual analysis, and extensions that surface CUSTOMn columns in BI Publisher layouts. A representative query joining the RBS dependencies is:

• SELECT f.WORKER_ID, f.PROJECT_ID, f.TIME_ID, f.CURRENCY_CODE, f.CUSTOM1, e.RBS_ELEMENT_NAME FROM PJI.PJI_FP_CUST_PJP0 f JOIN PA.PA_RBS_ELEMENTS e ON f.RBS_ELEMENT_ID = e.RBS_ELEMENT_ID JOIN PA.PA_RBS_VERSIONS_B v ON f.RBS_VERSION_ID = v.RBS_VERSION_ID;
• Aggregation queries grouped by PROJECT_ID, TIME_ID, CALENDAR_TYPE to produce period roll-ups.
• Filtering on WBS_ROLLUP_FLAG or PRG_ROLLUP_FLAG to isolate detail versus rolled-up facts.

Related Objects

The documented foreign-key relationships identify the following dependencies:

• PA.PA_RBS_ELEMENTS – joined on RBS_ELEMENT_ID.
• PA.PA_RBS_VERSIONS_B – joined on RBS_VERSION_ID.
• PA.PA_PROJECTS_ALL / PA_PROJECT_ELEMENTS – join on PROJECT_ID, PROJECT_ELEMENT_ID.
• PJI period and calendar dimension tables – join on TIME_ID, PERIOD_TYPE_ID, CALENDAR_TYPE.
• PJI fact population programs – the PL/SQL programs that populate PJI_FP_CUST_PJP0 from Oracle Projects transactional data.

Because the Data Vault classification is standalone, no additional undocumented FK relationships should be assumed without verification.