SAP EWM Inbound drive Opportunistics cross docking not cancelling existing open Pick task

[vivek_venkatachalam]

SAP EWM Inbound drive Opportunistics cross docking not cancelling existing open Pick task , but works when there are no open Pick task for ODO. can someone advice here? this is for SAP EWM 9.4.

[JuergenPitz · Accepted solution]

Hi,

I can not read the ABAP coding of the implementation (not my forte), but a consulting colleague who was in my class once checked and and described that the BAdI checks if the stock removal rule of the existing WT uses the GR date or the Best-before date for the quant determination. If yes - then the WT is not cancelled. You can try this by doing the following: create the situation as before (open Pick WT (RF relevant!)), then have a new inbound delivery with GR posted. In customizing remove the stock removal rule which was used for the pick WT (check how it is determined) (the system does now write the SRR in the WT, but rather it is checked during the check if the WT can be cancelled what SRR is used) - and then the WT should be cancelled. At least that happens in our class where I show this.

"So to overcome this, we need to enchance the BADi is the only option?"

To enhance the sample implementation of the BAdI is the only option anyway. Have you checked what the sample implementation does? FIFO is not checked. So is that useful?

This is a SAMPLE implementation. Means you see how CD can work. But I would not expect a customer to be happy with this sample implementation.

Brgds

Juergen

[vivek_venkatachalam]

Hi Juergen, It means when Stock removal rule is added , the CD BADi always check the GR date by default? So to overcome this, we need to enchance the BADi is the only option?

[JuergenPitz]

Hi,

according the documentation (https://help.sap.com/viewer/3d97bec9bf1649099384bb8167df3cf2/9.5.0.2/en-US/d349397317d64478aea5e1717d1dee95.html):

"If EWM is able to determine delivery items of this kind, it checks whether it has already generated pick warehouse tasks for these delivery items, which are assigned to the radio frequency environment."

So the first thing you need to check, is if the existing WTs are in a RF queue.

Further on it says: "If open pick warehouse tasks of this kind exist, EWM cancels these without violating the FIFO principle."

What I learned is that this is rather optimistically written. The system checks if the stock removal rule for the existing WTs uses the GR date. And if yes, then it does NOT cancel them. And this is what the default BAdI implementation does. If you want the system to behave differently you have to build your own implementation (which you should anyway, as the example implementation is what it is - an example).

Brgds

Juergen

---
Want to influence SAP software development decisions for EWM?
https://influence.sap.com/ewm2019

Want to learn EWM?
Check for EWM courses @ https://training.sap.com/trainingpath/Applications-Logistics+Execution+%26+Warehouse+Management-SAP+...
Get a SAP Learning Hub Subscription: https://training.sap.com/shop/learninghub

And it is EWM. NOT eWM - Duh!
And if your question includes the word "transfer order" - do NOT tag the question with Extended Warehouse Management!

[vivek_venkatachalam]

Thanks Juergen. I have tried both the RF queue assignment and without queue assignment but not cancelling open pick WT's while creating the putaway task.

Currently the stock removal strategy setup as FEFO and it was not considering any existing batches and not cancelling the Pick WT's open.

Since you mentioned that WTs considers the GR date, how we know this and how to stop by overwriting with own logic on BADI?

[vivek_venkatachalam]

Hello Jeurgen, For the Embedded EWM 1809 , the CD works well with Monitor transaction where it is able to create the Pick WT after GR and Putaway but the same not working with RF transaction of GR and Putaway. What is the reason behind this?