Results for “delete_geo_identifier”

20 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

HZ_GEOGRAPHY_PUB_UIW is a public PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that provides the programmatic interface for maintaining geography master data within the Oracle Trading Community Architecture (TCA) and Oracle Receivables geography model. Geography data underpins territory assignment, tax jurisdiction determination, address validation, and location-based reporting throughout EBS. The package serves as a user-interface wrapper ("UIW") that centralizes validation, identifier management, hierarchical relationships, and zone/range definitions for geography records, allowing forms, concurrent programs, and custom integrations to insert and update geography structures consistently without directly manipulating the underlying TCA tables.

The package header carries the version string ARHGEOWS.pls 120.2 2006/02/17, confirming its classification under the Receivables (AR) product family while remaining exposed through the shared HZ public naming convention. Because it is an OTHER-classified API rather than a fully supported public interface, customers and integrators should treat it as an internal building block used primarily by seeded EBS forms.

Key Procedures and Functions

The ETRM documentation identifies eleven documented entry points, organized around master geography definition, hierarchical relationships, identifiers, and geographic ranges and zones:

  • CREATE_MASTER_GEOGRAPHY — Creates a new master geography record, accepting a master geography structure containing geography type, name, code, code type, effective dates, provider, language, timezone, and module/application context.
  • UPDATE_GEOGRAPHY — Modifies an existing master geography record.
  • CREATE_MASTER_RELATION — Establishes a parent-child relationship between two geographies, using the master relation record type with geography ID, parent geography ID, and effective date range.
  • UPDATE_RELATIONSHIP — Maintains or modifies an existing geography hierarchy relationship.
  • CREATE_GEO_IDENTIFIER — Adds an identifier (such as a postal code, FIPS code, or alternate key) to a geography, supporting identifier type, subtype, value, provider, primary flag, and language.
  • UPDATE_GEO_IDENTIFIER — Modifies an existing geography identifier, including the new identifier value and subtype fields added under Bug 4578867.
  • DELETE_GEO_IDENTIFIER — Removes an identifier associated with a geography.
  • CREATE_GEOGRAPHY_RANGE — Defines a numeric or alphanumeric range of geography identifiers falling within a zone.
  • UPDATE_GEOGRAPHY_RANGE — Modifies an existing geography range definition.
  • CREATE_ZONE_RELATION — Associates a geography or range with a zone.
  • CREATE_ZONE — Creates the zone container used to group geographies and ranges.

Tables Accessed

The documented table reference is limited: the package operates against PLITBLM via APPS synonyms. PLITBLM is a generic PL/SQL index-by table and bulk-collection utility table used in EBS for array processing and does not represent the primary geography storage. In practice the procedural logic persists data into the TCA geography tables (HZ_GEOGRAPHIES, HZ_GEOGRAPHY_IDENTIFIERS, HZ_GEOGRAPHY_HIERARCHIES, HZ_GEOGRAPHY_RANGES, and related zone structures). These DML targets are not enumerated in the ETRM excerpt, so implementers should confirm actual table dependencies before extending the package.

Usage Notes

HZ_GEOGRAPHY_PUB_UIW is invoked predominantly by Oracle Receivables and Trading Community geography maintenance forms, and it is referenced by one other documented package. Typical invocation patterns include:

  • EBS Forms — Geography and zone setup forms call these procedures to create and maintain master geography data.
  • Custom Code — Integrators may call the procedures directly when bulk-loading geography hierarchies or identifier sets, although the OTHER classification means Oracle does not guarantee interface stability across releases.
  • Concurrent/Data Load Programs — Bulk geography and zone imports may leverage CREATE_MASTER_GEOGRAPHY and CREATE_GEO_IDENTIFIER as their persistence layer.

Because the package has not been re-certified as a supported public API, development teams should wrap calls in exception handling, verify version compatibility between 12.1.1 and 12.2.2, and avoid assumptions about parameter signatures that are not confirmed in ETRM documentation.