Search Results bom_bill_of_materials_u2

Overview

APPS.BOM_EXPLOSION_VIEW is a reporting and integration view in Oracle E-Business Suite that exposes the flattened output of a bill of materials explosion. It is built primarily over the BOM_EXPLOSION_TEMP table, which holds the transient result set generated by the BOM explosion engine when a user performs an indented or summarized BOM inquiry, a where-used query, or a cost rollup. The view joins this temporary explosion data to the bill of materials header, the system items master, and lookup tables to present a denormalized, presentation-ready record set in which each row represents one component occurrence at a specific level of the product structure.

The view is significant because it is one of the objects referenced in the lineage of the BOM_BILL_OF_MATERIALS_U2 index and, by extension, in the queries behind the "bom_bill_of_materials_u2" search term. It is commonly used by reports, concurrent programs, and custom forms that need the exploded structure without re-invoking the explosion engine, and it is a frequent target for ad hoc SQL written by technical consultants investigating structure, cost, and lead-time questions.

Underlying Base Objects

Per the documented view metadata, the view is defined over the following referenced base objects:

• BOM_EXPLOSION_TEMP (synonym) — the driving table; holds the exploded rows keyed by TOP_BILL_SEQUENCE_ID, BILL_SEQUENCE_ID, COMPONENT_SEQUENCE_ID, and GROUP_ID.
• BOM_STRUCTURES_B (synonym) — supplies the parent assembly definition, including ASSEMBLY_ITEM_ID, ALTERNATE_BOM_DESIGNATOR, and ASSEMBLY_TYPE.
• MTL_ITEM_FLEXFIELDS (view) — the descriptive flexfield view over MTL_SYSTEM_ITEMS, providing the underlying item attributes surfaced through MSI.
• MFG_LOOKUPS (view) — resolves lookup codes to their display meanings, such as basis type and sales-order basis.

The view text carries an ORDERED hint with explicit index directives, including INDEX(BOM BOM_BILL_OF_MATERIALS_U2), which forces the optimizer to drive the join through BOM_STRUCTURES_B using that unique index. This is the direct link between the view and the "bom_bill_of_materials_u2" search: the indexed access path on the parent bill header is what makes the join from explosion temp rows back to the assembly efficient.

Key Columns

The view exposes identifier, structural, quantity, and attribute columns:

• Identifiers: TOP_BILL_SEQUENCE_ID, BILL_SEQUENCE_ID, COMPONENT_SEQUENCE_ID, COMPONENT_ITEM_ID, TOP_ITEM_ID, PARENT_ITEM_ID, ORGANIZATION_ID, GROUP_ID.
• Structure and level: PLAN_LEVEL and DISPLAY_PLAN_LEVEL (an LPAD-formatted indented level), SORT_ORDER, ITEM_NUM, PARENT_ALTERNATE, TOP_ALTERNATE_DESIGNATOR, ENG_BILL.
• Quantities and costing: COMPONENT_QUANTITY, EXTENDED_QUANTITY, ITEM_COST, EXTENDED_COST (derived from EXTEND_COST_FLAG and EXTENDED_QUANTITY), COMPONENT_YIELD_FACTOR, PLANNING_FACTOR, MINIMUM_QUANTITY, MAXIMUM_QUANTITY.
• Dates and effectivity: EFFECTIVITY_DATE, DISABLE_DATE, IMPLEMENTATION_DATE, plus EFFECTIVITY_TIME and DISABLE_TIME extracted with TO_CHAR(...,'HH24:MI').
• Component attributes: OPTIONAL, WIP_SUPPLY_TYPE, SUPPLY_SUBINVENTORY, SUPPLY_LOCATOR_ID, CHECK_ATP, REQUIRED_TO_SHIP, REQUIRED_FOR_REVENUE, INCLUDE_ON_SHIP_DOCS, INCLUDE_IN_ROLLUP_FLAG, MUTUALLY_EXCLUSIVE_OPTIONS, CHANGE_NOTICE, OPERATION_SEQ_NUM, OPERATION_LEAD_TIME_PERCENT.
• Item master attributes: UNIT_OF_MEASURE, ITEM_TYPE, DESCRIPTION, BOM_ITEM_TYPE, ENG_ITEM_FLAG, ATO_FLAG, PICK_COMPONENTS_FLAG, ATP_COMPONENTS_FLAG, ATP_FLAG, SHIPPABLE_ITEM_FLAG, CUM_MANUFACTURING_LEAD_TIME, CUMULATIVE_TOTAL_LEAD_TIME, MANUFACTURING_LEAD_TIME, and RESERVABLE_TYPE (NVL'd to 2).
• Lookup-resolved meanings: BASIS_TYPE and SO_BASIS via MFG_LOOKUPS.

Common Use Cases and Queries

Typical applications include multi-level BOM reports, component cost summaries, lead-time aggregation, and ATP-relevant component analysis. A representative query filtering to a single exploded group and organization:

• SELECT plan_level, item_num, component_item_id, extended_quantity, extended_cost, unit_of_measure, effectivity_date FROM apps.bom_explosion_view WHERE group_id = :group_id AND organization_id = :org_id ORDER BY sort_order;
• SELECT parent_item_id, parent_alternate, item_num, component_quantity, manufacturing_lead_time FROM apps.bom_explosion_view WHERE top_item_id = :item_id AND organization_id = :org_id AND plan_level <= 2;
• SELECT item_num, SUM(extended_cost) total_cost FROM apps.bom_explosion_view WHERE group_id = :group_id GROUP BY item_num;

Because the underlying BOM_EXPLOSION_TEMP is populated and scoped by GROUP_ID, all queries against the view must be correlated to a valid group_id and organization_id. The view is read-only and should not be used as a substitute for the explosion engine; its value lies in providing a convenient, pre-joined projection of an already-exploded structure for reporting and integration purposes.