Search Results bom_explosions_all_v




Overview
Explore in AI Chat

Overview

BOM_EXPLOSIONS_ALL_V is an APPS-owned view in the Oracle E-Business Suite Bills of Material (BOM) module, valid in both release 12.1.1 and 12.2.2. It is defined directly over the BOM_EXPLOSIONS_ALL table and exists to expose the exploded bill of material structure alongside component-level detail, item attributes, and descriptive flexfield context. The base table BOM_EXPLOSIONS_ALL is populated by the BOM exploder when a bill is exploded, and it stores the flattened, multi-level result of that explosion (parent, component, level, quantity, sequence). Because reading the raw explosion table alone yields only IDs and numeric facts, this view joins in component master data and descriptive flexfield values to produce a report-ready result set.

The view plays a dual role. In reporting, it is the standard source for indented bill of material reports, cost rollup extracts, and component where-used style queries. In integration, it provides a stable projection of the explosion structure for concurrent programs and external interfaces that need item descriptions and flexfield context without rebuilding the joins themselves. Note that the view returns rows only for bills that have already been exploded; it does not itself perform the explosion.

Underlying Base Objects

The primary object is the synonym BOM_EXPLOSIONS_ALL. The view text also references BOM_COMPONENTS_B (for component-level attributes such as BASIS_TYPE, SO_BASIS, OPTIONAL, CHECK_ATP, and the quantity ranges), MTL_SYSTEM_ITEMS_TL (for the component description in the session language), and the ATTRIBUTE columns sourced through the component descriptive flexfield. The documented dependency list also includes MTL_SYSTEM_ITEMS_B, MTL_SYSTEM_ITEMS_KFV, MTL_ITEM_REVISIONS and MTL_ITEM_REVISIONS_B, BOM_ALTERNATE_DESIGNATORS_TL, ENG_ENGINEERING_CHANGES, FND_LOOKUPS, FND_DOCUMENTS_TL, FND_ATTACHED_DOCUMENTS, FND_DOCUMENT_CATEGORIES_VL, the MTL_ITEM_CATALOG_GROUPS_KFV structure-view, and DUAL.

Programmatic logic is supplied by the BOM_EXPLODER_PUB, BOM_GLOBALS and BOM_SECURITY_PUB packages, which govern explosion behavior and row-level access. Description resolution is conditional: when OBJ_NAME is null or equal to 'EGO_ITEM' the component is treated as an inventory (MSI) item and the description is fetched from MTL_SYSTEM_ITEMS_TL using PK1_VALUE (component item) and PK2_VALUE (organization) with USERENV('LANG') as the language. For non-MSI components, such as CAD-sourced objects, the description is resolved differently, which is why the same column can contain values from more than one source.

Key Columns

Regarding the user's search term object_version: neither this view nor its documented base objects expose an OBJECT_VERSION_NUMBER column. The view is built on the pre-versioning BOM_EXPLOSIONS_ALL structure, so concurrency control is not surfaced here. Applications requiring optimistic locking must obtain OBJECT_VERSION_NUMBER from the underlying entity tables (for example MTL_SYSTEM_ITEMS_B or BOM_COMPONENTS_B) rather than from this view, and should not assume its presence in a SELECT * against BOM_EXPLOSIONS_ALL_V.

Common Use Cases and Queries

The most frequent use is an indented bill report for a given top assembly and organization. The following returns components in structural order with descriptions:

  • SELECT b.top_item_id, b.component_item_id, b.plan_level, b.component_quantity, b.extended_quantity, b.primary_uom_code FROM bom_explosions_all_v b WHERE b.organization_id = :org_id AND b.top_item_id = :top_item_id AND b.explosion_type = :expl_type ORDER BY b.sort_order;
  • Filtering to a single level for a "first-level components" report by adding AND b.plan_level = 1.
  • Resolving descriptive flexfield values, e.g. selecting b.context, b.attribute1, b.attribute2 for a component where the context matches a known DFF structure.
  • Isolating unresolved components with WHERE b.component_item_id = -1 to detect explosion rows whose component master record could not be resolved.
  • Joining to MTL_SYSTEM_ITEMS_KFV on component_item_id for concatenated item names when the supplied description is insufficient.

Because the explosion table is populated by the exploder, callers should ensure the bill has been exploded for the relevant organization and explosion type before querying, and should apply organization and security predicates consistent with BOM_SECURITY_PUB access rules.