Search Results bom_operation_instructions

Overview

BOM.BOM_OP_SEQUENCES_INTERFACE is the open interface table used by Oracle Bills of Material to load routing operation definitions into Oracle E-Business Suite. It temporarily stores information about routing operations, including their resources and operation instructions, before Oracle Bills of Material validates the rows and transfers them into the permanent routing tables. The table contains user-friendly descriptive columns as well as the corresponding foreign key columns, allowing data to be entered in whichever form is most convenient. For example, ORGANIZATION_CODE may be supplied and the application derives the corresponding ORGANIZATION_ID; similarly, ASSEMBLY_ITEM_ID, ORGANIZATION_ID, and ALTERNATE_ROUTING_DESIGNATOR may be provided in place of ROUTING_SEQUENCE_ID, and the interface processor resolves the routing sequence identifier. In addition, each operation sequence row can carry up to three resources and three instructions, which Oracle Bills of Material inserts into BOM_OPERATION_RESOURCES and BOM_OPERATION_INSTRUCTIONS respectively.

The table resides in the APPS_TS_INTERFACE tablespace with PCTFREE 10 and is owned by the BOM schema. The documented physical schema for 12.2.2 lists 98 columns, with TRANSACTION_ID enforced by the unique index BOM_OP_SEQUENCES_INTERFACE_U1. From a Data Vault modeling perspective, the metadata classifies this object as standalone; it may therefore be treated as a staging or load structure rather than a modeled hub, link, or satellite.

Key Information Stored

The most significant columns fall into identification, scheduling, resource, and instruction groups:

• TRANSACTION_ID — unique business-key candidate enforced by index BOM_OP_SEQUENCES_INTERFACE_U1; identifies each interface row.
• OPERATION_SEQUENCE_ID, ROUTING_SEQUENCE_ID, OPERATION_SEQ_NUM — operation identification and ordering within the routing.
• ASSEMBLY_ITEM_ID, ASSEMBLY_ITEM_NUMBER, ORGANIZATION_ID, ORGANIZATION_CODE, ALTERNATE_ROUTING_DESIGNATOR — the routing context; the numeric and descriptive forms are alternatives resolved during validation.
• STANDARD_OPERATION_ID and DEPARTMENT_ID — foreign keys to WSM_OPERATION_DETAILS and BOM_DEPARTMENTS; DEPARTMENT_CODE provides the descriptive equivalent.
• EFFECTIVITY_DATE, IMPLEMENTATION_DATE, DISABLE_DATE — effectivity window for the operation.
• OPERATION_DESCRIPTION, LONG_DESCRIPTION, OPERATION_CODE — descriptive attributes of the operation.
• RESOURCE_ID1–RESOURCE_ID3 and RESOURCE_CODE1–RESOURCE_CODE3 — up to three resources per operation sequence.
• INSTRUCTION_CODE1–INSTRUCTION_CODE3 — up to three operation instructions, later written to BOM_OPERATION_INSTRUCTIONS.
• PROCESS_FLAG, TRANSACTION_TYPE, PROCESS_STATUS-type control columns — govern the interface processor's treatment of each row.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program audit columns.
• ATTRIBUTE1–ATTRIBUTE15 and ATTRIBUTE_CATEGORY — the standard DFF/descriptive flexfield columns.
• YIELD, CUMULATIVE_YIELD, RUN_TIME_OVERLAP_PERCENT, MINIMUM_TRANSFER_QUANTITY, COUNT_POINT_TYPE, BACKFLUSH_FLAG — planning and shop-floor control attributes.

Common Use Cases and Queries

The primary use case is bulk loading legacy routings into Oracle Bills of Material, typically via SQL*Loader or an external application, followed by the standard BOM open interface concurrent program. Common verification queries include counting unprocessed rows and reconciling descriptive values against their derived identifiers:

• Checking pending rows: SELECT TRANSACTION_ID, PROCESS_FLAG, TRANSACTION_TYPE, ASSEMBLY_ITEM_NUMBER, ORGANIZATION_CODE, OPERATION_SEQ_NUM FROM BOM_OP_SEQUENCES_INTERFACE WHERE PROCESS_FLAG IS NULL OR PROCESS_FLAG <> 'Y';
• Resolving routing context: SELECT ASSEMBLY_ITEM_NUMBER, ORGANIZATION_ID, ALTERNATE_ROUTING_DESIGNATOR, COUNT(*) FROM BOM_OP_SEQUENCES_INTERFACE GROUP BY ASSEMBLY_ITEM_NUMBER, ORGANIZATION_ID, ALTERNATE_ROUTING_DESIGNATOR;
• Auditing load provenance: SELECT REQUEST_ID, PROGRAM_ID, COUNT(*) FROM BOM_OP_SEQUENCES_INTERFACE GROUP BY REQUEST_ID, PROGRAM_ID;
• Inspecting resource and instruction payloads: SELECT OPERATION_SEQUENCE_ID, RESOURCE_CODE1, RESOURCE_CODE2, RESOURCE_CODE3, INSTRUCTION_CODE1, INSTRUCTION_CODE2, INSTRUCTION_CODE3 FROM BOM_OP_SEQUENCES_INTERFACE;
• Confirming persisted results by joining BOM_OPERATION_INSTRUCTIONS and BOM_OPERATION_RESOURCES on OPERATION_SEQUENCE_ID after processing.

Reporting users frequently extract YIELD, CUMULATIVE_YIELD, and count-point attributes for routing performance and capacity analyses, using the interface only while a load is in flight.

Related Objects

The following objects are most significant to interface processing:

• WSM_OPERATION_DETAILS — referenced via STANDARD_OPERATION_ID.
• BOM_DEPARTMENTS — referenced via DEPARTMENT_ID.
• BOM_OPERATION_INSTRUCTIONS — receives instruction rows derived from INSTRUCTION_CODE1–3.
• BOM_OPERATION_RESOURCES — receives resource rows derived from RESOURCE_ID/RESOURCE_CODE1–3.
• BOM_OPERATION_SEQUENCES — the destination table for validated operation sequences.
• BOM_ROUTINGS_INTERFACE / BOM_ROUTING_SEQUENCES_INTERFACE — companion interface tables for routing headers and sequences, linked through ROUTING_SEQUENCE_ID and ALTERNATE_ROUTING_DESIGNATOR.
• BOM_ENG_CHANGES_INTERFACE and BOM_REVISED_ITEMS_INTERFACE — linked via ENG_CHANGES_IFCE_KEY, ENG_REVISED_ITEMS_IFCE_KEY, and BOM_REV_OP_IFCE_KEY for engineering change integration.
• MTL_SYSTEM_ITEMS_B — source of ASSEMBLY_ITEM_ID and item validation.