Search Results hxc_lck_bus




Overview
Explore in AI Chat

Overview

HXC_LCK_BUS is a business-layer PL/SQL package owned by the APPS schema in Oracle E-Business Suite. Its name and dependencies place it within the time and labor family of modules — the HXC prefix denotes objects belonging to Oracle Time and Labor (OTL) and its related components, including the locker and locking functionality used to govern access to timecard structures. The package encapsulates the validation and security logic associated with locker type definitions, locking rules, and lock records, providing the application program interface by which forms and concurrent processes manipulate these entities in a controlled and consistent manner. In the ETRM classification the package is tagged as OTHER, reflecting that it is an internal business-layer component rather than a public, externally published API.

Key Procedures and Functions

The package body exposes five documented procedures and functions, each serving a distinct role in the locker/locking lifecycle:

  • SET_SECURITY_GROUP_ID — establishes the security group context under which the subsequent business operations execute, ensuring that any data manipulation respects the organizational security model enforced by Oracle EBS.
  • RETURN_LEGISLATION_CODE — returns the applicable legislation code, allowing the locker and locking logic to behave in a country- or legislation-specific manner where rules differ by legal jurisdiction.
  • INSERT_VALIDATE — performs the business validations required before a new locker type, locking rule, or lock record is inserted, rejecting data that violates the defined constraints.
  • UPDATE_VALIDATE — performs the corresponding validations applied when an existing record is modified, protecting referential and business integrity during changes.
  • DELETE_VALIDATE — determines whether a record may be removed, blocking deletions that would compromise dependent data or active locking configurations.

These routines form the standard validate-before-write pattern used throughout the EBS business layer, centralizing rules so that every caller applies identical enforcement.

Tables Accessed

Through APPS synonyms, the package operates on three core tables:

  • HXC_LOCKER_TYPES — the definitions of available locker types; read and validated when locker configurations are created or maintained.
  • HXC_LOCKING_RULES — the rules governing how and when locking applies; consulted during validation of inserts, updates, and deletes.
  • HXC_LOCKS — the actual lock records; the primary target of the validation logic that guards the integrity of lock data.

The package additionally references HXC_LCK_SHD and standard SYS constructs, and its behavior underlies the table-handler packages HXC_LCK_INS, HXC_LCK_UPD, and HXC_LCK_DEL, which are the documented callers that trigger its validations.

Usage Notes

HXC_LCK_BUS is not intended for direct invocation by end users. It is normally reached indirectly: the locker and locking maintenance forms within Oracle Time and Labor invoke the table-handler packages (HXC_LCK_INS, HXC_LCK_UPD, HXC_LCK_DEL), which in turn call the validation routines in this package before committing data. Security group initialization and legislation code resolution are likewise handled transparently as part of those flows. Customizations and extensions that need to insert, update, or delete locker and locking data should route through the same table-handler and business-layer pattern rather than issuing DML against HXC_LOCKS or its related tables directly, so that validation, security group context, and legislation-specific behavior remain intact. The VALID status of the package confirms it is available and consistent in both EBS 12.1.1 and 12.2.2.