Results for “constraint_type”

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

Overview

CZ_CONFIG_MESSAGES_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema and belonging to the CZ – Configurator product family. It is documented as the "Client view of Configuration Messages," meaning it exposes a filtered, presentation-oriented projection of the configuration message data used by the Configurator runtime and client components. In EBS 12.1.1 and 12.2.2, Configurator messages communicate constraint violations, rule outcomes, and other validation feedback generated during a configuration session. The view therefore plays a supporting role in reporting and integration: it allows external queries, custom reports, and interface programs to read the same set of "live" (non-deleted) messages that the Configurator UI surfaces to users, without having to reproduce the deletion filtering logic themselves.

Because the object type is a VIEW, it stores no data of its own. All reads are resolved against its underlying base object at runtime, so any change to the base message data is immediately visible through the view. This makes the view suitable for operational reporting on active configuration messages rather than for historical or audited snapshots.

Underlying Base Objects

The documented ETRM metadata identifies a single referenced base object, accessed through a synonym:

• CZ_CONFIG_MESSAGES (SYNONYM) – the base table that physically holds the configuration message rows.

The view definition is a straightforward select over that base object with one predicate applied:

• WHERE DELETED_FLAG='0' – the view always filters out rows that have been logically deleted.

Consequently, the view inherits every column of the base table but only exposes rows where the deletion flag indicates the record is still valid. It does not perform joins, aggregations, or column transformations; its value is entirely in the deletion filter and in presenting a stable, client-facing column set. From a dependency standpoint, the view will become invalid if the structure of the underlying CZ_CONFIG_MESSAGES table changes incompatibly.

Key Columns

The view exposes the following columns, each corresponding directly to a column on the base table:

• MESSAGE_SEQ – the sequence identifier for the message; this is the column most closely associated with the searched term "message_seq" and acts as a primary identifier for a given message row.
• CONFIG_HDR_ID, CONFIG_REV_NBR – the configuration header and revision number to which the message pertains.
• CONFIG_ITEM_ID – the configuration item the message relates to, when applicable.
• CONSTRAINT_TYPE – the category of constraint that produced the message.
• MESSAGE – the message text presented to the client.
• OVERRIDE – indicates whether the message may be or has been overridden.
• RULE_ID – the rule that generated the message.
• PS_NODE_ID – the configuration/pricing structure node associated with the message.
• INSTANCE_HDR_ID, INSTANCE_REV_NBR – the runtime instance header and revision.
• SECURITY_MASK, EFF_MASK, EFF_FROM, EFF_TO – security and effective-dating attributes.
• CHECKOUT_USER, DELETED_FLAG – checkout ownership and the logical deletion indicator (always '0' via the view).
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard EBS audit columns.

Common Use Cases and Queries

Typical scenarios include diagnosing configuration failures, reporting on constraints triggered for a given configuration, and driving downstream integrations that must react to configuration messages. Reporting on messages for a specific configuration header or rule is common, as is auditing which messages have been overridden.

• Retrieve all active messages for a configuration header:

  SELECT message_seq, config_hdr_id, constraint_type, message
  FROM   cz_config_messages_v
  WHERE  config_hdr_id = :p_config_hdr_id
  ORDER  BY message_seq;

• Find messages produced by a specific rule:

  SELECT message_seq, rule_id, message
  FROM   cz_config_messages_v
  WHERE  rule_id = :p_rule_id;

• List overridable or overridden messages:

  SELECT message_seq, config_hdr_id, override, message
  FROM   cz_config_messages_v
  WHERE  override IS NOT NULL;

• Audit recent message activity:

  SELECT message_seq, config_hdr_id, last_updated_by, last_update_date
  FROM   cz_config_messages_v
  WHERE  last_update_date >= :p_since_date;

In all cases, the view already excludes deleted rows, so no additional DELETED_FLAG predicate is required.