SyteLine error: invalid site or item not valid at this site
SyteLine invalid site error item not valid at this site
Also searched as
- SyteLine item does not exist at site
- invalid site for warehouse SyteLine
- SyteLine cannot select site error
Short answer
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.
Applies to: SyteLine 8.x, 9.x, CloudSuite Industrial (multi-site configurations)
Diagnose and fix the invalid site error
- 1Note the exact item number, warehouse, and site shown in the error, or the current site indicator in the SyteLine title bar / site selector.
- 2Open Items and Item Sites (or Item Sites specifically) and check whether the item has a row for the target site.
- 3If missing, use Copy Item Sites or manually add the item to the site with the correct warehouse, planner, and costing setup.
- 4Check Users (or the user's security profile) for the Sites they are authorized to access - the site must be listed there before it appears as selectable.
- 5Confirm the warehouse referenced belongs to the same site as the transaction (a warehouse cannot be cross-site in SyteLine).
- 6If the error appears during an order entry or transfer, verify the customer or supplier's default site matches the site you are transacting from, or explicitly override it on the line.
- 7For integration-driven records (EDI, ION BODs), check the inbound mapping is sending the correct site code, not defaulting to the sender's home site.
Why SyteLine enforces site scoping
Multi-site SyteLine partitions inventory, costing, and much of production data by site so that separate plants or distribution centers can run independent MRP, costing, and general ledger while optionally sharing item masters. An item record (co_item) is global at the description level, but its site-specific attributes - standard cost, planning parameters, default warehouse - live in a separate Item Sites (co_item_whse or itemsite-equivalent) record per site. If that site-specific row does not exist, any transaction that needs it fails fast rather than silently defaulting.
The three places to check
Item-site existence is the most common cause: someone created a new item at Site 100 and tried to transact it at Site 200 without running Copy Item Sites or manually adding it. User site access is the second: SyteLine security lets you restrict which sites a login can even see, so a valid item-site combination can still throw the error for a user who is not authorized for that site.
The third is site-context mismatch on the form itself - some SyteLine forms carry an implicit current site from the user's default or from a parent record (like a job or order header), and referencing an item or warehouse from a different site within that same transaction triggers the error even if both site-item combinations individually exist.
Copying items between sites correctly
Use the Copy Item Sites utility rather than re-keying item-site records by hand when rolling a new item out to additional plants; it preserves BOM, routing, and costing structures consistently. After copying, re-check standard cost and lead time fields, since defaults copied from the source site are not always correct for the destination site.
Common pitfalls
- !Adding an item at a new site without also setting up its costing (standard cost or average cost basis) will let the item-site error clear but cause a downstream costing error on the first transaction.
- !Restricting user site access is a legitimate security control - do not just add every user to every site to make errors go away without checking whether that access is appropriate.
- !Warehouses are strictly single-site in SyteLine; do not try to reuse a warehouse code across sites expecting it to behave like a shared location.
- !EDI and ION integration mappings that hardcode a single site will fail for every order routed to a different plant - map site dynamically from the incoming document.
- !Copy Item Sites does not automatically update lead times or safety stock for the new site's actual supply chain - review planning parameters after copying.
How an ERP-grounded AI assistant handles this
ERPray, asked 'why can't I select site 200 for item 4400-100', can check the item-site table, the user's site security profile, and the warehouse-to-site mapping in one grounded pass and state precisely which of the three is missing, instead of the user manually paging through Item Sites, Users, and Warehouses forms to rule each one out.
Frequently asked questions
Do I need to set up every item at every site?
No. Only items that are actually stocked, purchased, or manufactured at a given site need an item-site record there. Global item-only sites (pure sales offices, for example) typically only need order-entry-relevant items extended to them.
Can a user be restricted to a subset of sites?
Yes, SyteLine security lets an administrator limit which sites appear in a user's site selector and which site-scoped data they can transact against, which is common in shared multi-plant CloudSuite Industrial environments.
Why does this error only appear on some forms and not others?
Forms that do not require site-specific data (some reporting or global setup screens) will not check site scoping the same way transactional forms do, since only transactional and inventory-affecting records actually need an item-site record.
Does Copy Item Sites copy the BOM and routing too?
Yes, Copy Item Sites is designed to replicate the structural data (BOM, routing) along with the item-site record so the new site has a working manufacturing definition, though costs and lead times still need review.
Related
SyteLine error: this row has been modified by another user since you began editing it
This is SyteLine's IDO optimistic concurrency check. It fires when the row's timestamp column (usually ts_prefix or a similar rowversion field) on the database no longer matches the value the client loaded, meaning another session, a background job, or an integration already saved a change. Refresh the record and reapply your edit; if it recurs constantly on one record, look for a duplicate integration process or a stuck lock rather than user contention.
AdvancedHow to Set Up Multi-Site Configuration in SyteLine
SyteLine supports multiple manufacturing or distribution sites either as separate Site records within one shared database, or as fully separate databases linked through intersite transactions and, in CloudSuite Industrial, ION. Getting the site model right up front, shared versus separate master data, intersite transfer setup, avoids a painful data migration later.
Error fixSyteLine error: no cost record exists for this item at this site
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.
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.
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.