During MRP Run Error

[Former Member]

Hi Gurus,

When we run MRP we get error 3,067 date comes after end of valid factory calender.(Please Correct )

Above error comes so it is related with factory calendar or any note is to be applied.

Note that requirement given is not of future it is of same APR month only.

Regards

SANIL

[Former Member · Accepted solution]

hi sanil ,

please check if there is any open MRP elements for that material code which lies outside that factory calender range .

it can be open PO , PR , resrvation , planned order , process order etc.

need to check in the tables .

if the error is in production server , please check if the same you are geting in quality server (in case it is having same data)

than try to cahnge calender range in quality and check in MD05 / MD04 you will get the mrp elements there and so you can trace

the root cause.

hope this helps you

regards

satish

[former_member189817]

Check whether diffrent factory calendar assigned in workcenter or not ?

Regards,

Velmurugan S

[former_member207609]

Hi

The error can come up in any case of time calcaultion of MRP, not only the case of requirement date calculation.

For example, calculate the rescheduling horizon, planning horizon, coverage profile, etc, if the end time of the horizon is out of the factory calendar, the error would be rised. Please go to material master and OPPR and OPPQ to check if there are too long horizons.

If you are not sure how to check them or there are no problems in the points above, you can easily set the breakpoint in the function DATE_CONVERT_TO_FACTORYDATE to see the parameters of that when it is reached in debugging of MRP. (Set the break point in SE37 and run MRP.), this function can be reached many times, so you'd better get that which is the closest to the error.

The paramter FACTORY_CALENDAR_ID shows the ID of factory calendar used, of course, you can also go to SCAL to get the factory calendar id of the plant, however, the ways of debugging is much more correct.

Then, you can run another function FACTORYDATE_CONVERT_TO_DATE in SE37, input the 3,067 shows in the error and the factory calendar id, it would show the date what you can recognize e.g. 09.04.2010. Then, please go to SCAL to extend the calendar to cover the date, this should solve the issue.

(The 3,067 is the date used in system internally, so you need to TRANSALTE it by the second function.)

Edited by: Leon Shen on Apr 9, 2010 11:13 AM

Edited by: Leon Shen on Apr 9, 2010 11:16 AM

Edited by: Leon Shen on Apr 9, 2010 11:19 AM

[rupesh_brahmankar3]

Dear,

Please check if a valid factory calendar and Check that Valid Factory Calendar is assigned with your plant. You can check the detail in transaction OX10.

Use transaction SCAL to extend the factory calendar validity.

Please refer my reply from these threads,

Regards,

R.Brahmankar