# SyteLine error: invalid site or item not valid at this site > Source: https://netray.co/erp-help/syteline-invalid-site-error-fix > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## 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. ## Kind error ## System syteline ## Erp Infor SyteLine (CloudSuite Industrial) ## Module Multi-Site / Item Sites ## Query SyteLine invalid site error item not valid at this site ## Alternate Queries - SyteLine item does not exist at site - invalid site for warehouse SyteLine - SyteLine cannot select site error ## Applies To SyteLine 8.x, 9.x, CloudSuite Industrial (multi-site configurations) ## Steps ### Diagnose and fix the invalid site error **Items:** - Note the exact item number, warehouse, and site shown in the error, or the current site indicator in the SyteLine title bar / site selector. - Open Items and Item Sites (or Item Sites specifically) and check whether the item has a row for the target site. - If missing, use Copy Item Sites or manually add the item to the site with the correct warehouse, planner, and costing setup. - Check 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. - Confirm the warehouse referenced belongs to the same site as the transaction (a warehouse cannot be cross-site in SyteLine). - If 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. - For integration-driven records (EDI, ION BODs), check the inbound mapping is sending the correct site code, not defaulting to the sender's home site. ## Sections ### Why SyteLine enforces site scoping **Body:** 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 **Body:** 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 **Body:** 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. ## 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. ## Ai Angle 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. ## Faq ### Do I need to set up every item at every site? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms syteline invalid site error, syteline item not valid at this site, syteline item sites setup, copy item sites syteline, syteline multi-site warehouse error, syteline user site access, syteline site security, syteline warehouse invalid site --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json