Manufacturing, Distribution, and Internet Applications

[Libnic]

Is there a way to change a WO release date from MRP? 

Currently in our application, we just care for two dates in a  WO: the release date (since you can not enter transactions for the WO before it), and the Required Date (if the required qty has not been entered by then, the WO will be considered late).  When we create a WO using the "WO Creation" window, we enter the Entry Date and Release Date as the same; and we enter at the Required Date  and  the MFG Commit Date, the day when we want the WO finished.

But, when reviewing the Planned WO on MRP, it allows you to modify two dates: the "Req Date" and "Ord Date".  The "Req Date" gets entered in the WO as both the "Required Date" and the "Release Date"; the "Ord Date" from MRP gets entered as the "MFG Commit Date" in the WO. 

For us, it doesn't make sense that the Required Date and the Release Date are the same (as most of the times we enter apartial qty for the WO before the Required Date). 

I know you can modify the Release Date on the Work Order Maintenance screen, but we want to be able to do it from the MRP application (running  MRP seems almost as a waste of time if you need to go to each individual WO and correct the dates).

Again, we just want to be able to change the Release Date from the MRP window, and make it different than the Required Date.

Any suggestions?

[Russ]

This does not seem correct.  Could you let me know what version of MAS 500 you are running?  I just tested this and confirmed that I see the same results on the 7.3 December 2010 Product Update.  I am wondering if you are running the same version or if you are running a prior version.  This seems as though it would have been something that was reported to support long ago if this issue had existed on prior versions of MAS 500.

In my humble opionion, MRP should set the release date as the Entry Date (which is the Create Date when it is generated from MRP) or maybe someone could make case that this would be set as the MFG Commit Date.

I guess what I am saying is that my suggestion is that this should be reported to MAS 500 support.  

[Russ · Accepted solution]

One of my co-workers just reminded me of another "work around" to this.  In the Manufacturing Setup there is a setting for Release Date Days.  If you set this value to something other than zero, MRP and standard work order creation will default the release date to this number of days prior to the required date.  If you set this value to something that is longer than your longest lead time, then you should never have to adjust the Release Date on your work orders going forward.

Again, it really seems that it would make more sense that the release date would factor in something such as the MFG Commit Date, but hopefully this work around will solve your issue.

[Libnic]

We are using version 7.20.22.0

December 2010 Update.