Search Results pos_hz_location_bo_pkg

Overview

The PL/SQL package body APPS.POS_HZ_LOCATION_BO_PKG belongs to the Oracle E-Business Suite (EBS) supplier and party-location integration layer. It is classified under the ETRM as an "OTHER" API with a business-entity category of BUSSINESS_ENTITY AP_SUPPLIER, indicating that it exposes TCA (Trading Community Architecture) HZ location data specifically for use within the Oracle Payables supplier model. In release 12.1.1 and 12.2.2, the package acts as a thin business-object wrapper that surfaces records from the HZ_LOCATIONS table as a strongly typed PL/SQL record collection (pos_hz_location_bo_tbl), allowing callers to retrieve and construct location objects in a consistent, reusable form rather than issuing ad-hoc queries against the TCA tables.

The header comment records a revision of $Header: POSSPLOCB.pls 120.1 dated 25 November 2010, confirming the package's stability across the 12.x line. The package is documented as being referenced by one other package, which reflects its role as a lower-level utility consumed by broader supplier or location processing logic.

Key Procedures and Functions

The ETRM metadata documents two public procedures within this package body:

• GET_HZ_LOCATION_BO — Retrieves an HZ location business object. The source excerpt shows that it accepts an API version, an initialization message-list flag, a party identifier, and original-system/original-system-reference identifiers, and it returns a populated pos_hz_location_bo_tbl collection together with the standard EBS concurrent-style OUT parameters for return status, message count, and message data. Internally, the procedure performs a single SELECT that maps every column of the HZ_LOCATIONS row — including the twenty ATTRIBUTE columns, the twenty GLOBAL_ATTRIBUTE columns, the GLOBAL_ATTRIBUTE_CATEGORY, WHO audit columns, and the WH_UPDATE_DATE — into a pos_hz_location_bo record. It is annotated in the source with @rep:scope public, @rep:lifecycle active, and @rep:displayname Get HZ Location BO.
• CREATE_HZ_LOCATION_BO — Creates an HZ location business object. Although the excerpt does not reproduce its body, the naming convention and the presence of the GET counterpart indicate a complementary write-path routine that populates a new location business object for subsequent insertion through the underlying TCA APIs.

No parameter lists are asserted beyond those visible in the supplied source excerpt.

Tables Accessed

The package operates against the following tables, accessed through APPS synonyms:

• HZ_LOCATIONS — The primary TCA location entity. GET_HZ_LOCATION_BO selects the full column set from this table, making it the authoritative source of the returned business object.
• AP_SUPPLIERS — The supplier header table, relevant because the package is scoped to the AP_SUPPLIER business entity and is used to associate location objects with supplier records.
• AP_SUPPLIER_SITES_ALL — The supplier site table, which links suppliers to their address locations and therefore contextualises the retrieval of HZ location business objects in the payables supplier model.

Usage Notes

Because POS_HZ_LOCATION_BO_PKG is a public, active business-object API, it is typically invoked from Oracle Forms supplier maintenance screens, from Oracle Payables concurrent programs that process supplier and supplier-site data, and from custom PL/SQL that needs a structured representation of an HZ location linked to a party or supplier. Callers should pass a valid API version and initialise the message list as required, then inspect x_return_status, x_msg_count, and x_msg_data before consuming the returned x_hz_location_bo collection. The NOCOPY hint on the OUT parameters makes the API efficient for large collections. In 12.2.2 the package remains available under the APPS schema and continues to be referenced by dependent supplier-processing packages.