Search Results update_zone_type




Overview
Explore in AI Chat

Overview

APPS.HZ_GEO_STRUCTURE_PUB_UIW_JW is a PL/SQL package within the Oracle E-Business Suite Trading Community Architecture (TCA) geography model. It belongs to the HZ (Trading Community) schema family and supports the maintenance of the Geography Structure — the hierarchical framework of countries, states, provinces, counties, cities, and zones used throughout Oracle Receivables, Order Management, and other modules for address validation and tax jurisdiction determination.

The suffix "UIW" indicates that this is a User Interface Wrapper — a generated or wrapper-style package that exposes a stable, flattened interface over the underlying public geography APIs, typically to insulate forms or concurrent programs from internal signature changes. The "_JW" suffix reflects the internal generator/utility convention used within Oracle development. In this role the package does not implement geography business logic itself; it delegates to the internal HZ_GEO_STRUCTURE_PUB layer while presenting parameters in a simplified positional form (p1_a0 through p1_a6).

The package is classified as OTHER in ETRM, is owned by APPS, and is referenced by no other documented packages, reflecting its role as a terminal caller-facing wrapper rather than a shared dependency.

Key Procedures and Functions

  • ROSETTA_TABLE_COPY_IN_P0 / ROSETTA_TABLE_COPY_OUT_P0 — Utility procedures that convert between the PL/SQL associative-array type used by the package (HZ_GEO_STRUCTURE_PUB_UIW.INCL_GEO_TYPE_TBL_TYPE) and the JTF_VARCHAR2_TABLE_100 collection type. They marshal geography-type lists into and out of the wrapper interface and contain no business logic.
  • CREATE_GEOGRAPHY_TYPE — Creates a geography type definition (for example, a country, state, or city classification level) within the geography structure. It executes the create operation and returns the standard TCA return status, message count, and message data.
  • CREATE_GEO_STRUCTURE — Establishes a geography structure, binding a geography type to its parent node to define the hierarchical level-to-level relationship. This is the core call for building the structural map of a country's geography.
  • CREATE_GEO_REL_TYPE — Creates a geography relationship type, defining the semantic link permitted between two geography entities or levels. The procedure additionally returns the newly created relationship type identifier through x_relationship_type_id, making it the only wrapper routine that surfaces a generated primary key to the caller.
  • CREATE_ZONE_TYPE — Creates a zone type (a grouping of geography types used for sales territory, tax, or service coverage definitions). It accepts the included geography types as a JTF_VARCHAR2_TABLE_100 collection, demonstrating the collection-marshalling pattern that ROSETTA_TABLE_COPY_IN_P0 supports.
  • UPDATE_ZONE_TYPE — Modifies an existing zone type, accepting an in-out object version number for optimistic locking control together with the revised inclusion list.

Tables Accessed

The documented table reference is the APPS synonym PLITBLM, a legacy Oracle-supplied table used by the PL/SQL table/host-array utility mechanism. Access to this object is incidental to row-set handling rather than to geography persistence. The actual geography records are written by the underlying public API layer into the HZ_GEOGRAPHY_TYPE, HZ_GEO_STRUCTURE, HZ_RELATIONSHIP_TYPE, and HZ_ZONE_TYPE tables; these are reached indirectly and are not itemized in the ETRM metadata for this wrapper.

Usage Notes

Because this package is a UI wrapper, it is generally not invoked directly by customer code. It is called from TCA geography setup forms and from internal Oracle concurrent or initialization routines that need a parameter-stable entry point for creating geography types, structures, relationship types, and zone types. Parameters p1_a0 through p1_a6 are positional placeholders whose meanings vary per procedure and are populated by the calling layer.

When extending or debugging geography setup, developers should prefer the documented public API HZ_GEO_STRUCTURE_PUB over this wrapper, since the wrapper's flattened signature offers no named-parameter clarity and carries no documented support commitment. The presence of the ROSETTA_TABLE_COPY procedures and the JTF_VARCHAR2_TABLE_100 parameters indicates that custom callers must supply geography-type lists as that specific collection type. Customizations that call CREATE_GEO_REL_TYPE should capture x_relationship_type_id for subsequent use, and any update path must respect the object version number to avoid lost-update conflicts.