Results for “cz_layoutregions_lkv”

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

Overview

CZ_LAYOUTREGIONS_LKV is a read-only database view owned by the APPS schema in the Oracle E-Business Suite Configurator (CZ) module. It is a lookup-type view (the "_LKV" suffix denotes a lookup view) that resolves the LAYOUT_REGIONS lookup list into a set of descriptive region values, while simultaneously associating each region with a parent subject type drawn from the Configurator parent/child relationship model. The view is marked VALID in ETRM metadata for both 12.1.1 and 12.2.2, and its definition is stable across those releases.

Its principal role is to provide a denormalized, reporting-friendly projection of Configurator layout region data. Rather than requiring report authors or integration developers to join the lookup value tables and the parent/child relationship tables manually, the view pre-composes that join and exposes the derived PARENT_TYPE attribute directly. This makes it useful in BI Publisher reports, custom concurrent programs, and outbound interfaces that must enumerate the regions available within a Configurator model hierarchy.

Underlying Base Objects

The view text documents a two-object join:

• CZ_LOOKUP_VALUES_VL (VIEW) — the Configurator lookup value view, which supplies all descriptive columns and is filtered to LIST_NAME = 'LAYOUT_REGIONS'.
• CZ_PARENT_CHILD_RELS_V (VIEW) — the parent/child relationship view, which supplies the SUBJECT_TYPE value projected as PARENT_TYPE.

The join predicate links the two objects through LKV.NUMERIC_ID_VALUE = REL.OBJECT_TYPE, meaning each layout region's numeric identifier is matched against the object type recorded on the corresponding parent/child relationship. Because both sources are themselves views rather than base tables, this object is a view-over-views construct; the underlying physical lookup and relationship tables are abstracted and should not be accessed directly for region resolution.

Key Columns

• LIST_NAME — always 'LAYOUT_REGIONS' after the view's internal filter; identifies the lookup context.
• DATA_VALUE — the lookup's character value for the region entry.
• NUMERIC_ID_VALUE — the numeric identifier of the region; this is the join key to the relationship view.
• VALUE_SEQ — ordering sequence for presenting regions in a defined display order.
• DATA_TYPE_ID — indicates the data type of the associated value.
• NULL_VALUE_FLAG — indicates whether a null value is permitted or flagged for the entry.
• VALUE_LABEL — the translatable display label for the region.
• VALUE_DESCRIPTION — the longer descriptive text for the region.
• VALUE_NOTES — supplementary notes attached to the lookup value.
• LANGUAGE and SOURCE_LANG — the language context of the returned row, inherited from the VL suffix translation mechanism, enabling multilingual reporting.
• PARENT_TYPE — the subject type of the related parent/child record, aliased from REL.SUBJECT_TYPE; this is the column that answers the typical "parent_type" search and describes the higher-level object to which the layout region belongs.

Common Use Cases and Queries

Typical scenarios include enumerating available layout regions for configuration UI validation, reporting region membership against parent subject types, and driving migration or conversion scripts that need region identifiers and labels.

• Validating that a region value supplied during model maintenance exists in the seeded list.
• Producing a bilingual listing of regions by grouping on LANGUAGE.
• Correlating a region's PARENT_TYPE to determine which parent object governs it.

Sample query:

SELECT LIST_NAME, NUMERIC_ID_VALUE, DATA_VALUE, VALUE_LABEL, PARENT_TYPE, LANGUAGE
FROM APPS.CZ_LAYOUTREGIONS_LKV
WHERE LANGUAGE = USERENV('LANG')
ORDER BY VALUE_SEQ;

Because the view is owned by APPS, access is normally granted through standard Configurator responsibility grants; custom reports should reference it by the APPS synonym and avoid duplicating the join logic against the underlying views.