Job & Job Template Recost

Templates are a major use case, and the job search also supports other statuses. Select the intended status and exact job IDs. Earlier template-only releases and newer screen layouts are product generations, not separate editions.

No. Labor estimates, labor actuals, material estimates and material actuals have independent switches. Select the relevant items as well as the category. For a template refresh, choose estimates deliberately and leave unnecessary actual processing off.

Yes. Job Search IMPORT reads existing job IDs from column A of the first worksheet, with a header row. Use a clean XLSX or XLS file and preserve identifiers as text. Review the returned matches, then select and ACCEPT. The workbook identifies jobs; it does not import rates or cost values, and unknown IDs do not create jobs.

The selected source value may already match the job. Check category switches, selected items, current data and the chosen master cost field. A zero master value or unsuitable unit-conversion data can produce a zero proposal. Explain unexpected values before updating.

The job-search date range selects Job Order Date. LABOR DATE RANGE uses labor Work Date. PICK DATE RANGE limits the issue lots used for the lot-cost lookup; it does not limit the material actual total to the quantity issued in that period. Confirm full operation totals when using a labor date or employee subset.

The documented workflow looks up current matching material and lot-location costs and averages those values. It does not reconstruct a quantity-weighted historical pick cost. That basis can also influence estimates when both material categories are enabled; leave estimates off when they should be preserved and verify the saved fields.

Raw stock can use different stocking and costing units. Check the unit conversion and both stored unit and extended costs. The displayed Cost Each is Total Cost divided by Order Quantity, so confirm that quantity before interpreting the per-unit result.

Use REFRESH DATA or restart, then rebuild the target list and selections before calculating a different scenario. Explicitly click Standard, Average or Last again, even if it appears selected. In the documented Version 2 workflow, a subsequent preview can save earlier calculated operation changes. Repeated previews are not an isolated sandbox; CLEAR JOBS is not an undo or a fresh-data reset.

They can be selected. Actual-cost changes affect historical job cost information rather than creating a new current-date adjusting entry. Confirm the intended period and reporting impact with the company’s costing owner before changing closed or previously reported work.

Job Recost updates cost and selected synchronization fields. It does not rebalance recorded hours, adjust stock quantities or rewrite historical material issue and transfer transactions. Review already-transferred work through the established costing process.

The main comparison covers explicitly listed jobs. RECOST CHILD ASSEMBLIES expands the final update below a selected parent. Review descendant scope separately and confirm the saved results on affected children.

Do not rely on the older template wording as a status restriction. The option can synchronize selected jobs from the matching material master. Choose only the jobs whose selling price should change.

The documented utility workflow does not provide a separate estimate-only permission. Have the administrator manage access to the installed utility and ensure users understand the approved costing process and database connection.

Newer installed revisions may provide a per-job Detail window and Excel export for analysis. Use those controls where available. The illustrated Version 2 layout shows summary comparisons; JobBOSS job details and available cost reports support verification in that layout.

Keep the error text, target list, settings and approximate time. Check which jobs and descendants have already changed before repeating the batch. Refresh current data and resolve the cause with Neptune or the setup contact. Do not assume the entire batch rolled back or that a success message replaces detail verification.