Results for “prog_rep_usage_flag”

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

Overview

The PJI_PJP_RBS_HEADER table is a Project Intelligence (PJI) repository object in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the association between a project, a plan (budget or forecast version), and a Resource Breakdown Structure (RBS) version. In effect, it defines which RBS structure is used when resources are aggregated and reported for a given plan within a given project, and it also controls the purpose or usage context of that association through a set of usage flags. This table therefore acts as the linkage that allows Project Intelligence to resolve project-plan resource hierarchies consistently for reporting and analysis.

From a modeling perspective, the ETRM metadata classifies this object heuristically as a link table in Data Vault terms. This is consistent with its structure: it holds no descriptive master data of its own but rather resolves many-to-many-style relationships between PA_PROJECTS_ALL, PA_BUDGET_VERSIONS, and PA_RBS_VERSIONS_B. The grain of the row is one association of (PROJECT_ID, PLAN_VERSION_ID, RBS_VERSION_ID).

Key Information Stored

The table contains twelve documented columns. The most significant are the following:

• PROJECT_ID — foreign key to PA_PROJECTS_ALL, identifying the project to which the RBS association applies.
• PLAN_VERSION_ID — foreign key to PA_BUDGET_VERSIONS, identifying the specific plan or budget version.
• RBS_VERSION_ID — foreign key to PA_RBS_VERSIONS_B, identifying the resource breakdown structure version assigned to the plan.
• PLAN_TYPE_CODE — indicates the category of the plan (for example budget versus forecast) to which the RBS association belongs.
• REPORTING_USAGE_FLAG — signals whether this RBS version is used for reporting purposes.
• PROG_REP_USAGE_FLAG — signals whether the RBS version is used in program-level reporting.
• PLAN_USAGE_FLAG — signals whether the RBS version is used in plan processing.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard Oracle EBS audit columns recording who created and last modified each row and when.

No dedicated surrogate primary key column is documented among the twelve columns; the row is identified by the combination of PROJECT_ID, PLAN_VERSION_ID, and RBS_VERSION_ID, which functions as the business-key candidate for this link. Any uniqueness index documented for the table would be expected to cover this combination. Because the table is a pure association object, its columns are almost entirely identifiers, flags, and audit attributes.

Common Use Cases and Queries

Typical uses include determining which RBS version is active for a project-plan combination, verifying the usage context of an RBS through its flags, and joining project and plan data to resource hierarchies for Project Intelligence reporting. A representative query resolving the RBS for a plan is:

• Join PJI_PJP_RBS_HEADER to PA_PROJECTS_ALL on PROJECT_ID, to PA_BUDGET_VERSIONS on PLAN_VERSION_ID, and to PA_RBS_VERSIONS_B on RBS_VERSION_ID to return the project name, plan name, and RBS version detail for reporting.
• Filter by PLAN_TYPE_CODE to isolate budget versus forecast associations.
• Filter by REPORTING_USAGE_FLAG = 'Y' to retrieve only RBS versions designated for reporting, supporting program-level and project-level analysis.
• Use PROG_REP_USAGE_FLAG and PLAN_USAGE_FLAG to distinguish reporting RBS assignments from planning RBS assignments in custom extracts.

Because the table is narrow and link-oriented, it is well suited to being embedded in an analytic view or a reporting data model where the RBS dimension is joined to fact tables such as project cost or budget facts.

Related Objects

The table sits at the intersection of project, plan, and RBS structures, and its principal dependencies are the three foreign key targets:

• PA_PROJECTS_ALL — joined on PJI_PJP_RBS_HEADER.PROJECT_ID, supplying project master information.
• PA_BUDGET_VERSIONS — joined on PJI_PJP_RBS_HEADER.PLAN_VERSION_ID, supplying plan and budget version detail.
• PA_RBS_VERSIONS_B — joined on PJI_PJP_RBS_HEADER.RBS_VERSION_ID, supplying the resource breakdown structure version.

Derived from these, PA_RBS_VERSIONS_TL, the PA_RBS structures used for resource rollup reporting, and the Project Intelligence reporting views that consume PJI_PJP_RBS_HEADER to resolve resource hierarchies, are the most significant additional objects that reference or depend on this table. Together these objects form the project-plan-RBS chain that Project Intelligence relies upon.