Search Results pa_rbs_versions_b

Overview

The PA_RBS_VERSIONS_B table is a core data repository within the Oracle E-Business Suite Projects (PA) module, specifically for versions 12.1.1 and 12.2.2. It serves as the primary storage entity for version-specific information of a Resource Breakdown Structure (RBS). An RBS is a hierarchical framework used to categorize and organize project resources, facilitating planning, budgeting, and reporting. As an RBS evolves over time, multiple versions can be created and maintained. This table stores the distinct metadata for each of these versions, enabling historical tracking, auditability, and the application of different RBS structures to projects based on specific timeframes or requirements. Its central role is to act as the master definition point for each RBS version, which is then referenced by numerous other transactional and setup tables across the Projects and Project Intelligence modules.

Key Information Stored

While the provided metadata does not list all columns, the primary and foreign keys define the essential data relationships. The central column is RBS_VERSION_ID, which is the unique primary key identifier for each RBS version record. The RBS_HEADER_ID is a critical foreign key that links the version to its parent definition in the PA_RBS_HEADERS_B table, establishing which overall RBS the version belongs to. Another significant foreign key is JOB_GROUP_ID, which links to the PER_JOB_GROUPS table, associating the RBS version with a specific job or labor cost grouping for costing purposes. Additional columns, not detailed in the excerpt but typical for such tables, would include version number, effective dates, system status (e.g., 'DRAFT', 'ACTIVE'), and creation/update audit information.

Common Use Cases and Queries

Common operational and reporting scenarios involve querying this table to understand the RBS landscape. A frequent use case is identifying all active RBS versions for a given RBS header to determine which structure is currently in use for project planning. Another is auditing the version history of an RBS. Sample SQL patterns often involve joins to the header and translation tables. For instance, to retrieve active versions with their names, a query might join PA_RBS_VERSIONS_B to PA_RBS_VERSIONS_TL on RBS_VERSION_ID and to PA_RBS_HEADERS_B on RBS_HEADER_ID, filtering by the version's effective date and status. Reporting use cases include analyzing RBS version adoption across projects or validating setup before running critical processes like financial plan generation, which relies on the RBS_VERSION_ID specified in PA_PROJ_FP_OPTIONS.

Related Objects

As indicated by the extensive foreign key relationships, PA_RBS_VERSIONS_B is a pivotal hub in the RBS data model. Key related objects include:

• PA_RBS_HEADERS_B: Parent table joined via RBS_HEADER_ID.
• PA_RBS_VERSIONS_TL: Provides translated descriptive information for the version.
• PA_RBS_ELEMENTS: Stores the individual nodes of the hierarchy for a specific RBS version.
• PA_RBS_DENORM and PJI_RBS_DENORM: Denormalized structures for performance, joined via STRUCT_VERSION_ID.
• PA_PROJ_FP_OPTIONS: Links financial plan options for a project to a specific RBS version.
• PA_RBS_PRJ_ASSIGNMENTS: Records which projects are assigned to use a given RBS version.
• PJI_PJP_RBS_HEADER and PJI_ROLLUP_LEVEL_STATUS: Project Intelligence (PJI) tables that utilize the RBS version for analytics and summarization.

These relationships underscore the table's integral role in connecting RBS definitions to project execution, planning, and reporting functions.