Results for “pa_rbs_versions_pub”

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

Overview

PA_RBS_VERSIONS_PUB is a public PL/SQL API package in the Oracle EBS Applications (APPS) schema that manages the lifecycle of Resource Breakdown Structure (RBS) versions within Oracle Project Resource Management / Project Management. An RBS defines the hierarchical classification of project resources (for example, by organization, job, or competency), and each RBS can exist in one or more versions representing successive structural revisions. This package exposes the version-management operations to the rest of the application, providing controlled create, update, freeze, and delete capabilities so that callers do not manipulate the underlying base tables directly. Consistent with Oracle's API classification convention, the PUB suffix identifies it as a public, supported interface intended for external invocation, whereas private packages retain the internal implementation and validation logic.

Key Procedures and Functions

The documented interface comprises four procedures, each governing one stage of the version lifecycle:

• CREATE_WORKING_VERSION — Creates a new, editable version of an RBS by copying or deriving from an existing structure. New versions begin in a working (draft) state, allowing structural changes to be staged before they affect operational resource assignment.
• UPDATE_WORKING_VERSION — Modifies the contents of an existing working version, such as adding, removing, or restructuring RBS elements. Because the version has not been frozen, changes remain isolated from assignments that reference prior versions.
• FREEZE_WORKING_VERSION — Promotes a working version to a frozen, active state. Once frozen, the version becomes the authoritative structure available for use in resource assignment and planning, and is expected to be treated as read-only.
• DELETE_WORKING_VERSION — Removes a working version that is no longer required, providing cleanup of draft structures before they are frozen.

The package depends on FND_API, indicating that it follows the standard Oracle Application Object Library API pattern for message handling, error reporting, and transactional consistency. Parameter lists are not reproduced here; signatures should be verified against the ETRM-documented interface in the target instance.

Tables Accessed

Via APPS synonyms, the package operates across the following tables:

• PA_RBS_HEADERS_B / PA_RBS_HEADERS_TL — Base and translated header records identifying each RBS definition.
• PA_RBS_VERSIONS_B — The version entity itself, holding version identifiers and status used to distinguish working from frozen versions.
• PA_RBS_ELEMENTS / PA_RBS_ELEMENTS_S / PA_RBS_ELEMENTS_TEMP — RBS element definitions, their translation records, and temporary staging rows used during creation and update processing.
• PA_RBS_ELEMENT_IDENTIFIER_S — Identifier sequences for elements.
• PA_RBS_PRJ_ASSIGNMENTS — Associations between RBS versions and projects; freeze and delete operations must respect these assignments to preserve referential integrity for in-flight project resource structures.

Usage Notes

PA_RBS_VERSIONS_PUB is invoked programmatically rather than through direct table maintenance. Typical callers include the RBS setup and maintenance forms in Oracle Projects, concurrent programs that process version changes, and custom extensions that integrate resource structures with external planning or HR systems. The package is also referenced by PA_RBS_PUB, which uses it as part of the broader RBS public API surface. Custom code should always call this package instead of performing DML on the PA_RBS_* tables, so that validation, message propagation through FND_API, and version integrity rules are enforced. Callers should commit or roll back explicitly according to their transaction boundaries, and should sequence operations as create, update, freeze, and (only while unfrozen) delete. Available in Oracle EBS 12.1.1 and 12.2.2 with the documented status VALID.