Results for “input_val”

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

Overview

CZ_CONFIG_INPUTS is a Configurator (CZ) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the user inputs captured while a configuration is being created or modified. Each row represents a single answer, selection, or value supplied by a user (or generated by the Configurator runtime) against a configuration header, allowing the Configurator engine to resolve option values, drive derived inputs, and persist the state of a configuration session across revisions. The table sits at the transactional core of the Configurator data model, operating within the CZ schema and identified centrally by its primary key CZ_CONFIG_INPUTS_PK on (CONFIG_HDR_ID, CONFIG_INPUT_ID, CONFIG_REV_NBR).

From a heuristic Data Vault classification standpoint, the mined foreign-key structure suggests a satellite-leaning object. The composite of CONFIG_HDR_ID plus CONFIG_REV_NBR behaves as the primary hub-style linkage to the configuration header, while CONFIG_INPUT_ID and the supporting attribute columns (INPUT_VAL, INPUT_SEQ, EFF_FROM, EFF_TO, and so on) provide descriptive, time-effective payload. The presence of self-referencing foreign keys on CONFIG_HDR_ID with PARENT_INPUT_ID and TARGET_CONFIG_INPUT_ID further suggests hierarchical and dependency relationships that can be modeled as recursive links or same-as links.

Key Information Stored

The physical schema documents 31 columns. The most significant are:

• CONFIG_HDR_ID – Identifier of the parent configuration header; part of the primary key.
• CONFIG_INPUT_ID – Identifier of the individual input record within the configuration; part of the primary key and the business-key candidate.
• CONFIG_REV_NBR – Revision number of the configuration; part of the primary key, enabling multi-revision persistence.
• PS_NODE_ID – Reference to the Configurator model node (CZ_PS_NODES) against which the input was captured.
• INPUT_VAL and INPUT_NUM_VAL – Character and numeric representations of the value entered or derived for the input.
• INPUT_SEQ – Sequencing value controlling the order in which inputs are processed or displayed.
• INSTANCE_NBR – Instance counter used where the same input is repeated across multiple instances of a node.
• PARENT_INPUT_ID and TARGET_CONFIG_INPUT_ID – Self-referencing links that express hierarchy and dependency between inputs.
• CONFIG_ITEM_ID and TARGET_CONFIG_ITEM_ID – References to CZ_CONFIG_ITEMS, tying the input to the configured item in the BOM/routing structure.
• INPUT_TYPE_CODE, INPUT_SOURCE, and VIRTUAL_FLAG – Classify how the input was produced (user-entered, derived, default, virtual).
• EFF_FROM, EFF_TO, DELETED_FLAG – Effectivity and soft-delete markers supporting time-effective history.
• Audit columns such as CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, and LAST_UPDATED_BY.

The primary key (CONFIG_HDR_ID, CONFIG_INPUT_ID, CONFIG_REV_NBR) is the only documented unique index and is therefore the strongest business-key candidate. No surrogate sequence-only key is documented separately.

Common Use Cases and Queries

Typical reporting needs include tracing which inputs a user supplied for a given configuration, resolving option conflicts across revisions, and auditing configuration history. A representative query joining the header is:

• SELECT ci.CONFIG_INPUT_ID, ci.CONFIG_REV_NBR, ci.INPUT_VAL, ci.INPUT_TYPE_CODE FROM CZ.CZ_CONFIG_INPUTS ci WHERE ci.CONFIG_HDR_ID = :p_header_id AND NVL(ci.DELETED_FLAG,'N') = 'N';
• Join to CZ_PS_NODES via PS_NODE_ID to display the model node label associated with each input.
• Recursive CONNECT BY traversal on PARENT_INPUT_ID to reconstruct input hierarchies.
• Effectivity filtering using EFF_FROM/EFF_TO for point-in-time reconstruction of a configuration session.
• Reconciliation to CZ_CONFIG_ITEMS via CONFIG_ITEM_ID and TARGET_CONFIG_ITEM_ID to verify which configured items were produced.

Related Objects

• CZ_CONFIG_HDRS – Parent configuration header; joined on CONFIG_HDR_ID and CONFIG_REV_NBR.
• CZ_CONFIG_ITEMS – Configured items; joined on CONFIG_HDR_ID, CONFIG_REV_NBR, and CONFIG_ITEM_ID (and TARGET_CONFIG_ITEM_ID).
• CZ_PS_NODES – Model node definitions; joined on PS_NODE_ID.
• CZ_CONFIG_INPUTS (self) – Joined via PARENT_INPUT_ID and TARGET_CONFIG_INPUT_ID to model hierarchy and dependency.
• Configurator runtime APIs and concurrent programs that read CZ_CONFIG_INPUTS when instantiating a configuration for order entry or BOM explosion.