Search Results hxc_locker_types_upload_pkg




Overview
Explore in AI Chat

Overview

APPS.HXC_LOCKER_TYPES_UPLOAD_PKG is a PL/SQL upload utility package in Oracle E-Business Suite that supports the mass loading and maintenance of locker type definitions used by the Oracle Time and Labor (OTL) application. Locker types in HXC represent configurations of time entry "lockers," the containers that hold timecard data for a worker within a process type; they are closely tied to the process type of a time collection process and to the locale-based (owner) customization model that governs seeded versus customer-defined data. The package body provides the loader logic invoked during data migration, patching, and customer-side setup uploads, ensuring that locker type records in HXC_LOCKER_TYPES are correctly inserted or updated with proper ownership and custom-mode semantics. It is classified under the ETRM as an "OTHER" API and is not referenced by any other packages in the EBS codebase, indicating it is a standalone uploader rather than a reusable business API.

Key Procedures and Functions

The package body exposes one documented procedure name, overloaded twice:

  • LOAD_LOCKER_TYPES_ROW — the primary loader procedure for a single locker type row. One overload accepts a process type, a locker type, an owner, and a custom-mode flag; the second overload accepts the same parameters plus a last-update-date value, which allows the upload process to preserve or validate the source system's date metadata rather than stamping the current database date.

In operation, LOAD_LOCKER_TYPES_ROW first attempts to query the existing HXC_LOCKER_TYPES row matching the supplied process type and locker type, deriving the current owner name through FND_LOAD_UTIL.OWNER_NAME. If a matching row exists, and if the custom mode is FORCE or the existing row is Oracle-owned, the procedure calls HXC_LCK_UPD.UPD to update the record; this condition implements the standard EBS rule that seeded ORACLE rows may be updated only under explicit force conditions. When no matching row is found (NO_DATA_FOUND), the procedure calls HXC_LCK_INS.INS to insert a new locker type. The overload's additional last-update-date parameter supports the comparison of source and database metadata during upload.

Tables Accessed

  • HXC_LOCKER_TYPES — the core table storing locker type definitions. The package reads LOCKER_TYPE_ID, LOCKER_TYPE, PROCESS_TYPE, and the audit columns LAST_UPDATED_BY and LAST_UPDATE_DATE to determine existence, ownership, and whether an update is permissible. Writes are performed indirectly through HXC_LCK_UPD.UPD and HXC_LCK_INS.INS, which maintain the underlying rows on behalf of the uploader.

Usage Notes

This package is typically invoked by upload or migration routines that seed locker type data, rather than by end-user forms directly. Its parameters and internal flow — particularly the process type and custom-mode handling — mirror the conventions of Oracle's standard EBS upload APIs (for example the FND_LOAD-style loaders), where the process type identifies the owning business process context for the locker and custom mode governs whether Oracle-seeded rows may be overwritten. Typical callers include concurrent-program-based data loaders and custom migration scripts executed under the APPS schema after the prerequisite collection and process type definitions exist. Because the package is referenced by no other package, implementations relying on it should treat it as a supporting uploader and validate row-level dependencies on process type and locker type before invocation.