Search Results cz_lookup_values




Overview
Explore in AI Chat

Overview

CZ_LOOKUP_VALUES is a Configurator (CZ) module table in Oracle E-Business Suite that provides lookup-value storage for the Oracle Configurator runtime and modeling environment. Oracle Configurator uses lookup values to define the finite domains from which configurable options draw their allowable selections — for example, the permitted colors, sizes, capacities, or feature flags available to a model. Each row in the table represents a single value within a named lookup list, allowing the Configurator engine to resolve selections, validate user input, and drive rules evaluation during a configuration session.

The table resides in the CZ schema and is documented as VALID in both EBS 12.1.1 and 12.2.2. The ETRM metadata classifies CZ_LOOKUP_VALUES heuristically as standalone under the Data Vault model, meaning it does not participate in a foreign-key hub/link/satellite relationship with other CZ objects. In practice, this suggests modeling the table as an independent reference (a lookup dictionary keyed by list name and data value) rather than as a dependent child of a parent entity. The physical schema documents 14 columns in 12.2.2.

Key Information Stored

The primary key CZ_LOOKUP_VALUES_PK is a composite business key composed of two columns:

  • LIST_NAME — the name of the lookup list to which the value belongs; this is the grouping identifier (for example, a list of valid voltage ratings).
  • DATA_VALUE — the individual value contained within that list; the human-readable or seed value presented to the Configurator.

Together, LIST_NAME and DATA_VALUE uniquely identify each lookup value, so no separate surrogate key column is documented; the composite pair functions as the business key and appears in the PK constraint.

Supporting attributes documented in the physical schema include:

Common Use Cases and Queries

Typical uses include reporting on the valid value sets available to a Configurator model, auditing custom values added by implementers, and troubleshooting configuration failures caused by missing or deleted lookup values.

Listing active values for a specific list:

  • SELECT list_name, data_value, value_seq, data_type_id FROM cz.cz_lookup_values WHERE list_name = :p_list AND deleted_flag = 'N' ORDER BY value_seq;

Identifying custom (non-seeded) values introduced during implementation:

  • SELECT list_name, data_value FROM cz.cz_lookup_values WHERE seeded_flag = 'N' AND deleted_flag = 'N';

Reporting all list names and their value counts:

  • SELECT list_name, COUNT(*) FROM cz.cz_lookup_values WHERE deleted_flag = 'N' GROUP BY list_name;

Because the DELETED_FLAG implements logical deletion, all production queries should filter on it to avoid returning retired values. In R12.2 environments, queries can optionally exploit the ZD_EDITION_NAME column during online-patching analysis.

Related Objects

The metadata documents CZ_LOOKUP_VALUES as standalone with no outbound foreign keys. The following objects are the most significant that reference or depend on its lookup data by conceptual join on LIST_NAME and DATA_VALUE:

  • CZ_LOOKUP_LISTS (or equivalent list-header object) — parent list definition keyed by LIST_NAME.
  • CZ_LOOKUP_VALUES_TL — translatable/language overlay, if present, joined on LIST_NAME and DATA_VALUE.
  • CZ_PS_VALUES / model value tables — Configurator model values that resolve to a lookup selection.
  • CZ_CONFIG_HDRS / configuration session tables — runtime sessions consuming lookup values during configuration.
  • CZ_RULE_* rule objects — rules that reference lookup values in their conditions.
  • CZ_LOOKUP_VALUES public view or synonym — the application-facing access path used by Configurator APIs.

DBA review should confirm these relationships against the actual foreign-key catalog, since the ETRM FK classification is heuristic and the table is documented as standalone.