Search Results selected_qty

Overview

The ICX_CONFIG_COMPONENTS_WEB_V view is a valid, APPS-owned database object within the Oracle iProcurement (ICX) product family, described in the ETRM repository as a "Configurator Components View." It exists in Oracle E-Business Suite releases 12.1.1 and 12.2.2 and is registered against the APPS schema. Its purpose is to expose the exploded component structure of configured items — that is, the bill-of-material components and their associated pricing, quantity, and selection attributes — in a flattened, web-friendly format suitable for iProcurement's configuration and checkout flows.

In practical terms, the view mediates between the internal BOM configuration explosion logic and the presentation layer used by iProcurement hosted pages and reporting. Rather than requiring callers to join configuration explosion data with item master information manually, the view pre-joins these sources and presents derived flags and calculations, such as DISPLAY_FLAG and EXT_PRICE, so that consuming applications receive a ready-to-render result set.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both exposed as synonyms within the APPS schema:

• BOM_CONFIG_EXPLOSIONS — aliased as BCE in the view definition. This object supplies the exploded configuration component lines, including component item identifiers, pricing, quantity ranges, plan levels, selection indicators, and the SO_BASIS column, along with a set of descriptive flexfield context and attribute columns (CONTEXT, ATTRIBUTE1 through ATTRIBUTE15) and numeric/date columns used downstream.
• MTL_SYSTEM_ITEMS_KFV — aliased as MSI. This key flexfield view of the item master provides the concatenated item name (ITEM_NAME) and item description (ITEM_DESCRIPTION).

The two sources are joined on the component item and organization: MSI.INVENTORY_ITEM_ID = BCE.COMPONENT_ITEM_ID AND MSI.ORGANIZATION_ID = BCE.ORGANIZATION_ID. Because the driving table is the configuration explosion, the view returns only components that resolve to a valid item master record in the matching organization.

Key Columns

The view exposes a broad set of columns that fall into several functional groups:

• Identity and context: ROW_ID, COMPONENT_ITEM_ID, ORGANIZATION_ID, TOP_BILL_SEQUENCE_ID, GROUP_ID, COMPONENT_CODE.
• Descriptive data: ITEM_NAME (concatenated segments), ITEM_DESCRIPTION.
• Pricing: LIST_PRICE, SELLING_PRICE, and the derived EXT_PRICE (SELECT_QUANTITY multiplied by SELLING_PRICE).
• Quantity and UOM: COMPONENT_QUANTITY, LOW_QUANTITY, HIGH_QUANTITY, EXTENDED_QUANTITY, PRIMARY_UOM_CODE, PRIMARY_UNIT_OF_MEASURE.
• Configuration behavior: OPTIONAL, MUTUALLY_EXCLUSIVE_OPTIONS, SORT_ORDER, PLAN_LEVEL, and the derived DISPLAY_FLAG (set to 'N' when PLAN_LEVEL is 0, otherwise 'Y'). Also SELECT_QUANTITY (aliased SELECTED_QTY), SELECT_FLAG (aliased SELECTED_FLAG), and AUTOSELECTED_FLAG.
• The SO_BASIS column — passed through from BOM_CONFIG_EXPLOSIONS. The searcher's term "so_basis" maps directly to this column, which carries the sales-order basis used by the configurator to determine how component quantities are derived (for example, per order versus per item).
• Effectivity and ATP dates: EFFECTIVITY_DATE, DISABLE_DATE, EARLIEST_ATP_DATE, GROUP_ATP_DATE.
• Flexfield attributes: CONTEXT and ATTRIBUTE1 through ATTRIBUTE15.

Common Use Cases and Queries

Typical consumers include iProcurement configuration pages, custom order-entry reporting, and integration extracts that need exploded configuration detail. A representative query retrieving priced, selectable components for a top-level bill might appear as follows:

• Retrieve component pricing and selection state:
  SELECT item_name, item_description, selling_price, ext_price, selected_qty, so_basis FROM apps.icx_config_components_web_v WHERE top_bill_sequence_id = :bill_seq ORDER BY sort_order;
• Filter to displayable, non-optional lines:
  SELECT * FROM apps.icx_config_components_web_v WHERE display_flag = 'Y' AND optional = 'N';
• Inspect sales-order basis behavior:
  SELECT component_item_id, component_code, so_basis FROM apps.icx_config_components_web_v WHERE group_id = :group_id;

Because the view is read-only and pre-joins item master data, it is well suited for reporting extracts and custom page regions. Queries should always bind on organization and bill/group identifiers to constrain the configuration explosion and avoid unnecessary full scans of BOM_CONFIG_EXPLOSIONS.