EWM LOSC - how to choose any source HU

[StanislavDvorak1]

Hi, is there any way how to use LOSC and let decide user to choose any source HU?

LOSC works fine but LOSC reserves specific HU from source bin - it's not good as on the pallet are lot of HUs and user is forced to move pallet down, search for specific HU and move pallet back - it tooks ages. I would like him go to source bin and scan any HU. I tried to change settings of source st.type / wpt and I achieve this (user was able to scan any HU from source) but of course it was not HU task so LOSC was deactivated. Any way how to pick any source HU with LOSC? 

Thank you 

Standa

[Muhammad_Ashraf]

SAP Standard System will always create WT with some Stock, you can do RF enhancement, using Wrapper FM, where you can put one button, and upon click as user to scan any HU, it will link the current HU to the DLV and old link for Stock ID will go off. this is the only possible solution i can think of.

[Daniil · Accepted solution]

Hi Stanislav,

LOSC works as well for product task with hu movement. But HU must be known. In your case LOSC should work as well if you use RFUI to confirm the task. When HU is picked to resource HU-Wt created from resource to the destination bin, and at this point of time LOSC is triggered, and resource gets open LOSC tasks to move hu to the intermediate bin.

BR,

Daniil

[StanislavDvorak1 · Accepted solution]

Do you mean HU must be known and first LOSC WT must be created with HU number inside? At this case its really timeconsuming as user will need to search whole pallet for specific HU (we have HU management on Box level)

[Daniil · Accepted solution]

no, you can keep the availability level on the bin, first you should get open product WT for picking ( without LOSC ). When picking is done with rfui the picking task is confirmed to the rsrc and followup task is created from rsrc to the dest. bin, here you have already a HU (pickHU or srcHU which you fully picked) ( and it is a HU task ) so LOSC works.

[StanislavDvorak1 · Accepted solution]

Daniil and Juergen, thank you ! I really didnt thought the one WT may change after confirmation and new will be created. But it did !

[JuergenPitz]

"Anyway, I dont want to system select source HU, I would like to let user to decide and select HU during first pick. Its possible if I change configuration to create product HU - but at this case the LOSC doesnt work and system creates only one WT - from 2020 to 2030 (but the user can scan any source HU). I believe the reason is, the system creates Product WH task and LOSC is not activated as LOSC requiring to have HU WH task....."

Then you do what Daniil describes. You process the WT with RF, then LOSC is working, also if there is no HU WT at the beginning.

Brgds

Juergen

[JuergenPitz]

Hi,

I would not think that this is not caused by using LOSC, but due to your storage type putaway and picking strategies. Does it work differently when you are not using LOSC?

Brgds

Juergen

---
All the above is no official SAP statement.

Want to learn EWM?
Check for EWM courses: https://training.sap.com/trainingpath/Applications-Extended+Warehouse+Management-EWM+in+S4HANA
Get a SAP Learning Hub Subscription: https://training.sap.com/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!

[StanislavDvorak1]

Hi Juergen,thank you for the answer. My process is following: 1) from receiving putaway into destination st. type 20202) Replenishment with LOSC from st. type 2020 - inter st. type REPV - destination st. type 2030  - it works fine in case I configured HU WH task to be created (two WT created for HU, first from 2020 to REPV, second B from REPV to 2030). System choose source HU and present it to user for picking, user pick by queue and scan source HU selected by system. Anyway, I dont want to system select source HU, I would like to let user to decide and select HU during first pick. Its possible if I change configuration to create product HU - but at this case the LOSC doesnt work and system creates only one WT - from 2020 to 2030 (but the user can scan any source HU). I believe the reason is, the system creates Product WH task and LOSC is not activated as LOSC requiring to have HU WH task.....

[StanislavDvorak1]

Sorry for formating, it didnt let me to change it. also I did typo, i wrote "Its possible if I change configuration to create product HU" but i meant "Its possible if I change configuration to create product WT"