How-toInfor LNCommon Data / Items

Infor LN item sales session, item purchase session and site data: where each lives

Question
infor ln item sales session

Also searched as

  • infor ln session item purchase site
  • site session table infor
  • infor ln item sales data table tdisa001

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.

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.

How to find and maintain item sales, purchase and site data

  1. 1Open the Items - General session (search 'Items - General' in the LN menu or use the session code search) and select the item.
  2. 2From 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.
  3. 3Choose the Purchase data option to open Items - Purchase. Supplier-specific conditions are kept separately in purchase price books and item-by-business-partner data.
  4. 4Open 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.
  5. 5Check that the Sites (enterprise units of type site) are defined and linked to the company before you maintain site-level data.
  6. 6To audit, query the tables directly with a read-only tool, or use the table's Display Table Contents function in LN.

The item master is a family of tables, not one

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.

-- read-only inspection, names as in the standard data model
SELECT t_item, t_dsca FROM ttcibd001<company>;
SELECT t_item, t_cpgp FROM ttdisa001<company>;
SELECT t_item, t_cpgp FROM ttdipu001<company>;

Why site matters: item-by-site records

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

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.

Try it here, free

Infor LN Session Test Script Template

Open full tool

UAT test script for an LN process or session with prerequisites, numbered steps, expected results and tester sign-off.

Common 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.

How an ERP-grounded AI assistant handles this

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.

Frequently asked questions

What is the item sales table in Infor LN?

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?

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?

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?

Use standard conversion or data exchange tooling so validation runs. Direct SQL updates skip DAL checks and are not supported for production data.

Related

How-to

How to Create an Infor LN User from a User Template and Copy Authorizations

In Infor LN you create a user in User Data, link it to a user template that carries defaults such as language, printer, company and package combination, and assign roles that grant session and table authorizations. Copying authorizations from an existing user is possible but is the least safe approach compared with role-based assignment.

Error fix

Infor LN DAL Out of Sync After a Custom Field: Cause and Fix

Infor LN throws a DAL, or table, out of sync error, or simply drops a new custom field silently, when a table's dictionary definition is changed but the generated DAL and dependent forms are not regenerated afterward. Running the standard sequence, table compile, DAL generation, then session/form compile, in Tools > Development after every dictionary change resolves it. Skipping any one of the three steps is what causes the mismatch.

How-to

How to calculate item cost prices in Infor LN

Infor LN calculates an item's cost price by rolling up material, labor, machine, subcontract and overhead costs defined against cost components, using the item's bill of material and routing as the calculation base for manufactured items and purchase price for bought items. The calculation can run in simulation mode to preview the result or in update mode to actually change the item's standard cost, which then drives inventory valuation and variance reporting going forward.

How-to

How to process a sales order to invoice in Infor LN

In Infor LN a sales order moves from order entry to cash through four linked steps: create and approve the Sales Orders session, release the order lines to Warehousing so a warehouse order is generated, confirm the outbound shipment, and then run the invoicing session that composes and posts the sales invoice to Financials. Each step hands off through an integration document, so a stuck invoice almost always traces back to a missing or unconfirmed step earlier in the chain.

Error fix

Infor LN bshell Process Stuck at 100% CPU: How to Diagnose and Fix It

A bshell process pinned at 100% CPU on the Infor LN application server almost always means one session is stuck in a 4GL loop, scanning an unindexed table, or waiting on a database lock. End the session from the Sessions Monitor first, then kill the OS process only if that fails, and check for a blocking database transaction before assuming it is a bug.

Error fix

Infor LN Not Authorized to Run This Session: How to Fix It

Infor LN refuses to open a session with a not authorized message when the logged-in user's assigned role does not include that session, or when the session is blocked for the company they are logged into. Grant the session through Common > Authorization Management > Roles, or check the user's role and company context, and the session opens on retry. In most cases this is a permissions configuration issue, not a bug.

AI for ERP

AI for Infor LN: Sessions, BODs, and Engineer-to-Order Work

Add grounded AI to Infor LN 10.x or CloudSuite: natural-language answers over sessions and BODs, agents for project and engineer-to-order work, on-prem options.

AI for ERP

AI for Infor LN Purchasing: Faster Exception Handling on Orders, Schedules and Suppliers

AI for Infor LN purchasing: triage late orders and schedules, answer supplier performance questions, and draft POs with buyer approval. On-prem option.

Stuck on Infor LN?

Talk to engineers who work inside Infor LN every week, and who build private AI that answers these questions from your own ERP data.

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

Guides

Integrations