Results for “node_identifier”

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

Overview

CZ_CONFIG_ITEMS is the core transactional table within the Oracle Configurator (CZ) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It stores the individual items that have been selected, instantiated, or generated as part of a configured item instance. In the Oracle Configurator architecture, a configuration is created when a user models a product against a model structure defined by the Configurator Developer. The resulting selections—BOM components, options, and nested sub-configurations—are persisted as rows in CZ_CONFIG_ITEMS. The table belongs to the CZ schema and is validated as VALID across the documented releases.

Each configuration is identified by a header and revision, and each row represents one selected item within that configuration. The table is heavily denormalized in the sense that it carries both structural pointers (parent/child relationships via CONFIG_ITEM_ID hierarchy) and descriptive attributes (BOM item type, quantity, organization, UOM, effectivity). With 62 documented columns, it also carries Oracle-standard audit, effectivity, security mask, and multi-org fields.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure classifies CZ_CONFIG_ITEMS as a hub. This is a modeling suggestion: the table contains the unique business keys (configuration header, revision, and config item) around which attributes, input records, and usages cluster as satellites and links.

Key Information Stored

The primary key of the table is the surrogate/uniqueness constraint CZ_CONFIG_ITEMS_PK, defined on (CONFIG_HDR_ID, CONFIG_REV_NBR, CONFIG_ITEM_ID). This composite key uniquely identifies a single configured item within a configuration revision. Two additional unique indexes act as business-key candidates:

• CZ_CONFIG_ITEMS_U1 (INSTANCE_HDR_ID, INSTANCE_REV_NBR, CONFIG_ITEM_ID) — ties the item to a specific configuration instance.
• CZ_CONFIG_ITEMS_U2 (PARENT_CONFIG_ITEM_ID, CONFIG_ITEM_ID, INSTANCE_HDR_ID, INSTANCE_REV_NBR, DELETED_FLAG) — enforces hierarchy correctness at the parent/child level, excluding soft-deleted rows.

The most significant columns include:

• CONFIG_HDR_ID, CONFIG_REV_NBR, CONFIG_ITEM_ID — the PK triad identifying the item.
• PS_NODE_ID — foreign key to CZ_PS_NODES, the model node this item was instantiated from.
• ROOT_BOM_CONFIG_ITEM_ID — self-referencing pointer to the root BOM config item.
• PARENT_CONFIG_ITEM_ID — self-referencing pointer enabling the parent/child hierarchy of configured items.
• VALUE_TYPE_CODE, ITEM_VAL, ITEM_NUM_VAL — the user-entered or derived value of the option.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, COMPONENT_SEQUENCE_ID — link to the BOM/inventory item that satisfies this configuration node.
• UOM_CODE, BOM_ITEM_TYPE, COMPONENT_INSTANCE_TYPE — unit of measure and BOM classification.
• DELETED_FLAG, DISCONTINUED_FLAG, ORDERABLE_FLAG, QUOTABLE_FLAG, QUOTEABLE_FLAG — status flags governing whether the item is active, orderable, or quotable.
• EFF_FROM, EFF_TO, SECURITY_MASK — effectivity and security (organization-level access) fields.
• CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Oracle-standard audit columns.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include tracing a configured sales order line back to its constituent selections, auditing which BOM components a configuration produced, and confirming the hierarchy of nested sub-configurations.

• List all items for a configuration header and revision:

  SELECT CONFIG_ITEM_ID, PARENT_CONFIG_ITEM_ID, INVENTORY_ITEM_ID, ITEM_VAL, UOM_CODE FROM CZ.CZ_CONFIG_ITEMS WHERE CONFIG_HDR_ID = :hdr AND CONFIG_REV_NBR = :rev AND NVL(DELETED_FLAG,'N') = 'N';

• Find top-level (root) items: filter where ROOT_BOM_CONFIG_ITEM_ID equals CONFIG_ITEM_ID, or where PARENT_CONFIG_ITEM_ID is null.
• Trace children of a given option: SELECT * FROM CZ.CZ_CONFIG_ITEMS WHERE PARENT_CONFIG_ITEM_ID = :parent_item_id AND CONFIG_HDR_ID = :hdr AND CONFIG_REV_NBR = :rev;
• Orderable/quotable configuration items: filter on ORDERABLE_FLAG = 'Y' and QUOTABLE_FLAG = 'Y' for downstream order import or quote generation.
• Audit trail: join to CZ_CONFIG_USAGES and CZ_CONFIG_INPUTS to reconstruct how user inputs drove each selection.

Because the CZ tables are transactional and volume can be very large for complex ATO/PTO models, queries should generally be filtered by CONFIG_HDR_ID and CONFIG_REV_NBR to leverage the PK index, and should exclude rows where DELETED_FLAG = 'Y'.

Related Objects

CZ_CONFIG_ITEMS is central to the Configurator data model and participates in numerous foreign key relationships, both as a referencing table and as a parent to dependent tables.

• CZ_CONFIG_HDRS — parent configuration header; joined via CONFIG_HDR_ID and CONFIG_REV_NBR.
• CZ_PS_NODES — model structure nodes; joined via PS_NODE_ID, identifying the graphical model element instantiated.
• CZ_CONFIG_ATTRIBUTES — feature/option attribute values for a configured item; referenced by (CONFIG_HDR_ID, CONFIG_REV_NBR, CONFIG_ITEM_ID).
• CZ_CONFIG_EXT_ATTRIBUTES — extension (flexfield) attribute values; same three-column FK.
• CZ_CONFIG_INPUTS — user inputs that generated selections; references both CONFIG_ITEM_ID and TARGET_CONFIG_ITEM_ID.
• CZ_CONFIG_USAGES — records the components actually used in a configuration; FK on (CONFIG_HDR_ID, CONFIG_REV_NBR, CONFIG_ITEM_ID).
• CZ_DRILL_DOWN_ITEMS — supports drill-down navigation across the configured item tree; same compound FK.
• CZ_CONFIG_ITEMS (self) — self-referencing via PARENT_CONFIG_ITEM_ID and ROOT_BOM_CONFIG_ITEM_ID to represent hierarchy.

Together these tables form the runtime persistence layer that connects Configurator model definitions to actual orderable inventory items, BOM component sequences, and organization-specific configurations.