Search Results update_gnr

Overview

ZX_HR_LOCATIONS_GNR_HOOK is a public PL/SQL package owned by the APPS schema that implements the geography name reference (GNR) hook interface for HR locations within Oracle E-Business Suite. Its role is to keep the geography reference data attached to a location synchronized with the underlying geography model maintained by the Oracle E-Business Suite tax and geography engine (ZX and HZ modules). The package name reflects this purpose: "HR locations" identify the source entity, and "GNR hook" indicates that the package is a callback point invoked by the geography name reference framework rather than a directly called application API.

In EBS 12.1.1 and 12.2.2, the geography name reference infrastructure resolves an address into one or more geography hierarchy nodes (for example, country, region, city, postal code) according to a configurable geography structure and mapping. When a location record in HR (PER_LOCATIONS) is created or modified, the framework must produce, refresh, or invalidate the corresponding geography reference rows. ZX_HR_LOCATIONS_GNR_HOOK provides the two entry points the framework uses to perform that synchronization. The package is declared with AUTHID CURRENT_USER, so it executes with the privileges of the invoking user and relies on the caller's access to the underlying HZ and ZX objects through APPS synonyms.

Key Procedures and Functions

• CREATE_GNR — Invoked when a new HR location is created. It accepts the location identifier together with the address attributes that participate in geography resolution: country, up to three region segments, town or city, postal code, and a style. The procedure resolves those attributes against the geography model and generates the geography name reference data for the new location, so that address validation, tax determination, and geography-based reporting can use the location immediately after creation.
• UPDATE_GNR — Invoked when an existing HR location is changed. It receives the new address attribute values (country, region_1 through region_3, town or city, postal code, and style) together with the corresponding old (suffixed "_o") values. Comparing old and new values allows the procedure to determine which geography references require regeneration and which can be retained, thereby avoiding unnecessary hierarchy lookups and preserving reference integrity for address components that did not change.

The package exposes no documented functions and no additional public procedures beyond these two. Both are declared in the package specification, which makes them callable by the geography name reference framework and by any custom code that legitimately needs to resynchronize location geography data.

Tables Accessed

All documented tables are reached through APPS synonyms and belong to the Oracle Trading Community Architecture and tax geography model:

• HZ_GEOGRAPHIES, HZ_HIERARCHY_NODES, and HZ_GEO_STRUCT_MAP / HZ_GEO_STRUCT_MAP_DTL — read to resolve the supplied address attributes to geography hierarchy nodes and to interpret the configured geography structure and mapping rules.
• HZ_ADDRESS_USAGES and HZ_ADDRESS_USAGE_DTLS — read or written to associate the resolved geography reference with the address usage of the HR location.
• PLITBLM — the standard EBS PL/SQL index-by table used as a transient structure inside the package for holding collections of identifiers during processing; it is not a persistent application table.

No persistent writes to HR tables themselves are documented for this package; the HR location of record remains PER_LOCATIONS, while this hook maintains the geography-side reference data.

Usage Notes

This package is an integration hook rather than a general-purpose API. It is referenced by two other packages in the ETRM inventory and is normally invoked indirectly by the geography name reference framework when HR location records are inserted or updated. In practice the calls originate from the location maintenance flows in Oracle HRMS and from the address validation processing owned by the tax and TCA geography components.

Because the hook is driven by the geography framework, direct invocation by custom code is uncommon and should be limited to controlled resynchronization scenarios, such as repairing geography references after bulk location data loading that bypassed the standard location forms. Required setup includes a correctly defined geography structure and geography structure mapping for the relevant country; without that configuration, the hook cannot derive the expected hierarchy nodes. The package header identifies a base version of 120.1 with a 2006 build date, indicating that the interface has remained stable across the 12.1.1 and 12.2.2 releases.