Search Results pji_pjp_rbs_header




Overview
Explore in AI Chat

Overview

The PJI_PJP_RBS_HEADER table is a core data object within the Project Intelligence (PJI) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as a central junction table that maintains the critical associations between a project, a specific financial plan (budget or forecast version), and a Resource Breakdown Structure (RBS) version. This linkage is fundamental to the PJI module's analytical and reporting capabilities, enabling the aggregation and analysis of project financial and resource data according to the hierarchical structure defined in the RBS. By storing these relationships, the table provides the necessary metadata for accurate performance measurement, earned value analysis, and resource planning across the project portfolio.

Key Information Stored

The table's primary function is to store foreign key references that define the association. While the full column list is not detailed in the provided metadata, the documented foreign key relationships explicitly identify the key columns. The central columns are PROJECT_ID, which references the specific project in PA_PROJECTS_ALL; PLAN_VERSION_ID, which references the budget or forecast version in PA_BUDGET_VERSIONS; and RBS_VERSION_ID, which references the specific version of the Resource Breakdown Structure in PA_RBS_VERSIONS_B. The table likely includes additional control columns such as a primary key (potentially a combination of these IDs or a surrogate key), creation dates, and last update information to manage the lifecycle of these associations.

Common Use Cases and Queries

This table is primarily queried in scenarios requiring an understanding of which RBS is applied to a project's financial plans for analytical purposes. A common use case is validating or reporting on the RBS setup for projects during period-end closing or audit reviews. For instance, to list all active project and plan associations with their corresponding RBS, a query would join the related master tables. Sample SQL to retrieve this foundational information would be:

  • SELECT p.segment1 project_number, bv.version_name plan_name, rbsv.name rbs_version_name
  • FROM pji_pjp_rbs_header hdr,
  • pa_projects_all p,
  • pa_budget_versions bv,
  • pa_rbs_versions_b rbsv
  • WHERE hdr.project_id = p.project_id
  • AND hdr.plan_version_id = bv.budget_version_id
  • AND hdr.rbs_version_id = rbsv.rbs_version_id;

This data is essential for downstream PJI summarization processes that roll up project costs, revenue, and quantities by the RBS hierarchy.

Related Objects

As defined by its foreign keys, PJI_PJP_RBS_HEADER has direct dependencies on three key tables from the Project Accounting (PA) module. These relationships are:

  • PA_PROJECTS_ALL: Joined via PJI_PJP_RBS_HEADER.PROJECT_ID = PA_PROJECTS_ALL.PROJECT_ID. This links the association to a specific project.
  • PA_BUDGET_VERSIONS: Joined via PJI_PJP_RBS_HEADER.PLAN_VERSION_ID = PA_BUDGET_VERSIONS.BUDGET_VERSION_ID. This links the association to a specific budget or forecast plan version.
  • PA_RBS_VERSIONS_B: Joined via PJI_PJP_RBS_HEADER.RBS_VERSION_ID = PA_RBS_VERSIONS_B.RBS_VERSION_ID. This links the association to a specific version of the Resource Breakdown Structure.

This table is a prerequisite for the PJI summarization engine and is referenced by various PJI reporting views and online analytical processing (OLAP) cubes that provide project intelligence metrics.