Results for “attribute_code2”

2 results




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

Overview

The ICX_CONFIG_ERROR_ITEMS_V view belongs to the ICX (Oracle iProcurement) product family and is documented as a "Java Configurator Error Messages Validation View." Its purpose is to expose configuration error records generated during Java-based configurator processing so that invalid item configurations, component relationships, and pricing anomalies can be identified and validated. The view joins configuration explosion data to attribute-value storage and error tracking tables, producing a consolidated result set suitable for error review, troubleshooting, and downstream reporting within iProcurement and related selling/configurator flows.

The user search term "ak_inst_attribute_values" directly corresponds to the AK_INST_ATTRIBUTE_VALUES table (aliased as AIAV in the view text), which is a central dependency of this view. This table stores instance-level attribute values for extensible attributes defined in the AK (Application Kit / Attribute Knowledge) framework. ICX_CONFIG_ERROR_ITEMS_V uses it to retrieve attribute codes for items configured against the MTL_SYSTEM_ITEMS_KFV database object, scoped to application 702 (Oracle iProcurement).

Underlying Base Objects

The ETRM documentation for this view records no explicitly documented base objects, and the object is noted as "Not implemented in this database" in the excerpt. However, the embedded view text reveals the full set of referenced objects:

The view therefore sits atop the BOM configurator explosion model, joined to AK attribute infrastructure and CZ error tracking.

Key Columns

Prominent columns include ROW_ID, COMPONENT_ITEM_ID, ORGANIZATION_ID, and ITEM_NAME (concatenated segments from MTL_SYSTEM_ITEMS_KFV), along with ITEM_DESCRIPTION. Pricing fields include LIST_PRICE, SELLING_PRICE, and a derived EXT_PRICE computed as SELECT_QUANTITY * SELLING_PRICE. Configuration behavior is captured through BOM_ITEM_TYPE, OPTIONAL, MUTUALLY_EXCLUSIVE_OPTIONS, SORT_ORDER, PLAN_LEVEL, and a derived DISPLAY_FLAG (DECODE of PLAN_LEVEL). Quantity columns include COMPONENT_QUANTITY, LOW_QUANTITY, HIGH_QUANTITY, and EXTENDED_QUANTITY. Attribute infrastructure is exposed via ATTRIBUTE_CODE from AIAV and the fifteen ATTRIBUTE1..ATTRIBUTE15 columns from the explosion table. Error linkage is provided by ASSIGNMENT_ID from CZ_ERRORS and GROUP_ID.

Common Use Cases and Queries

This view is typically queried to diagnose configurator errors, verifying which components failed validation and what attribute values or prices were involved.

SELECT ITEM_NAME, COMPONENT_ITEM_ID, ORGANIZATION_ID,
       ASSIGNMENT_ID, ATTRIBUTE_CODE, EXT_PRICE
FROM   ICX_CONFIG_ERROR_ITEMS_V
WHERE  GROUP_ID = :p_group_id;

Analysts may also aggregate error counts by item or review configuration options that are optional or mutually exclusive. Because the object may not be deployed in every environment ("Not implemented in this database"), availability should be confirmed prior to relying on it. When present, it provides a convenient single source joining BOM configuration explosions, AK instance attribute values, and CZ error records in the iProcurement context.