Lineside replenishment SAP WM

[SaleemSk]

We use certain parts in almost every kit. To streamline the process, we're considering having these parts readily available at workstations, eliminating the need to add them individually to each kit. For example, parts would be stored in a bin within storage type 009 at workstation WS5, managed by WM.

Here are the key points to consider:

1. **Replenishment Trigger:**
- Explanation: We need a system to trigger restocking when the material in the bin drops below a certain level.
- Question: How should we set up the replenishment trigger to ensure timely restocking?

2. **Material Consumption:**
- Explanation: We want to keep the materials WM-managed while allowing for backflushing.
- Question: Can the materials remain WM-managed and still be backflushed, or do we need a different approach for consumption?

#sapwm #sapwarehousemanagement #replenishment

[DominikTylczyn]

Hello @SaleemSk 

I would suggest to use standard WM-PP Interface and set up the staging indicator to 4 "Manual Staging" in control cycles. The numbers of the storage bins at work centers are defined in the control cycles too. 

Then when a component is backflushed, it is taken directly from a bin defined in a control cycle. LE-WM won't create a transfer requirement for such a good issue and no further actions are needed in LE-WM.

As the staging indicator is 4 "Manual Staging", you can move components to the bins at work centers manually or you can use Replenishment for Fixed Storage Bins process.

Best regards

Dominik Tylczynski

[SaleemSk]

Hi @DominikTylczyn Thanks for your response, we want to utilze on WM stock not at IM level how to achieve this

[SaleemSk]

@DominikTylczyn if WM activity not requires ,we dont want to Goods issue IM level stock wrt Production order

[DominikTylczyn]

Hello @SaleemSk 

Honestly I don't understand your comments, I don't know what you need anymore. The solution I've suggested will post backflush both in WM and IM. Backflushing is automatic posting of components consumption - by definition it's an IM movement. If your storage location is WM managed, then the consumption will also be reflected in WM.

You can't reduce WM stock without simultaneously reducing IM stock, both are integrated. WM movements as such do not change overall stock levels; they only move stock between bins.

You need to be more precise, so I can help you better.

Best regards

Dominik Tylczynski

[SaleemSk]

Hi @DominikTylczynski

[SaleemSk]

Hi @DominikTylczynski we don’t want to keep stock at IM level , we allocate component stock from WM level( where our storage location WM managed is that possible ?

[DominikTylczyn]

Hello @SaleemSk 

If you want to keep stock in WM, you have to keep the same stock in IM as stock is simultaneously managed both in IM and WM.

WM-PP interface allows to staget components to production in WM only, by moving them between WM storage bins, without any IM postings.

Best regards

Dominik Tylczynski