Search Results cz_config_inputs




Overview
Explore in AI Chat

Overview

The CZ_CONFIG_INPUTS table is a core data object within the Oracle E-Business Suite Configurator (CZ) module. It functions as the transactional repository for all user selections and inputs captured during the interactive configuration of a product, service, or solution. When a user makes a selection—such as choosing a component, specifying a quantity, or entering a parameter value—that discrete piece of data is stored as a record in this table. Its primary role is to persist the complete state of a configuration session, enabling the Configurator engine to evaluate rules, validate choices, and ultimately generate a bill of material or a structured output. This table is essential for the integrity of the configuration process in both Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to link user inputs to the broader configuration context and to model hierarchical relationships between selections. The primary key is a composite of CONFIG_HDR_ID, CONFIG_INPUT_ID, and CONFIG_REV_NBR, ensuring uniqueness for each input across configuration revisions. Critical columns include:

  • CONFIG_HDR_ID and CONFIG_REV_NBR: Foreign keys to CZ_CONFIG_HDRS, tying the input to a specific configuration session header.
  • PS_NODE_ID: Foreign key to CZ_PS_NODES, linking the input to the specific model node (e.g., a feature or option) in the Configurator knowledge base.
  • CONFIG_ITEM_ID: Foreign key to CZ_CONFIG_ITEMS, associating the input with a configured component instance in the output structure.
  • PARENT_INPUT_ID and TARGET_CONFIG_INPUT_ID: These columns support hierarchical and referential relationships between inputs, allowing for complex parent-child dependencies and cross-references within the configuration.

Common Use Cases and Queries

A primary use case is auditing and analyzing configuration history. Support or operations teams may query this table to understand what a user selected for a past order. Another critical use is in debugging configuration logic, where developers trace the inputs that led to a specific validation or pricing outcome. A common query pattern retrieves all inputs for a given configuration session:

SELECT ci.* FROM cz_config_inputs ci WHERE ci.config_hdr_id = :header_id AND ci.config_rev_nbr = :revision ORDER BY ci.config_input_id;

For reporting on popular options or feature selections across many configurations, analysts often join CZ_CONFIG_INPUTS with CZ_PS_NODES to get descriptive names. Integration with order management or manufacturing modules also relies on this table to pass the finalized configuration details for further processing.

Related Objects

As indicated by its foreign keys, CZ_CONFIG_INPUTS has strong dependencies on several other Configurator tables. The CZ_CONFIG_HDRS table is the parent, providing the master record for each configuration instance. The CZ_PS_NODES table supplies the definitional metadata for the configurable model elements. The CZ_CONFIG_ITEMS table stores the resulting component instances generated from the inputs. The table also has a recursive relationship with itself via PARENT_INPUT_ID and TARGET_CONFIG_INPUT_ID, enabling the modeling of input hierarchies and dependencies. These relationships are fundamental to the Configurator's operation and data integrity.