From Simulator, Cannot do Update Batch After Batch is Changed on Batch Details, Including After it was Completed Then Reverted To WIP and Unreleased

(Doc ID 2330320.1)

Last updated on DECEMBER 11, 2017

Applies to:

Oracle Process Manufacturing Product Development - Version 12.2.6 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.6 version, Simulator Issues

Retrieve a batch on the Simulator, change an ingredient quantity and a technical parameter value.
Save the Simulation.
Do Update Batch.

Once you have done this, if you later make any change on the Batch Details form and then retrieve the Simulation on Simulator, make a change, and try to do Update Batch
the following error occurs.

ERROR
-----------------------
Record has been updated by another user in the table GME_BATCH_HEADER. Please start over.

It seems that the last update date is stored with the simulation, and if the date on the saved simulation is different from the one on the batch header, you get this error. This is to prevent users from inadvertently overwriting changes that had been made on the batch.

The customer's scenario involves Releasing and Completing the batch, then realizing an error was made and Reverting to WIP and Unreleasing, and then trying to make the change on the Simulator, but I have confirmed that even just updating a flexfield on the batch header causes the error to occur.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create Batch
2. Retrieve batch on Simulator, edit ingredient qty and technical parameter value
3. Save Simulation, and do Update Batch.
4. Retrieve batch on Batch Details and make any change that updates the last updated date on the batch header.
5. Retrieve the simulation by Simulation name on the Simulator
6. Make a change to an ingredient quantity and do Update Batch.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot update the batch and simulation with the same changes after the batch has been changed.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms