Results for “attribute_code2”

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

Overview

The CZ_CONSTRAINT_CLAUSES_V view is a Bills of Material (BOM) module object that exposes Oracle EBS constraint clause definitions used by the Configurator (CZ) schema. Constraint clauses describe the logical rules applied during configuration validation, linking a constraint to the specific attribute, function, comparator, operator, and value logic that must be satisfied. In Oracle EBS 12.1.1 and 12.2.2, this view serves as a reporting and integration surface over the underlying CZ constraint definition tables, allowing developers and analysts to read clause-level rule metadata without navigating the normalized base tables directly.

The view carries a prominent ATTRIBUTE_CODE2 column, which is significant because users searching for "attribute_code2" are typically investigating the second operand of a constraint clause expression. This column identifies the attribute used on the right-hand side of the comparison when a clause compares two attributes or references a secondary attribute value.

Underlying Base Objects

According to the documented ETRM metadata, no base objects are formally documented for this view, and the implementation note states "Not implemented in this database." The view text, however, reveals that it is defined over the CZ constraint clause table (aliased C, keyed by CLAUSE_ID and CONSTRAINT_ID), joined to several lookup and descriptive flexfield sources. These include FND lookup views (aliased FCL1, FCL2, FCLC, FCLO, FCLN1, FCLN2) that resolve meaning strings for functions, comparators, and operators, and AK attribute dictionary views (AK1, AK2) that resolve attribute names and data types. It also references SO_LINES_V and SO_HEADER_V through the DB_OBJECT_NAME1 and DB_OBJECT_NAME2 columns, and descriptive flexfield views (DESC1, DESC2) for order management context attributes.

Key Columns

• CLAUSE_ID, CONSTRAINT_ID — keys identifying the clause and its parent constraint.
• NAME, SEQUENCE_NUMBER — clause label and evaluation order.
• ATTRIBUTE_CODE1, ATTRIBUTE_CODE2 — the operand attribute identifiers for the left and right sides of the clause. ATTRIBUTE_NAME1 and ATTRIBUTE_NAME2 provide resolved display names, with ATTRIBUTE_NAME2 falling back to ATTRIBUTE_CODE2 when no dictionary or flexfield name is available.
• ATTRIBUTE_TYPE1, ATTRIBUTE_TYPE2 — resolved data types (VARCHAR2 or NUMBER), derived from DB_OBJECT_NAME and, for clause two, from the comparator and function combination.
• COMPARATOR, COMPARATOR_NAME — the comparison operator (for example IN, NOT IN) and its meaning.
• OPERATOR, OPERATOR_NAME — logical joining operator (AND/OR) and meaning.
• FUNCTION1, FUNCTION2, DB_FUNCTION1, DB_OBJECT_NAME1, DB_OBJECT_NAME2 — function and database object identifiers used to resolve operand values.
• ACTION_IF_NULL, PREFIX, SUFFIX — clause behavior modifiers.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE8 — descriptive flexfield columns.

Common Use Cases and Queries

Typical uses include auditing constraint logic, documenting configuration rules, and integrating clause definitions with external validation engines. A sample query to inspect second-operand attributes follows:

SELECT CONSTRAINT_ID, CLAUSE_ID, NAME, ATTRIBUTE_CODE1, ATTRIBUTE_CODE2, ATTRIBUTE_NAME2, COMPARATOR_NAME, OPERATOR_NAME FROM CZ_CONSTRAINT_CLAUSES_V ORDER BY CONSTRAINT_ID, SEQUENCE_NUMBER;

Analysts may also filter on ATTRIBUTE_CODE2 IS NOT NULL to isolate clauses that reference a secondary attribute, or join back to the constraint header for full rule reporting.