Search Results per_org_structure_versions_s




Overview
Explore in AI Chat

Overview

APPS.PER_ORG_STRUCTURE_VERSIONS_PKG is a PL/SQL package body within the Oracle E-Business Suite Human Resources (PER) schema that manages the versioning of organization hierarchies in Oracle HRMS. Organization structures, such as reporting hierarchies, cost structures, and other grouping hierarchies, are maintained as dated versions stored in the PER_ORG_STRUCTURE_VERSIONS table. Each version carries a version number, an effective start date, and an effective end date, allowing the hierarchy to evolve over time while preserving historical definition.

This package encapsulates the business logic required to insert, update, copy, and delete hierarchy versions while enforcing the integrity rules that prevent overlapping, gapped, or duplicate version definitions. These rules are essential because HRMS date-tracked datetrack validation requires that contiguous and non-overlapping effective periods be maintained for any organization structure used by downstream payroll, budgeting, or reporting processes.

Key Procedures and Functions

The package exposes eleven documented procedures and functions, each focused on a specific validation or maintenance operation:

  • GET_NEXT_FREE_NO — Returns the next available version number for an organization hierarchy. It derives the value as the maximum existing version_number for the structure plus one, defaulting to 1 when no versions exist. The query always returns a single row regardless of whether the supplied organization structure version identifier is valid.
  • CHECK_DATE_GAPS — Examines the effective dates of existing versions to determine whether a gap would exist between adjacent hierarchy versions, returning a warning indicator through an OUT parameter.
  • CHECK_VERSION_NUMBER — Validates that a proposed version number does not conflict with an existing version for the same organization structure.
  • CHECK_OVERLAP — Detects whether proposed effective dates overlap the date range of another version of the same hierarchy.
  • COPY_ELEMENTS — Copies the element (position/assignment) definitions from one version of the hierarchy into another, supporting the common "copy and amend" workflow used when maintaining hierarchies.
  • INSERT_ROW — Inserts a new organization structure version record after the appropriate validations have been performed.
  • LOCK_ROW — Obtains a row-level lock on a version record, protecting it from concurrent modification during an update or delete operation.
  • UPDATE_ROW — Applies changes to an existing version record, preserving date-track integrity.
  • PRE_DELETE_CHECKS — Performs the business-rule validations required before a version can be deleted.
  • UPDATE_COPIED_VERSIONS — Adjusts the version records that were generated by a copy operation so they reflect correct effective dates and version numbers.
  • DELETE_ROW — Removes a version record once the pre-delete checks have passed.

Tables Accessed

The package operates across the core organization structure tables:

  • PER_ORG_STRUCTURE_VERSIONS and PER_ORG_STRUCTURE_VERSIONS_S — The version definitions themselves, including version_number, date_from, and date_to, which are read and written by the insert, update, delete, and gap/overlap-checking logic. GET_NEXT_FREE_NO reads PER_ORG_STRUCTURE_VERSIONS to derive the maximum version number.
  • PER_ORG_STRUCTURE_ELEMENTS and PER_ORG_STRUCTURE_ELEMENTS_S — The member elements (positions or organizations) belonging to each structure version, maintained by COPY_ELEMENTS and the row-maintenance routines.
  • PER_ORGANIZATION_STRUCTURES — The parent definition of the hierarchy itself, providing the context in which versions and elements are validated.

Usage Notes

PER_ORG_STRUCTURE_VERSIONS_PKG is referenced by zero other documented packages, indicating it is consumed primarily as a top-level service rather than as a shared internal utility. It is most commonly invoked from the Oracle HRMS Organization Hierarchy forms (such as the Organization Hierarchy window in the HRMS manager responsibility), where users define, copy, and date-track hierarchy versions. In that context, GET_NEXT_FREE_NO supplies the default version number displayed to the user, and PRE_DELETE_CHECKS and CHECK_DATE_GAPS drive the validation messages surfaced during entry.

Custom code and extensions that programmatically create or modify organization hierarchy versions should invoke these procedures rather than inserting directly into the tables, since the package enforces the non-overlap and continuity rules required for HRMS datetrack consistency.