While MFBF , expired batch determined for component when WM SLOC

[Former Member]

We have components which are Batch managed , and repetitive manufacturing scenario.

When we use MFBF transaction, while GI for components expired batches are determined in case of WM SLOC (control cycles are maintained for supply area).

The batch determination setup is in place -

a) Batch class - LOBM_VFDAT is maintained in batch class assigned to material.

b) Search class - LOBM_RLZ, LOBM_VFDAT_, LOBM_LFDAT in search class.

C) Sort rule - LOBM_LFDAT maintained in ascending

Condition records for 261 mvt maintained in MBC1 with LOBM_RLZ>1 d so as to exclude expired batch.

This setup works perfectly in case of IM SLOC to determine batches as per earliest SLED and exclude expired batches but when component is issued from WM SLOC it is not considered if batch is expired. We implemented SAP Note 769036 to determine earliest SLED for WM.

[JL23]

QA07 can be used to move the stock into blocked stock even when QM is not active

[JL23]

SAP Note 769036 did not do much, it added just the shelf life date into the sorting.

So I bet your sorting is correct, it is the selection that does not work. Why don't you move your batches into restricted status or blocked stock when their shelf life is expired?

[Former Member]

Thank you Jurgen for your answer. Moving batches to blocked stock is solution but will have manual intervention every time to transfer to blocked stock.

I wanted to know if there is any solution with which we can exclude expired batch which will be a full proof solution.as this works for IM SLOC but not when WM SLOC or control cycle.

Any suggestion on using User Exit or BADI ?

Also can we have any program to automate to transfer expired batch stock to blocked stock. QA07 will not work as QM is not active in our scenario.