Results for “parent_description”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BOM_IMPLOSION_VIEW is a reporting view in the Oracle E-Business Suite Bills of Material (BOM) module, owned by the APPS schema and documented as VALID in ETRM. Its stated purpose is to support inquiry reporting: it presents the results of a bill-of-material implosion (the multi-level upward traversal of a component to all assemblies in which it is used) in a flattened, presentation-ready format. In EBS 12.1.1 and 12.2.2 this view is typically consumed by the BOM implosion inquiry screens and by custom reporting that reproduces "where-used" analysis across a manufacturing organization.

The view does not store data. It joins a temporary working table (BOM_IMPLOSION_TEMP), populated by the implosion inquiry process, to item master and lookup views so that the caller receives item descriptions, units of measure, and decoded basis types alongside the hierarchical implosion structure.

Underlying Base Objects

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

• BOM_IMPLOSION_TEMP (SYNONYM) — the driving source, holding the exploded implosion rows (ALIAS T).
• MTL_ITEM_FLEXFIELDS (VIEW) — supplies the parent item number and description (ALIAS F); joined on PARENT_ITEM_ID and ORGANIZATION_ID.
• MTL_SYSTEM_ITEMS_B (SYNONYM) — supplies primary UOM and item type (ALIAS I); joined on ORGANIZATION_ID and CURRENT_ITEM_ID to INVENTORY_ITEM_ID.
• MFG_LOOKUPS (VIEW) — an outer-joined lookup (ALIAS LU) decoding BASIS_TYPE via LOOKUP_TYPE 'BOM_BASIS_TYPE', defaulting to 1 when BASIS_TYPE is null.

Because the driving object is a temporary table, the view returns meaningful rows only while an implosion inquiry session is active; it is not a persistent reporting source for historical data.

Key Columns

• SEQUENCE_ID, SORT_CODE, CURRENT_LEVEL — ordering and hierarchy control for the implosion result set.
• LOWEST_ITEM_ID, PARENT_ITEM_ID, ORGANIZATION_ID — the component being traced and the assembly in which it is used, scoped to an inventory organization.
• PARENT, PARENT_DESCRIPTION, PARENT_UOM — presentation columns mapped from F.ITEM_NUMBER, F.DESCRIPTION and I.PRIMARY_UOM_CODE.
• PARENT_ALTERNATE_DESIGNATOR, PARENT_ENGINEERING_BILL — alternate BOM designator and engineering bill indicator.
• COMPONENT_OP_SEQ_NUM, COMPONENT_EFFECTIVE_DATE, COMPONENT_DISABLE_DATE — operation sequence and effectivity window of the component usage.
• BASIS_TYPE, COMPONENT_QUANTITY — decoded basis (per assembly or per unit) and the component quantity per parent.
• CHANGE_NOTICE, REVISED_ITEM_SEQUENCE_ID, ITEM_TYPE, IMPLEMENTED_FLAG — engineering change and implementation context.
• DISPLAY_PLAN_LEVEL — LPAD-based dotted indentation used by the inquiry report to render level depth.

Common Use Cases and Queries

The principal use case is the BOM implosion / where-used inquiry, where a component is traced upward through all parent assemblies. A representative query is:

SELECT CURRENT_LEVEL, PARENT, PARENT_DESCRIPTION, PARENT_UOM, BASIS_TYPE, COMPONENT_QUANTITY FROM APPS.BOM_IMPLOSION_VIEW WHERE ORGANIZATION_ID = :org_id ORDER BY SORT_CODE, SEQUENCE_ID;

Additional scenarios include reproducing inquiry output in custom reports, inspecting effectivity and change-notice context for a component, and validating basis-type decoding. Because the view depends on BOM_IMPLOSION_TEMP, SQL submitted outside an active implosion run generally returns no rows; developers requiring persistent where-used data should instead query BOM_BILL_OF_MATERIALS and BOM_COMPONENTS_B or use the BOM implosion APIs.