BMCOIN: Error BOM_OP_NOT_UNIQUE When Updating Routing Operation Sequence Number Using Open Interface Or API To An Existing Operation Sequence Number That Is Disabled (Doc ID 3005645.1)

Last updated on FEBRUARY 22, 2024

Applies to:

Symptoms

Error BOM_OP_NOT_UNIQUE when updating Routing Operation Sequences to an existing operation sequence on the routing that is disabled using the BMCOIN (interface) update process.

ERROR
The combination of Operation Seq Num and Effective Date you are trying to create or update in Operation 30 is duplicate in this routing. If this operation is Process or Line Operation, the Operation Seq Num must be unique in this routing. 
 
STEPS 
1. Clear the interface tables - BOM_OP_ROUTINGS_INTERFACE, BOM_OP_SEQUENCES_INTERFACE, MTL_INTERFACE_ERRORS

delete from BOM_OP_ROUTINGS_INTERFACE;
delete from BOM_OP_SEQUENCES_INTERFACE;
delete from mtl_interface_errors;

2. Insert record into BOM_OP_SEQUENCES_INTERFACE update op seq 21 -> 25

5. Review errors in mtl_interface_errors table

select * from mtl_interface_errors;

> Table_Name     > BOM_OP_SEQUENCES_INTERFACE
> Message_Name > BOM_OP_NOT_UNIQUE
> Error_Message  > The combination of Operation Seq Num and Effective Date you are trying to create or update in Operation 20 is duplicate in this routing. If this operation is Process or Line Operation, the Operation Seq Num must be unique in this routing.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.