Search Results cz_combo_features_pk

Overview

The CZ_COMBO_FEATURES table is a core data structure within the Oracle E-Business Suite (EBS) Configurator (CZ) module, specifically for releases 12.1.1 and 12.2.2. It functions as an explicit compatibility table for options and features. Its primary role is to store and enforce compatibility rules defined during the product modeling process. When a configurator modeler defines that a specific feature or option is explicitly compatible with a particular model configuration, that relationship is recorded in this table. This enables the runtime configurator engine to validate user selections and ensure only valid combinations of components can be chosen, which is fundamental for complex, rule-based product configuration.

Key Information Stored

The table's structure centers on linking key identifiers to establish compatibility relationships. As defined by its primary key (CZ_COMBO_FEATURES_PK), the critical columns are FEATURE_ID, MODEL_REF_EXPL_ID, and RULE_ID. The FEATURE_ID column stores a reference to a specific configurable feature or option, typically pointing to a record in the CZ_PS_NODES table. The MODEL_REF_EXPL_ID column holds a reference to a model explanation or configuration context from the CZ_MODEL_REF_EXPLS table. The RULE_ID column links to the overarching rule definition in the CZ_RULES table that governs this compatibility. An additional notable column is GRID_COL_ID, which is linked via a foreign key to the CZ_GRID_COLS table, indicating this table can also support compatibility rules within the context of a configurator UI grid.

Common Use Cases and Queries

The primary use case is the validation and interrogation of product compatibility rules. This is critical for troubleshooting configuration models, generating compliance reports, and supporting data migration or integration efforts. A common query pattern involves joining CZ_COMBO_FEATURES to related descriptive tables to produce a human-readable report of all explicit compatibilities for a given model. For example:

• Reporting Compatible Features: A query to list all features explicitly compatible with a specific model configuration, joining CZ_PS_NODES to get feature names and CZ_MODEL_REF_EXPLS for context.
• Rule Analysis: Analyzing the density or scope of compatibility rules by joining with CZ_RULES to count the number of FEATURE_ID entries per RULE_ID.
• Data Integrity Validation: SQL scripts to identify orphaned records where FEATURE_ID or MODEL_REF_EXPL_ID values no longer exist in their parent tables, which is essential for maintaining a clean model repository.

Related Objects

As indicated by its foreign key constraints, CZ_COMBO_FEATURES is centrally connected to several other core Configurator tables. The CZ_RULES table is the parent for the rule definition. The CZ_PS_NODES table provides the definition of the feature or option itself. The CZ_MODEL_REF_EXPLS table supplies the model explanation context. Finally, the CZ_GRID_COLS table relates to user interface presentation details. Any comprehensive analysis or data operation involving explicit compatibility rules will require navigating this network of related objects, with CZ_COMBO_FEATURES serving as the critical junction table.