Skip to Content
avatar image
Former Member

Planned Order not deleted after MRP run

Hi Experts,

Our client is maintaining MRP Type: VM (Autromatic reorder point plng). We maintain a re-order point and maximum stock level in the material master. Based on my knowledge of MRP runs, when a material stock reaches below the re-order point, MRP should created a planned order (we use planned orders instead of direct PR creation) with a proposed amount to satisfy the maximum stock level. MRP also takes into account already created PRs or POs and it will not create planned orders if there are enough stock levels. Upon MRP Run - MD01, our material which already had a PO incoming, did not delete an existing planned order it had.

My material has a re-order point of 3, with replenish to maximum stock level of 6. Current stock was 1, so doing the math, MRP created a planned order for 5. Meanwhile, a PO was created for this same item with a qty of 15 (exceeding the maximum stock). Why didn't the planned order disappear upon MRP run? If it helps, at my Stock/Requirements List (MD04), my planned order has an exception message of 07 and my PO has an exception message of 20.

I would like to discuss this matter more in detail if need be, thank you!

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

9 Answers

  • Best Answer
    May 24, 2013 at 07:15 AM

    Hello Paolo

    Exception 20 for a firmed element usually means that this is outside the rescheduling horizon or it is not included on the rescheduling check at all.

    I wrote a WIKI about the rescheduling check, already refered by Senthil on this thread.

    The following note may also be useful:

    1745312MRP creates redundant proposals though there are fixed future receipts which ca

    BR

    Caetano

    Add comment
    10|10000 characters needed characters exceeded

  • May 23, 2013 at 03:12 PM

    HI

    Use planning Mode 3, while running MRP in MD01 as shown below, which will delete existing planned orders and will recreate planned orders if existing order proposals will not satisfy the max stock level

    Regards

    Satish


    mrp_screen.jpg (41.8 kB)
    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 24, 2013 at 06:23 AM

    What is your delivery date in production order. Is it within the tolerance level of Rescheduling horizon. Actually as per exception message 20, the date of GR for the material is outside of tolrance level and system is asking you to delete the production order as it is not required.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 23, 2013 at 03:17 PM

    Hi Paolo,

    Please check the Rescheduling Horizon set in OMDW; and if needed, adjust/increase the no. of days

    Pls refer to the following links as well -

    https://help.sap.com/saphelp_45b/helpdata/en/b4/7055967935d1118b3f0060b03ca329/content.htm

    http://wiki.sdn.sap.com/wiki/display/ERPMan/What+is+rescheduling+and+how+does+it+work

    Regards,

    Senthil

    Add comment
    10|10000 characters needed characters exceeded

  • May 24, 2013 at 06:55 AM

    Dear Paolo,

    It seems planning time fence must be set either at material level or MRP group level, and normally the firmed planned order does not gets changed during the planning run.

    So check if the firming indicator is set for these procurement proposal. Remove this and then re run MRP keeping planning mode 3and check the results.

    Best Regards,

    Amit Kataria

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 24, 2013 at 07:03 AM

    Hi Experts,

    Inserting images for clarification,

    This is Stock Requirements screen for my item.

    This is the MRP details of the material.

    As seen, a PO with 15 order quantity has been created, yet the planned order of 5 will still not go away after MRP run.

    Is there a way to bypass the date check?

    Thank you all.


    111.jpg (89.8 kB)
    222.jpg (154.2 kB)
    Add comment
    10|10000 characters needed characters exceeded

    • If its un-firm planned order ( Check MD12-Planned Order -Firm check box marked or not ) , then while re-planning( Select  or running MRP in MD02 or MD03  with Planning Mode -3), it should will be nullified with available stock , fixed receipt and total demand qty .Apart from that you can also try to make use of Consumption Mode ( Bwd/Fwd )  in MRP3 view based on the periods ( Bwd& Fwd consumption period)  .

  • avatar image
    Former Member
    May 26, 2013 at 07:07 AM

    While scheduling MRP, set the variant for planning mode to '3' "Delete and recreate the planning data".

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    May 27, 2013 at 05:26 AM

    Hi Paolo

    What is your delivery date in production order. Is it within the tolerance level of Rescheduling horizon. Actually as per exception message 20, the date of GR for the material is outside of tolrance level and system is asking you to delete the production order as it is not required.

    Regards

    Prashanth

    Add comment
    10|10000 characters needed characters exceeded

  • May 28, 2013 at 06:31 PM

    Hi ,

    Please check the following before you run MRP in MD01 or MD03 :

    1.Check the planned order as it should not be Firmed ( should not be marked with STAR symbol in MD04) .This happens if you changes anything in planned order  like dates or mark the firming  indicator in change mode of planned order

    2.Check the Re-scheduling Horizon days as defined and the day you are running MRP , number of days you have defined in material master as Fwd , Bwd periods , indicator in Material Master MRP3 view .

    3.While running MRP in MD02 or MD01  , please select as planning mode as 3 - Delete and Re-create planning date .

    4.Please check the Total Receipt in MD04  as well as total requirement ( un firmed planned order , PR, PIR , SO,STPR)

    Add comment
    10|10000 characters needed characters exceeded