Search Results hr_location_bk1




Overview
Explore in AI Chat

Overview

The APPS.HR_LOCATION_BK1 package is a private (backing) API package within the Oracle E-Business Suite Human Resources location management layer. It is generated as the "before-processing" half of a Table Handler / Business API pair, working alongside HR_LOCATION_API and its public wrapper to enforce business rules, defaults, and referential integrity when location records are created or updated. In the context of Oracle EBS 12.1.1 and 12.2.2, the _BK1 suffix denotes the low-level body that implements the row-level logic executed before the corresponding public procedure commits changes to HR_LOCATIONS and related location tables.

Location definitions are foundational master data: they represent physical addresses used for shipping, receiving, billing, office, and inventory organizations across Operating Units and Legal Entities. Because of this wide dependency, the backing package encapsulates validation logic that guards address quality, site flags, time-zone consistency, and descriptive-flexfield integrity before persistence.

Key Procedures and Functions

ETRM documents two procedures for this package:

  • CREATE_LOCATION_B — The "before" procedure for location creation. It accepts the full set of location attributes (effective date, language code, location code, description, time-zone, address lines, site flags such as bill-to, ship-to, receiving, office, and in-organization, country, region-1 through region-3, postal code, town or city, telephone numbers, tax name, style, and the descriptive-flexfield attributes and attribute category). The "_B" suffix indicates this routine runs prior to the DML that inserts the HR_LOCATIONS row, performing defaulting and validation of these inbound values.
  • CREATE_LOCATION_A — The "after" procedure for location creation. The "_A" suffix marks it as the post-processing step that executes after the row is inserted, typically handling derived or downstream actions such as populating dependent entities, propagating address information, or invoking cross-entity relationships tied to the new location.

Together these procedures implement the standard "_B / _A" API symmetry used throughout Oracle HRMS, ensuring that the same business logic applies regardless of whether a location is created through the professional forms UI, a concurrent program, or external integration code.

Tables Accessed

The ETRM metadata excerpt does not enumerate the tables referenced through APPS synonyms, and the visible source listing truncates before the insert/select statements. Based on the documented parameter set and standard HRMS design, the backing package writes to and reads from the core location repository, principally HR_LOCATIONS (the base location definition, including site flags and address lines) and HR_LOCATIONS_TL (the translated description). Attribute and category values map to the descriptive-flexfield columns, while organization-scoped attributes such as operating-unit and inventory-organization identifiers link the location to its owning entities. Validation routines inherently query reference values and country/time-zone definitions to verify the incoming data.

Usage Notes

HR_LOCATION_BK1 is not intended for direct invocation by end users or custom applications. It is the private backing implementation invoked by the public HR_LOCATION_API procedures; the ETRM metadata records it as referenced by one other package, consistent with this one-way dependency. Typical call paths include the Locations form in Oracle HRMS, address and site setup flows in Order Management and Payables, and concurrent programs or custom PL/SQL that call the public location API. The relevant search term, "株式会社 第一住設 埼玉営業所" (a Japanese corporate office/site name), illustrates the kind of address and location name data — including translated descriptions and region attributes — that ultimately flows through CREATE_LOCATION_B and CREATE_LOCATION_A. Because the package header references patch version 120.2.12010000.2, it is the release-maintained ship-level code for the 12.1.x and 12.2.x code lines. Developers should always call the public API rather than this backing package to preserve validation and auditing behavior.