Search Results hr_loc_ins




Overview
Explore in AI Chat

Overview

APPS.HR_LOC_INS is a private PL/SQL package body in the Oracle E-Business Suite human resources schema that implements the insert-side table handler for the HR_LOCATIONS base table. In the Oracle HRMS architecture, each major entity is supported by a family of generated table handlers: an RKI (row key information) package that derives and validates the primary key, an INS package that performs the physical insert, an UPD package for updates, and a DEL package for deletions. HR_LOC_INS is the member of that family responsible for creating new rows in HR_LOCATIONS_ALL and its shadow table HR_LOCATIONS_S.

The package status is documented as VALID in ETRM for both 12.1.1 and 12.2.2, and its API classification is recorded as OTHER, meaning it is not a public, certifiable business API. It is infrastructure code intended to be called by the HR_LOCATIONS business API and by generated table-handler chains rather than by end users or third-party integrations directly. Because it is not referenced by any other database object, it is a leaf-level dependency: it consumes several other packages but nothing in the database depends on it.

Key Procedures and Functions

  • SET_BASE_KEY_VALUE — Assigns the base key value for the location row being inserted. This routine participates in the surrogate-key generation convention used across HRMS table handlers, ensuring that the new HR_LOCATIONS row receives a correctly derived primary key before the insert proceeds. It underpins the RKI/INS handshake in which the RKI package supplies key information and the INS package applies it.
  • INS — The core insert routine. It accepts the row attributes for a new location and performs the physical insertion into the HR_LOCATIONS table through the HR_LOCATIONS_ALL synonym, maintaining the corresponding HR_LOCATIONS_S shadow record used for the DateTrack (effective-dating) model. It also invokes the after-insert processing supplied by HR_LOC_RKI so that row key information is updated consistently after the row is written.
  • Third documented procedure — ETRM records three documented procedures or functions in total; the two named above are those surfaced individually. The remainder forms internal supporting logic within the same package body.

Tables Accessed

  • HR_LOCATIONS_ALL — The primary insert target. This synonym resolves to the HR_LOCATIONS base table, which stores location definitions such as address, ship-to and bill-to flags, and inventory organization associations.
  • HR_LOCATIONS_S — The shadow table that holds the DateTrack history for HR_LOCATIONS. HR_LOC_INS writes to it so that the newly created row has a consistent effective-dated record.
  • DBMS_DESCRIBE — Utilized to introspect the signature of the underlying insert routine, allowing the generated handler to bind the correct arguments at runtime.

Usage Notes

HR_LOC_INS is invoked indirectly. The typical path is through the HR_LOCATIONS business API (HR_LOC_INS / HR_LOC_UPD style calls) or through the HR_LOCATIONS form, which routes inserts to the API. It also appears in concurrent processing and in the location utility routines used by Oracle iRecruitment (IRC_LOCATION_UTILITY) when locations are created programmatically.

Because the package is classified as OTHER and is not referenced by any database object, customizations and third-party code should not call HR_LOC_INS directly. Instead, developers should use the supported HR_LOCATIONS API or the location business logic layer. Direct invocation risks bypassing validation performed by HR_LOC_BUS and HR_UTILITY, and would not be preserved across patching or upgrades. The dependency list confirms the package also references FND_PROFILE, HR_API, and MDSYS.SDO_GEOMETRY, indicating that profile-option checks and spatial geometry attributes are honoured during insertion.