How to Update Estimated Job Costs

Greetings All,

I have searched High and Low to try to find if there is a process to update Job Mtl costs on jobs already created. Here is the setup. We are using Sts Cost

Jobs Created.
Cost rollup executed ( all mfg Parts)
Job executed
End of month Closing
Variance thrown, Job using old costs.

Is there any way ( In Epicor) to update the mtl costs in bulk ? As everyone knows, costs are fluctuating a lot these days.

Thanks

Dean Miller

1 Like

Hi Dean, you could do this with DMT if you’re licensed for it. If not, you could build an updateable dashboard and copy the data from Excel, then do a Paste Update into the dashboard.

Hi Jacquelyn,

Mmmm, never thought of DMT. BAQ of open jobs, not started, grab PN, join PartCosts, Import to DMT…Could work. I guess on the Wish List for out of the box solutions.

Thank You !! Sometimes fresh set of eyeds helps. Will keep post open just in case someone chimes in with Out of the box solution…

Dean

Dean, I didn’t think that variances were calculated off of job fields, I thought it was actual costs v.s. standard cost in the Part Cost table?

You are using standard costing yeah?

Utah,

From what I have seen, When the job is created, the Mtl cost at the time is recorded in the JobDtl(?). If the standard cost for the component part changes, the estimated cost for the job still reflects the old cost, that is what it has stored. Maybe variance is not the correct term, Estimated cost gets out of sync with the actual cost. we do not record time on jobs, just qty, labor standards are set so there should be no differences.

I hope I am not making a mountain out of a molehill…

Dean

Dean, okay that is consistent with what I am also seeing.

I have the same issue as you in that I want to look into my variances using the production detail report, but my estimates are always off and don’t match what the standard cost used…

I haven’t tried to climb the mountain that you are trying to climb right now.

Yes Std Cost

Dean, this is why I was wondering, can you just unrelease and then release the job again to refresh the costs?

I believe it happens when Engineered but I may be wrong.

1 Like

Will it re-calculate?

Thanks for taking the time to respond Mark.

1 Like

Thank you Mr Wonsil. This is sounding like a big DMT job. Un-release, Un-Engineer. Engineer, Release ??

Un-Engineering does an implicit Un-Release and Release will also do an implicit Engineer, so it’s only two passes with DMT.

That is correct, I have a good memory, its just short… :laughing:

1 Like

Slow Update on this. Un engineer/engineer does not refresh the costs. Right click-Delete all in the ASM 0 tree then get details will work.

Little surprised there is not an Epicor out of the box solution. We had to schedule these jobs last fall for this spring ( supply chain issues…) . Meantime, costs changed. Did cost roll up so sales could set Price but jobs still at old STD costs…

Dean

@DeanMiller You can reset in a post processing MD on JobEntry.ChangeJobHeadJobReleased.

A foreach on JobMtl with a lookup on PartCost. We were forced to do this as some of our components on jobs are brand new and have zero for cost so the estimate to actual was a mess.

Mr Payne,

Ahhhhh, the light bulb goes off. One step further… If dmt unrelease all open jobs then release same list, Will MD still fire ?

Dean

Ouch!

@DeanMiller I don’t know if the change JobHeadJobReleased will fire from the DMT, but I assume Update will if it doesn’t.

If you are looking to do a mass run of cost updates you can hang the bpm on the update of UDxx and just fire it off. Add the UDxx table maintenance screen to a menu. Add one record to the table to begin the process.