Results for “validated_flag”

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

Overview

PA_RBS_VERSIONS_B is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores version-specific information for a Resource Breakdown Structure (RBS). The RBS is the hierarchical framework through which a project's resources — people, organizations, and roles — are organized for planning, budgeting, and cost rollup. Because RBS definitions are maintained over time through multiple versions, this table represents the header-level record of each distinct RBS version, capturing when it applies and how it is classified. It is the anchor point for downstream RBS elements, assignments, and reporting accumulators.

From a dimensional modeling perspective, the metadata's heuristic classification is hub-leaning. This suggests treating PA_RBS_VERSIONS_B as a hub entity in a Data Vault construct, with RBS_VERSION_ID as the durable business key and the surrounding foreign-key tables acting as links and satellites. Note that this is a modeling suggestion, not an enforced design; the physical implementation remains a standard normalized transactional table.

Key Information Stored

The primary key is PRB_PK, which maps to the RBS_VERSION_ID column. A unique index, PA_RBS_VERSIONS_B_U1, exists on RBS_VERSION_ID, making it the principal business-key candidate. The table contains 18 documented columns, of which the following are the most important:

• RBS_VERSION_ID — Surrogate primary key and unique business key; referenced by nearly all dependent RBS tables.
• VERSION_NUMBER — Sequential identifier of the version within the parent RBS header.
• RBS_HEADER_ID — Foreign key to PA_RBS_HEADERS_B, tying the version to its owning RBS definition.
• VERSION_START_DATE and VERSION_END_DATE — Effective-dating range that governs when the version is active.
• JOB_GROUP_ID — Foreign key to PER_JOB_GROUPS, indicating the job group this RBS version is associated with.
• RULE_BASED_FLAG — Indicates whether the RBS version is maintained through rules rather than direct assignment.
• VALIDATED_FLAG — Tracks whether the version has passed validation.
• STATUS_CODE — Lifecycle status of the version (e.g., draft, active).
• CURRENT_REPORTING_FLAG — Identifies the version used for current reporting and rollup.
• RESOURCE_CLASS_FLAG — Distinguishes resource-class-based structuring within the version.
• OLAP_ELEMENT_ID — Links the version to an OLAP element used for analytic aggregation.
• RECORD_VERSION_NUMBER — Optimistic locking and change-tracking column.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard EBS audit columns.

Common Use Cases and Queries

The table is central to RBS-driven planning, budgeting, and resource rollup reporting. A typical query retrieves all versions for a given RBS header with their effective dates:

SELECT rbs_version_id, version_number, version_start_date, version_end_date, status_code
FROM pa_rbs_versions_b
WHERE rbs_header_id = :p_header_id
ORDER BY version_number;

To find the currently reporting version for a header:

SELECT rbs_version_id
FROM pa_rbs_versions_b
WHERE rbs_header_id = :p_header_id
AND current_reporting_flag = 'Y';

Common reporting scenarios include reconstructing RBS element hierarchies per version via PA_RBS_ELEMENTS, auditing version effective-date ranges for planning calendar alignment, and joining to PJI rollup and denormalized tables for project performance reporting.

Related Objects

The strongest relationships are defined by foreign keys:

• PA_RBS_HEADERS_B — joined on RBS_HEADER_ID; the parent RBS definition.
• PER_JOB_GROUPS — joined on JOB_GROUP_ID; supplies job group context.
• PA_RBS_ELEMENTS — joined on RBS_VERSION_ID; holds the version's structural elements.
• PA_RBS_PRJ_ASSIGNMENTS — joined on RBS_VERSION_ID; maps versions to projects.
• PA_RBS_VERSIONS_TL — joined on RBS_VERSION_ID; translation (language) records.
• PA_RBS_DENORM and PA_RBS_TXN_ACCUM_MAP — joined on STRUCT_VERSION_ID; denormalized and accumulator mappings.
• PA_PROJ_FP_OPTIONS — joined on RBS_VERSION_ID; forecasting/planning options.
• PJI_PJP_RBS_HEADER and PJI_ROLLUP_LEVEL_STATUS — joined on RBS_VERSION_ID; project performance rollup metadata.