SyteLine error: no cost record exists for this item at this site
SyteLine no standard cost exists for this item error
Also searched as
- SyteLine cost record not found error
- syteline item has no cost element error
- syteline transaction fails missing cost
Short answer
SyteLine will not post an inventory, job, or purchasing transaction that has no valid standard (or average) cost record for the item at that site and cost type, because the transaction needs a cost to value the GL entry. Run a cost rollup or manually enter the item's standard cost in Item Costs, make sure the cost is effective-dated to cover the transaction date, then reprocess.
Applies to: SyteLine 8.x, 9.x, CloudSuite Industrial (standard costing and average costing environments)
Fix a missing cost record
- 1Identify the item, site, and cost type (frozen standard, current standard, or average) referenced in the error.
- 2Open Item Costs (or Costed Item BOMs) for that item-site and check whether a cost record exists for the required cost set.
- 3If the item is manufactured, run Cost Rollup for that item (and its BOM components if they also lack costs) to calculate and populate standard costs.
- 4If the item is purchased, manually enter a standard or average cost via Item Costs, or process a receipt with a cost that establishes an average cost.
- 5Check the cost's effective date - a cost record dated after the transaction date will not satisfy a transaction posted earlier.
- 6For a new item just added via Copy Item Sites, remember cost is not always copied automatically - verify and roll up costs before the item goes live for transactions.
- 7Reprocess the failed transaction (job transaction, PO receipt, inventory adjustment) once the cost record is confirmed.
Why every transaction needs a cost
SyteLine's standard costing model requires every inventory-affecting transaction to post a dollar value to the general ledger at the moment it occurs - a job material issue, a PO receipt, an inventory adjustment. If the item has no cost record for the relevant cost type at that site, the system has nothing to value the GL entry with and rejects the transaction rather than posting a zero-dollar or estimated entry that would distort inventory valuation and variance reporting.
Cost Rollup versus manual entry
Manufactured items should get their standard cost from Cost Rollup, which walks the BOM and routing to calculate material, labor, and overhead cost elements bottom-up. Running the rollup on a parent item before its components have costs of their own will produce an incomplete or zero cost, which then causes the same missing-cost error further up the chain, so rollups should generally run from the lowest BOM level upward or use the multi-level rollup option.
Purchased items typically get a cost either by manual entry in Item Costs before the first purchase, or by letting the first PO receipt establish an average cost if the site uses average costing - but standard costing sites still need a standard cost entered up front since average-cost mechanics do not apply.
-- Quick check: does the item-site have any cost record at all SELECT item, site_ref, cost_type, std_matl_cost, std_labor_cost, std_burden_cost, eff_date FROM item_cost WHERE item = 'YOUR-ITEM-NUMBER' AND site_ref = 'YOUR-SITE';
Effective-dated costs and back-dated transactions
SyteLine supports effective-dated standard costs so a company can schedule a cost change for a future date without disrupting current transactions. If someone tries to post or back-date a transaction to a period before the earliest effective cost record exists, the system will report the same missing-cost condition even though a cost record technically exists - just not one covering that date.
Common pitfalls
- !Rolling up a parent assembly before its purchased or manufactured components have costs produces a misleadingly low or zero standard cost - always cost the lowest BOM level first.
- !Copying an item to a new site with Copy Item Sites does not guarantee costs came along correctly - verify before the item is used in a live transaction.
- !Effective-dating a cost change too far in the future will cause the missing-cost error on any transaction posted before that date, even if a record technically exists.
- !Switching cost sets (frozen standard versus current standard) mid-year without rolling both sets forward leaves one set stale and can trigger this error selectively.
- !Average-costed items still need an initial cost basis; leaving cost at zero on the first receipt understates inventory value from day one.
How an ERP-grounded AI assistant handles this
ERPray can trace a failed job transaction back to the specific missing item_cost row, including which cost set and effective date range is absent, and suggest whether a Cost Rollup or a manual Item Costs entry is the right fix for that item type - turning a costing error that normally needs a controller or planner to interpret into a direct, sourced answer.
Frequently asked questions
Does this error mean the item has never been costed at all?
Not necessarily. It can also mean a cost record exists but is not effective as of the transaction date, or exists for a different cost type or site than the one the transaction needs, so check effective dates and cost type before assuming there is no record at all.
Can I just post the transaction at zero cost to unblock it?
SyteLine generally will not let you post at zero for a standard-costed item because it distorts inventory valuation and variance reporting; the correct fix is to establish the cost record first, not to bypass the check.
Why did the error only appear after I copied the item to a new site?
Copy Item Sites replicates BOM, routing, and item-site setup but cost records for the new site are not always guaranteed to carry over identically, so a rollup or manual cost entry is often still needed after the copy.
Does a multi-level cost rollup fix components automatically?
Yes, a multi-level rollup will recursively cost subassemblies and purchased components as part of rolling up the parent, which is usually the safer option versus rolling up a single level and hoping components are already costed.
Related
How to Run a Cost Rollup in SyteLine
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.
Error fixSyteLine error: invalid site or item not valid at this site
SyteLine is a multi-site system where items, warehouses, and most master data are site-specific by design. This error means either the item has never been extended to the site you are transacting in, your user login does not have access to that site, or the current site context on the form does not match the site of the referenced record. Add the item to the site via Item Sites, or correct the user's site security, and the error clears.
Error fixFixing SyteLine's 'transaction out of balance' GL posting error
This posting error means SyteLine tried to create a general ledger journal entry where total debits do not equal total credits, which the GL will not accept. The most frequent causes are a missing or misconfigured account in the automatic account determination setup (COA mapping), currency rounding on multi-currency transactions, or a source transaction (inventory, job cost, AP/AR) that only partially calculated its cost or tax components before posting.
How-toHow 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.
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.
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.