We’d like to have MRP assign a Scheduling Priority Code to job suggestions based on the part operation. I don’t see anywhere I’d change/add this code other than directly on the job.
My inclination is to add a UD field to PartOpr and then a Data Directive on JobHead to automagically update the priority code.
Joe,
So this sounds like you want to prioritize Jobs that contain a certain operations for certain parts… a UD field on PartOpr might work. But you might want to first explore the Setup Group field on PartOpr. The idea behind Setup Groups is that you want to schedule all PartOprs that belong to the same Setup Group together and going further, each Setup Group can be assigned a Scheduling Precedence so you can control the Order of the overall Setup Groups. The downside is that the Setup Group is not evaluated during Scheduling but instead it’s part of the ‘Load Leveling’ function in the Scheduling Board since usually Setup Groups are not idea for Global Scheduling since you can end up in a situation where you get stuck in the same group forever.
However, you ‘could’ hijack the Setup Group for your Priority Code, meaning you can create Setup Group values that match your Priority Codes and then have the BPM during Job creation just setup the Job Head Priority Code to the First/Last/Other Criteria JobOper.SetupGroup value when it exist on a Job. This really depends on specific details of your environment, obviously.
The way I used BPM’s to set the Priority Code on the Job Head was with Product Groups (cause that worked for the client). We added a UD combo called ‘Scheduling Priority’ that pulled it’s list from the Scheduling Priorities table, then during MRP the BPM would set the Job’s Priority to whatever the value it found for the Job’s Product Group.
Really depends on what works.
I’d really love it if I could use the Setup Group to have MRP schedule like products on the same resource, but my results have been disappointing. Using the field for the priority code, though, might just have some merit.