Parent Batch And Phantom Batch Actual Quantities Are Out of Synch Due to the Batch Material Exceptions Form Not Handling Errors Correctly (Doc ID 3048764.1)

Last updated on OCTOBER 03, 2024

Applies to:

Symptoms

When a batch is Released and the Material Exceptions form comes up, the form is not correctly handling a situation in which a user clicks Proceed, gets an error, tries to fix it, and then clicks Proceed again. The system is creating duplicate transactions, as well as stuck transactions. In addition, when this occurs in a parent/phantom batch pair, the quantity of the phantom item in the parent batch gets out of sync with the quantity of the phantom item in the child batch. Rows in the gme_transaction_pairs table are also created incorrectly.

Background:
Customer has dual UOM items. These are used in batches in the secondary UOM.
Because of rounding issues, customer occasionally gets onhand quantity for a lot in which the primary onhand qty is .00001 but the secondary onhand quantity is 0.
Users then create a new parent/phantom pair of batches, in which the item above is an ingredient in the phantom batch.
Autodetail reserves the lot that has 0 secondary onhand and .00001 primary onhand, as well as reserving remaining qty from another lot.
When Releasing the batches and the Material Exceptions screen comes up, showing the reservations that will be turned into transactions, they click Proceed and get an error that transaction qty cannot be zero, because the system is trying to create a transaction from the reservation with 0 qty.
They click OK on the message, delete the row with the zero qty, and click Proceed again.
The behavior is not completely consistent, but the system creates duplicate transactions (one for each Proceed, apparently), sometimes stuck transactions, and sometimes the actual qty of the phantom item in one of the batches gets set to the planned qty but the actual of that item gets set to twice the planned qty in the other batch.

Once the phantom qty is out of sync between the parent and child batch, further processing gives errors.



The issue can be reproduced at will with the following steps:
1. Responsibility: Production Supervisor
2. Navigation: Batch Details and perform steps below.
3. Create parent/phantom batch pair.
4. Run Autodetail on the phantom batch.
5. Release from the parent batch.
6. On Material Exceptions, click Proceed, and acknowledge the error that you cannot transact zero qty.
7. Delete the row with zero qty.
8. Click Proceed again.

Changes

Cause

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