Search Results pji_rbs_denorm




Overview

The PJI_RBS_DENORM table is a core data repository within the Oracle E-Business Suite Project Intelligence (PJI) module, which is now designated as obsolete. Its primary function is to store denormalized or "flattened" Resource Breakdown Structure (RBS) information. In project management, an RBS defines a hierarchical framework for categorizing and organizing resources (people, equipment, materials) required for project execution. This table transforms the normalized, parent-child relationships of the standard RBS into a denormalized format optimized for analytical reporting and performance summarization within the Project Intelligence dashboards and data warehouse.

Key Information Stored

While specific column details are not fully enumerated in the provided metadata, the table's structure is defined by its foreign key relationships. It centrally stores the linkage between a Resource Breakdown Structure version and its constituent elements in a denormalized hierarchy. Key columns logically include STRUCT_VERSION_ID, which links to a specific RBS version (PA_RBS_VERSIONS_B), and the paired columns SUB_ID and SUP_ID. These represent the hierarchical relationship between a subordinate (child) RBS element and its superior (parent) RBS element, both linking to the PA_RBS_ELEMENTS table. Additional columns typically found in such denormalized tables include hierarchy levels, element names, and potentially rollup flags to facilitate efficient aggregation of project financial and resource metrics across the RBS.

Common Use Cases and Queries

This table is primarily accessed by the PJI reporting engine to support resource-centric analytics. Common use cases include generating reports on resource utilization, capacity planning, and cost aggregation rolled up by RBS nodes. A typical query pattern involves joining this table to project fact tables (like PJI_PROJ_RES_F or PJI_ACT_RES_F) to slice performance data by the resource hierarchy. For example, to find all project resources under a specific RBS parent element, a query would join on SUB_ID to the fact table's resource identifier and filter on the SUP_ID. Its denormalized nature allows for simpler, more performant SQL without recursive queries, which is critical for the complex aggregations in OLAP-style reporting.

Related Objects

The PJI_RBS_DENORM table has documented foreign key relationships with two foundational tables from the Project Foundation (PA) module:

  • PA_RBS_VERSIONS_B: Joined via PJI_RBS_DENORM.STRUCT_VERSION_ID. This links the denormalized data to a specific, versioned instance of a Resource Breakdown Structure.
  • PA_RBS_ELEMENTS: Joined via two separate foreign keys. PJI_RBS_DENORM.SUB_ID links to the child RBS element, and PJI_RBS_DENORM.SUP_ID links to the parent RBS element. This dual relationship encapsulates the hierarchical rollup path stored in the table.
As a component of the obsolete PJI module, this table is part of a legacy data warehouse schema. Its data is populated via ETL processes from the source PA_RBS* tables and is consumed by other PJI summary and fact tables for reporting purposes.