Search Results line_op

Overview

The WIP_EXPLOSIONS_V view, owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2, exposes work in process (WIP) explosion information for discrete and repetitive manufacturing environments. It is a reporting and integration construct that presents the flattened component structure of an assembly as defined by the bill of materials (BOM) and routing, joined against item master attributes. Because it is a view rather than a base table, it carries no storage of its own and reflects the current state of the underlying BOM and item definition data at query time. The view filters its resultset to explosion type ALL and to components whose quantity is greater than zero, ensuring that only active, quantity-bearing components are returned. Its primary value lies in providing a single denormalized source for component descriptions, quantities, supply subinventories, and locators without requiring the caller to replicate the multi-table join logic.

Underlying Base Objects

The view is defined over six documented base objects: BOM_EXPLOSIONS, BOM_INVENTORY_COMPONENTS, BOM_OPERATIONAL_ROUTINGS, BOM_OPERATION_SEQUENCES, BOM_STANDARD_OPERATIONS, and MTL_SYSTEM_ITEMS_KFV. The driving table is BOM_EXPLOSIONS, aliased BE, which supplies the component item, organization, top bill sequence, effectivity and disable dates, and the operation sequence number. BOM_INVENTORY_COMPONENTS (BIC) is joined on component sequence and contributes yield factor, WIP supply type, supply subinventory, and supply locator. MTL_SYSTEM_ITEMS_KFV (MSIK) is joined on inventory item and organization, providing the concatenated segment identifier and description. Routing information is joined through BOM_OPERATIONAL_ROUTINGS (BOR), BOM_OPERATION_SEQUENCES (BOS), and BOM_STANDARD_OPERATIONS (BSO), with a correlated subquery against BOM_OPERATION_SEQUENCES resolving the line operation sequence. Results are ordered by component code.

Key Columns

• ROW_ID — the ROWID of the BOM_EXPLOSIONS row, useful as a surrogate identifier.
• OPERATION_SEQ_NUM — the operation sequence number at which the component is consumed.
• LINE_OP and LINE_OP_CODE — the line operation sequence and its corresponding operation code.
• COMPONENT — the concatenated flexfield segments of the component item.
• COMPONENT_ITEM_ID — the inventory item identifier of the component.
• COMPONENT_DESCRIPTION — the item description; this is the column most commonly targeted by users searching for "component_description".
• COMPONENT_QUANTITY — the required quantity, divided by the component yield factor to normalize for expected loss.
• SUPPLY_SUBINVENTORY and SUPPLY_LOCATOR_ID — the supply subinventory and locator, resolved from BOM_INVENTORY_COMPONENTS falling back to item-level WIP defaults.
• WIP_SUPPLY_TYPE, COMPONENT_CODE, MTL_TRANSACTIONS_ENABLED_FLAG, PRIMARY_UOM_CODE, and REVISION_QTY_CONTROL_CODE — supporting supply, transaction, and unit-of-measure attributes.
• TOP_BILL_SEQUENCE_ID, TOP_ITEM_ID, and ORGANIZATION_ID — identify the parent assembly and organization.
• EFFECTIVITY_DATE, DISABLE_DATE, and ALTERNATE_ROUTING_DESIGNATOR — date ranges and routing context for the explosion.

Common Use Cases and Queries

Typical uses include component where-used reporting, BOM structure validation, pick-list generation, and feeding downstream integration tables with component descriptions and supply defaults. A common query returns descriptions for all components of a given assembly in an organization:

• SELECT TOP_ITEM_ID, OPERATION_SEQ_NUM, COMPONENT, COMPONENT_DESCRIPTION, COMPONENT_QUANTITY FROM WIP_EXPLOSIONS_V WHERE TOP_ITEM_ID = :item_id AND ORGANIZATION_ID = :org_id ORDER BY COMPONENT;
• SELECT COMPONENT, COMPONENT_DESCRIPTION FROM WIP_EXPLOSIONS_V WHERE COMPONENT_ITEM_ID = :component_item_id; — resolves the assemblies and operation context in which a component is used.
• SELECT DISTINCT COMPONENT_ITEM_ID, COMPONENT_DESCRIPTION FROM WIP_EXPLOSIONS_V WHERE ORGANIZATION_ID = :org_id; — produces a distinct component list for validation or mapping.

Because the view performs joins across routing and component tables and includes a correlated subquery, queries should be constrained by ORGANIZATION_ID and, where possible, TOP_ITEM_ID or COMPONENT_ITEM_ID to limit execution cost.