Search Results bom_explosions

Overview

SO_CONFIG_COMPONENTS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, registered under the Oracle Order Entry (OE) product family. It exposes the configured bill-of-material component structure associated with order lines, presenting the exploded component hierarchy produced during model and option configuration. The view is defined over the BOM explosion and inventory component data sets, joining them to item master information so that each configured component row carries descriptive and identification attributes alongside its order-entry control flags.

The view plays a central role wherever downstream logic must evaluate the composition of a configured item after configuration validation: pricing, shipping, ATP, pick release, and revenue recognition all rely on the component-level flags surfaced here. Because it draws from the BOM explosion tables rather than maintaining a separate persistent structure, SO_CONFIG_COMPONENTS_V reflects the current state of the exploded configuration and is therefore typically consumed at the point of order booking, repricing, or order import validation.

The object is documented as VALID in the ETRM metadata for both 12.1.1 and 12.2.2, and the column list is identical across those releases, indicating a stable interface suitable for custom reports and integrations spanning both certification levels.

Underlying Base Objects

The view is defined over four documented base objects:

• BOM_EXPLOSIONS (synonym) — supplies the exploded component rows, including top and common bill sequence identifiers, plan level, explosion group, quantities, and the ordering/ATP flags.
• BOM_INVENTORY_COMPONENTS (view) — provides component-level BOM attributes such as mutually exclusive options and component code, used in the DECODE logic that derives the display sequence and option behaviour.
• MTL_SYSTEM_ITEMS_KFV (synonym) — supplies the concatenated segment identifier for each component item.
• MTL_SYSTEM_ITEMS_VL (view) — supplies the item description in the session language.

The join is driven from the BOM explosion rows, aliased BE, with the item master joins keyed on the component and base item identifiers. The SELECT list is explicitly enumerated and includes a DISTINCT clause over BE.ROWID, which prevents duplicate explosion rows from appearing when a component is referenced through more than one BOM path.

Key Columns

Structural columns identify the configured item and its placement in the hierarchy. TOP_BILL_SEQUENCE_ID, BILL_SEQUENCE_ID, and COMMON_BILL_SEQUENCE_ID link each component to its bill, while TOP_ITEM_ID and ASSEMBLY_ITEM_ID locate the component within the configured model. PLAN_LEVEL, SORT_ORDER, EXPLODE_GROUP_ID, and OPERATION_SEQ_NUM control sequencing and level placement.

Quantity and unit columns include EXTENDED_QUANTITY, COMPONENT_QUANTITY, PRIMARY_UOM_CODE, and PRIMARY_UNIT_OF_MEASURE. Order-entry control columns include SO_BASIS, OPTIONAL, REQUIRED_TO_SHIP, REQUIRED_FOR_REVENUE, SHIPPING_ALLOWED, INCLUDE_ON_SHIP_DOCS, INCLUDE_ON_BILL_DOCS, PICK_COMPONENTS, CHECK_ATP, ATP_COMPONENTS_FLAG, ATP_FLAG, LOW_QUANTITY, and HIGH_QUANTITY.

The LOOP_FLAG column indicates whether the component participates in a circular or repeating BOM relationship. It is used during explosion and validation to detect configurations whose structure would otherwise recurse indefinitely. Complimentary diagnostic fields include REXPLODE_FLAG, EXPLOSION_TYPE, COMPONENT_CODE, BOM_ITEM_TYPE, PARENT_BOM_ITEM_TYPE, EFFECTIVITY_DATE, DISABLE_DATE, and the fifteen CONTEXT/ATTRIBUTE pairs reserved for descriptive flexfield data.

Common Use Cases and Queries

Typical scenarios include retrieving all components for a configured order line, filtering optional or mutually exclusive components, identifying components that require ATP checking, and detecting loop conditions during configuration validation.

Components for a top-level configuration:

• SELECT component_item_id, concatenated_segments, component_quantity, plan_level, sort_order FROM so_config_components_v WHERE top_bill_sequence_id = :p_top_bill_seq_id ORDER BY sort_order;

Optional components subject to ATP:

• SELECT component_item_id, optional, check_atp, atp_flag FROM so_config_components_v WHERE top_item_id = :p_top_item AND optional = 1;

Loop detection during validation:

• SELECT component_item_id, loop_flag, rexplode_flag FROM so_config_components_v WHERE loop_flag = 'Y';

Shipping-relevant components:

• SELECT component_item_id, shipping_allowed, required_to_ship, pick_components FROM so_config_components_v WHERE top_bill_sequence_id = :p_top_bill_seq_id AND shipping_allowed = 'Y';