cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Replenishment LOSC process

0 Likes
3,375

EWM Experts,

Trying to set up LOSC for replenishment for storage type 0070. Objective is to replenish from our case picking location (st. type 0010) and transfer to an intermediate storage location (st. type 0072) before fixed bin location (st. type 0070). Final location is not HU managed.

Searched other articles but did not find one specifically for replenishment and LOSC. Able to create LOSC for outbound and internal transfer from existing SAP articles. These were full HU withdrawal however.

Any help would be appreciated. Thanks!

Storage type 0072 - intermediate

Storage type 0070 - final location

LOSC setup

Accepted Solutions (0)

Answers (4)

Answers (4)

spy1010
Explorer
0 Likes

Hi Adrian,

Were you able to find the solution, I am stuck at the same point.

Best Regards,

jlivio90
Active Participant
0 Likes

Hi Adrian.

What Juergen said is probably what is going to happen in your system, after confirm the first WT the second one will be created.

That happens because if you are not moving the complete HU from the source to destination, the system doesn not create the second WT, because the system does not know yet the HU number that will be moved to the destination bin.

Good luck.

Janderson

Private_Member_324719
Participant
0 Likes

Hello Adrian,

LOSC only works with HU WTs.

What you can do (and this is already done) is to set Y in the HU requirement in the last st.type.

So i would expect that the scenario to be succesful. User working in the RF can still confirm the task from the intermediate st.type to the final st.type based on an HU, but once this task is confirmed, the HU will remain empty in the resource and the stock will be in the destination st.type, without HU.

Based on the packaging material configuration, you can set the 'delete empty HUs' flag, so that empty HUs are deleted once you confirm the last replenishment task.

João

0 Likes

Thanks João.

We have this in our system in regards to the HU settings so I believe it will work once we get the LOSC up and running.

JuergenPitz
Product and Topic Expert
Product and Topic Expert
0 Likes

Hi,

and, what is the problem?

Brgds

Juergen

---

Want to learn EWM?
Check for EWM courses: https://training.sap.com/search?q=ewm
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!

0 Likes

The replenishment task creation is generating WT from source to final destination. Should be expected 2 WT with one inactive until the transfer to the intermediate location is completed. Will check with my developers to further investigate.

JuergenPitz
Product and Topic Expert
Product and Topic Expert

Hi,

"The replenishment task creation is generating WT from source to final destination. Should be expected 2 WT with one inactive until the transfer to the intermediate location is completed."

OK, but have you tried to PROCESS the WT (with RF!)? Because in such an instance the system behaves dynamically. It changes when you process the WT and it becomes a HU WT. That is what is required: you either have to pick a full HU or create a pick HU.

Brgds

Juergen

0 Likes

Hi Juergen,

The process is working as you described. Should have tried it on RF first.

However, one additional requirement is needed and hoping you can point me in the right direction. When generating replenishment for multiple fixed bins, one WO is created and a separate HU is created for each product (as expected since different destination). How can I set up the system to create a higher level HU for this WO which upon confirmation at intermediate location will move all the lower level HU (used for LOSC) into the location?

Any help and insight on this would be appreciated