Search Results pre_delete_checks

Overview

APPS.PER_POS_STRUCTURE_VERSIONS_PKG is a server-side PL/SQL package in the Oracle E-Business Suite Human Resources (PER) module that manages the versioning of position hierarchies. Position structures in Oracle HRMS represent hierarchical organizations of positions, and each structure may exist in multiple concurrent or sequential versions to reflect reorganizations over time. This package encapsulates the business rules that govern the creation, maintenance, and deletion of those structure versions and their associated position structure elements. It is declared with AUTHID CURRENT_USER, so it executes with the privileges of the calling schema, and the header indicates it has been part of the product since at least the 11i code line. The package centralizes validation logic such as version numbering, date gap detection, and overlap checking, ensuring that position structure versions remain internally consistent across the enterprise.

Key Procedures and Functions

The package exposes ten documented program units. The procedures most relevant to the user's search term, pre_delete_checks, and the surrounding version-management logic are summarized below; parameter lists are not reproduced here.

• GET_NEXT_FREE_NO — Returns the next available version number for a given position structure, supporting the automatic assignment of sequential version identifiers.
• CHECK_VERSION_NUMBER — Validates that a proposed version number is acceptable for the position structure, typically guarding against duplicates or invalid ranges.
• CHECK_DATE_GAP — Evaluates the date range of a version against its neighbors and returns a warning when a gap exists between consecutive versions.
• CHECK_OVERLAP — Detects overlapping effective dates between versions of the same structure, returning a closedown warning when the new date range conflicts with existing rows.
• COPY_ELEMENTS — Copies position structure element rows from one structure version to another, enabling a new version to be seeded from an existing one.
• PRE_DELETE_CHECKS — The procedure identified in the search. It performs the validations required before a position structure version may be deleted, taking the version identifier, business group, position structure, and an HR installation indicator. It verifies that deletion is permissible given dependencies and installed-product context, allowing the calling form or API to raise an appropriate error or warning prior to the physical delete.
• INSERT_ROW, LOCK_ROW, UPDATE_ROW, DELETE_ROW — The standard DML interface for the version entity, handling row creation, pessimistic locking, modification, and removal while enforcing the validation rules above.

Tables Accessed

The package operates against the base and translated/secure views of the position structure model, referenced through APPS synonyms:

• PER_POS_STRUCTURE_VERSIONS and PER_POS_STRUCTURE_VERSIONS_S — the version header records that define each dated version of a position hierarchy; these are the primary subject of the INSERT, UPDATE, DELETE, and check routines.
• PER_POS_STRUCTURE_ELEMENTS and PER_POS_STRUCTURE_ELEMENTS_S — the element (position membership) rows belonging to each version, read and maintained by COPY_ELEMENTS and the DML procedures.
• PER_SECURITY_PROFILES — consulted to enforce security profile restrictions that determine which position structures and versions a user may view or modify.

Usage Notes

PER_POS_STRUCTURE_VERSIONS_PKG is normally invoked indirectly through the Oracle HRMS Position Structure and Position Hierarchy forms rather than called directly by end users. The form triggers call PRE_DELETE_CHECKS before issuing a delete, and the INSERT/UPDATE/DELETE routines when versions are maintained. Because the package is documented as an OTHER-classified API and is referenced by zero other packages per the ETRM metadata, it is not a published integration interface; custom code that calls it should treat its behavior as internal and subject to change across releases such as 12.1.1 and 12.2.2. Extensions needing to manage position structure versions programmatically should prefer supported public APIs or the underlying tables, invoking this package only where the standard forms logic is being replicated. When it is called from custom concurrent programs or scripts, the caller must supply a valid business group and observe the date-gap and overlap warnings returned through the OUT NOCOPY parameters to preserve data integrity.