Results for “cz_model_usages_vl”

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

Overview

CZ_MODEL_USAGES_VL is a multilingual (VL) view in the Oracle E-Business Suite Configurator (CZ) module. Configurator is the engine that drives Oracle's model and option selection capabilities within Order Management, allowing customers and order entry clerks to configure complex, made-to-order products by selecting features and options. Within this framework, "model usages" represent the named contexts or classifications under which configuration models are organized and applied — for example, distinguishing how a model is used across different business scenarios or product lines.

The VL suffix follows Oracle's standard multilingual design pattern. The view presents translated descriptive content alongside the base transactional data, restricting the translation join to the session's current language as returned by USERENV('LANG'). This makes CZ_MODEL_USAGES_VL the primary source for reports, concurrent programs, and integrations that need to display model usage information in a user's native language without manually resolving translation rows. It is owned by the APPS schema and carries a VALID status in both ETRM 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over two documented base objects, each referenced through a synonym:

• CZ_MODEL_USAGES — the base table holding the non-translatable attributes of each model usage record, including its identifier, name, note, usage flag, and standard WHO audit columns.
• CZ_MODEL_USAGES_TL — the translation table holding language-specific description text, keyed by MODEL_USAGE_ID and LANGUAGE.

The view text joins these two objects on MODEL_USAGE_ID and filters CZ_MODEL_USAGES_TL.LANGUAGE to the current session language via USERENV('LANG'). It also exposes SOURCE_LANG, the language from which a translation was originally derived. Only one translation row per model usage is therefore visible in any given session, which is the defining behavior of a _VL view.

Key Columns

• MODEL_USAGE_ID — the primary key of the model usage; the join key between the base and translation tables.
• NAME — the internal, language-independent name of the model usage, sourced from the base table.
• DESCRIPTION — the translated descriptive text, sourced from CZ_MODEL_USAGES_TL for the session language.
• LANGUAGE and SOURCE_LANG — the current display language and the original source language of the description.
• NOTE — a free-text annotation on the usage, drawn from the base table.
• IN_USE — a flag indicating whether the model usage is currently active or referenced.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle WHO audit columns tracking record creation and modification.

Common Use Cases and Queries

The view is typically used to populate LOVs, validation queries, and reports that must present model usage descriptions in the user's language. A basic listing retrieves all active usages with their translated descriptions:

• SELECT model_usage_id, name, description FROM cz_model_usages_vl WHERE in_use = 'Y' ORDER BY name;

To resolve a specific usage by name, a parameterized query filters on the NAME column, while the DESCRIPTION is returned already translated for the current session:

• SELECT model_usage_id, description FROM cz_model_usages_vl WHERE name = :p_usage_name;

Because the view enforces the USERENV('LANG') predicate, reports never need to add their own language filter; the display language automatically follows the session's NLS settings. This makes the view suitable for concurrent programs and BI Publisher reports where users expect localized output without additional logic. When querying from outside EBS, the same restrictions apply, and the reporting user must have appropriate privileges on the APPS synonyms.