Does exist availability check in EWM? Any way to prevent the usage of batch already assigned?

[Former Member]

Hello team,

I do have a big question for you where the answers I have found do not make happy at all.

Facts::

a) We run ATP/Reservation at ERP level (When the Outbound Delivery is created)

b) We run batch determination only for export processes at ERP level.

Scenario:

STEP 1: We create a SO and an Outbound Delivery in the ERP with the TOTAL quantity of a batch. Let's call it BATCH1.

STEP 2: We create a second SO and an Outbound Delivery in the ERP without a batch

Now both ODOs are in EWM and if we check the requeriement we can see one ODO with batch and one without it.

STEP 3: The second ODO is processed first and it selects the batch BATCH1 even it was assigned to the other ODO.

Expectation:

At least one way to prevent the usage/picking of the batch reserved before the tasks are created.

Thank you very much in advance!

[Ajit_Routray · Accepted solution]

Hi Irene,

"We create a SO and an Outbound Delivery in the ERP with the TOTAL quantity of a batch. Let's call it BATCH1."

I guess you need an additional step (manually or automatic) in ECC or EWM for reserve stock at inventory as well as warehouse level.

-> Move Batch stock from unrestricted to SO stock after creation of SO or OD in MIGO (I guess Movement type 412/413 E) .

-> This will create a posting change document in EWM (Stock under SO reserved) or directly post change in EWM.

Whenever you will create task for this SO , it will first refer the reserved stock against SO.

Please let us know if you have any doubts on this.

Kind Regards,

Ajit