Search Results get_org_structure_version_id

Overview

APPS.PQH_RST_BUS is an Oracle E-Business Suite PL/SQL business logic package residing in the APPS schema, associated with the Public Sector/HR (PQH) module family and organized around rule sets and organizational structures. In Oracle EBS 12.1.1 and 12.2.2, the package serves as a centralized container for validation and retrieval logic that supports the maintenance of rule set and organization structure data. Its header identifies it as an internally-used development package, and it is classified under the ETRM "OTHER" API category rather than as a public, supported PL/SQL API. The package combines low-level validation routines that are invoked as part of standard insert, update, and delete processing with a small number of retrieval utilities, such as the determination of the legislation code for a given rule set and the resolution of an organization structure version identifier from an organization structure identifier. The presence of both "business rule" validation procedures and reference lookups indicates that the package acts as a supporting layer behind the forms and processes that manage PQH rule set and structure configuration rather than as an end-user-facing entry point.

Key Procedures and Functions

The ETRM metadata documents five procedures and functions within APPS.PQH_RST_BUS:

• RETURN_LEGISLATION_CODE — A function that returns the business group legislation code associated with a specific rule set primary key. The rule set identified by the supplied rule set identifier must already exist; if the value is not found, an error is raised.
• GET_ORG_STRUCTURE_VERSION_ID — A procedure declared for invocation from forms. It accepts an organization structure identifier and returns the corresponding organization structure version identifier through an output parameter.
• INSERT_VALIDATE — A procedure that controls the execution of all insert business rule validations. It is described as a private procedure called from the insert ("ins") procedure and operates against a PL/SQL record structure.
• UPDATE_VALIDATE — The counterpart validation controller for update processing, executing the business rules applicable when existing records are modified.
• DELETE_VALIDATE — The counterpart validation controller for delete processing, executing the business rules applicable when records are removed.

The validation procedures follow a consistent pattern: on success, processing continues uninterrupted; on failure, errors are only surfaced if explicitly coded within the validation routine. This design places responsibility for error handling with the implementing developer.

Tables Accessed

The package reads and writes against the following tables via APPS synonyms:

• PQH_RULE_SETS and PQH_RULE_SETS_TL — the base and translated rule set tables, used by RETURN_LEGISLATION_CODE to resolve legislation information for a rule set.
• PER_ORGANIZATION_STRUCTURES, PER_ORG_STRUCTURE_VERSIONS, and PER_ORG_STRUCTURE_ELEMENTS — the organization structure definition, version, and element tables, used by GET_ORG_STRUCTURE_VERSION_ID and by the validation routines that enforce structural integrity.
• HR_ALL_ORGANIZATION_UNITS — the organization unit definition table, supporting organization-related validations and lookups.
• DUAL — used for single-row expression evaluation within the package logic.

Usage Notes

APPS.PQH_RST_BUS is typically invoked indirectly rather than directly. The validation procedures (INSERT_VALIDATE, UPDATE_VALIDATE, DELETE_VALIDATE) are called automatically from the package's own insert, update, and delete routines, and therefore execute as part of standard DML against rule set and organization structure data performed through Oracle Forms or other supported maintenance paths. GET_ORG_STRUCTURE_VERSION_ID is explicitly declared for call from forms, making it available to form-level triggers that need to resolve the current version of an organization structure. RETURN_LEGISLATION_CODE may be called by dependent packages; the ETRM metadata records that this package is referenced by three other packages, indicating it participates in a wider dependency chain within the PQH module. Given its "Internal Development Use Only" access designation, custom code should exercise caution when invoking these routines directly, as signatures and behavior are not guaranteed across releases and are not covered by Oracle's public API support policy.