Search Results pji_rollup_level_status




Overview
Explore in AI Chat

Overview

The table PJI_ROLLUP_LEVEL_STATUS is a supporting data object within the Project Intelligence (PJI) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. Its primary function is to track the processing state of resource rollup slices, which are aggregations of project financial and resource data organized according to a Resource Breakdown Structure (RBS). This table acts as a status registry, indicating whether the necessary rollup data slices for a specific project, budget plan version, and RBS version have been successfully created and are available for consumption by the PJI summarization engine and subsequent reporting. Its existence is critical for ensuring data integrity and completeness in the complex, multi-dimensional aggregation processes that underpin Project Intelligence analytics.

Key Information Stored

While the provided ETRM metadata does not list specific columns beyond the foreign key columns, the table's description and foreign key relationships define its core data model. It stores status flags linked to a unique combination of three key entities: a Project, a Budget Plan Version, and an RBS Version. The central piece of information is a status indicator (likely a column such as `ROLLUP_STATUS` or `CREATION_STATUS`) that signifies if the rollup slices are "CREATED" or not. The foreign key columns are `PROJECT_ID` (linking to `PA_PROJECTS_ALL`), `PLAN_VERSION_ID` (linking to `PA_BUDGET_VERSIONS`), and `RBS_VERSION_ID` (linking to `PA_RBS_VERSIONS_B`). This structure allows the system to query, for any given project-plan-RBS combination, whether the aggregated data is ready for reporting.

Common Use Cases and Queries

A primary use case is monitoring the health and progress of the PJI summarization process. Administrators or batch programs can query this table to identify projects or plans for which rollup data generation has failed or is pending, enabling targeted re-processing. A typical diagnostic query would join to the related master tables to get meaningful names. For example:

SELECT p.segment1 project_number, bv.version_name, rbsv.name rbs_version_name, prls.status
FROM pji_rollup_level_status prls,
    pa_projects_all p,
    pa_budget_versions bv,
    pa_rbs_versions_b rbsv
WHERE prls.project_id = p.project_id
AND prls.plan_version_id = bv.budget_version_id
AND prls.rbs_version_id = rbsv.rbs_version_id
AND prls.status != 'CREATED';

This table is also integral to the internal logic of PJI's refresh and incremental update mechanisms, which check this status before attempting to utilize rolled-up data for further summarization to higher reporting levels.

Related Objects

As documented in the foreign key relationships, PJI_ROLLUP_LEVEL_STATUS has direct dependencies on three core Project Foundation tables:

  • PA_PROJECTS_ALL: Joined via the `PROJECT_ID` column. This links the status record to a specific project.
  • PA_RBS_VERSIONS_B: Joined via the `RBS_VERSION_ID` column. This links the status to the specific version of the Resource Breakdown Structure used for the rollup.
  • PA_BUDGET_VERSIONS: Joined via the `PLAN_VERSION_ID` column. This links the status to the specific budget plan version for which the resource data is rolled up.

This table is a child table to these master entities and is fundamentally part of the PJI summarization architecture, feeding into the larger PJI reporting tables (PJI_* facts and dimensions).