Good Morning,
I have a duplicate database for testing, one in version 905702A the other in version 10.1.500.15. I am running MRP to see what difference I might have between versions. I am not getting ANY UNFIRM jobs in the E10. I looked for any new variables in company or site configuration and don’t see anything that looks to be telling system not to generate any unfirm jobs.
Anyone have any ideas of why my E10 wouldn’t be generating any unfirm jobs on MRP run?
Thanks!
Nancy
Have you run MRP with logging turned on and have you reviewed the log files?
Mark Wagner
Sr. Partner
Capstone Alliance Partners 888.597.2227 Ext. 71
<888.597.2227%20Ext.%20714>2 | 904.412.6847 mwagner@capstoneap.com (cell)
| www.capstoneap.com
Hi Mark,
Yes. Here’s the beginning of the main log file showing comparison of E9 vs E10 run. Then as far as other log files get, I have 364 unfirm jobs log files from E9 and NO unfirm job log files in E10.
Also, at the end of the processor 001 log from E9 I get:
14:24:25 MRP Process 1 done
14:24:25 MRP process 1 done. Total Wait/Scheduling Time = 00:03:23
14:24:25 Parts: 13380; New Jobs: 145; Reused Jobs: 0; Deleted Jobs: 99; Scheduled Jobs: 0; Saved Load: 132
At the end of the processor 001 log from E10 I get:
11:18:56 MRP Process 1 done
11:18:56 MRP process 1 done. Total Wait/Scheduling Time = 00h:00m:00s:000ms
11:18:56 Parts: 6745; New Jobs: 0; Reused Jobs: 0; Deleted Jobs: 0; Scheduled Jobs: 0; Saved Load: 0
Thanks,
Nancy
Hooray!
Mark, your comment on the logs got me thinking to go through and evaluate the details on processing a part that had an unfirm job in E9 vs did not have one in E10. Thank you.
There was a bpm on Job Head that was created during upgrade, when BAM was changed into data directive.
The strangest part is, all of the non-job table BAMs that were made into data directives were made “outdated” and were not checked “enabled”, but the Job ones were made into data directives and checked as outdated and enabled 
Nancy
