Search Results lowest_item_id




Overview
Explore in AI Chat

Overview

APPS.BOM_IMPLOSION_VIEW is a reporting view in Oracle E-Business Suite (validated against 12.1.1 and 12.2.2) that exposes the results of the Bill of Materials implosion process. Whereas an explosion walks downward from a parent assembly to its components, an implosion walks upward from a component (or a "lowest item") through every parent assembly in which it is used. The view presents the flattened, denormalized result of that upward traversal, joining the staging table produced by the implosion concurrent program to item master and lookup data so that each row is presentation-ready.

The view is defined over BOM_IMPLOSION_TEMP and three supporting objects, and it is intended primarily for querying and reporting rather than for transactional maintenance. Because the implosion logic writes intermediate results into BOM_IMPLOSION_TEMP, the view acts as a stable, join-enriched facade over that temporary data, sparing report authors from reconstructing the item flexfield, UOM, and basis-type lookups themselves. The presence of columns such as CURRENT_LEVEL, SEQUENCE_ID, and SORT_CODE confirms that the view preserves the hierarchical ordering produced by the implosion engine.

Underlying Base Objects

The documented base objects behind this view are:

  • BOM_IMPLOSION_TEMP (SYNONYM) — the driving table, holding one row per node visited during the implosion, including level, sequencing, and quantity data.
  • MTL_ITEM_FLEXFIELDS (VIEW) — supplies descriptive flexfield attributes keyed by ITEM_ID and ORGANIZATION_ID.
  • MTL_SYSTEM_ITEMS_B (SYNONYM) — the item master, providing inventory item identifiers, UOM, and item type.
  • MFG_LOOKUPS (VIEW) — resolves the basis type code to a user-facing meaning.

The joins are explicit: T.PARENT_ITEM_ID = F.ITEM_ID and T.ORGANIZATION_ID = F.ORGANIZATION_ID tie the temp row to flexfield data; T.ORGANIZATION_ID = I.ORGANIZATION_ID and T.CURRENT_ITEM_ID = I.INVENTORY_ITEM_ID tie it to the item master. The MFG_LOOKUPS join is an outer join (LU.LOOKUP_TYPE (+) = 'BOM_BASIS_TYPE' with LU.LOOKUP_CODE = NVL(T.BASIS_TYPE,1)), so rows survive even when no basis type lookup exists, defaulting the lookup code to 1.

Key Columns

Notable columns include:

  • SEQUENCE_ID / SORT_CODE — ordering keys that preserve the implosion traversal sequence.
  • CURRENT_LEVEL — the depth of the node relative to the implosion start point; also rendered hierarchically via LPAD(CURRENT_LEVEL, LEAST(CURRENT_LEVEL,8), '.') for indented display.
  • LOWEST_ITEM_ID — the originating (lowest-level) item from which the implosion began.
  • PARENT_ITEM_ID / CURRENT_ITEM_ID — the assembly and component for a given node row.
  • ORGANIZATION_ID — the inventory organization context.
  • ITEM_NUMBER / DESCRIPTION / ITEM_TYPE / PRIMARY_UOM_CODE — descriptive and UOM attributes sourced from the item master and flexfields.
  • ALTERNATE_DESIGNATOR, OPERATION_SEQ_NUM, COMPONENT_QUANTITY, EFFECTIVITY_DATE, DISABLE_DATE — component-specific BOM attributes.
  • BASIS_TYPE — the decoded meaning from MFG_LOOKUPS.
  • CHANGE_NOTICE, REVISED_ITEM_SEQUENCE_ID, IMPLEMENTED_FLAG — engineering change and implementation status indicators.

Common Use Cases and Queries

Typical uses include "where-used" analysis, component impact reporting, and multi-level BOM roll-ups for costing or change management. A common query filters by organization and displays the level indentation:

  • SELECT current_level, item_number, description, component_quantity FROM apps.bom_implosion_view WHERE organization_id = :org_id ORDER BY sequence_id;
  • SELECT parent_item_id, current_level, item_number FROM apps.bom_implosion_view WHERE lowest_item_id = :item_id AND organization_id = :org_id ORDER BY sort_code;
  • SELECT item_number, basis_type, change_notice FROM apps.bom_implosion_view WHERE organization_id = :org_id AND implemented_flag = 'Y';

Note that BOM_IMPLOSION_TEMP is populated by the implosion process, so meaningful results depend on that program having run for the relevant session or item. Afterward, this view provides a convenient, pre-joined source for concurrent reports, Oracle Discoverer/BI Publisher datasets, and custom forms.