Skip to Content
avatar image
Former Member

how to exclude expiring batches from the MRP run

Does anyone know how to run MRP to make sure that batches are not to be considered for planning after their expiration date?

any help is greatly appreciated

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • Best Answer
    avatar image
    Former Member
    May 16, 2012 at 09:31 PM

    Hi Uwe

    to the best of my knowledge  standard SAP does not take into the batch expiry date during the mrp run. If the quantity is there, then it's taken into account irrespective of expiry date - but I am happy to be proven wrong.

    Have you thought of coding a mrp user-exit ?

    Best regards.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      thanks Pascal... that's what I feared is the case. It is a little unfortunate because I have quite a few clients who have this problem :-(

  • May 22, 2012 at 08:50 AM

    A potential workaround:

    1. Select by reporting the batches, which are close or at the expiration date.
    2. Post them manually into blocked stock.
    3. Next MRP run would create new planned orders

    If you have many batches, probably you need to develop for step 2 a z-transaction, to do a mass posting into blocked stock.

    Add comment
    10|10000 characters needed characters exceeded

  • May 21, 2012 at 07:21 AM

    Hello,

    you have discussed about MRP run in ERP.

    Looking into APO our friends from Chemical / Food industries using following functionality:

    Planning with Shelf Life Data in PP/DS

    http://help.sap.com/saphelp_scm70/helpdata/en/4c/4e5ac8eb096ad8e10000000a42189c/frameset.htm

    Greetings,

    Stefan Haag

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 14, 2014 at 04:59 AM

    This message was moderated.

    Add comment
    10|10000 characters needed characters exceeded

  • May 28, 2015 at 09:18 AM

    Hello,

    There are two known solutions for this issue.Either buy and connect a software that takes expiry dates into account (like SAP APO), or develop a solution to upgrade MRP runs. For example, create a program that:

    _ runs MRP in order to generate stock reservations.

    _ compares (incrementally) expiry dates of the available batches with the reservation dates.

    _ in case of expiry date < reservation date, the system creates a new reservation for the predictably expiring batch. the reservation aims to block this batch, it should be linked with a new movement code that do not really 'move' this batch, until his expiry and destruction.

    _ run again MRP. It will only consider 'safe' batches.

    Add comment
    10|10000 characters needed characters exceeded