Search Results hz_gnr_pub




Overview
Explore in AI Chat

Overview

HZ_GNR_PUB is a public PL/SQL package in the APPS schema of Oracle E-Business Suite that supports geocode name reference (GNR) processing for the Trading Community Architecture (TCA) and related location, party site, and tax assignment modules. The "PUB" suffix designates the package as a public API layer. Its documented API classification is PUB, meaning its procedures and functions are intended to be invoked by other application modules, forms, and custom code rather than being restricted to internal package use.

Functionally, HZ_GNR_PUB serves as the validation and reference-resolution layer between higher-level location and party APIs and the underlying TCA geography structures. It validates location addresses against geography name reference data, determines the address validation level applicable to a given location context, and records geocode name reference transactions in the appropriate log table. The package participates in the geocode validation workflow used by location services, tax assignment, and HR location processing.

Key Procedures and Functions

  • PROCESS_GNR — The principal entry point for geocode name reference processing. It drives the GNR workflow, coordinating validation and logging of geography name reference activity for a location or address context.
  • VALIDATELOC — Performs validation of a location against geography name reference rules and structures, determining whether the supplied address components conform to the defined geography hierarchy.
  • GET_ADDR_VAL_LEVEL — Returns the address validation level applicable to a given location or address context, enabling callers to determine the degree of validation that applies or has been applied.
  • GET_ADDR_VAL_STATUS — Returns the address validation status, allowing callers to query the current validation state of an address or location for downstream processing decisions.

The ETRM metadata documents five procedures/functions in total for this package; the four named above are the documented API routines associated with geocode name reference processing.

Tables Accessed

  • HZ_GEO_NAME_REFERENCE_LOG — The log table for geography name reference activity. PROCESS_GNR and related routines write to this table to record reference and validation transactions, providing an audit trail of GNR processing.
  • HZ_GEO_STRUCTURE_LEVELS — Defines the levels within a geography structure. This table is read to establish the hierarchy and validation context required by VALIDATELOC and the address validation level/status functions.
  • HZ_LOCATIONS — The TCA locations table storing address and location records. It supplies the address data validated by this package and is central to the address validation level and status lookups.

Access is performed through APPS synonyms, consistent with standard EBS public API design.

Usage Notes

HZ_GNR_PUB is referenced by seven other packages, including HZ_GNR_PKG, HZ_GNR_PVT, HZ_LOCATION_SERVICES_PUB, HZ_LOCATION_V2PUB, HZ_TAX_ASSIGNMENT_V2PUB, AST_PARTY_LOCATIONS_V2PUB, and ZX_HR_LOCATIONS_GNR_HOOK. This dependency pattern indicates that the package is invoked indirectly through location and party site APIs, tax assignment processing, and HR location geocode hooks rather than being called directly by end users.

Typical invocation occurs during address validation and geocode name reference resolution workflows triggered by location creation or update in TCA-based forms, by concurrent geocode validation programs, and by public APIs such as HZ_LOCATION_V2PUB. Custom code integrating with location or tax assignment functionality may call the public routines directly to obtain validation levels and statuses or to trigger GNR processing. The package depends on FND_API and the SYS.STANDARD package, reflecting its conformance to the standard Oracle API error-handling and return-status conventions. As a public API, callers should expect standard API parameters, including return status and message handling, and should not modify the package or its underlying tables directly.