Job Batching - Actual Cost to original Job

Hey Friends,

We are seeing some odd behavior relating to job batching and cost roll up to the main job.

Say we have main job 123, it then has a batch job of 123-A. When running the production detail report we see batch job 123-A has actual costs and a status of complete. Job 123 shows no actual costs and has a status of closed.

We would expect to see the actual costs roll up to the parent jobs. Is there a setting in Kinetic where we can adjust this? Any ideas what could cause this?

Any insights here would help us out a ton. Thanks!

Hi Jeff - can you confirm that the parts from the batched job moved back onto the original jobs? I.e. either a Job Receipt to Job transaction was manually made or the ‘Auto Receive’ box was flagged on the last operation on the batched job. If a transaction didn’t occur to move the parts back, then the costs wouldn’t show up on the original jobs.

I have also seen issues with timing - if the parent job is marked complete/closed/goes into inventory before the batched job has all transactions completed, the costs may not carry through as expected.

3 Likes

Hi Beverly, thanks for the insight!

I can see the operation on the job is marked as final and auto receive. Looking at the manufactured receipts on the batch job I see a positive qty went to the parent job.

If this is indeed an issue with timing, how could this be corrected? Is there a system process we can run to recalculate the costs?

Fixing it is going to depend on how the parent jobs were structured as far as a demand link, the costing method you use, whether the COS Capture process has run, and potentially some other financial implications that I can’t think of at the moment.
This thread may help provide some insight: Add Labor & Burden to closed jobs