Results for “czbv_config_constraint_clauses”

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

Overview

CZBV_CONFIG_CONSTRAINT_CLAUSES is a read-only database view in the Oracle E-Business Suite Bills of Material (BOM) module. It exposes the individual clauses that make up configuration constraints used by Oracle Configurator and the Configure-to-Order (CTO) process. In EBS, configuration constraints define the rules that govern how configurable items may be assembled — for example, which options are compatible, which are mutually exclusive, or which features must be selected together. The CZBV_ prefix identifies this object as a "B" (business) view created during a retrofitting effort to standardize the naming and structure of constraint-related objects that were historically exposed under the CZ_ prefix. The underlying CZ_CONSTRAINT_CLAUSES table stores each discrete logical clause (expressed as a comparison between functions, database objects, or attributes, joined by operators), and CZ_CONSTRAINTS stores the parent constraint header. This view joins the two and exposes a flattened, human-readable perspective. It is primarily used for reporting, data extraction, and integration — for instance, exporting constraint definitions to an external configuration engine, auditing constraint rules across a model, or troubleshooting validation behavior. Because it is defined WITH READ ONLY, it cannot be used to insert, update, or delete constraint clauses; modifications must target the base tables through supported application APIs.

Underlying Base Objects

The view is defined over two base tables:

• CZ_CONSTRAINTS (CO) — the constraint header table, providing the constraint name (CO.NAME) and the primary key CONSTRAINT_ID.
• CZ_CONSTRAINT_CLAUSES (COCL) — the clause detail table, holding each clause's sequence, prefix/suffix, functions, comparators, and the ACTION_IF_NULL flag.

The join condition is COCL.CONSTRAINT_ID = CO.CONSTRAINT_ID, making the relationship one-to-many: a single constraint header resolves to one or more clause rows. The ETRM metadata states that the view is "Not implemented in this database" in some environments, meaning it may be absent or invalid depending on patch level and whether the retrofitting scripts were applied. The documented referenced base objects are limited to these two tables; no additional objects are documented.

Key Columns

• CONSTRAINT_NAME (CO.NAME) — name of the parent constraint.
• CONFIG_CONSTRAINT_CLAUSE_NAME (COCL.NAME) — name of the individual clause.
• SEQUENCE_NUMBER — evaluation order of the clause within the constraint.
• PREFIX / SUFFIX — textual parentheses or punctuation surrounding the clause expression.
• FUNCTION1 / FUNCTION2 — the two operands of the comparison.
• DB_FUNCTION1 / DB_OBJECT_NAME1 / DB_OBJECT_NAME2 — database function and object references used in clause evaluation.
• ATTRIBUTE_CODE1 / ATTRIBUTE_CODE2 — model attribute identifiers referenced by the clause.
• COMPARATOR / OPERATOR — the relational and logical connectors (e.g., =, >, AND/OR).
• ACTION_IF_NULL — defines clause behavior when a referenced value evaluates to null; central to the user's "action_if_null" search and directly relevant when diagnosing null-attribute validation outcomes.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns.

Common Use Cases and Queries

Typical scenarios include listing all clauses for a named constraint, inspecting null-handling behavior, and auditing recently modified rules.

SELECT constraint_name,
       config_constraint_clause_name,
       sequence_number,
       function1, comparator, function2,
       action_if_null
FROM   czbv_config_constraint_clauses
WHERE  constraint_name = :p_constraint
ORDER  BY sequence_number;

SELECT constraint_name, config_constraint_clause_name, action_if_null
FROM   czbv_config_constraint_clauses
WHERE  action_if_null IS NOT NULL;

Because the view is read-only, all maintenance must be performed against CZ_CONSTRAINTS and CZ_CONSTRAINT_CLAUSES through the supported Oracle Configurator APIs rather than by direct view manipulation.