Search Results bom_impl_inquiry_view




Overview

BOM_IMPL_INQUIRY_VIEW is an APPS-owned, VALID database view in the Oracle E-Business Suite Bills of Material (BOM) product. The ETRM metadata describes its purpose as being "used for inquiry window," which identifies it as a presentation-layer construct rather than a foundational transactional object. The view presents an exploded, multi-level bill of material structure together with descriptive item attributes, unit-of-measure information, effectivity dates, and basis type meanings, and is designed to feed an inquiry screen through which users examine implemented BOM structures. Its columns are exposed under display-oriented aliases such as PARENT, PARENT_DESCRIPTION, PARENT_UOM, PARENT_ALTERNATE_DESIGNATOR, PARENT_ENGINEERING_BILL, COMPONENT_OP_SEQ_NUM, COMPONENT_EFFECTIVE_DATE, COMPONENT_EFFECTIVE_TIME, COMPONENT_DISABLE_DATE, COMPONENT_DISABLE_TIME, BASIS_TYPE, COMPONENT_QUANTITY, CHANGE_NOTICE, REVISED_ITEM_SEQUENCE_ID, ITEM_TYPE, DISPLAY_PLAN_LEVEL, and IMPLEMENTED_FLAG. In reporting and integration contexts, the view is used to render implemented bill structures without requiring callers to reconstruct joins between the exploded temporary structure and item master data. It is documented in ETRM for both Oracle EBS 12.1.1 and 12.2.2 with identical base-object dependencies.

Underlying Base Objects

The view text joins four documented base objects. BOM_SMALL_IMPL_TEMP is referenced as a synonym and supplies the exploded structure columns, including SEQUENCE_ID, LOWEST_ITEM_ID, SORT_CODE, CURRENT_LEVEL, PARENT_ITEM_ID, ORGANIZATION_ID, CURRENT_ITEM_ID, ALTERNATE_DESIGNATOR, CURRENT_ASSEMBLY_TYPE, OPERATION_SEQ_NUM, EFFECTIVITY_DATE, DISABLE_DATE, BASIS_TYPE, COMPONENT_QUANTITY, CHANGE_NOTICE, REVISED_ITEM_SEQUENCE_ID, and IMPLEMENTED_FLAG. MTL_ITEM_FLEXFIELDS, documented as a view, provides item flexfield descriptive data via ITEM_ID and ORGANIZATION_ID and is joined on PARENT_ITEM_ID and ORGANIZATION_ID. MTL_SYSTEM_ITEMS_B, referenced as a synonym, supplies item master attributes through a join on ORGANIZATION_ID and CURRENT_ITEM_ID = INVENTORY_ITEM_ID. MFG_LOOKUPS, documented as a view, is outer-joined (LU.LOOKUP_TYPE (+) = 'BOM_BASIS_TYPE') and supplies the BASIS_TYPE meaning where LOOKUP_CODE equals NVL(BASIS_TYPE, 1).

Key Columns

  • SEQUENCE_ID, LOWEST_ITEM_ID, SORT_CODE, CURRENT_LEVEL — structural identifiers used to order and level the exploded hierarchy.
  • PARENT_ITEM_ID, ORGANIZATION_ID, PARENT — the parent assembly identifier and its display item number.
  • PARENT_DESCRIPTION, PARENT_UOM, PARENT_ALTERNATE_DESIGNATOR, PARENT_ENGINEERING_BILL — descriptive and alternate information for the parent assembly.
  • COMPONENT_OP_SEQ_NUM — the operation sequence number associated with the component.
  • COMPONENT_EFFECTIVE_DATE, COMPONENT_EFFECTIVE_TIME, COMPONENT_DISABLE_DATE, COMPONENT_DISABLE_TIME — effectivity and disable timing for the component.
  • BASIS_TYPE — the basis type meaning resolved from MFG_LOOKUPS for lookup type BOM_BASIS_TYPE.
  • COMPONENT_QUANTITY — the component quantity per assembly.
  • CHANGE_NOTICE, REVISED_ITEM_SEQUENCE_ID — engineering change order and revised sequence references.
  • ITEM_TYPE — the item type of the parent or component item.
  • DISPLAY_PLAN_LEVEL — a formatted level string produced by LPAD(CURRENT_LEVEL, LEAST(CURRENT_LEVEL, 8), '.').
  • IMPLEMENTED_FLAG — indicates whether the structure is implemented.

Common Use Cases and Queries

Typical use is inquiry-style retrieval of an implemented bill structure for one organization and parent assembly, or reporting on component quantities with descriptive item data. The view is not intended for high-volume transaction processing, given its dependence on an exploded temporary structure.

  • Retrieve all levels for a parent assembly in an organization, ordered by SORT_CODE or SEQUENCE_ID.
  • Filter on IMPLEMENTED_FLAG to display only implemented structures.
  • Report component quantities by operation sequence number.

SELECT sequence_id, current_level, parent, parent_description, parent_uom, component_op_seq_num, component_quantity, basis_type, component_effective_date, component_disable_date, change_notice, implemented_flag FROM apps.bom_impl_inquiry_view WHERE organization_id = :org_id AND parent_item_id = :parent_item_id ORDER BY sort_code;

SELECT parent, parent_description, count(*) component_count FROM apps.bom_impl_inquiry_view WHERE organization_id = :org_id GROUP BY parent, parent_description ORDER BY parent;