Search Results territory_map

Overview

UTL_GDK is a SYS-owned PL/SQL package shipped as part of the Oracle Database kernel and exposed to the Oracle E-Business Suite environment through a PUBLIC synonym. The name reflects its role as a Globalization Development Kit (GDK) utility: the package provides programmatic access to the locale, language, character set, and territory metadata that Oracle's globalization infrastructure relies upon. In an EBS 12.1.1 or 12.2.2 deployment, this metadata underpins the multilingual and multi-organization behavior of the application, including NLS (National Language Support) settings that govern date, number, and currency formatting, sort order, and character encoding for user sessions and concurrent requests.

Because UTL_GDK belongs to the SYS schema and carries a VALID status in the ETRM inventory, it is treated as a trusted, system-level dependency. The package is classified as OTHER in the API taxonomy, indicating that it is not an EBS application API in the sense of a business-facing interface such as FND or AR packages, but rather a low-level infrastructure component.

Key Procedures and Functions

Three documented subprograms are exposed by UTL_GDK. Parameter lists are intentionally omitted here, as the ETRM metadata does not publish signatures and inventing them would be misleading.

• CHARSET_MAP — Maps character set information to its corresponding globalization attributes. This supports resolution of database and session character set identifiers to the properties Oracle uses when interpreting or converting textual data.
• LANGUAGE_MAP — Provides mapping between language identifiers and their NLS language definitions. It enables code to translate a language code into the language name and related attributes used by the runtime environment.
• TERRITORY_MAP — Resolves territory identifiers to their associated NLS territory definitions, supporting correct formatting of dates, numbers, and currencies according to the conventions of a given country or region.

Collectively these three functions form a lookup layer over Oracle's internal globalization tables, allowing callers to convert between short codes and the descriptive metadata required for locale-sensitive processing.

Tables Accessed

The documented metadata records no tables referenced via APPS synonyms. This is consistent with the package's placement in the SYS schema: UTL_GDK operates against Oracle's internal globalization data dictionary structures rather than the EBS application tables that would normally be visible through APPS-owned synonyms. As a result, there is no application-table dependency to report, and no custom EBS table is read or written by this package.

Usage Notes

The ETRM inventory records that UTL_GDK is referenced by zero other packages, and its dependent objects are limited to the STANDARD package within SYS plus the PUBLIC synonym that exposes it. This pattern indicates that the package is consumed directly by the Oracle kernel and by session-level NLS initialization rather than being called from EBS application code.

In practice, DBAs and developers encounter UTL_GDK through NLS-related troubleshooting, for example when investigating character set conversion issues, language-dependent sort behavior, or territory-specific formatting discrepancies. Custom code should not call UTL_GDK directly; Oracle does not document it as a supported public API, and its signatures may change between database releases. Validation of the package is normally performed with the standard ALTER PACKAGE SYS.UTL_GDK COMPILE or by re-running catalog scripts, and any INVALID status observed in ETRM should be resolved before upgrading from 12.1.1 to 12.2.2, since NLS initialization depends on the package being valid at database startup.