Results for “cz_ui_msttmp_pagination_lkv”

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

Overview

The view CZ_UI_MSTTMP_PAGINATION_LKV is an Oracle E-Business Suite database object owned by the APPS schema and registered under the CZ (Configurator) product family. It is a configuration-oriented lookup view that exposes the set of valid pagination values used by the Configurator user interface for master templates. In EBS 12.1.1 and 12.2.2 the object is documented with a status of VALID, confirming it is a supported, queryable view rather than a deprecated or invalidated object.

The name encodes its purpose: CZ identifies the Configurator module, UI indicates the user-interface layer, MSTTMP abbreviates "master template," PAGINATION identifies the functional concern, and the LKV suffix denotes a "list of key values" lookup view. Functionally, the view supplies the discrete option set that governs how records are paged within Configurator master template screens. For reporting and integration purposes, it acts as a stable reference surface over the underlying lookup-value storage, allowing report writers and interface developers to resolve pagination codes without querying the general-purpose lookup tables directly.

Underlying Base Objects

The view is defined entirely over a single documented base object: APPS.CZ_LOOKUP_VALUES_VL, itself a view. The definition is a filtered projection, selecting columns from CZ_LOOKUP_VALUES_VL where LIST_NAME = 'UI_MASTERTEMPLATE_PAGINATION'. As a result, the view inherits the translation-aware behavior of CZ_LOOKUP_VALUES_VL, which conventionally joins lookup values with their translations to expose language-specific labels.

Because the view is built on CZ_LOOKUP_VALUES_VL rather than on a physical table, no data is stored in CZ_UI_MSTTMP_PAGINATION_LKV itself; all rows are derived at query time from the underlying lookup infrastructure governed by the UI_MASTERTEMPLATE_PAGINATION list. This design means changes to the lookup list are reflected immediately in the view, and the view remains free of maintenance overhead or data synchronization concerns.

Key Columns

• LIST_NAME — The lookup list identifier. For this view it is always UI_MASTERTEMPLATE_PAGINATION, constant across all returned rows by virtue of the view's filter predicate.
• DATA_VALUE — The stored internal code for the pagination option; the value persisted in transactional or configuration records.
• VALUE_SEQ — The sequence number controlling display ordering of pagination options.
• DATA_TYPE_ID — Identifier describing the data type of the lookup value.
• NULL_VALUE_FLAG — Indicator of whether a null value is permitted for the lookup.
• VALUE_LABEL — The translated, user-facing label rendered in the Configurator UI.
• VALUE_DESCRIPTION — A longer translated description of the pagination option.
• VALUE_NOTES — Supplementary notes associated with the value.
• LANGUAGE — The language of the returned label and description, enabling multilingual reporting.
• SOURCE_LANG — The source language from which the translation was derived.

Common Use Cases and Queries

Typical uses include decoding pagination codes appearing in Configurator configuration data, populating report parameters with valid pagination choices, and validating inbound interface values against the supported option set.

Retrieve all pagination options in display order:

• SELECT VALUE_SEQ, DATA_VALUE, VALUE_LABEL FROM APPS.CZ_UI_MSTTMP_PAGINATION_LKV ORDER BY VALUE_SEQ;

Restrict to a specific language:

• SELECT DATA_VALUE, VALUE_LABEL, VALUE_DESCRIPTION FROM APPS.CZ_UI_MSTTMP_PAGINATION_LKV WHERE LANGUAGE = USERENV('LANG');

Resolve a stored code to its label:

• SELECT VALUE_LABEL FROM APPS.CZ_UI_MSTTMP_PAGINATION_LKV WHERE DATA_VALUE = :p_code;

Because the view is read-only lookup data with a constant LIST_NAME, queries are lightweight and suitable for embedded use in concurrent programs, BI Publisher data templates, and custom validation routines.