Skip to main content

Hi All,

One of the customers has an issue with the Pick_Customer_Order_API. Pick_Reservations__ procedure
as it does not seem to roll back in full if it encounters errors during the execution.

They encounter the error like below time to time
ORA-20113: CustomerOrder.LOCKED2

And sometimes, this may cause the issue of not fully picking the customer order.
The customer does not care about the locking issue but they want to know why the IFS procedure (Pick_Customer_Order_API. Pick_Reservations__) does not roll back fully when any issues come as above.  They experienced this while using with third-party integration tool.

Is there a way to handle the locked record issue in integration with full rollbacking functionality as the customer expected?

Best Regards
-Kelum

Hi @Kelum Niranjana , 

Transaction rollback is handled automatically in DB(if specified) if interruption occurred but it’s not guaranteed for complex flows with multiple transactions. i.e: perhaps  “Pick_Customer_Order_API.Pick_Reservations__”  have multiple transactions so unless it’s handled in business logic(core).

It seems to be “ CustomerOrder.LOCKED2” was the trigger for rollback so, identifying and avoiding the above lock would be a solution. If “CustomerOrder.LOCKED2” is a lock for an update, it can be also handled in integration logic to avoid the lock.

I hope this is helpful. 

Terms & ConditionsCookie settings