Results for “cz_expressions”

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

Overview

CZ_EXPRESSIONS is the master repository table for expressions within Oracle EBS Configurator (CZ). In Configurator, an expression is the fundamental logical unit used to define rules, constraints, and computations that drive product configuration models. Each row in CZ_EXPRESSIONS represents a single expression — a conditional statement, formula, or logical predicate — that the Configurator runtime engine evaluates to select options, validate selections, or derive values during a configuration session.

Because the table serves as the central anchor for expression definitions, it sits at the intersection of the Configurator development and runtime subsystems. Expressions are consumed by expression nodes (the trees and parse structures), attached to filter sets, and referenced repeatedly by the rule engine as antecedents, consequents, and amount assignments. This broad referencing footprint explains why CZ_EXPRESSIONS behaves as a highly connected entity within the Configurator schema.

From a data-modeling perspective, the metadata classifies CZ_EXPRESSIONS as hub-leaning based on its foreign key topology. In a Data Vault model, this suggests treating CZ_EXPRESSIONS as a hub whose business key is the expression identity, with relationships to development projects, expression nodes, filter sets, and rules modeled as links or satellites. This classification is heuristic and should be validated against the actual modeling requirements of the implementation.

Key Information Stored

The table contains nineteen documented columns. The most significant include:

• EXPRESS_ID — the surrogate primary key, defined by unique index CZ_EXPRESSIONS_PK. This is the value referenced by all downstream tables.
• NAME — the user-facing expression name, the primary business-key candidate alongside EXPRESS_ID.
• EXPR_STR — the raw expression string or formula text as authored by the modeler.
• DESC_TEXT — descriptive narrative for the expression.
• PRESENT_TYPE — indicates the presentation or representation type of the expression.
• PARSED_FLAG — signals whether the expression string has been successfully parsed into the internal node representation.
• DEVL_PROJECT_ID — foreign key to CZ_DEVL_PROJECTS, tying the expression to a development project.
• PERSISTENT_EXPRESSION_ID — stable across-version identifier used for expression persistence.
• EFF_FROM and EFF_TO — effective dating bounds controlling expression validity.
• DELETED_FLAG — soft-delete indicator, preserving historical rows.
• CHECKOUT_USER — the user currently holding the expression in a checked-out state.
• SECURITY_MASK and EFF_MASK — masking flags supporting access and effective-date logic.

The remaining columns are standard Oracle EBS audit fields (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

Typical reporting scenarios include listing all expressions in a development project, identifying unparsed expressions requiring attention, and tracing which rules depend on a given expression.

• List expressions by project: SELECT EXPRESS_ID, NAME, EXPR_STR FROM CZ_EXPRESSIONS WHERE DEVL_PROJECT_ID = :proj AND DELETED_FLAG = 'N';
• Find unparsed expressions: SELECT EXPRESS_ID, NAME FROM CZ_EXPRESSIONS WHERE PARSED_FLAG = 'N';
• Audit recently modified expressions using LAST_UPDATE_DATE.
• Identify checked-out expressions via CHECKOUT_USER for development governance.
• Trace rule usage by joining to CZ_RULES on ANTECEDENT_ID, CONSEQUENT_ID, or AMOUNT_ID.

Related Objects

FK relationships establish these dependencies:

• CZ_DEVL_PROJECTS — referenced by CZ_EXPRESSIONS.DEVL_PROJECT_ID.
• CZ_EXPRESSION_NODES — references CZ_EXPRESSIONS.EXPRESS_ID.
• CZ_FILTER_SETS — references CZ_EXPRESSIONS.EXPRESS_ID.
• CZ_RULES — references CZ_EXPRESSIONS three times via CONSEQUENT_ID, ANTECEDENT_ID, and AMOUNT_ID, making it the most tightly coupled dependent table.