Search Results instance_nbr

Overview

OKX_CONFIG_ITEMS_V is a reporting and integration view owned by the APPS schema in Oracle EBS 12.1.1 and 12.2.2. It is registered under the OKX - Contracts Integration product, which supports the integration of configured item structures with Oracle Contracts and related order-capture flows. The view exposes the set of items that have been selected for a given configuration, together with the revision, hierarchy, and instance information required to reconstruct the configured bill of materials at the time of contract or order creation. For a user searching on config_hdr_id, this view is significant because CONFIG_HDR_ID is the primary correlation key that ties every configured component row back to its parent configuration header. The view presents a denormalized, read-only projection of configured item data, allowing external processes and reports to consume configuration detail without querying the underlying configuration tables directly.

Underlying Base Objects

The view is defined over a single base object, CZ_CONFIG_ITEMS, which is referenced through a synonym in the APPS schema. The defining query aliases CZ_CONFIG_ITEMS as CFG and selects each column explicitly, applying only column renaming in one case: NODE_IDENTIFIER is exposed as COMPONENT_CODE. No joins, filters, or aggregation logic are applied, so OKX_CONFIG_ITEMS_V is effectively a pass-through projection of CZ_CONFIG_ITEMS with a stable, integration-friendly column list. Because the view contains no embedded predicates, row counts and data content mirror the base table exactly; all restrictions such as DELETED_FLAG handling must be applied by the calling query. The view status is VALID in the documented environment.

Key Columns

• CONFIG_HDR_ID — Identifier of the configuration header to which the item belongs; the principal join key for the search term supplied.
• CONFIG_REV_NBR — Configuration revision number, enabling retrieval of a specific revision of the configured structure.
• CONFIG_ITEM_ID — Unique identifier for the configuration item row itself.
• ROOT_BOM_CONFIG_ITEM_ID, PARENT_CONFIG_ITEM_ID — Self-referencing pointers that define the configured BOM hierarchy.
• INVENTORY_ITEM_ID, ORGANIZATION_ID — The inventory item and inventory organization context for the selected component.
• COMPONENT_CODE — Derived from NODE_IDENTIFIER; identifies the node within the configuration model.
• COMPONENT_SEQUENCE_ID, SEQUENCE_NBR — Sequencing and BOM component correlation.
• ITEM_VAL, INSTANCE_NBR, UOM_CODE, VALUE_TYPE_CODE — Descriptive and quantitative attributes of the selected item.
• DELETED_FLAG, EFF_FROM, EFF_TO, SECURITY_MASK, EFF_MASK, CHECKOUT_USER — Lifecycle, date-effectivity, and security control columns.
• USER_STR01–04, USER_NUM01–04 — Descriptive flexfield-style attribute columns available for extension.

Common Use Cases and Queries

The view is typically queried to retrieve all items selected for a configuration, to drive contract line generation, or to report configured structures for a given header. A representative query is:

SELECT config_hdr_id, config_rev_nbr, config_item_id, parent_config_item_id, inventory_item_id, organization_id, component_code, sequence_nbr, item_val, uom_code FROM apps.okx_config_items_v WHERE config_hdr_id = :p_config_hdr_id AND NVL(deleted_flag,'N') = 'N' ORDER BY sequence_nbr;

Additional scenarios include joining CONFIG_HDR_ID to the corresponding configuration header table to obtain header-level attributes, traversing PARENT_CONFIG_ITEM_ID recursively to display the configured BOM, and filtering by ORGANIZATION_ID or INVENTORY_ITEM_ID for item-specific reporting. Because the view is a direct projection of CZ_CONFIG_ITEMS in the APPS schema, it is suitable for read-only integration extracts and custom concurrent programs without risk to transactional logic.