Search Results fill_values

Overview

HZ_GNR_MAP10000 is an Oracle Trading Community Architecture (TCA) generated package body within the APPS schema, created to support geoName referencing (GNR) functionality in Oracle E-Business Suite. The package was generated automatically by TCA on 30 December 2011 and carries the standard Oracle Corporation copyright header. Its principal business role is to provide an abstraction layer between geography-related usage types and their corresponding validation APIs, allowing the TCA geography framework to invoke the correct validation routine dynamically based on a usage code stored in the reference data.

Organizations implementing Oracle EBS 12.1.1 or 12.2.2 with multiple geography-dependent modules — such as Tax, Human Resources, and Receivables — rely on this package to ensure that geography validation dispatches to the appropriate business logic without hard-coded conditional branching in each consuming module. The package is one of a numbered family of generated map packages (indicated by the "10000" suffix), each supporting a discrete set of geoName reference mappings.

Key Procedures and Functions

• GET_USAGE_API — Accepts a usage code and returns the name of the validation API associated with that usage. Internally it iterates the global usage table (G_USAGE_TBL) and maps specific usage codes to their API names; for example, the usage code 'GEOGRAPHY' resolves to validateGeo, 'TAX' resolves to validateTax, and any other usage resolves to a generated name of the form 'validate' concatenated with the usage ID. This function forms the dispatch mechanism that the rest of the geoName referencing framework depends upon.
• VALIDATEGEO — The validation routine designated for geography usage. It is the target invoked when GEOGRAPHY usage validation is required and is responsible for verifying that the supplied geography reference satisfies TCA geoName referencing rules.
• VALIDATETAX — The validation routine designated for tax usage. It is invoked when a geography reference must be validated in a tax context, ensuring the reference is acceptable to tax-related geography processing.

No parameter lists are documented in the available metadata; the procedures and function should be treated as internal, generated entry points rather than supported public APIs. Private global variables declared in the body include map records, map detail tables, usage tables, usage detail tables, and MDU (multi-detail usage) tables typed from HZ_GNR_UTIL_PKG, confirming the package is tightly coupled to the shared GNR utility package.

Tables Accessed

The only documented table referenced through APPS synonyms is PLITBLM. This is an internal TCA geoName referencing structure used by the generated code to resolve and cache location and geography reference data during map operations. Because the package is generated and maintained by TCA, its table usage is implementation-internal; custom code should not depend on PLITBLM directly within this context. Additional data structures are held in memory through the HZ_GNR_UTIL_PKG record and table types declared as package globals rather than being read directly from base tables.

Usage Notes

HZ_GNR_MAP10000 is not intended for direct invocation by end users or custom applications. It is called by the TCA geoName referencing engine and by other TCA-generated components during geography validation flows. Invocation typically occurs indirectly: a form or concurrent program triggers geography validation, the GNR framework resolves the usage, and GET_USAGE_API dispatches to validateGeo, validateTax, or a generated validate routine. ETRM documents zero other packages referencing this body, indicating it functions as a leaf-level generated component within the HZ_GNR_UTIL_PKG framework.

The search term "check_gnr_for_usage" does not correspond to any documented procedure in this package. It most likely reflects a conceptual or legacy check within the broader GNR usage-validation mechanism rather than a concrete entry point in HZ_GNR_MAP10000. Consultants troubleshooting geoName reuse or validation errors should treat this package as read-only generated code and direct remediation toward the TCA geography setup, the usage definitions consumed by HZ_GNR_UTIL_PKG, and the underlying geography reference data, rather than attempting to modify the package body.