Search Results hxc_lck_shd




Overview
Explore in AI Chat

Overview

HXC_LCK_SHD is an internal PL/SQL package in the APPS schema of Oracle E-Business Suite that supports the Time and Labor (HXC) "locker" subsystem. The locker subsystem provides the canonical access-control and state-management layer used by Time and Labor self-service and administrative flows to serialize operations against a given timecard, assignment, or date range while editing is in progress. The "_SHD" suffix indicates a shadow or companion implementation that carries the low-level primitives consumed by the primary locker packages (HXC_LCK_BUS, HXC_LCK_INS, HXC_LCK_UPD, HXC_LCK_DEL) rather than being called directly by application code.

The package is classified as OTHER in the ETRM metadata, i.e. it is neither a published public API nor a documented private API, and it should be treated as an implementation detail that Oracle may change without notice. Its role is to isolate the mechanics of determining whether a row can be locked, detecting conversion or environment errors, and translating caller-supplied argument structures into the forms expected by the underlying locker business logic.

Key Procedures and Functions

  • CONSTRAINT_ERROR — Handles constraint-related error conditions encountered while the locker subsystem attempts to insert, update, or delete lock records. Used to translate Oracle constraint violations into application-friendly outcomes.
  • API_UPDATING — Indicates whether the package is executing in an API-update context, allowing the locker logic to behave differently when invoked from an API rather than from a form or concurrent program.
  • LCK — The core locking routine that performs the actual locker acquisition or validation logic against the HXC_LOCKER_TYPES configuration and related state.
  • CONVERT_ARGS — Converts incoming argument structures into the format expected by the locker business logic, normalizing parameter types between callers and the underlying routines.

Parameter lists are intentionally not documented here; they are not published and should not be assumed stable.

Tables Accessed

Two tables are documented as accessed via APPS synonyms:

  • ALL_CONSTRAINTS — The data dictionary view used by CONSTRAINT_ERROR to inspect constraint definitions and to interpret constraint violations raised during locker operations.
  • HXC_LOCKER_TYPES — The Time and Labor setup table that defines the locker types and their behavior. The LCK routine reads this table to determine the locking semantics applicable to a given locker type.

No other tables are documented as directly referenced, though indirect access may occur through the calling packages.

Usage Notes

HXC_LCK_SHD is not intended for direct invocation by customers, form personalizations, or custom concurrent programs. It is referenced exclusively by the Time and Labor locker packages HXC_LCK_BUS, HXC_LCK_INS, HXC_LCK_UPD, HXC_LCK_DEL, and by itself, which collectively expose the locker operations consumed by Time and Labor self-service pages, the Timecard form, and administrative timecard processes. All four of these referencing packages are also classified as private, confirming that the locker subsystem as a whole is an internal implementation layer.

Because HXC_LCK_SHD is private, extensions and customizations should interact with Time and Labor through the supported public APIs (for example, HXC_TIME_ATTRIBUTE_API and the Time and Labor self-service flows) rather than through this package. Direct dependencies on HXC_LCK_SHD risk breakage during patching or upgrades between 12.1.1 and 12.2.2, and its behavior should be treated as an undocumented implementation detail.