Search Results item_type_description




Overview
Explore in AI Chat

Overview

BOM_EXPL_INQUIRY_VIEW is an APPS-owned database view in the Oracle E-Business Suite Bills of Material (BOM) module. It exposes the indented bill of material structure that is displayed by the Bills of Material inquiry window, presenting the multilevel explosion of an assembly as a flat, query-friendly result set. Rather than requiring the caller to walk the BOM explosion hierarchy manually, the view returns one row per component occurrence at each level, already joined to item master attributes, lookup meanings, and lead-time data.

Because the view is a read-only projection, it is safe to use in custom reports, Discoverer workbooks, and integration extracts without risk of modifying BOM data. The view text carries an ORDERED FIRST_ROWS hint with explicit index directives against MTL_SYSTEM_ITEMS_U1, BOM_BILL_OF_MATERIALS_U2, MFG_LOOKUPS_U1, and FND_COMMON_LOOKUPS_U1, indicating it was tuned for interactive, first-screen retrieval in a form window. Report developers should therefore expect fast response on the leading rows but should not assume the hint will survive rewrites or force a different plan under high-volume batch extraction.

Underlying Base Objects

The documented base objects referenced by the view are as follows:

The view does not own storage; all data originates from these referenced objects, with the temporary explosion table supplying the per-level component sequence.

Key Columns

Common Use Cases and Queries

Typical uses include multilevel BOM inquiry reports, costed or non-costed explosion extracts, engineering change impact analysis, and integration feeds into planning or MES systems. Users filtering on item status typically want either to exclude obsolete or inactive components or to isolate items flagged with a particular inventory status.

Example — list components and their inventory status for a given top assembly:

  • SELECT plan_level, component_item_id, item_num, unit_of_measure, component_quantity, item_status, description
  • FROM apps.bom_expl_inquiry_view
  • WHERE organization_id = :org_id
  • AND top_item_id = :top_item_id
  • ORDER BY sort_order;

Example — find all exploded rows where a component carries a specific inventory item status:

  • SELECT top_item_id, parent_item_id, component_item_id, item_num, plan_level, item_status
  • FROM apps.bom_expl_inquiry_view
  • WHERE organization_id = :org_id
  • AND item_status = 'Inactive'
  • ORDER BY top_item_id, sort_order;

Because the view is tuned for FIRST_ROWS retrieval, queries returning a full organization-wide explosion should be constrained by ORGANIZATION_ID and TOP_ITEM_ID, and batch extracts should be scheduled off-peak. Remember that the explosion reflected is driven by the temporary explosion table populated during the inquiry session, so results reflect the alternate, revision, and effectivity parameters in force at runtime.