A part with two transactions appears as shown below:

If we go by time created, the timeline is correct, but if we go by transaction ID, it is not.

And the display by transaction id will cause the balance in quantity on hand development to be -1 instead of zero.

The on-hand development screen orders the display in descending order of transaction ID so in reality, INTSHIP for the above part should have had a transaction ID higher than the OOREC.

Transaction ID column is generated by an ORACLE sequence.

We tried to recreate a similar scenario in the in a recently refreshed development instance and observed that for an INTSHIP to happen, material line reservation had to be done prior and that material line was not available for reservation unless the OOREC received that part into inventory.

So, in this situation, the OOREC got saved later in the database with a higher transaction ID (sequence) and an earlier time, but the INTSHIP got saved first with a lower transaction ID (sequence) and later time.

Note: Database environment is on a 2-node Linux RAC Cluster

Has anyone come across this? Resolution ideas will be greatly appreciated.

Thank you in advance