Search Results cz_localized_texts

Overview

The CZ_LOCALIZED_TEXTS table is a core data object within the Oracle E-Business Suite Configurator (CZ) module. It functions as the central repository for all user-facing text strings displayed in the Configurator runtime interface. Its primary role is to enable the multi-language support essential for global deployments by storing translated versions of UI labels, messages, prompts, and other descriptive text. By decoupling textual content from application logic and storing it in a dedicated table, the Configurator can dynamically serve the appropriate language based on a user's session locale, facilitating a localized user experience.

Key Information Stored

The table's structure is designed to map unique text identifiers to their language-specific content. The critical columns, as indicated by the primary and foreign key constraints, are:

• INTL_TEXT_ID: A foreign key linking to the CZ_INTL_TEXTS table. This column holds the unique identifier for a specific piece of text (e.g., a label for a feature) that requires translation.
• LOCALE_ID / LANGUAGE: These columns identify the language and locale for the stored text. LOCALE_ID is a foreign key to the CZ_LOCALES table, which defines supported languages and territories. The primary key constraint includes LANGUAGE, signifying its critical role in uniquely identifying a localized entry for a given text ID.
• Text Content Column(s): While the provided metadata does not list all columns, a table of this nature typically contains at least one column (e.g., TEXT) to store the actual translated string corresponding to the INTL_TEXT_ID and LOCALE_ID combination.

Common Use Cases and Queries

This table is primarily accessed by the Configurator engine during runtime to render the UI. Common administrative and development use cases include:

• Translation Management: Extracting untranslated text for a new language or verifying translation coverage. A typical query would join CZ_LOCALIZED_TEXTS with CZ_INTL_TEXTS and CZ_LOCALES to find text IDs missing entries for a specific locale.
• UI Text Reporting and Validation: Generating reports of all displayed text for a given model or module to ensure consistency and correctness. This often involves complex joins through the CZ_INTL_TEXTS table to related configurator model objects.
• Troubleshooting: Querying for specific UI labels that appear incorrectly to identify missing or erroneous translations. A sample pattern: SELECT * FROM cz_localized_texts WHERE intl_text_id = (SELECT intl_text_id FROM cz_intl_texts WHERE key = '&KEY') AND language = '&LANG_CODE';

Related Objects

The CZ_LOCALIZED_TEXTS table has integral relationships with other key Configurator schema objects, as defined by its foreign key constraints:

• CZ_INTL_TEXTS: This is the parent table, providing the master list of text identifiers (INTL_TEXT_ID) that require localization. The relationship ensures referential integrity for all translatable text.
• CZ_LOCALES: This table defines all application-supported languages and locale settings. The foreign key on LOCALE_ID validates that localized text is only stored for a properly defined locale.
• Configurator Runtime Engine: While not a database object, the runtime engine is the primary consumer of data from this table, querying it to fetch the correct text strings for the user's session context.