Search Results cz_verticalalignment_lkv

Overview

CZ_VERTICALALIGNMENT_LKV is a read-only lookup view in the Oracle E-Business Suite Configurator (CZ) product, owned by the APPS schema. Its purpose is to expose the finite set of valid "vertical alignment" values used throughout the Configurator user interface and reporting layer, filtered specifically to the lookup type VERTICAL_ALIGNMENT. The view is a convenience wrapper: rather than requiring developers and integrators to query the generic CZ_LOOKUP_VALUES_VL view and remember to filter on LIST_NAME = 'VERTICAL_ALIGNMENT', the view applies that predicate internally and presents only the relevant rows.

In Oracle EBS 12.1.1 and 12.2.2, CZ_*_LKV views follow a consistent naming convention ("LKV" denotes Lookup View), and are used to render enumerated values in Configurator runtime screens, in generated user interface elements, and in downstream reports and integrations that need to resolve a stored vertical alignment code into its translatable display label. Because it selects from a _VL (translated) source view, the view is language-aware and returns the display label appropriate to the session language.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: CZ_LOOKUP_VALUES_VL (itself an APPS-owned view over the Configurator lookup value tables, which resolve to CZ_LOOKUP_VALUES_B and CZ_LOOKUP_VALUES_TL). CZ_VERTICALALIGNMENT_LKV is therefore a thin projection and filter over that translated lookup view, applying the constant predicate:

• LIST_NAME = 'VERTICAL_ALIGNMENT' — restricts the result set to the vertical alignment lookup type only.

There are no joins, aggregations, or functions applied beyond the row filter, so the view inherits the full column set of CZ_LOOKUP_VALUES_VL and adds no new business logic. It is deterministic and side-effect free, making it safe to use in concurrent programs, BI Publisher data models, and OAF/web service integrations.

Key Columns

The view exposes the columns of the underlying lookup view:

• LIST_NAME — the lookup type identifier; always 'VERTICAL_ALIGNMENT' in this view.
• DATA_VALUE — the internal lookup code stored against configuration data; the value persisted in Configurator records.
• NUMERIC_ID_VALUE — numeric surrogate identifier associated with the lookup value, used where a numeric key is required.
• VALUE_SEQ — display sort sequence controlling the order in which alignment options appear.
• DATA_TYPE_ID — identifies the data type of the underlying value.
• NULL_VALUE_FLAG — indicates whether the entry represents a null/blank option.
• VALUE_LABEL — the translated display label shown to users.
• VALUE_DESCRIPTION — the translated long description of the alignment option.
• VALUE_NOTES — additional translated notes or annotations.
• LANGUAGE — the language of the returned translated columns.
• SOURCE_LANG — the source language of the translation, used by the translation framework.

Common Use Cases and Queries

Typical scenarios include building a dropdown or value set for a Configurator parameter, translating a stored alignment code into a printable label for a report, and validating incoming integration payloads against the permitted values. A simple listing, ordered for presentation, is shown below.

• Populating a UI list of alignment choices ordered by VALUE_SEQ.
• Decoding a stored alignment code into a user-readable label on a report.
• Validation of imported configuration data against permitted alignment values.

Sample SQL:

SELECT DATA_VALUE, VALUE_LABEL, VALUE_DESCRIPTION
FROM APPS.CZ_VERTICALALIGNMENT_LKV
ORDER BY VALUE_SEQ;

To resolve a single stored code to its label:

SELECT VALUE_LABEL
FROM APPS.CZ_VERTICALALIGNMENT_LKV
WHERE DATA_VALUE = :p_alignment_code;

Because the view is a LOV/lookup view rather than a transactional object, no DML should ever be issued against it. Access is by SELECT privilege only, generally granted through the APPS schema and reachable from custom reports, OAF pages, and concurrent programs registered against the CZ product.