Results for “source_lang”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CZ_MODEL_USAGES_TL is a translation (TL) table within the Oracle EBS Configurator (CZ) module, owned by the CZ schema. It stores translatable, language-specific descriptions for model usages defined in the Configurator. Model usages represent the different ways a configuration model can be consumed or applied — for example, as a sales-order configurable item, a purchase-order item, or a work-in-process assembly — and this table provides the human-readable descriptive text associated with each usage in each installed language. The table carries a status of VALID in the referenced ETRM 12.2.2 documentation.

From a dimensional modeling perspective, the Data Vault classification mined from the foreign-key structure is described as satellite-leaning. This suggests treating CZ_MODEL_USAGES_TL as an attribute-bearing satellite attached to the parent CZ_MODEL_USAGES entity, keyed by the parent's identifier plus the language discriminator, rather than as an independent hub or link. This is a modeling suggestion drawn from the FK topology, not an enforced EBS constraint.

Key Information Stored

The table contains four documented columns. Its primary key is the composite CZ_MODEL_USAGES_TL_PK, defined over (MODEL_USAGE_ID, LANGUAGE), which also serves as the unique index and business-key candidate. The columns are as follows:

• MODEL_USAGE_ID — the surrogate identifier of the parent model usage; a foreign key to CZ_MODEL_USAGES. Together with LANGUAGE it forms the primary key.
• LANGUAGE — the language code identifying the translation row's locale; the second component of the composite primary key.
• SOURCE_LANG — the source language from which the translation was derived or seeded, supporting translation-management and reconciliation processes.
• DESCRIPTION — the translatable, language-specific description text for the model usage; the core attribute payload of this satellite table.

The surrogate identifier (MODEL_USAGE_ID) should not be confused with the business-key candidate: uniqueness of the natural key is achieved only through the combination of MODEL_USAGE_ID and LANGUAGE, since a single usage may hold many translated descriptions.

Common Use Cases and Queries

Typical scenarios include retrieving the localized description of a model usage for a given session language, validating translation completeness across locales, and joining usage descriptions into configuration reporting. A representative query resolves the description for a specific language:

• SELECT mu.model_usage_id, mutl.description FROM cz_model_usages_tl mutl, cz_model_usages mu WHERE mutl.model_usage_id = mu.model_usage_id AND mutl.language = :session_language;
• Coverage audit: SELECT l.language_code, COUNT(mutl.model_usage_id) FROM fnd_languages l LEFT JOIN cz_model_usages_tl mutl ON mutl.language = l.language_code GROUP BY l.language_code;
• Untranslated detection: SELECT model_usage_id FROM cz_model_usages WHERE model_usage_id NOT IN (SELECT model_usage_id FROM cz_model_usages_tl WHERE language = :target_language);

These patterns support localization QA, reporting against Configurator usage definitions, and integration extracts where display text must be resolved per locale.

Related Objects

The following objects are most significant to CZ_MODEL_USAGES_TL, anchored by the documented foreign-key relationships:

• CZ_MODEL_USAGES — parent table; joined on CZ_MODEL_USAGES_TL.MODEL_USAGE_ID = CZ_MODEL_USAGES.MODEL_USAGE_ID. This is the primary FK relationship and the base entity for the satellite.
• CZ_MODEL_USAGES_TL_PK — the composite primary-key unique index over (MODEL_USAGE_ID, LANGUAGE).
• Other CZ Configurator TL tables — sibling translation tables (for models, features, and options) that follow the same TL pattern and are frequently joined for consolidated localization reporting.
• FND_LANGUAGES — supplies the installed language list used to reconcile LANGUAGE values and audit translation coverage.
• CZ Configurator public APIs and concurrent programs — procedures that create or maintain model usages, and translation-import processes that populate LANGUAGE-specific DESCRIPTION rows.

Because the object is a narrow translation table, its principal dependency remains the parent CZ_MODEL_USAGES; other references are indirect and driven by localization and reporting workflows.