Search Results create_hz_location_bo




Overview
Explore in AI Chat

Overview

APPS.POS_HZ_LOCATION_BO_PKG is a PL/SQL package in Oracle E-Business Suite that exposes a business-object (BO) interface over the Oracle Trading Community Architecture location model, specifically the HZ_LOCATIONS entity. Its role is to provide a controlled, API-driven mechanism for retrieving and creating location records that are associated with a party and identified through the Oracle source-system / source-reference key pair (p_orig_system and p_orig_system_reference). In this respect it belongs to the family of "BO" wrapper packages used by Oracle Supplier and iSupplier-facing flows to maintain address and location data in a consistent, describable manner rather than through direct table DML. The package is declared AUTHID CURRENT_USER, so privileges and synonyms resolve in the schema of the caller, and it depends on the standard FND_API error-handling conventions (p_init_msg_list, x_return_status, x_msg_count, x_msg_data). The header dates place the shipped version at 120.1 (2010), and the package remains documented in the 12.1.1 and 12.2.2 code lines.

Key Procedures and Functions

  • GET_HZ_LOCATION_BO — Retrieves the location business object for a given party and source-system identity. It accepts an API version, initialization flag, the party identifier, and the originating system and reference, and returns the location business object (typed as POS_HZ_LOCATION_BO_TBL) together with the standard return status, message count, and message data.
  • CREATE_HZ_LOCATION_BO — Creates or maintains a location business object. It accepts the API version, initialization flag, the source-system and source-reference keys, an instance of POS_HZ_LOCATION_BO, and a create/update flag indicating the intended operation. It returns the generated location identifier, the object version number (for optimistic locking / subsequent updates), and the standard return status, message count, and message data.

Both procedures are the only documented entry points in the specification, and each is designed to be called within the standard FND_API transaction and message stack, with results conveyed through the OUT NOCOPY parameters.

Tables Accessed

  • HZ_LOCATIONS — the primary target. The create procedure inserts or updates the location row, and the get procedure reads it to populate the returned business object.
  • AP_SUPPLIERS — accessed to relate the location to the supplier/party context, since location records created through this interface are used by supplier and supplier-site processes.
  • AP_SUPPLIER_SITES_ALL — accessed to maintain the association between a location and the supplier site that uses it, ensuring address data stays consistent with purchasing and payables processing.

Access is performed through APPS synonyms, so the underlying objects resolve to the applications schema.

Usage Notes

This package is typically invoked from supplier-facing forms, from concurrent programs that load or synchronize supplier addresses, and from custom integrations that need to create or fetch TCA location records without calling the lower-level HZ_LOCATION_V2PUB APIs directly. Because it stores identifiers through the originating system and reference pair, callers should always supply a stable source-system key so that repeated calls are idempotent and the object version number returned by create can be used for later updates. Callers must inspect x_return_status and call the standard FND_MSG_PUB utilities when it is not FND_API.G_RET_STS_SUCCESS, and should only commit at the top of their own transaction boundary. The package is referenced by one other package, indicating that it functions as a reusable service layer rather than a standalone application entry point.