I installed the service pack. Now, when I try to post a cost batch in Job Cost (was retrieved from A/P) it will not let me post all entries. States "ERROR: Estimate does not exist for this job", when in fact an exact estimate does exist for that job. I tried re-entering the entry in Job cost, using the finder (insuring that the information is in fact there) and it still will not let me post, stating the same error.
Help!

Hi Karen,

There is a known situation where jobs with 'Simple job costing' enabled and estimates that have a phase and/or category for some reason generate the error message on the cost batch listing report. This does not adversly affect posting, just the list report. It is currently in development's hands.

In my tests, posting is not affected and works as expected, so we would need some information regarding the settings enabled on the job and estimate in order to try and duplicate the problem you are experiencing.

Hi Tech Support:

I'm bringing this back to the top because one of our clients has the same problem with the Job Cost report (each line is printed with "Estimate does not exist for this job" even when there is an estimate).

The March Service Pack didn't address this problem.

Is there a solution? Do you need to see actual data?

Thanks.

Hi Bruce Gardner,

Yes, we'd like to see the data.

Andrew:

The dataset has been uploaded to the data repair FTP site.

More information:
-DIC is clean
-Our client just upgraded from PLUS JC about 4 wks ago
-Apart from error message on report, everything else seems correct.

Hi Bruce,

This report error was not addressed in the March 2006 service pack (it was mostly for compatibility to Inventory 8.0B), so this is why your client is getting the error.

Again, the reason is that the job has the 'Simple job costing' enabled and estimates have a phase and/or category. I was able to post the batch, so the report error is a nuisance, but doesn't prevent anything from working.

Hello Bruce Gardner,

Thanks for the data. It will help us confirm that we have fixed the problem for the next JobCost Service Pack.