Skip to Content
avatar image
Former Member

rrp3 order issue

Hi

supposing i am planning order 5000 on july 1st and 2000 on july 5th..... so it makes an completed order of 6000 on 9 th july and 1000 on 10th july( so totally 7000)

now i want to know how it was split ......where this 6000 precisely is coming from how much from july 1st session and how much from july 5th session.

how do i find it....rrp3 is the most complicated place on earth.....where and how in rrp3 i find out.

thanks

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • Best Answer
    Nov 15, 2013 at 05:35 AM

    Please check the lot size method, minimum lot sie qty., max lot size and rounding value from product master in APO. The order quantities are a result of these settings

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 15, 2013 at 10:40 AM

    Order size (quantity) would depend on lot-size. You can check Product Master in RRP3 page itself. Go to "Lot Size" tab and within that tab "Procedure" and also "Quantity and Date Determination". These fields are of your interest. If you can share the values you see there, we can try to reconstruct and explain.


    pastedImage_0.png (13.8 kB)
    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 15, 2013 at 05:37 PM

    RO,

    For this purpose, //RRP3 is no different from MD04/MD05; which you already know. Typically, the links between specific supply and demand elements are only logical and dynamic (can change at any time), unless you are talking about MTO or some other business condition that requires fixed pegging.

    The advantage of //RRP3 is that there usually is a nice pegging structure to tell you which supply element is currently being planned to support which demand element. Look at the 'Pegging Overview' tab to see the relationships.

    Best Regards,

    DB49

    Add comment
    10|10000 characters needed characters exceeded