Search Results create_in_location

Overview

The APPS.HR_IN_LOCATION_API package body is a public Oracle E-Business Suite API belonging to the Oracle HRMS (Human Resources) module, with specific applicability to the India localization (indicated by the IN component in its name). Its principal business function is to provide a programmatic interface for the creation and maintenance of location records that describe physical addresses, sites, and inventory-related attributes used across Oracle HR, Oracle Inventory, and Oracle Payables.

The package is classified as an API in the ETRM registry, meaning it is designed for direct invocation by external code, concurrent programs, and forms-based user interfaces. Location records created through this API underpin multiple downstream processes, including employee assignment to a work location, shipping and receiving site configuration, bill-to and ship-to address derivation, and tax registration associated with a legal entity operating unit.

The source header indicates the body was last shipped at version 115.0 in 2004, which places the interface in the long-term supported set of HRMS APIs that remain available in both EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents two public procedures within this package:

• CREATE_IN_LOCATION — Creates a new location record. It accepts parameters that describe the location's identity (location code, description, style), its geographic address components (country, flat/door/block, building/village, road/street, area, town/city/district, state or union territory, postal code), and its operational classifications. The procedure exposes default-flagged parameters for several site roles, including bill-to, ship-to, office, receiving, and inventory organization indicators, allowing the caller to declare which business uses the location supports. Optional parameters permit assignment of a timezone, telephone and fax numbers, e-mail address, designated receiver, inactive date, operating unit, inventory organization, ship-to location reference, ECE trading partner header and location code, and descriptive flexfield attributes. A p_validate parameter governs whether the procedure performs a validation-only dry run or commits the record.
• UPDATE_IN_LOCATION — Modifies an existing location record. It follows the same attribute model as CREATE_IN_LOCATION, applying changes to an already-identified location for the supplied effective date.

Tables Accessed

The ETRM metadata for this object does not enumerate the base tables referenced through APPS synonyms. By design, HR location APIs persist their data primarily into the HR location entity tables (HR_LOCATIONS and its associated address and translation tables), with site-flag information stored in the location's site-usage attributes. The package is additionally recorded as echoing data to inventory and payables-related location constructs where bill-to, ship-to, and receiving flags are supplied.

The package is referenced by two other packages, confirming it is consumed as a shared service rather than being a terminal consumer.

Usage Notes

The API is typically invoked from HRMS forms that maintain locations, from custom PL/SQL interfaces that mass-load locations during implementations or data conversions, and from concurrent programs that synchronize site definitions across organizations. Callers searching on the term create_in_location are usually attempting to build such a load routine or to locate the documented signature for the creation entry point.

Recommended practice is to invoke the procedure with p_validate set to true during development to confirm that the supplied address and flag combinations pass validation, then re-invoke with validation disabled. Callers should always supply an effective date, since the API is date-effective by design, and should respect the required address elements for the India localization.