Search Results create_zone

Overview

The APPS.HZ_GEOGRAPHY_PUB_UIW_JW package is a generated PL/SQL wrapper that forms part of the Oracle E-Business Suite Trading Community Architecture (TCA) geography infrastructure. Its name reflects its role: the UIW suffix denotes a "User Interface Wrapper," while the _JW suffix identifies it as a Java Wrapper artifact produced by Oracle's Rosetta/JPublisher generation framework. This package exposes the business logic of the underlying HZ_GEOGRAPHY_PUB API to Java-based clients, such as Oracle Application Framework (OAF) pages and JTT (Java Technology Toolkit) consumers.

Geographies in EBS represent the hierarchical structure of countries, states, provinces, counties, cities, and postal code ranges. Master relations establish the parent-child links that define this hierarchy, while geo identifiers, geography ranges, and zone relations support additional classification and grouping semantics used by tax, shipping, and address validation processes.

Key Procedures and Functions

The package documentation lists thirteen procedures, grouped into Rosetta table-copy utilities and public business API calls:

• ROSETTA_TABLE_COPY_IN_P2 / ROSETTA_TABLE_COPY_OUT_P2 — Internal plumbing that marshals data between PL/SQL record types (parent_geography_tbl_type) and JTF_NUMBER_TABLE collections for Java interoperability.
• ROSETTA_TABLE_COPY_IN_P6 / ROSETTA_TABLE_COPY_OUT_P6 — Equivalent conversion utilities for the zone_relation_tbl_type structure, handling seven parallel collection arrays (numbers, two VARCHAR2(400) tables, two VARCHAR2(100) tables, and two DATE tables).
• CREATE_MASTER_RELATION — Establishes a new master relationship record between geographies, returning the generated relationship identifier through an OUT parameter. This is the entry point users typically reach when searching for the create_master_relation operation.
• CREATE_GEO_IDENTIFIER / UPDATE_GEO_IDENTIFIER — Insert and modify geo identifier records, which hold alternate codes or external references associated with a geography.
• CREATE_MASTER_GEOGRAPHY / UPDATE_GEOGRAPHY — Create or amend the master geography definition itself.
• CREATE_GEOGRAPHY_RANGE / UPDATE_GEOGRAPHY_RANGE — Maintain postal-code or numeric ranges assigned to a geography.
• CREATE_ZONE_RELATION / CREATE_ZONE — Define zones and the relationships that associate geographies (or zones) with one another.

Every business procedure follows the standard TCA API contract: a p_init_msg_list flag, an x_return_status, x_msg_count, and x_msg_data set of OUT parameters for error handling, plus positional p1_a0...p1_aN arguments that map directly to underlying entity columns.

Tables Accessed

The ETRM metadata documents a single referenced table accessed through APPS synonyms: PLITBLM. This is the standard PL/SQL persistent-array/interim table used by Rosetta-generated wrappers to stage collection data across the Java-PLSQL boundary. The actual business data — master relations, identifiers, ranges, and zones — resides in the base HZ_GEOGRAPHY and related TCA tables manipulated by the underlying HZ_GEOGRAPHY_PUB package, which this wrapper delegates to rather than accessing directly.

Usage Notes

HZ_GEOGRAPHY_PUB_UIW_JW is not intended for direct invocation by forms, concurrent programs, or custom PL/SQL. It exists solely to service Java-layer callers requiring geography hierarchy maintenance. No other package references it (referenced-by count is zero), confirming its position as a leaf-level integration artifact. Custom developers needing equivalent functionality should call the documented public API HZ_GEOGRAPHY_PUB directly with the same parameter semantics. Because the wrapper signature mirrors the underlying API, any upgrade to HZ_GEOGRAPHY_PUB in 12.1.1 or 12.2.2 is reflected here automatically at regeneration time.