How to Run a Cost Rollup in SyteLine
How do I run a cost rollup in SyteLine?
Also searched as
- SyteLine cost rollup steps
- how to update standard costs in SyteLine
- SyteLine Item Cost Rollup form
- CSI cost rollup simulate vs update
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.
Applies to: SyteLine 8.x/9.x, CloudSuite Industrial (CSI) 10.x-11.x, Mongoose and classic UI
Run a standard cost rollup in SyteLine
- 1Open Product Definition > Costing > Cost Rollup, or search "Cost Rollup" in the global search bar.
- 2Set Site, then define the item selection: a specific item, an item range, or a Planner/Product Code filter.
- 3Choose the cost set you are rolling: live Standard cost, or a What-If cost set for comparison.
- 4Check Simulate so the run only calculates and reports without posting to live Item Cost records.
- 5Run and review the Cost Rollup Exceptions/Variance report for items with missing routings, missing BOM components, or zero-cost purchased items.
- 6Fix flagged items: add the missing routing operation, correct the phantom BOM flag, or update the purchased item's last cost.
- 7Re-run in Simulate until variances are explained, then clear Simulate and run live to post costs.
- 8Print or export the Costed Bill of Material report to archive the new cost basis before it goes live.
- 9Tell Finance the new effective date, since it affects WIP and inventory valuation from the next transaction forward.
What the rollup actually calculates
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
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
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.
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
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.
Try it here, free
SyteLine Cost Rollup Variance Calculator
Compare actual job cost to the rolled standard by material, labor and overhead, and see the inventory revaluation caused by a standard cost change.
Common 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.
How an ERP-grounded AI assistant handles this
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.
Frequently asked questions
Does cost rollup change costs on open job orders?
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?
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?
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?
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.
Related
How to Close a Job Order in SyteLine
Close a job order from Production > Job Orders once every routing operation is reported complete and the finished quantity has been received, then run Close Jobs to post the remaining WIP balance to variance and lock the job from further transactions.
How-toHow to Run a Cycle Count in SyteLine
Cycle counting in SyteLine runs through Inventory > Cycle Count: generate a count list by ABC class or location, print or enter tags, key the counted quantities into Cycle Count Entry, then review the variance report before posting the count to update on-hand quantity.
How-toHow to Run MRP in SyteLine
MRP in SyteLine runs from Planning > MRP Processing as either a full Regenerative run or a Net Change run against demand from customer orders, forecasts, and safety stock; results appear as planned orders and Action Messages in the Planner Workbench.
How-toSyteLine Customer Order to Invoice: Step by Step
A SyteLine customer order flows from Order Entry through pick, pack, and Customer Shipment, then to invoicing, either through the Auto Invoice batch utility or manual Invoice Entry, posting revenue and relieving inventory once the shipment is confirmed.
Error fixFixing SyteLine's 'Object reference not set to an instance of an object' error
This is a generic .NET NullReferenceException surfacing through the SyteLine IDO Runtime, not a SyteLine-specific error code. It almost always means a form, script or IDO method referenced a field, row or object that came back null, usually after a customization, a missing related record, or a view/IDO method call before the form finished loading. Turn on detailed client logging and check the most recent customization or form event first.
Error fixDiagnosing and fixing SyteLine session timeout errors
SyteLine session timeouts come from one of three independent layers: the IDO Data Service session timeout on the app server, the IIS/application pool idle timeout for the web (Mongoose Web) client, or a load balancer/proxy idle timeout in front of a CloudSuite hosted environment. Fixing the wrong layer is the most common mistake - you need to identify which layer is actually expiring the session before changing anything.
AI for ERPAI for Infor SyteLine and CloudSuite Industrial
Add grounded AI to Infor SyteLine or CloudSuite Industrial: natural-language answers, agents over IDOs and ION, on-prem or CloudSuite deployment.
AI for ERPOn-Prem AI for CloudSuite Industrial, Without the Multi-Tenant Cloud Move
Add generative AI to CloudSuite Industrial without moving to Infor's multi-tenant cloud. On-prem private LLM options for CSI, with governance and audit built in.
Stuck on Infor SyteLine (CloudSuite Industrial)?
Talk to engineers who work inside Infor SyteLine (CloudSuite Industrial) every week, and who build private AI that answers these questions from your own ERP data.
New to Infor SyteLine? Start with the Infor SyteLine guide and toolkit, or plan with Training Path Builder, ERP Certification Study Planner, Upgrade Path Planner.
Keep exploring
Free tools
- SyteLine Cost Rollup Variance CalculatorCompare actual job cost to the rolled standard by material, labor and overhead, and see the inventory revaluation caused by a standard cost change.
- Product Cost Rollup CalculatorRoll material, direct labor, applied overhead, machine time, and scrap loss into a single defensible unit cost the way your ERP cost rollup should.
- Job Costing Variance WorksheetCompare the estimated and actual quantity and rate on a job by cost element and split the difference into quantity and rate variance.
ERP fixes and how-tos
- How to Change an Item's Standard Cost in SyteLineUpdate a SyteLine item's standard cost by hand or through Cost Rollup, then run Recost Inventory to revalue on-hand stock and post the GL variance correctly.
- SyteLine error: no cost record exists for this item at this siteWhy SyteLine blocks a transaction with a missing standard cost or cost element error, and how to fix it via Item Costs, Cost Rollup, and cost effective-dating.
- How to Close a Job Order in SyteLineClose a SyteLine job order the right way: finish routings, issue material, receive finished goods, then run Close Jobs to post WIP to variance accounts.
Guides
- How to Fix SyteLine Cost Rollup VariancesDiagnose and resolve cost rollup variances in Infor SyteLine including material, labor, and overhead cost discrepancies with SQL validation queries and BOM audit steps.
- How to Configure Standard Costing in SyteLineStep-by-step guide to configuring standard costing in Infor SyteLine CloudSuite Industrial. Set up cost types, material costs, overhead rates, and cost rollup parameters.
- How to Run Cost Rollup in SyteLineComplete guide to running cost rollups in Infor SyteLine. Learn how to calculate rolled-up costs across BOM levels, validate results, and update standard costs.
AI on your ERP
- AI for Cost Accounting and Variance Analysis: Explain Why Standard and Actual Cost DivergedAI that explains purchase price, usage, efficiency and rate variances from ERP cost data, flags rollup problems and drafts variance commentary. Private and on-prem.
- On-Prem AI for CloudSuite Industrial, Without the Multi-Tenant Cloud MoveAdd generative AI to CloudSuite Industrial without moving to Infor's multi-tenant cloud. On-prem private LLM options for CSI, with governance and audit built in.