Planned order start date change not working

[Shiva_Ram]

Hi,

I try to change the start date in the planned order (for intermediate material), which is created by MRP run. In MD04, the exception reads 06 (start date as past). Through MD04, change button, I changed the start date from current date to future date (say 02/07/2012) and after saving I go back in display mode, it still holds today's date. May I know what master data/parameter not allowing to change the date? How to change the planned order start date? I already searched the forum/web, but could not find suitable answer. The SAP version is 4.7 and I have service packs upto SAPKH47029, so OSS Note 944965 - Planned order conversion: changing planned order data won't help.

This is happening for only one material, others working ok, so compared the material master found no difference except production storage location. There is no entry for this field. Does this cause the start date problem?

Thanks for your inputs,

Regards,

[former_member184701 · Accepted solution]

dear friend,

just a quick question - what will happened if you re-run MRP ?

i mean the follwing steps:

1. run MD04 and change the start date in planned order (save order of course)

2. leave MD04

3. run MRP for, say, manufacturing and palnning plants

4.run MD04 and check that planned order

regards,

P.S. did you try to use MD12 ?

[Shiva_Ram · Accepted solution]

Thanks for your response, Yes I tried with MD12. I will check with for the MRP run with the user and update. Do you mean only the second MRP run will correct the date?

Regards,

Edited by: Shiva Ram on Dec 13, 2011 3:54 PM

[former_member184701 · Accepted solution]

thank you friend.

i strongly recommend the MD01 for both plants (if you have planning and manufacturing) but not the MD02 just for that product

good luck!

[Former Member · Accepted solution]

Can you upload screenshots of MD04, MRP1-4 views, OPU5 setup, MD12 (for the planned order which has the issue) to some portal & paste the link here?

[Shiva_Ram · Accepted solution]

Thank you all for your time, finally we figured it out. The routing data (in t.code CA03) for capacity planning and scheduling the user maintained wrong number of hours and that created the issue. The total number of days was more than 1000 days, hence system trying to do forward scheduling, keeping the current date as start date. User was advised to correct the route data.

Regards,