Search Results configuration_constraint_id

Overview

CZBV_CONFIGURATION_CONSTRAINTS is a read-only Oracle EBS view that presents configuration constraint definitions used by Oracle Configurator within the Bills of Material (BOM) product family. The view exposes the master constraint records stored in the CZ_CONSTRAINTS table, joined to their translatable message text and to the constraint type lookup, so that reporting queries and integrations can obtain constraint identity, classification, and user-facing message text in a single query.

The ETRM metadata records the object title as "View: CZBV_CONFIGURATION_CONSTRAINTS" under product BOM – Bills of Material, with a description of "- Retrofitted." The metadata further states "Not implemented in this database," which indicates that in the documented environment the view is defined at the interface level but is not deployed. The "Retrofitted" designation reflects Oracle's practice of rebuilding seeded views during upgrades so they continue to conform to the current underlying schema. The view is marked WITH READ ONLY, so it can be used for query and integration purposes but cannot be used to maintain constraint data.

Underlying Base Objects

The view text is defined over three base objects:

• CZ_CONSTRAINTS (CO) — the master table holding configuration constraint definitions, including constraint type and descriptive attributes.
• CZ_CONSTRAINT_MESSAGES_TL (COTL) — the translatable message text table, joined on CONSTRAINT_ID and restricted to the session language derived from USERENV('LANGUAGE').
• FND_COMMON_LOOKUPS (COLO) — the standard EBS lookup table, joined on CONSTRAINT_TYPE = LOOKUP_CODE with LOOKUP_TYPE = 'CZ_CONSTRAINT_TYPES' and APPLICATION_ID = 702.

The joins require CO.CONSTRAINT_ID = COTL.CONSTRAINT_ID and CO.CONSTRAINT_TYPE = COLO.LOOKUP_CODE. The lookup join is conceptually the source of the "constraint type" that users reference when searching for "cz_constraint_types." Notably, the ETRM metadata lists no referenced base objects ("none documented") for the deployment in question, consistent with the "Not implemented in this database" entry.

Key Columns

• CONFIGURATION_CONSTRAINT_ID / CONSTRAINT_ID — unique identifier for the constraint, returned in the view as CO.CONSTRAINT_ID and surfaced in the column list under the alias CONFIGURATION_CONSTRAINT_ID.
• NAME — the internal name of the configuration constraint.
• DESCRIPTION — free-form description of the constraint's purpose.
• TYPE — the constraint type derived from the CZ_CONSTRAINT_TYPES lookup; the view text exposes this as COLO.MEANING.
• MESSAGE_TEXT — the translated message presented to the user when the constraint is evaluated, sourced from CZ_CONSTRAINT_MESSAGES_TL.
• CREATED_DATE / CREATED_BY / LAST_UPDATED_DATE / LAST_UPDATED_BY — standard audit columns reflecting creation and last modification of the constraint record.

Common Use Cases and Queries

Typical uses include auditing configuration constraints across models, producing extracts of constraint definitions with their localized messages, and validating that every constraint type referenced resolves to a valid CZ_CONSTRAINT_TYPES lookup entry. A representative query is:

SELECT configuration_constraint_id, name, description, type, message_text FROM czbv_configuration_constraints WHERE type = 'Include';

To enumerate the available constraint types referenced by the view, query the lookup directly:

SELECT lookup_code, meaning FROM fnd_common_lookups WHERE lookup_type = 'CZ_CONSTRAINT_TYPES' AND application_id = 702;

Because the view is read-only and resolves the language at runtime, integrations should be aware that MESSAGE_TEXT is filtered to the session language; environments with missing translations may return no row for a given constraint. Where the view is not implemented, as recorded in the ETRM metadata, the equivalent query should be constructed directly against CZ_CONSTRAINTS, CZ_CONSTRAINT_MESSAGES_TL, and FND_COMMON_LOOKUPS.