Results for “update_location_b”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.HR_LOCATION_BK2 is a PL/SQL package that forms part of the Oracle E-Business Suite HR location API infrastructure. In the Oracle EBS architecture, the HR location APIs are delivered as a family of paired packages that follow the "before" and "after" processing convention: the _BK (before) package handles row population and validation for the base table record, while the corresponding _AR or "after" package manages the interface-table and denormalized-attribute logic. The suffix 2 on HR_LOCATION_BK2 indicates a secondary or alternate variant of the before-processing package, typically used where a distinct procedure signature or processing path is required without disturbing the primary shipped package.

The functional purpose of the package is to support the maintenance of HR location records — the addresses and site attributes that Oracle HRMS, Inventory, Purchasing, and Receivables all consume. Rather than updating the base HR location tables directly, callers invoke these APIs so that all mandatory columns, descriptive flexfields, and derived attributes are validated and populated consistently. This package therefore underpins the correctness of location data used across the enterprise, including addresses associated with specific operating units and countries.

Key Procedures and Functions

The package exposes two documented procedures:

• UPDATE_LOCATION_B — The "before" procedure that performs validation and populates the base HR location record in preparation for the update. It accepts a wide range of location attributes, including effective date, language code, location identifier and code, description, timezone, telephone numbers, town or city, address lines, country, postal code, operating unit, inventory organization, and the site flags (bill-to, ship-to, receiving, office, and organization). It also carries the descriptive flexfield columns attribute_category, attribute1 through attribute7, the loc_information13 through loc_information20 information fields, and the region_1 through region_3 fields. This is the procedure invoked first in any update operation.
• UPDATE_LOCATION_A — The "after" procedure that completes the update, handling any post-processing that must occur once the base record has been written. It is the standard companion to the _B procedure and is called immediately after it.

Tables Accessed

The ETRM metadata records no explicitly documented table references through APPS synonyms for this package. By its nature as an HR location API, the package operates against the HR location base tables — principally HR_LOCATIONS_ALL and its associated flexfield and information-type structures — with the corresponding _TL table holding translated descriptions. The before/after split is designed so that the base table is touched in the _B call and the ancillary or derived records are touched in the _A call. Because the documented metadata does not enumerate the tables, the precise list should be confirmed by inspecting the package body in the target instance.

Usage Notes

These procedures are not intended to be called directly against the base tables by end users. They are typically invoked from the HR location maintenance forms, from other Oracle HRMS APIs that create or cascade location updates, and from custom PL/SQL that needs to modify location data in a supported manner. The standard invocation pattern is to call UPDATE_LOCATION_B followed by UPDATE_LOCATION_A within the same transaction, supplying values retrieved from the _B procedure's output parameters into the _A procedure. The metadata notes that this package is referenced by one other package, indicating a layered dependency within the HR API stack. Custom code should always use these APIs rather than direct DML so that validation, flexfield derivation, and dependent records remain consistent.