on 2022 Sep 27 3:12 PM
Hi,
I have a search sequence for some materials that replenish the picking area storage type. For example:
100 (Picking area ST - Fixed bins, one material per bin) <-- 101 (fixed bins, mixed storage) <-- 102 (bulk storage)
Nowadays, whenever the stock in ST 100 goes below the min stock value for a certain material, the system generates a replenishment order. If there is stock in ST 101, then it is extracted from it. If not, the TO will be generated from ST 102, supposing there is stock there.
We have 2 main problems with this strategy:
1) When there is no stock in ST 101, we have to look for the material in ST 102 that is a "bulk" storage type with a single bin with no capacity limit on quant or number of materials. So this is a time consuming task compared to searching on ST 101, where the materials are on fixed bins.
2) It is hard to respect FIFO. Upon good receipts, the putaway search sequence is 101-->102. So, if there is available capacity, the system will putaway in ST 101. If not, it will do it in ST 102 bulk. It can happen that there is available capacity in ST 101 and also material in ST102. In this case, the system will putaway in ST 101 and when a replenishment is triggered the material stored there will be transported to ST 100 (picking area) before the batch that is in ST 102 (due to the replenishment search sequence) violating FIFO.
So, my question is: Is it possible to configure a "cascade" replenishment? I would like the system to replenish automatically not only the ST 100 but also the ST 101 when it goes below a certain stock or there is available capacity to store the material that is in ST 102.
Nowadays, we have a person that does this manually, consulting the stock in ST102 and checking if there is capacity available in ST 101. This helps but is not the best solution.
I would appreciate any assistance.
Thanks.
Request clarification before answering.
Hi,
"1) When there is no stock in ST 101, we have to look for the material in ST 102 that is a "bulk" storage type with a single bin with no capacity limit on quant or number of materials. So this is a time consuming task compared to searching on ST 101, where the materials are on fixed bins."
Well, that is the case when you use a bulk storage type. So the problem is caused by yourself.
"2) It is hard to respect FIFO. Upon good receipts, the putaway search sequence is 101-->102. So, if there is available capacity, the system will putaway in ST 101. If not, it will do it in ST 102 bulk. It can happen that there is available capacity in ST 101 and also material in ST102. In this case, the system will putaway in ST 101 and when a replenishment is triggered the material stored there will be transported to ST 100 (picking area) before the batch that is in ST 102 (due to the replenishment search sequence) violating FIFO."
For this you use stringent fifo. Described either here (if this is an EWM question): https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/9832125c23154a179bfa1784cdc9577a/a0c8cb53ad377114e10...
or here (for WM, which I think your question really is about): https://help.sap.com/docs/SAP_ERP/34fc810a607e4ae5a287b6e233b8566f/e490c95360267214e10000000a174cb4....
Whereas for WM you have to add a little more, you need to use a warehouse movement type reference code.
In EWM definitely, I believe in WM as well. You define your replenishment strategies per storage type. You only need to define all the required master data (min and max quantities).
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
4 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.