Search Results fcl_type

Overview

The CZ_CONSTRAINTS_VL view is a Bills of Material (BOM) module dictionary object that exposes constraint definitions used by Oracle's configuration and rules engine (the CZ schema). It presents the header-level attributes of each constraint along with its translated message text, its lookup-derived constraint type name, and a computed maximum sequence value. The "_VL" suffix indicates a "view with language" — the view joins to a translation (_TL) table and filters rows by the session's language, so consumers see the message text in the appropriate installed language.

Because the view bridges a base constraints table with lookup and translation data, it is the natural reporting and integration entry point for anyone auditing, exporting, or querying constraint metadata, rather than querying the underlying transactional tables directly.

Underlying Base Objects

The view is defined over three documented base objects joined in a single SELECT:

• CZ_CONSTRAINTS (aliased B): the primary base table holding constraint headers.
• CZ_CONSTRAINT_MESSAGES_TL (aliased T): the translation table supplying MESSAGE_TEXT, filtered to the language derived from USERENV('LANGUAGE').
• FND_COMMON_LOOKUPS (aliased FCL_TYPE): the lookup table supplying the constraint type meaning, restricted to LOOKUP_TYPE = 'CZ_CONSTRAINT_TYPES' and APPLICATION_ID = 702.

The join conditions require B.CONSTRAINT_ID = T.CONSTRAINT_ID and FCL_TYPE.LOOKUP_CODE = B.CONSTRAINT_TYPE. The view also invokes the PL/SQL function CZDVCONS.CONSTRAINT_MAX_SEQUENCE(B.CONSTRAINT_ID) to derive the MAX_SEQUENCE column. Note the ETRM metadata records that this view is "Not implemented in this database," and references no documented base objects in the 12.2.2 metadata — so the view text above is the authoritative structural source.

Key Columns

• ROW_ID: the underlying row identifier of CZ_CONSTRAINTS.
• CONSTRAINT_ID: primary key and the join key into messages and the max-sequence function.
• NAME / DESCRIPTION: constraint identifiers and descriptive text.
• CONSTRAINT_TYPE / CONSTRAINT_TYPE_NAME: the lookup code and its decoded meaning from FND_COMMON_LOOKUPS.
• VALID_FLAG / MESSAGE_LEVEL: constraint validity and violation severity.
• MESSAGE_TEXT: the language-specific message returned to the user on violation.
• MAX_SEQUENCE: derived via CZDVCONS.CONSTRAINT_MAX_SEQUENCE — the highest sequence value assigned to the constraint's rules/elements. This is the value users search for when investigating "max_sequence" and is not stored physically on the base table.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15: the standard descriptive flexfield (DFF) columns.
• Audit columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include auditing constraint definitions, exporting messages for localization review, and inspecting the computed maximum sequence for capacity or ordering checks.

• List constraints with their type names and message text:

SELECT constraint_id, name, constraint_type_name, valid_flag, message_text
FROM   cz_constraints_vl
ORDER  BY name;

• Find constraints by maximum sequence, the "max_sequence" search topic:

SELECT constraint_id, name, constraint_type, max_sequence
FROM   cz_constraints_vl
WHERE  max_sequence IS NOT NULL
ORDER  BY max_sequence DESC;

• Filter by validity and severity to locate active errors:

SELECT constraint_id, name, message_level, message_text
FROM   cz_constraints_vl
WHERE  valid_flag = 'Y';

Because MAX_SEQUENCE is computed per row via a PL/SQL function, queries filtering or ordering on it can be relatively expensive on large constraint sets; include additional predicates such as CONSTRAINT_ID whenever possible.