Results for “bom_inv_comps_interface_v”

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

Overview

BOM_INV_COMPS_INTERFACE_V is an APPS-owned view in Oracle E-Business Suite that exposes the Bill of Materials mass change component interface for reporting, validation, and integration purposes. Its documented description is "Mass change components," and it is delivered in the BOM – Bills of Material product family. The view presents the transient, unprocessed contents of the mass change component interface so that concurrent programs, custom forms, and integration code can inspect staged component rows prior to validation and loading into the production bill structures.

Functionally, the view serves as a controlled read layer over BOM_INVENTORY_COMPS_INTERFACE. It joins interface rows to master item attributes, supplying descriptive and defaulting information that the mass change engine subsequently applies to the target bill. This makes the view central to engineering change workflows where component substitutions, quantity revisions, yield factor changes, or effectivity adjustments are applied across multiple assemblies.

Underlying Base Objects

The documented base objects referenced by BOM_INV_COMPS_INTERFACE_V are BOM_INVENTORY_COMPS_INTERFACE (synonym), BOM_ITEM_CURRENT_REV_VIEW (view), ENG_REVISED_ITEMS_INTERFACE (synonym), FND_COMMON_LOOKUPS (view), FND_GLOBAL (package), MFG_LOOKUPS (view), and MTL_SYSTEM_ITEMS (synonym).

The primary source is BOM_INVENTORY_COMPS_INTERFACE, which supplies the component rows, including operation sequence numbers, component item IDs, quantities, yield factors, effectivity dates, planning attributes, and the standard WHO audit columns. MTL_SYSTEM_ITEMS contributes item master attributes such as description, primary unit of measure, BOM item type, ATP flags, shippable and cost rollup defaults, and WIP supply defaults. BOM_ITEM_CURRENT_REV_VIEW and ENG_REVISED_ITEMS_INTERFACE link the interface rows to current revisions and to revised item changes staged during mass change processing. FND_COMMON_LOOKUPS and MFG_LOOKUPS supply lookup meanings for coded columns, while FND_GLOBAL provides session context. The interface columns carry the standard request identifiers — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE — that associate staged rows with the concurrent request that created them.

Key Columns

• ROW_ID — the ROWID of the underlying interface row, used to uniquely identify a staged record.
• COMPONENT_ITEM_ID / ITEM_NUM — identifies the component item being introduced or modified.
• OPERATION_SEQ_NUM / COMPONENT_SEQUENCE_ID / OLD_COMPONENT_SEQUENCE_ID — routing operation and the current versus prior component sequence, enabling the change to be tracked.
• COMPONENT_QUANTITY / COMPONENT_YIELD_FACTOR / PLANNING_FACTOR / COST_FACTOR — usage quantity and scalar factors applied to the component.
• DISABLE_DATE, LOW_QUANTITY, HIGH_QUANTITY, ACD_TYPE — effectivity and attribute-change context for the row.
• OPTIONAL, MUTUALLY_EXCLUSIVE_OPTIONS, QUANTITY_RELATED, SO_BASIS — model/option and sales order basis flags.
• WIP_SUPPLY_TYPE, SUPPLY_SUBINVENTORY, SUPPLY_LOCATOR_ID — supply defaults for the component.
• DESCRIPTION, PRIMARY_UOM_CODE, BOM_ITEM_TYPE, ATP_COMPONENTS_FLAG, REPLENISH_TO_ORDER_FLAG — item master attributes joined from MTL_SYSTEM_ITEMS.
• DEFAULT_SHIPPABLE, DEFAULT_COST_ROLLUP, DEFAULT_WIP_SUPPLY_TYPE, DEFAULT_SUPPLY_LOCATOR_ID, DEFAULT_CHECK_ATP — derived defaulting flags from MTL_SYSTEM_ITEMS used by the interface.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program association and audit columns.

While the base interface table does not expose a column literally named ITEM_TYPE_NAME, item classification is represented through BOM_ITEM_TYPE and MTL_SYSTEM_ITEMS attributes; queries requiring a type name commonly resolve it through the item type lookup or the system item's type attributes.

Common Use Cases and Queries

Typical usage includes pre-processing validation of staged mass change rows, reconciliation of interface records to the concurrent request that generated them, verification of inherited item defaults before the mass change is run, and diagnostic reporting on rows that fail validation.

SELECT item_num, component_item_id, component_quantity,
       operation_seq_num, bom_item_type, description
FROM   apps.bom_inv_comps_interface_v
WHERE  request_id = :p_request_id;

SELECT item_num, description, bom_item_type, primary_uom_code,
       default_wip_supply_type, default_cost_rollup
FROM   apps.bom_inv_comps_interface_v
WHERE  component_item_id = :p_item_id;

Because the view is a query-only interface layer, no DML should be issued against it; corrections must be made to the underlying interface table prior to launching the mass change program.