bin determination according to FEFO rule

[former_member597616]

Hello experts,

Need your advice on below

In our EWM system we use FEFO rule for stock removal. The search sequence is assigned with multiple storage type . The scenario is , the oldest batch in stored two different storage types , however when system creates the warehouse task it creates the first WT and picks the partial quantity from oldest batch from the first storage type and than system does not look the same batch to different storage type rather it picks the second oldest batch within the first storage type.

This means that the FEFO principle is applied by storage type only, not globally.

Thanks

Sandeep

[JuergenPitz]

"I have two storage bins in the same storage type, each containing handling units (HUs) with different expiration dates: BIN1: 01/10, 01/11, 01/12 BIN2: 01/09, 01/13, 01/14 I need to pick a quantity of 20 with the earliest expiration dates."

Well, besides that it general you should avoid such a putaway strategy when you want to pick by any proper strategy: there are several things which influences what happens here: what are your settings?

- storage behaviour, putaway rule, 
- Level of available quantity
- Mixed storage settings

- What do you see when checking physical stock / available stock?

- Does the system propose which HUs to pick?
Brgds

Juergen

[Tomas_Norkus]

Storage Behavior: General Storage or Bulk Storage Putaway Rule: Addition to existing stock or empty bin Level of Available Quantity: Addition to stock at the bin level Mixed Storage Settings: Mixed Storage: Allows multiple handling units (HUs) with different batches of the same product Mixed Storage in HUs: Not allowed Mixed GR Dates: Not allowed Mixed SLEDs (Shelf Life Expiration Dates): Not allowed

[Tomas_Norkus]

As well I see we have sap note for similar issue: 2962880 - System allows same product/batch with different SLED in the same storage bin

[JuergenPitz]

I think that "Level of Available Quantity: Addition to stock at the bin level" is already enough to mess it up. The system is not proposing which HU to pick, yes? So how should the system distribute the pick?

[Tomas_Norkus]

No, I don't need the system to propose an HU. That's why I set bin quantities. Currently, the system proposes bins based on FEFO, but it doesn't account for whether the stock in the bin is sufficient for picking base on FEFO. So I assume that system should look of all storage type bins and propose to pick earles stock from bins. But look like it not happening.

[JuergenPitz]

"That's why I set bin quantities." - Remember I ask to check what you see for physical stock and available stock? When you check available stock, how many different GR or Expiration Dates do you see there? I guess only one? So how is that supposed to work?

[Tomas_Norkus]

Yes, for available stock, it is managed using a single date. However, for physical stock, it is tracked at the HU (Handling Unit) level. I assume this is non standard and we will need to activate Badi or even more