Search Results component_description

Overview

BOM_IMPLOSIONS_V is a predefined Oracle E-Business Suite view owned by the APPS schema and shipped as part of the Bill of Materials (BOM) product family. In Oracle EBS 12.1.1 and 12.2.2 it exposes the "where-used" side of a bill of materials — that is, the parent assemblies in which a given component is consumed — as opposed to the standard explosion view (BOM_EXPLOSIONS_V), which walks downward from a parent to its components. ETRM documents the object as a VALID view "for displaying BOM implosions," and this single-purpose definition underpins its role in reporting and integration.

Because the view is defined over the same implosion engine used by the BOM Inquiry "Where Used" window, it is the natural source for any custom report, concurrent program, or interface that must determine where an item is used across organizations without re-implementing the indented bill logic. The view returns one row per occurrence of the current item within a parent structure, carrying both the parent identity and the current item identity, so a single query can return a component together with every assembly above it.

Underlying Base Objects

The view is defined with a driving hint (/*+ LEADING(T) */) over the implosion temporary structure BOM_SMALL_IMPL_TEMP, aliased T. This synonym holds the flattened, temporarily materialized implosion rows populated by the BOM implosion APIs and packages such as BOM_GLOBALS. The view joins that structure to descriptive and validation objects, notably:

• MTL_SYSTEM_ITEMS_VL and EGO_ITEMS_V — parent, current, and inventory item attributes, including concatenated segments and descriptions.
• MTL_ITEM_REVISIONS_B — revision labels resolved through scalar subqueries for effectivity control by revision.
• MFG_LOOKUPS and FND_LOOKUP_VALUES — meanings for effectivity control, basis type, and item type.
• BOM_ALTERNATE_DESIGNATORS_TL and BOM_STRUCTURE_TYPES_VL — alternate designator and structure type context.
• ENG_ENGINEERING_CHANGES — engineering change order reference carried on the row.
• HR_ORGANIZATION_UNITS plus the HR_SECURITY, HR_GENERAL, FND_GLOBAL, and FND_FLEX_SERVER packages — organization name resolution and security enforcement.
• MTL_PARAMETERS, MTL_ITEM_CATALOG_GROUPS — inventory organization parameters and catalog grouping context.

Key Columns

• ORGANIZATION_CODE, ORG_NAME, ORGANIZATION_ID — the manufacturing organization for the implosion row.
• CURRENT_ITEM_ID, CURRENT_CONCATENATED_SEGMENTS, CURRENT_DESCRIPTION — the component being located.
• PARENT_ITEM_ID, CONCATENATED_SEGMENTS, DESCRIPTION — the parent assembly that consumes the component.
• COMPONENT_QUANTITY — the usage quantity of the component in the parent.
• CURRENT_LEVEL — the indentation level within the imploded structure.
• ALTERNATE_DESIGNATOR, OPERATION_SEQ_NUM — alternate bill and routing operation context.
• CURRENT_REVISION — revision of the current item.
• COMPONENT_EFFECTIVE_FROM / COMPONENT_EFFECTIVE_TO — decoded effectivity dates, unit numbers, or revision labels depending on EFFECTIVITY_CONTROL.
• IMPLEMENTED_FLAG, DISABLED_FLAG — whether the usage is implemented and whether the disable date has passed.
• CHANGE_NOTICE, REVISED_ITEM_SEQUENCE_ID — engineering change association.

Common Use Cases and Queries

The most frequent use is locating every parent consuming a component, often prompted by item number or description. A typical query filters by the current item description:

SELECT organization_code,
       concatenated_segments      parent_item,
       current_concatenated_segments component_item,
       component_quantity,
       current_level
FROM   apps.bom_implosions_v
WHERE  current_description LIKE :component_description
AND    organization_id = :org_id;

Additional scenarios include impact analysis for engineering change orders (joining on CHANGE_NOTICE), multi-level where-used reporting for cost roll-up, and data extraction for downstream planning or master-data governance. Because the view depends on organization security and implosion parameters, callers should always restrict by ORGANIZATION_ID and initialize the BOM/HR security context before querying.