Problems with Both Move Order Creation and Autodetail Upon Batch Creation, End Up With Double Reservations (Doc ID 2027153.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.

Symptoms

On : 12.1.3 version, Batches

ACTUAL BEHAVIOR
---------------
There is a problem when both Move Order creation and AutoDetail are set to be done upon batch creation.

The move order does not inherit the details from the autodetail. So after allocating the move order (if there is sufficient inventory to do that in addition to the reserved inventory from autodetail) and then transacting it, you end up with double reservations on the batch.
If the available inventory is less than double the requirements, then the move order cannot be autoallocated.


EXPECTED BEHAVIOR
-----------------------
Suppose for a finished good you need a component.
You have a stock of 8 in your production area (supply subinventory) and an additional stock in warehouse.
You create a first batch requiring 10 and you asks system to automatically create a move order.
System creates a move order of 2 from your warehouse to your supply subinventory, that's correct.
If (before transacting previous move order) you create a second batch it will do exactly the same.
So you have two batches expecting to consume the 8 pieces, while you give order to move additional 4.
That's not correct, you can consume the 8 pieces only once, so you need to move 12.
This issue is solved if you autodetail material, so that it's reserved against the batch.
But then you have an issue when transacting the move order as it doubles the reservation.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Set Process Execution Parameters to Autodetail upon batch creation and create move orders upon batch creation
2. Create batch

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, you either end up with twice the necessary inventory reserved, or you end up with a move order that cannot be allocated and transacted.

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