Search Results cz_errors




Overview
Explore in AI Chat

Overview

CZ_ERRORS is a Configurator error table within the Oracle E-Business Suite Bills of Material (BOM) module. It records errors generated during the runtime execution of Oracle Configurator, the rules-based engine used to validate, configure, and price configurable items in order capture and quoting flows. When a configuration fails validation, violates a constraint, or cannot reconcile selected options against the model's rules, Configurator writes a diagnostic record to CZ_ERRORS so that the failure is persisted and auditable rather than discarded after the session ends.

The table plays a supporting diagnostic role rather than a transactional master role. In ETRM metadata terms, CZ_ERRORS is classified by heuristic Data Vault modeling as a link table. This classification reflects its position: it holds foreign key references to both the constraint assignment that triggered the error and the sales order line being configured, making it a junction-style object that associates configuration context with order context. It is not a hub, since it carries no independent natural business key, and it is not a satellite, since it is not a descriptive attribute set hanging off a single parent key.

Key Information Stored

The documented metadata identifies the primary key CZ_ERRORS_PK, defined on ERROR_ID. ERROR_ID is the surrogate key — a system-generated identifier that uniquely distinguishes each error row. It is not a business key and carries no meaning to end users. Business-key candidates are not enumerated in the available metadata; the table is primarily identified through its foreign key relationships rather than through a user-facing unique index.

The two documented foreign key columns are the most significant non-key attributes:

  • ASSIGNMENT_ID — References CZ_CONSTRAINT_ASSIGNMENTS. This ties the error to the specific constraint assignment in the Configurator model whose evaluation produced the failure, allowing the rule set involved to be traced.
  • LINE_ID — References SO_LINES_ALL. This ties the error to the sales order line that was being configured at the time, linking the diagnostic to the actual order transaction.

Together, ERROR_ID, ASSIGNMENT_ID, and LINE_ID form the core structure documented in the ETRM metadata. Error message text and severity attributes are conventionally present in such diagnostic tables but are not enumerated in the supplied excerpt, so they are not asserted here as documented facts.

Common Use Cases and Queries

The principal use case is troubleshooting failed configurations. Support and implementation teams query CZ_ERRORS to determine why a particular sales order line could not be configured, then join to the constraint assignment to identify the offending rule. A typical diagnostic pattern is:

  • Retrieve all errors for a given order line: SELECT * FROM CZ_ERRORS WHERE LINE_ID = :line_id;
  • Trace errors back to the rule that caused them: SELECT e.ERROR_ID, e.LINE_ID, e.ASSIGNMENT_ID FROM CZ_ERRORS e, CZ_CONSTRAINT_ASSIGNMENTS a WHERE e.ASSIGNMENT_ID = a.ASSIGNMENT_ID;

Reporting use cases include counting configuration failures by assignment to identify problem rules, and analyzing error frequency across order lines to detect patterns in a particular model or option combination. Because the table links to SO_LINES_ALL, error data can be correlated with order header and customer information for trend analysis in high-volume configure-to-order environments.

Related Objects

The following objects are the most significant related entities based on the documented relationship data:

  • CZ_CONSTRAINT_ASSIGNMENTS — joined via CZ_ERRORS.ASSIGNMENT_ID; identifies the constraint assignment whose evaluation failed.
  • SO_LINES_ALL — joined via CZ_ERRORS.LINE_ID; identifies the sales order line under configuration.
  • CZ_ERRORS_PK — the primary key constraint on ERROR_ID, enforcing row uniqueness.

Because Configurator errors arise during configuration sessions, related Configurator runtime objects (configuration sessions and model structures in the CZ schema) are logical dependencies even where explicit foreign keys are not documented. Note that the ETRM metadata states CZ_ERRORS is not implemented in this database, so the table may be absent in installations where Oracle Configurator is not licensed or deployed.