Search Results component_effective_time

Overview

APPS.BOM_IMPL_INQUIRY_VIEW is a reporting view in Oracle E-Business Suite that exposes the results of the Bill of Materials inquiry engine, specifically the flattened, multi-level explosion and implosion data produced by the BOM inquiry "small implementation" temporary structure. The view joins that temporary hierarchy against item master and descriptive flexfield data so that each row represents a single component occurrence within a multilevel bill, enriched with item attributes, unit of measure, effectivity, and lookup-translated basis information.

The view is principally consumed by Oracle Bills of Materials inquiry forms, concurrent report output, and custom reporting or integration layers that need to present an indented bill structure without directly querying the transient BOM_SMALL_IMPL_TEMP table. Because the underlying temporary table holds query-scoped results, this view is meaningful only while a BOM inquiry session has populated that table. It presents the organizational hierarchy columns, the parent-to-component relationship, quantity, and the basis type that governs how component quantity is interpreted.

Underlying Base Objects

As documented in the ETRM metadata, the view is defined over four referenced objects:

• BOM_SMALL_IMPL_TEMP (SYNONYM) — the driving table, aliased T, holding the exploded hierarchy: sequence_id, lowest_item_id, sort_code, current_level, parent_item_id, current_item_id, organization_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 (VIEW) — aliased F, supplying item_number, description, and item_type; joined on parent_item_id = item_id and organization_id.
• MTL_SYSTEM_ITEMS_B (SYNONYM) — aliased I, supplying primary_uom_code; joined on organization_id and current_item_id = inventory_item_id.
• MFG_LOOKUPS (VIEW) — aliased LU, an outer-joined lookup resolving lookup_type = 'BOM_BASIS_TYPE' to the basis_type meaning.

The join path is therefore a standard EBS item-master enrichment pattern: hierarchy facts from the temporary explosion joined to item descriptive data, inventory attributes, and lookup translation.

Key Columns

• SEQUENCE_ID / REVISED_ITEM_SEQUENCE_ID — identifies each row and revision lineage within the exploded structure.
• CURRENT_LEVEL and its LPAD derivative — the indentation depth of the component, with indentation capped at eight dots.
• PARENT_ITEM_ID / CURRENT_ITEM_ID — the assembly-to-component relationship; the view exposes ITEM_NUMBER, DESCRIPTION, and ITEM_TYPE for the parent via the flexfields join.
• PRIMARY_UOM_CODE — the unit of measure of the current component.
• BASIS_TYPE — the lookup meaning for BOM_BASIS_TYPE, resolved through NVL(T.BASIS_TYPE,1); this is the column most directly relevant to the user's search on "bom_basis_type," indicating whether the component quantity is expressed per assembly or per unit of measure.
• COMPONENT_QUANTITY — the quantity required, whose interpretation depends on BASIS_TYPE.
• EFFECTIVITY_DATE / DISABLE_DATE — component validity window, each paired with an HH24:MI time component.
• ALTERNATE_DESIGNATOR, OPERATION_SEQ_NUM, CHANGE_NOTICE, IMPLEMENTED_FLAG, CURRENT_ASSEMBLY_TYPE — manufacturing and engineering context.

Common Use Cases and Queries

Typical uses include indented bill reports, where-to-used and where-used analysis, engineering change-in-progress review, and feeder queries for integration into third-party planning systems. Because BASIS_TYPE is a lookup-driven column, analysts frequently filter or group by it to separate per-assembly from per-item quantities.

A representative query selects the indented hierarchy for a given organization and parent:

• SELECT v.current_level, v.item_number, v.description, v.basis_type, v.component_quantity, v.primary_uom_code
• FROM apps.bom_impl_inquiry_view v
• WHERE v.organization_id = :org_id
• AND v.parent_item_id = :parent_id
• ORDER BY v.sort_code, v.sequence_id;

To isolate basis-type behaviour, add AND v.basis_type = 'Item' or group by BASIS_TYPE to compare quantity semantics. Because the view depends on session-populated temporary data, these queries are normally executed within the context of the BOM inquiry form or after the explosion routine has been invoked for the organization and item in question.