Putaway WT and Queue

[former_member578259]

Hi folks,

I wanted to know how Inbound driven CD functions. I will appreciate if anyone who has actually worked on it will help me to understand. I know many of you will find it very common question but i want to knew in little more detail.

Q1. During Putaway WT confirmation it will create CD WT? If we create only ODO and no pick WT then in this case, will system create CD during Putaway WT confirmation? or System will always check for Pick WT of ODO and then only it will trigger CD during Putaway WT confirmation.

Q2. Queue determination and RF environment role for Inbound driven CD.

Type of Queue systems checks ? Inbound Queue or Outbound Queue ? or we have set new queue type for CD ? We have always process our putaway WT via RF then it will cancel Putaway WT and create CD WT ?

Q3. Do we also need to include GI-ZONE in Putaway storage type search sequence ? just the way we include GR-ZONE in removal strategy ?

Many many thanks.

regards,

[former_member578259]

hi peter,

thanks.

But in my case i am only able to do cross dock for non hu items.

where we can do settings to cross dock hu items to gi-zone.

regards,

ankit

[petrzak]

Hi Ankit,

ODO needs to be in the system upfront in any CD scenario. Assuming you have considered all relevant EWM config, it all starts with appropriate ATP check rule for outbound delivery creation.

I have worked on multiple CD scenarios through the time. I mostly did auto-GR with PPF action and auto-WT creation with PPF. During WT creation system is doing CD checks - depending on CD scenario. In standard opportunistic CD it checks whether OBD exists, if yes - sends the HU to staging area, if not - creates putaway task. In MEDI, you want to fail WT creation if ODO does not exist (that is what standard does). In FT you send the product for further picking.

Q2 - you can use standard configuration by defining - GR-ZONE as source activity area and - GI-ZONE's as destination activity area

Q3 - system is taking over the staging information from the ODO when the putaway task is created as the destination data

Petr

[JuergenPitz]

Hi,

"Q1. During Putaway WT confirmation it will create CD WT? If we create only ODO and no pick WT then in this case, will system create CD during Putaway WT confirmation? or System will always check for Pick WT of ODO and then only it will trigger CD during Putaway WT confirmation."

No. The system always checks during the WT creation if CD is relevant / possible and then creates the WT accordingly. No matter if the WT is created for the ODO or for the IDN - the WT for CD is always a putaway WT (at least in the standard setting, not sure if this could be influenced by the BAdI).

"Q2. Queue determination and RF environment role for Inbound driven CD."

Whatever you set up and what you use for the determination.

"Q3. Do we also need to include GI-ZONE in Putaway storage type search sequence ? just the way we include GR-ZONE in removal strategy ?"

No. As I wrote above, it is always pick driven. So all you do is include the GR-Zone in the stock removal storage type search sequence.

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!