# SyteLine error: no cost record exists for this item at this site > Source: https://netray.co/erp-help/syteline-no-cost-record-error > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## 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. ## Kind error ## System syteline ## Erp Infor SyteLine (CloudSuite Industrial) ## Module Costing / Standard Costs ## Query SyteLine no standard cost exists for this item error ## Alternate Queries - SyteLine cost record not found error - syteline item has no cost element error - syteline transaction fails missing cost ## Applies To SyteLine 8.x, 9.x, CloudSuite Industrial (standard costing and average costing environments) ## Steps ### Fix a missing cost record **Items:** - Identify the item, site, and cost type (frozen standard, current standard, or average) referenced in the error. - Open Item Costs (or Costed Item BOMs) for that item-site and check whether a cost record exists for the required cost set. - If 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. - If 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. - Check the cost's effective date - a cost record dated after the transaction date will not satisfy a transaction posted earlier. - For 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. - Reprocess the failed transaction (job transaction, PO receipt, inventory adjustment) once the cost record is confirmed. ## Sections ### Why every transaction needs a cost **Body:** 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 **Body:** 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. **Code:** -- 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 **Body:** 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. ## 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. ## Ai Angle 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. ## Faq ### Does this error mean the item has never been costed at all? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms syteline no cost record error, syteline missing standard cost, syteline cost rollup error, syteline item cost not found, syteline effective dated cost, syteline average cost missing, syteline job transaction cost error, csi standard costing error --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json