# Infor LN item sales session, item purchase session and site data: where each lives > Source: https://netray.co/erp-help/infor-ln-item-sales-purchase-site-sessions-tables > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer In Infor LN the item master is split by business function. General data sits in the Items - General table (tcibd001), sales data in Item - Sales (tdisa001) and purchase data in Item - Purchase (tdipu001). Site-dependent data such as ordering and planning parameters is held per item and site, so one item can behave differently in each site. ## Kind how-to ## System infor-ln ## Erp Infor LN ## Module Common Data / Items ## Query infor ln item sales session ## Alternate Queries - infor ln session item purchase site - site session table infor - infor ln item sales data table tdisa001 ## Applies To Infor LN 10.x and Baan 5.x style data model. Session codes differ between versions, so confirm with the session search before scripting. ## Steps ### How to find and maintain item sales, purchase and site data **Items:** - Open the Items - General session (search 'Items - General' in the LN menu or use the session code search) and select the item. - From the item's specific menu, choose the Sales data option to open the Items - Sales session for the same item. A record is created here only if the item is sold. - Choose the Purchase data option to open Items - Purchase. Supplier-specific conditions are kept separately in purchase price books and item-by-business-partner data. - Open the item's ordering data by site (Item - Ordering and the by-site ordering sessions) to set order policy, lot sizes and planning parameters for each site. - Check that the Sites (enterprise units of type site) are defined and linked to the company before you maintain site-level data. - To audit, query the tables directly with a read-only tool, or use the table's Display Table Contents function in LN. ## Sections ### The item master is a family of tables, not one **Body:** A common confusion is looking for one 'item master' screen with everything on it. LN follows a layered model. The Items - General table (tcibd001) holds identity: item code, description, item type, unit of measure and the status flags. Everything function-specific hangs off that key. Sales data (tdisa001) carries sales-related attributes such as sales unit, price and discount groups, and delivery defaults. Purchase data (tdipu001) holds purchase unit, purchase price group and procurement defaults. Because these are separate tables with separate session sets, a user can have authorization for one and not the other. **Code:** - -- read-only inspection, names as in the standard data model - SELECT t_item, t_dsca FROM ttcibd001; - SELECT t_item, t_cpgp FROM ttdisa001; - SELECT t_item, t_cpgp FROM ttdipu001; ### Why site matters: item-by-site records **Body:** Multi-site LN implementations store planning and ordering parameters per item and per site. The same item can use a lot-for-lot policy in one plant and a fixed order quantity in another. This is why changing a value in one session seems to have no effect: you may have edited the general record while the site record overrides it. Sites themselves are enterprise units, defined in the Common Data enterprise structure. If a site is not linked to the right company or financial company, item-by-site records either cannot be created or fail validation when orders are entered. ### Authorizations and data creation order **Body:** Create the item in general first, then complete the function-specific records. Order entry sessions generally refuse an item that has no sales data or no data for the relevant site, and the message you see names the missing record. Controlling who may create sales or purchase data through session authorizations keeps item governance clean. For mass changes, use the standard conversion or exchange schemes rather than SQL updates. Direct updates bypass DAL validation and can leave sales and general data inconsistent. ## Pitfalls - Editing the general item and expecting sales or purchase behavior to change, when a site-level or function-level record overrides it. - Updating item tables with SQL, which bypasses DAL rules and audit. - Assuming session codes are identical across LN versions and scripts breaking after an upgrade. - Forgetting that purchase prices for a supplier live in price books, not only on the item. - Creating items in one company and expecting them in another without a data-sharing or mapping setup. ## Ai Angle With an on-prem AI layer that can read the LN tables, a planner asks 'which items have sales data but no purchase data in site X' and gets the query, the rows and the sessions to fix them. ERPray is read-only by default and respects LN roles, so the question runs inside your own network and cannot update the item master. ## Faq ### What is the item sales table in Infor LN? **Answer:** The standard table is Item - Sales, tdisa001. It extends the general item record in tcibd001 with sales-specific attributes. Table and session names can vary slightly by version and by customization, so verify in your own environment using the table definitions session before relying on a name in a script. ### Is there one session for item sales and purchase together? **Answer:** No. Sales and purchase data are maintained in separate sessions, reached from the general item through its specific menu. This is by design so that authorizations and ownership can differ between sales and procurement teams. ### How do I know which site an item parameter applies to? **Answer:** Site-level sessions show the site code in the key. If you see a field in the general item but the behavior differs, open the corresponding by-site session and compare. The by-site value wins for planning and ordering. ### Can I bulk update item sales data? **Answer:** Use standard conversion or data exchange tooling so validation runs. Direct SQL updates skip DAL checks and are not supported for production data. ## Search terms infor ln item sales session, infor ln item purchase session, infor ln site session, tcibd001, tdisa001, tdipu001, infor ln item by site, infor ln item master --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json