SAP EWM: Creation of putaway WHT with RF

[axelkimmel]

Hello everyone,

I'm having a little struggle with an inbound process in EWM and the following scenario:

Goods receipt and transfer to the identification point has to be automated with PPF which is not an issue for me. At the ID-Point it is possible that the HU will not be further processed for a couple of hours which is why the following WHT to the final destination bin shall not be created directly after the confirmation of the WHT to the ID-Point. (LOSC and inactive WHT is not an option since it could block the final storage bin for several hours) Preferably, the WHT for the final putaway should be created with RF when the Handling unit is scanned by the worker.

There is an option in the custimizing for Warehouse process types "Allow WT creation in RF Putaway" that says it is possible to create HU putaway WHT within RF in combination with POSC:

So I customised a storage process with 2 steps:

The first step represents the transfer to the ID-point and the second should create the final putaway WHT.

The warehouse process type for the putaway is connected to a putaway control indicator and a putaway strategy. Unfortunately, the process stops after the transfer from goods receipt to the ID-Point and when I try to scan the HU in RF with the function "Putaway by HU" I receive the following error:

As far as I understood the documentation for the Automatic WT creation with RF EWM should check whether there is an existing WT and if not it would create one according to my putaway strategy that's referenced to the wharehouse process type of the second step in my storage process.

Has anyone of you an advice that could help me solving this problem? I think the documentation in this case is quite precise when I understood it correctly.

Thanks in advance your help is highly appreciated!

Regards,

Axel

[former_member609991]

Hi Alex,

Does this scenario work for you. I gave try the function you are expecting..i could not able to do either. It seems after you drop the HU in ID point..the WH status is completed. If it gets completed..the HU will loose the referance of the inbound delivery. So when you scan via RFUI it can find the respective IBD. So it can't create WT. Also logically this is correct if the WH ativity is completed.That means putway is completed. As for as I know after dropping the pallet in ID point , if you want to create a WT after some time..it only works via MFS.

So for your senario..you either take POSC via decon or packing workcenter. Simple ID point will not work. This is my opinion. However can correct me if I am worng.

Thansk & Br

Mathi

[axelkimmel]

Hi Ajit Routray,

that was a good guess with the warehouse process type determination, thanks! CT_CREATE_HU_DELAY is empty except for the GUID of the HU.

When I type in the right WH process type "BPL5" manually the process works just fine and a WT is created. But I actually don't know where the WH process type is lost or what else I should customise regarding the determination:

POSC:

The determination for Inbound delivery delivery is working as well as for manually created HU WT in ADHU

Do you have any idea how I could determine the WH process type differently / additionally? Probably somewhere at initial HU creation?

Thank you a lot!

Regards, Axel

[Ajit_Routray]

Hi Axel Kimmel,

How are you creating HU ? Manually or automatic with PAckspec or..?

Can you please check storage process is getting update while HU creation ?

Kind Regards,

Ajit

[Ajit_Routray]

Hi Axel Kimmel,

I believe WH Process Type should read from inbound delivery.

Sorry, no guess this time why it is not getting filled in HU in your case.

Kind Regards,

Ajit

[JuergenPitz]

Hi,

but you have still these process settings for the POSC? I would think this messes it all up. The ID Point is not supposed to work as you describe what happens. The customizing for the storage type look ok, except that there is no reason to assign a process step and to something in "putaway storage control" (this field is also for POSC). I guess due to the POSC settings the ID point does not properly work. And the LOSC settings have no effect.

Brgds

Juergen

[axelkimmel]

Hi Juergen Pitz,

here's the ID-Point:

Putaway storage type:

and the LOSC customising:

This is a screenshot of /scwm/ordim_o where you can see the inactive WHT

Regards,

Axel

[JuergenPitz]

Hi,

"I tried the LOSC and ID-Point storage type but then I received inactive WHTs with status "B"."

Sorry, but this is not how it is supposed to work and how it know it to work.

Could you show screenshots of your storage type customizing and the LOSC customizing?

Brgds

Juergen

[axelkimmel]

Hi Ajit Routray,

here's the LOG for the HU movement from GR Zone to ID-Point (works well!):

This is the LOG for the final putaway via ADHU: (works well with ADHU!)

The bin is found according to the putaway strategy which is nice. But I expected to do that with RF / 03 Inbound Processes / 03 Putaway / 01 Putaway by HU as it is stated in the documentation. Unfortunately, I still get the Error "no WHT exists for HU XXXX"

What I'm wondering about is that in the from GR-Zone to ID-Point the right warehouse process type "BINI" is found whereas the WHPT in the final putaway is the one for unloading "BENT" and not for the final putaway "BPL5". Nevertheless, when I create the WHT manually with ADHU and the correct WHPT then I receive the following message in RF:

Actually not sure where this comes from ..

Anyways, thanks for your reply Ajit!

Regards, Axel

[Ajit_Routray]

Hi Axel Kimmel,

"The bin is found according to the putaway strategy which is nice. But I expected to do that with RF / 03 Inbound Processes / 03 Putaway / 01 Putaway by HU as it is stated in the documentation. Unfortunately, I still get the Error "no WHT exists for HU XXXX"

As per my understanding, Process should work in the system.It might be issues in WH process type determination. Please check the below points.

-> What is WH process type in inbound delivery and HU header ?

Please put break points on screen shot attached

"What I'm wondering about is that in the from GR-Zone to ID-Point the right warehouse process type "BINI" is found whereas the WHPT in the final putaway is the one for unloading "BENT" and not for the final putaway "BPL5". Nevertheless, when I create the WHT manually with ADHU and the correct WHPT then I receive the following message in RF:"

I assume its Queue determination or resource issue. Please check.

Kind Regards,

Ajit

[JuergenPitz]

Hi,

question: obviously you are not using MFS, right? So have you tried an ID-Point scenario at all? With a storage type with the storage type role "ID-Point"? Because then you will not have a WT from the ID point to the final bin, until you create it. So for the scenario you describe and ID point and LOSC is exactly the solution.

Brgds

Juergen

---
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!

[axelkimmel]

Hi Jürgen,

thanks for your answer. I tried the LOSC and ID-Point storage type but then I received inactive WHTs with status "B". Those are already blocking the final storage bin when I'm confirming the WHT to the ID-Point. I really thought I could create putaway WHTs by scanning the HU with RF "Putaway by HU" so the trigger could be set by the user and not the system with the confirmation of the previous WHT.

Have you ever heard of a similar scenario?

Best regards,

Axel

[Ajit_Routray]

Hi Axel Kimmel,

Could you please try to create Putaway WT via Tcode: /SCWM/ADHU ? (Enter HU then hit create button)

-> And also activate log

Objective:

-> To check Putaway Strategy with POSC

Kind Regards,

Ajit

[axelkimmel]

You'll find my comment below