# How to Run a Cost Rollup in SyteLine > Source: https://netray.co/erp-help/syteline-how-to-run-cost-rollup > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer Run Item Cost Rollup from Product Definition > Costing > Cost Rollup, select the site and item range, run it in Simulate mode first to review variances, then run it live to post new standard costs to Item records and the Costed Bill of Material. ## Kind how-to ## System syteline ## Erp Infor SyteLine (CloudSuite Industrial) ## Module Product Definition / Costing ## Query How do I run a cost rollup in SyteLine? ## Alternate Queries - SyteLine cost rollup steps - how to update standard costs in SyteLine - SyteLine Item Cost Rollup form - CSI cost rollup simulate vs update ## Applies To SyteLine 8.x/9.x, CloudSuite Industrial (CSI) 10.x-11.x, Mongoose and classic UI ## Steps ### Run a standard cost rollup in SyteLine **Items:** - Open Product Definition > Costing > Cost Rollup, or search "Cost Rollup" in the global search bar. - Set Site, then define the item selection: a specific item, an item range, or a Planner/Product Code filter. - Choose the cost set you are rolling: live Standard cost, or a What-If cost set for comparison. - Check Simulate so the run only calculates and reports without posting to live Item Cost records. - Run and review the Cost Rollup Exceptions/Variance report for items with missing routings, missing BOM components, or zero-cost purchased items. - Fix flagged items: add the missing routing operation, correct the phantom BOM flag, or update the purchased item's last cost. - Re-run in Simulate until variances are explained, then clear Simulate and run live to post costs. - Print or export the Costed Bill of Material report to archive the new cost basis before it goes live. - Tell Finance the new effective date, since it affects WIP and inventory valuation from the next transaction forward. ## Sections ### What the rollup actually calculates **Body:** The rollup explodes each item's bill of material from the lowest level up, pulling in material cost from purchased components and lower-level manufactured items that have already been costed in the same run. Labor and machine burden come from the routing operations attached to the item, using the standard rates on the work centers. Overhead is applied according to whatever overhead method the site has configured, either a percentage of labor or a fixed rate per unit. Because the roll works bottom-up, a change to a purchased component's cost or a sub-assembly's routing ripples up through every parent that uses it in the same run, which is why a single rollup can move standard cost on hundreds of finished items at once. ### Simulate mode vs a live update **Body:** Simulate mode calculates the new standard costs and produces the variance report but does not write to the live Item Cost fields, so it is safe to run repeatedly while cleaning up data. A live run overwrites the current standard cost on the item record and immediately changes what new job orders and purchase estimates use going forward. Most sites treat the live rollup as a controlled, period-end event rather than an ad hoc action, because it changes the cost basis Finance uses for WIP and inventory valuation reporting for every transaction after the effective date. ### Common causes of rollup variance **Body:** The exceptions report usually points to a small set of repeat offenders: a manufactured item with no routing operations attached (so labor and burden roll as zero), a purchased item with no recent purchase order or vendor item cost (so material cost rolls as zero), a phantom item incorrectly flagged as a stocked component, or an obsolete BOM line that should have been end-dated but is still in the active structure. A quick way to find zero-cost purchased items before running the rollup is to query the item table directly for make items with no material cost, which flags the gaps that will otherwise show up buried in the variance report. **Code:** - SELECT item, description, std_labor, std_material, std_burden FROM item WHERE site_ref = 'MAIN' AND make_buy = 'M' AND std_material = 0 ### Where the new numbers land **Body:** A live rollup updates the standard material, labor, burden, and service cost fields on the item record for the selected site, and those fields feed the Costed Bill of Material report, the estimated cost captured when a new job order is released, and any quote or price-code logic that references standard cost. Released job orders are not retroactively repriced; they keep the estimated cost that was captured at release time, so the effect of a rollup is visible on new activity, not on work already in progress. ## Pitfalls - Running the live rollup mid-period rather than at a controlled cutover corrupts WIP variance reporting for that month. - Leaving a phantom BOM flag wrong causes the same cost to be counted twice as the roll passes through the structure. - Purchased items with no recent PO or vendor item cost silently roll to zero material cost instead of throwing a hard error. - The rollup only updates items included in the selection filter, so a narrow item range leaves stale costs on the rest of an assembly tree. - In a multi-site configuration, forgetting to run the rollup separately for each site leaves some sites on old standard costs. - Assuming the rollup reprices open job orders; it only sets the cost basis for new activity from the effective date forward. ## Ai Angle ERPray, grounded on the SyteLine IDO layer, can be asked which items had the biggest standard cost swing at the last rollup and why, and answer directly from item and BOM history instead of someone re-running the variance report and eyeballing it - useful the week after a rollup when Finance wants a one-line explanation of margin movement. ## Faq ### Does cost rollup change costs on open job orders? **Answer:** No. Released job orders keep the estimated cost captured at release time; only new job orders and the Costed Bill of Material reflect the new standard cost after a live rollup. ### What is the difference between Simulate and a What-If cost set? **Answer:** Simulate just stops the run from posting to live item records. A What-If cost set is a separate named cost set you can roll and compare against Standard cost without touching production data at all, even after clearing Simulate. ### Why does the rollup show a variance report but no dollar change? **Answer:** The exceptions report also flags structural issues, such as a missing routing or a phantom mismatch, that do not move cost but do indicate the item's cost basis is unreliable and should be reviewed before you trust the roll. ### Can cost rollup be scheduled to run unattended? **Answer:** Some CSI environments run a saved cost rollup job through the batch/task scheduler, but most shops still run it manually at period-end or whenever material costs are known to have moved, so the exceptions report gets reviewed by a person first. ## Search terms syteline cost rollup, csi cost rollup steps, syteline standard cost update, infor syteline item costing, syteline costed bom, cloudsuite industrial cost rollup, syteline simulate cost rollup, syteline job order estimated cost, syteline rollup variance report, syteline multi-site cost rollup --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json