I am hoping someone can help me understand how Epicor determines which revision to use on job’s sub-assembly. I have always thought Epicor was comparing your current system date against the approved revision’s effective date. Picking the revision with the date closest to this date without going past. If you happen to have more than one approved revision with the same effective date, then Epicor would pick the revision with the highest revision number (arranging revisions ordered by RevisionNum).
In our testing we noticed that for our sub-assembly Epicor was using the Job’s required by date instead of the system date and comparing that value against the effective dates of your approved revisions.
We had two approved revisions, one with an August 23rd date and the second revision has a future October 24th date. If we set the Job’s Required date to 10/23, then perform the Action> Get Detailsm Epicor picks the first revision for the sub-assembly when we pull in dates for the job. If we change the Job’s required date to 10/30, Epicor will select the second revision.
If this is true, then why doesn’t Epicor use the same logic when I pull in the details for the job’s primary part. The Get Details form places the selection arrow next to the revision with the closest effective date compared to the current date. It doesn’t seem to matter if I can the job’s Required Date then go to Get Details.
DueDate = JobAsmbl.DueDate ?? JobHead.ReqDueDate;
SetAsOfDate(PartRev.PartNum, PartRev.RevisionNum, PartRev.AltMethod, DueDate, out newRev, out AsOfDate);
It basically uses the Job’s Due Date to determine what revision is Effective on that Date and it will use that. However for many other items epicor uses CompanyDate.Today.
I am unsure why Epicor uses DueDate to determine Revision on Sub-Assemblies. Because what if you want to use the current one and simply build the next 3 jobs STILL with current Revision, it sneaks up on you. If you for example use Quick Job Entry, and date something a month out and assume it will use the current Revision, you are wrong - it will use what’s Effective Then.
Maybe @timshuwy can elaborate on this a bit more, I know he knows his Revisions.
Thanks for the vote of confidence. Yes, it is as you said… the revision effectivity date is aligned with the DUE date. Personally, I would have probably specified that it should be aligned with the START date, but it is consistant.
Maybe this deserves an Epicor IDEA posting… I woudl suggest that the idea be to "Create a system flag that defines whether the revision effective date is is driven by the START or END date of the Job.
But there could be some challenges to this… I believe that in the sales system, the system decides which rev to use based on the delivery date. In sales, we dont know the start date of the job, so, again, it is consistent the due date drives the chosen revision.
