Search Results cz_lookups




Overview
Explore in AI Chat

Overview

CZ_LOOKUPS is a Configurator-specific view owned by the APPS schema in Oracle E-Business Suite. It exposes the set of lookup values that belong to the Configurator (CZ) product family, which is the engine behind Oracle Configurator and its integration with order management, bills of material, and related modules. Rather than presenting a generic lookup listing, the view filters the shared FND_LOOKUP_VALUES repository to only those rows owned by the Configurator application, identified internally by application identifier 708.

In Oracle EBS 12.1.1 and 12.2.2, lookup codes drive validation, list-of-values behavior, and configurator rule processing. The CZ_LOOKUPS view provides a read-only, language-aware, and security-aware projection of the Configurator lookup values, making it suitable for reporting, diagnostics, data migration validation, and integration queries where the raw base table would return values for every application. Because it is a view and not a table, it holds no data of its own; all values are resolved at query time from its underlying sources.

Underlying Base Objects

The view is defined over the FND_LOOKUP_VALUES synonym, with a reference to the FND_GLOBAL package. The documented view text is:

FND_LOOKUP_VALUES is the central lookup repository in EBS, storing every lookup type and code across all applications and languages. The VIEW_APPLICATION_ID = 708 predicate restricts the result set to Configurator-owned lookups. The call to FND_GLOBAL.LOOKUP_SECURITY_GROUP enforces row-level security based on the lookup security group assigned to the current user, so results are automatically scoped to the responsibility and security context. Together these conditions ensure the view returns only the Configurator lookups the current session is entitled to see, in the session language.

Key Columns

  • LOOKUP_TYPE — The lookup category or class name, such as the Configurator-specific lookup types used to classify rule, feature, or option values.
  • LOOKUP_CODE — The internal code stored in tables and referenced by validation logic; this is the value written to dependent records.
  • MEANING — The user-facing, translated display text corresponding to the lookup code.
  • DESCRIPTION — Optional extended text describing the purpose or usage of the lookup value.
  • ENABLED_FLAG — Indicates whether the lookup value is active (Y) or disabled (N) for selection and validation.
  • START_DATE_ACTIVE — The date from which the lookup value becomes effective; may be null for immediate activation.
  • END_DATE_ACTIVE — The date after which the lookup value is no longer effective; may be null for open-ended validity.

Common Use Cases and Queries

Typical uses include validating that expected Configurator lookups are defined and enabled, generating translated reference listings, and troubleshooting configuration behavior caused by disabled or expired codes. A simple query to list all enabled Configurator lookups is:

  • SELECT LOOKUP_TYPE, LOOKUP_CODE, MEANING FROM CZ_LOOKUPS WHERE ENABLED_FLAG = 'Y' ORDER BY LOOKUP_TYPE, LOOKUP_CODE;

To examine the effective date window of active values, filter on the date columns:

  • SELECT LOOKUP_TYPE, LOOKUP_CODE, MEANING, START_DATE_ACTIVE, END_DATE_ACTIVE FROM CZ_LOOKUPS WHERE NVL(START_DATE_ACTIVE, SYSDATE) <= SYSDATE AND NVL(END_DATE_ACTIVE, SYSDATE+1) > SYSDATE;

Because the view applies USERENV('LANG') and the lookup security group function, results automatically reflect the session language and the current user's security context. This makes CZ_LOOKUPS particularly useful in multilingual environments and in reports where row-level lookup security must be honored. It does not expose the underlying FND_LOOKUP_VALUES columns for application, territory, or attribute categories, so queries needing those details should target the base table directly.