Search Results create_location_b

Overview

The APPS.HR_LOCATION_BK1 package body is a generated PL/SQL API stub belonging to the Oracle HRMS Location API family. Its name carries the _BK1 suffix, which in Oracle E-Business Suite conventions identifies it as an API Hook Pre-processor artifact produced automatically by the Oracle HRMS API Hook Pre-processor. The header comment within the source, "Code generated by the Oracle HRMS API Hook Pre-processor," and the timestamp line, "Created on 2013/08/13 18:46:39," confirm that the package body was machine-generated rather than hand-coded.

The business purpose of the package is to provide the pre-processing layer for the Location business object. In HRMS, a Location represents a physical place of business — an office, warehouse, plant, or receiving site — that is referenced by organizations, business groups, addresses, and third-party delivery information. Before the standard Location API executes its own validation and DML logic, the API Hook architecture routes the call through a _BK1 pre-processor, allowing customers and integrators to register custom validation or defaulting logic without modifying Oracle-owned code. For the user who searched for create_location_b, this package is the direct dependency containing the companion CREATE_LOCATION_A procedure that precedes the _B entry point.

Key Procedures and Functions

• CREATE_LOCATION_A — the primary documented procedure. It exposes the full parameter surface used to create a new Location record. The signature covers the effective date, language code, location code, description, and timezone, as well as third-party (TP) header and location code identifiers used for ECE/trading partner address synchronization. Address attributes include address lines 1 through 3, town or city, postal code, country, region 1 through 3, and telephone numbers 1 through 3. Site behavior is controlled by flags such as bill-to site, ship-to site, receiving site, office site, and in-organization flag, along with designated receiver and ship-to location identifiers. Financial and inventory context is supplied through operating unit and inventory organization IDs. A large trailing block of LOC_INFORMATION13 through LOC_INFORMATION20 and ATTRIBUTE_CATEGORY/ATTRIBUTE1–ATTRIBUTE12 parameters exposes descriptive flexfield and developer extensibility columns. The procedure acts as the pre-processor hook: it marshals incoming values and passes them forward to the main API implementation.
• CREATE_LOCATION_B — the second documented procedure, representing the paired hook that follows CREATE_LOCATION_A in the generation sequence. Both procedures are registered as part of the same hook group so that custom business rules can be applied at either point of the creation flow.

Tables Accessed

The ETRM metadata records no directly referenced tables for this package body through APPS synonyms. This is consistent with its generated pre-processor role: HR_LOCATION_BK1 primarily stages and forwards parameters rather than performing direct DML. The underlying writes to the HR location tables — HR_LOCATIONS_ALL and its _TL translation table, along with HR_LOCATION_EXTRA_INFO — are executed by the downstream API procedures that this hook precedes. The package is referenced by one other package within the APPS schema, confirming its position in the Location API call chain.

Usage Notes

HR_LOCATION_BK1 is not intended for direct invocation by end users or custom code. It is typically reached through the HR_LOCATION_API public interface, the Location maintenance forms, or concurrent/interface programs that create locations during data loading. Customers extending Location creation should implement their logic in the supported API hook package (often HR_LOCATION_BK or the corresponding _BK1 customization point) rather than editing this generated body, since regeneration by the API Hook Pre-processor will overwrite any manual changes — as evidenced by the "generated ship" revision string in the header.