Search Results hz_geo_structure_pub_uiw_jw

Overview

APPS.HZ_GEO_STRUCTURE_PUB_UIW_JW is a PL/SQL package body in the Oracle E-Business Suite Applications (APPS) schema, classified under the Trading Community Model / Geography subsystem of Oracle Customers Online and Receivables. Its name structure follows Oracle's UIW (User Interface Wrapper) and JW conventions, indicating that it serves as a thin wrapper layer that surfaces the public geography-structure API to a caller, typically translating an inbound record payload into calls against the underlying HZ_GEO_STRUCTURE_PUB_UIW package. The suffix "JW" is characteristic of wrapper packages generated to adapt the public API surface for a specific integration or UI mechanism, allowing transaction data to be marshalled into the standard API parameter model.

The package is reported as VALID in the ETRM repository and depends directly on FND_API (the Oracle Application Object Library framework package providing the standard API return-status and message-handling model), HZ_GEO_STRUCTURE_PUB_UIW (the underlying public API), the JTF_VARCHAR2_TABLE_100 collection type, and PLITBLM, the standard PL/SQL integer table used for message and record indexing within the Oracle API framework.

Key Procedures and Functions

The ETRM repository documents seven procedures and functions within this package body. They fall into two functional categories.

• ROSETTA_TABLE_COPY_IN_P0 and ROSETTA_TABLE_COPY_OUT_P0 — marshalling utilities that transform an inbound record structure into the tabular (PL/SQL table) representation expected by the public API, and conversely copy outbound result data back into the caller's record structure. The "P0" designation denotes the base or primary table-copy variant.
• CREATE_GEOGRAPHY_TYPE — creates a geography type definition, the highest level of the geography hierarchy used to classify geopolitical and administrative structures.
• CREATE_GEO_STRUCTURE — creates a geography structure, establishing the relationship between a geography type and its parent/child hierarchy within a country model.
• CREATE_GEO_REL_TYPE — creates a geography relationship type, defining the permissible relationship semantics between geography nodes.
• CREATE_ZONE_TYPE — creates a zone type, used to define tax, territory, or sales zones for geography-based processing.
• UPDATE_ZONE_TYPE — modifies an existing zone type definition.

As the metadata does not disclose parameter signatures, no arguments are reproduced here. Each procedural entry is understood to accept the standard API parameter set (p_init_msg_list, x_return_status, x_msg_count, x_msg_data, and record identifiers) consistent with the HZ public API convention.

Tables Accessed

The ETRM metadata documents a single table reference accessed through APPS synonyms: PLITBLM. This is not an application data table but the standard Oracle PL/SQL integer-index table used internally to hold message and record indices during API processing and bulk operations. No HZ geography base tables (such as HZ_GEOGRAPHIES, HZ_GEO_STRUCTURE_LEVELS, or HZ_GEO_STRUCTURE_TYPES) are recorded as direct references in this document; data manipulation against the geography model is performed through the underlying HZ_GEO_STRUCTURE_PUB_UIW package rather than by this wrapper directly.

Usage Notes

This package is not referenced by any other database object, indicating it is top of the dependency stack rather than a shared internal utility. It is therefore invoked directly by an external or presentation-layer caller — typically a Forms-based geography setup screen, a concurrent program, or custom integration code that needs to create or maintain geography types, geography structures, relationship types, and zone types without calling the lower-level public API directly. Because it sits above HZ_GEO_STRUCTURE_PUB_UIW, it is the appropriate entry point when a caller already holds a record structure matching the Rosetta table layout. The presence of ROSETTA_TABLE_COPY_IN_P0 and ROSETTA_TABLE_COPY_OUT_P0 confirms the intended use pattern: callers prepare an input record table, invoke the create or update routines, then copy results back out. The same source is valid in Oracle EBS 12.1.1 and 12.2.2, as the HZ geography model was not materially restructured between these releases.