Search Results autoselected_flag

Overview

APPS.ICX_CONFIG_COMPONENTS_WEB_V is an Oracle E-Business Suite reporting view owned by the APPS schema. It exposes the component-level detail of configured bills of material—the individual options, features, and included items that make up an orderable configuration—in a denormalized form suitable for web storefronts, order capture, quoting, and ATP (available-to-promise) inquiries. The view is a core data source for Oracle iStore and Oracle Configurator-related self-service pages, where end users select and price configurable products before an order is placed.

The view joins configuration explosion rows to the item master, presenting pricing, quantity ranges, selection state, planning level, and derived date and numeric attributes in a single record set. Notably, it maps the generic column DATE_COL1 to a business-meaningful alias EARLIEST_ATP_DATE and DATE_COL2 to GROUP_ATP_DATE. This is directly relevant to the search term "group_atp_date": the value returned in the GROUP_ATP_DATE column represents the aggregate (group-level) available-to-promise date associated with the configured component. It complements EARLIEST_ATP_DATE, which reflects the earliest ATP date for the individual component, allowing callers to distinguish the earliest availability of a single line from the promise date that applies to the configuration group as a whole.

Underlying Base Objects

The view is defined over two documented base objects, both accessed through APPS synonyms:

• BOM_CONFIG_EXPLOSIONS (aliased BCE) — supplies the configuration explosion rows, including component identity, organization, pricing, quantity constraints, planning attributes, selection flags, effectivity, and the generic context/attribute flex columns.
• MTL_SYSTEM_ITEMS_KFV (aliased MSI) — supplies the item name (CONCATENATED_SEGMENTS) and description (DESCRIPTION).

The two objects are joined on inventory item and organization: MSI.INVENTORY_ITEM_ID = BCE.COMPONENT_ITEM_ID and MSI.ORGANIZATION_ID = BCE.ORGANIZATION_ID. Each returned row is anchored to BCE.ROWID, exposed as ROW_ID, which permits the caller to map a view row back to its underlying explosion record for update or drill-down operations.

Key Columns

• ROW_ID, COMPONENT_ITEM_ID, ORGANIZATION_ID — Row identifier and item/organization key linking to the item master.
• ITEM_NAME, ITEM_DESCRIPTION — Concatenated segments and description from MTL_SYSTEM_ITEMS_KFV.
• LIST_PRICE, SELLING_PRICE, EXT_PRICE — List and selling price for the component; EXT_PRICE is computed as SELECT_QUANTITY * SELLING_PRICE.
• BOM_ITEM_TYPE, COMPONENT_QUANTITY, PRIMARY_UOM_CODE, PRIMARY_UNIT_OF_MEASURE — Item type and quantity/UOM detail.
• OPTIONAL, MUTUALLY_EXCLUSIVE_OPTIONS, SORT_ORDER, COMPONENT_CODE, SO_BASIS — Configuration and ordering behavior attributes.
• PLAN_LEVEL, DISPLAY_FLAG — Planning level; DISPLAY_FLAG is derived as 'N' when PLAN_LEVEL = 0, otherwise 'Y'.
• LOW_QUANTITY, HIGH_QUANTITY, EXTENDED_QUANTITY, SELECT_QUANTITY (SELECTED_QTY), SELECT_FLAG (SELECTED_FLAG) — Quantity constraints and current selection state.
• EARLIEST_ATP_DATE (DATE_COL1), GROUP_ATP_DATE (DATE_COL2) — Earliest component ATP date and the group-level ATP date for the configuration.
• NUMBER_KIDS (NUM_COL1) — Count of child components.
• AUTOSELECTED_FLAG — Derived from ITEM_SVRID: 'N' when null or -1, 'Y' when 0, otherwise 'Y'.
• TOP_BILL_SEQUENCE_ID, EFFECTIVITY_DATE, DISABLE_DATE, GROUP_ID, CONTEXT, ATTRIBUTE1–ATTRIBUTE15 — Structural, effectivity, grouping, and descriptive flexfield attributes.

Common Use Cases and Queries

Typical use cases include rendering configuration options on a storefront, validating selection combinations, calculating extended configuration pricing, and displaying availability—especially the Group ATP date. The following example retrieves the ATP dates and pricing for a configuration group:

• SELECT component_item_id, item_name, group_id, earliest_atp_date, group_atp_date, selling_price, ext_price FROM apps.icx_config_components_web_v WHERE group_id = :p_group_id ORDER BY sort_order;
• SELECT item_name, group_atp_date, select_quantity, ext_price FROM apps.icx_config_components_web_v WHERE component_item_id = :p_item_id AND organization_id = :p_org_id;
• SELECT component_code, item_description, display_flag, autoselected_flag, selected_flag FROM apps.icx_config_components_web_v WHERE top_bill_sequence_id = :p_top_bill_seq_id;

Because GROUP_ATP_DATE and EARLIEST_ATP_DATE map to DATE_COL1 and DATE_COL2 of BOM_CONFIG_EXPLOSIONS, consumers relying on the "group_atp_date" search should reference the view column GROUP_ATP_DATE to obtain the configuration-level promise date; the underlying explosion table must be populated with the corresponding date for this column to return a meaningful value.