High Level Reservations not Deleted after Transacting Automatically Created Move Order
(Doc ID 1679438.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Process Manufacturing Process Execution - Version 12.1.3 and later
Information in this document applies to any platform.
Process Execution parameters has both the Create High Level Reservations and
Create Move Orders parameters checked, so that when a batch is created a high
level reservation is created for each ingredient and a move order is created.
When the move order is then allocated and transacted, a detailed reservation
is created for the material that was moved, but the high level reservation
remains, so that twice the required quantity is reserved.
If the move order is instead created through Picking, then the high level
reservation is correctly removed when the move order is transacted.
Expect the high level reservation to go away, just like it does when the move
order is created by picking.
The issue can be reproduced at will with the following steps:
1. Set GME parameters to automatically create high level reservations and
move orders when creating batch
2. Create batch
3. Go to Transact Move Orders screen, manually allocate move order, and
4. Go back to batch and look at reservations. There are now two reservation
lines, the original high level reservation and the one created when the move
order was transacted.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!