Results for “curr_record_type_id”

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

Overview

PJI_ROLLUP_LEVEL_STATUS is a Project Intelligence (PJI) table in the Oracle E-Business Suite that tracks the creation status of resource rollup slices generated against the Resource Breakdown Structure (RBS). Its purpose is to record, for a given project and plan, whether the RBS-based resource rollup slices have been created. In ETRM 12.1.1 and 12.2.2 the table is owned by the PJI schema and is reported as VALID. PJI is the analytical reporting layer for Oracle Projects, and this table acts as a control and audit checkpoint for the rollup processes that populate project resource analytics.

The documented physical schema contains 15 columns. Because the table exists primarily to relate a project, a plan version, and an RBS version while recording status flags against those relationships, a Data Vault modeling heuristic classifies it as a link. This is a suggestion rather than a delivered constraint: the object carries both foreign-key relationships and descriptive status attributes, so a satellite pattern would typically be layered on top of the link to hold the changing flags.

Key Information Stored

The most significant columns describe the key context of each rollup status record and the flags that indicate rollup completion.

• PROJECT_ID – identifies the project; foreign key to PA_PROJECTS_ALL. This is the primary business context for the record.
• PLAN_VERSION_ID – identifies the plan (budget) version; foreign key to PA_BUDGET_VERSIONS.
• RBS_VERSION_ID – identifies the Resource Breakdown Structure version; foreign key to PA_RBS_VERSIONS_B.
• PLAN_TYPE_CODE – distinguishes the plan category (for example budget versus forecast) associated with the rollup record.
• WBS_ELEMENT_ID – the work breakdown structure element against which the rollup entry applies.
• RBS_AGGR_LEVEL – the aggregation level within the RBS at which the slice was created.
• WBS_ROLLUP_FLAG – indicates whether the WBS-level rollup slice has been created.
• PRG_ROLLUP_FLAG – indicates whether the program-level rollup slice has been created.
• CURR_RECORD_TYPE_ID – classifies the record type of the current status entry.
• CALENDAR_TYPE – the calendar context used for the rollup period.

The remaining documented columns are standard Oracle audit attributes: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN. No explicit surrogate primary key or unique index is documented in the supplied metadata; the concatenation of PROJECT_ID, PLAN_VERSION_ID, RBS_VERSION_ID, and the WBS-related columns functions as the effective business key for a status row.

Common Use Cases and Queries

Administrators and developers query this table to determine whether resource rollup slices are complete before running PJI-based resource reports. Typical scenarios include troubleshooting missing resource analytics, validating that a rebuild of RBS rollups completed for every plan version, and auditing status by project.

A representative query joins the foreign-key targets to resolve business identifiers:

• SELECT prs.project_id, prs.plan_version_id, prs.rbs_version_id, prs.wbs_rollup_flag, prs.prg_rollup_flag FROM pji_rollup_level_status prs WHERE prs.project_id = :project_id
• Join 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 obtain project number, plan name, and RBS version name.
• Filter on WBS_ROLLUP_FLAG or PRG_ROLLUP_FLAG equal to a not-created value to isolate projects whose rollup slices still require generation.

Related Objects

The table is anchored to three documented foreign-key parents, and reporting typically fans out to their associated views and APIs.

• PA_PROJECTS_ALL – joined via PJI_ROLLUP_LEVEL_STATUS.PROJECT_ID; supplies project definition and organization context.
• PA_BUDGET_VERSIONS – joined via PJI_ROLLUP_LEVEL_STATUS.PLAN_VERSION_ID; supplies plan version and plan type detail.
• PA_RBS_VERSIONS_B – joined via PJI_ROLLUP_LEVEL_STATUS.RBS_VERSION_ID; supplies the RBS version definition.
• PA_PROJECTS_VL / PA_PROJECTS_TL – commonly used alongside PA_PROJECTS_ALL to resolve translatable project names.
• PA_RBS_VERSIONS_TL – used to resolve the descriptive name of the RBS version referenced here.

Because PJI rollup status is consumed by the Project Intelligence reporting layer, other PJI fact and staging objects that depend on resource rollups may reference this table indirectly through the Project and RBS dimensions rather than by direct foreign key.