Skip to Content
author's profile photo Former Member
Former Member

Fix the planned order dates to the Planning date in the MRP run

Hi!

I have a scenario where I want to carry out an MRP run that shall create Stock Transfer Order requirements in the form of planned orders between supplying central warehouse (DC) and plants (sites). We are using PD as MRP type and forecasted future sales from the plants as the input for creating the required quantity on the planned order (we have forecasted sales as an unplanned requirement for each day in the future).

Now to the challenge that I am facing: The SAP standard way of working seems to be that a planned order is created for the day when the shortage actually occurs in the plant/site. In the example in the picture below I have run the MRP job for a planning date of today in MD01/MD03 (09.07.2015) and the dates that are set in the planned order is when there is a shortage and the stock runs out according to the future forecasted requirements (20.07.2015).

What I want the system to do is to, in the MRP run (that is set up as a daily job), calculate what the required quantity would be today and set the dates on the planned order to today (or actually the planning date that is entered in MD01/MD03). Any suggestion in how to do this without development?

Thanks and regards,

Claes

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

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jul 10, 2015 at 01:45 AM

    Claes,

    A planned order with a due date of 'today' seems to make no sense, if it will take longer than one day to ensure that the material can be prepared for shipment in the source, and then to get the material from the source to the destination.

    Anyhow, your requirements can largely be satisfied using Manual Reorder Point planning with external requirements in the destination. MRP type V1 or a custom clone thereof. Lead time in the destination should be 'however long it takes to get the material into the destination'. The system will accept zero days replenishment if you want to have your planned order due dates of 'today'. The down side of this method is that system will always plan to fill the destination to 'reorder point', even if there is no demand. You could make the reorder point '1', which would minimize this 'problem'.

    If your business requirements only are that you want to have your supply elements be created earlier than your demand elements, then forget about reorder point planning, just try using MRP type PD with Safety Time (MRP2 TAB of MM02).

    Best Regards,

    DB49


    Capture.JPG (114.1 kB)
    Capture.JPG (50.7 kB)
    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi!

      Thanks for your reply. The reason behind the requirement is that we are not using the planned orders to carry out the actual physical goods supply. It will not generate any follow-on documents, only act as an input to a custom program that needs to understand what the store would need if we would send anything on that particular day.

      I have not tried the re-order point approach as we are not triggering the MRP job according to a certain order-point but as you mention, setting it to 1 could be a workaround to that (I will test that).

      The second approach, with safety time, I have already tested and it actually works fine together with an extension in the program where we have tested to implement a kind of planning horizon that restricts the system of looking on forecasted requirements to far in the future after the next planned delivery.

      Regards,

      Claes

  • Posted on Jul 09, 2015 at 02:56 PM

    Hi Claes,

    Why would you do this i.e. planned order are planned on the basis of MRP execution date. If I understood you correctly you want to see date as 09.07.2015 because you took MRP today. Same way if you take MRP tomorrow you prefer to have date as tomorrow, am I right?

    If this is correct then aren't you killing the purpose of MRP to a extent where it checks shortage and triggers supply accordingly?

    Regards

    Rahul

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Rahul,

      That is correct that we want the dates in the planned order to be today when we run the MRP job today and tomorrow when we run the job again the following day. The reason behind the requirement is partly because we are using the MRP job and the planned orders as an input to a custom program that is creating the actual follow-on documents in the distribution flow such as STOs, outbound deliveries etc. and partly for creating suggestions for the buyer in the form of PRs. We are not firming the planned orders or using them to perform the actual physical goods supply, it is only to understand what the store requires that particular day and as we are updating the forecast each day and as the stock in the store has been reduced we want to delete and create new planned orders the following day.

      For the distribution flow the planned orders should only be created to understand what the stores requires each day if we have incoming goods or GR goods that we could allocate accordingly taking into consideration the lead time between the DC and store.

      For the procurement flow we want to use the planned orders to generate PRs, taking into consideration the lead time between supplier and the store.

      Regards,

      Claes

  • author's profile photo Former Member
    Former Member
    Posted on Jul 10, 2015 at 10:49 AM

    use reorder point planning

    md01/04 should be scheduled as a time bound job

    have vb or v2 as mrp type

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      It does not seem to solve my problem. The re-order point procedure does not create the correct quantity as it only gives a required quantity between stock up to reorder-point level. This does not solve my issue as the lot-size needs to take future forecasted requirements into consideration.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.