Infor LN & BaanFree referencePDF, Excel, Word exportInfor LNAll Infor LN and Baan tools

Infor LN Item Master Tables Reference: tcibd001, tdisa001, tdipu001 and More

LN splits one item over many tables: a general record in tcibd001 plus separate records for sales, purchase, ordering, warehousing and production. This reference shows which LN 10.x table and session holds each attribute and how to join them.

Download:

Table	Description	Session that maintains it	Key fields	Important columns	Typical join	Notes
tcibd001	Items - general	tcibd0501m000 Items	item	dsca description, kitm item type, citg item group, cuni inventory unit, ctyp product type, cpcl product class, cmnf manufacturer, ltct lot controlled, seri serialized, wght weight, cwun weight unit	Parent of every other item table on item	Item code includes the project segment, so standard items carry leading spaces.
tcibd003	Conversion factors	tcibd0103m000 Conversion Factors	item, citg, unit, basu	unit unit, basu base unit, conv conversion factor, rpow raise 10 to the power, appr approved	tcibd003.item = tcibd001.item	Holds item-specific and item-group-level unit conversions; blank item means the factor applies more widely.
tcibd004	Item codes by item code system	Item code system sessions in tcibd	citt, bpid, aitc	citt item code system, bpid business partner, aitc external item code, aitd description, item	tcibd004.item = tcibd001.item	Customer and supplier item numbers; tdsls401.citt and citm reference this.
tcibd200	Item - ordering	tcibd2100m000 Item - Ordering	item	omth order method, cwar warehouse, mioq minimum order quantity, ecoq economic order quantity, reop reorder point, sfst safety stock, sftm safety time, cplb planner	tcibd200.item = tcibd001.item	Defaults come from tcibd2101m000 Item - Ordering Defaults.
tdisa001	Items - sales	tdisa0501m000 Items - Sales	item	cuqs sales unit, cups sales price unit, pris sales price, ccur sales currency, cpgs sales price group, csgs sales statistics group, cwar warehouse, sfsi site, qimo minimum order quantity, cvat tax code	tdisa001.item = tcibd001.item	Defaults from tdisa0502m000 Items - Sales Defaults.
tdisa010	Items - sales business partner	tdisa0510m000 Items - Sales Business Partner	item, ofbp, stbp, efdt	citg item group, ofbp sold-to BP, stbp ship-to BP, efdt effective date, exdt expiry date, cuqs sales unit, qimo minimum order quantity, blck blocked, cwar warehouse	tdisa010.item = tcibd001.item; tdisa010.ofbp = tccom110.ofbp	Customer-specific item settings; can also be defined for an item group.
tdipu001	Items - purchase	tdipu0101m000 Items - Purchase	item	otbp default buy-from BP, buyr buyer, cuqp purchase unit, cupp purchase price unit, prip purchase price, ccur purchase currency, cpgp purchase price group, csgp purchase statistics group, cwar warehouse, suti supply time	tdipu001.item = tcibd001.item	Defaults from tdipu0102m000 Items - Purchase Defaults.
tdipu010	Item - purchase business partner	tdipu0110m000 Item - Purchase Business Partner	item, otbp, sfbp, efdt	otbp buy-from BP, sfbp ship-from BP, efdt effective date, exdt expiry date, ibps status, pref preferred, qimi minimum, qiec economic order quantity, suti supply time, qual inspection	tdipu010.item = tcibd001.item; tdipu010.otbp = tccom120.otbp	Approved-supplier style data per item and supplier.
whwmd400	Items - warehousing	whwmd4500m000 Items - Warehousing	item	locc location controlled, niwo allow negative inventory, obpr outbound method, linv lots in inventory, lttr lot tracking, sinv serials in inventory, pkdf package definition, hama hazardous material	whwmd400.item = tcibd001.item	Item-level warehousing settings that apply in every warehouse.
whwmd210	Item data by warehouse	whwmd2510m000 Item Data by Warehouse	cwar, item	iwhs status, valm inventory valuation method, omth order method, sups supply system, reop reorder point, sfwh supply from warehouse, supw supply warehouse, niwo allow negative inventory	whwmd210.item = tcibd001.item; whwmd210.cwar = tcmcs003.cwar	uidt Use Item Ordering Data decides whether tcibd200 values apply.
whwmd215	Warehouse - item inventory	whwmd2515m000 Warehouse - Item Inventory	cwar, item	qhnd on hand, qall allocated, qord on order, qblk blocked, qbpl blocked for planning	whwmd215.item = tcibd001.item	Totals per warehouse; location and lot detail is in whinr140.
tiipd001	Item - production	tiipd0101m000 Item - Production	item	scpf scrap percentage, scpq scrap quantity, cpha phantom, runi routing unit, bfep backflush materials, bfhr backflush hours, rgrp routing group, sfpl shop floor planner	tiipd001.item = tcibd001.item	Only manufactured items need a row.
tcmcs023	Item groups	tcmcs0123m000 Item Groups	citg	citg item group, dsca description, ccur currency, spec costs to be specified	tcibd001.citg = tcmcs023.citg	Item groups also drive defaults and many tcibd003 and tdisa010 entries.
tcmcs001	Units	tcmcs0101m000 Units	cuni	cuni unit, icun ISO code, tccu physical quantity, crnd rounding factor	tcibd001.cuni = tcmcs001.cuni	Every unit field on item tables (cuni, cuqs, cuqp, cwun) references this.
tcmcs024	Price groups	tcmcs0124m000 Price Groups	cprg	cprg price group, dsca description	tdisa001.cpgs = tcmcs024.cprg; tdipu001.cpgp = tcmcs024.cprg	Shared by sales and purchase price groups.
tcmcs044	Statistical groups	tcmcs0144m000 Statistical Groups	csgp	csgp statistical group, dsca description	tdisa001.csgs = tcmcs044.csgp; tdipu001.csgp = tcmcs044.csgp	Used to roll up sales and purchase statistics.
tcmcs060	Manufacturers	tcmcs0160m000 Manufacturers	cmnf	cmnf manufacturer, otbp buy-from BP, ccty country, indt effective date, exdt expiry date	tcibd001.cmnf = tcmcs060.cmnf	Manufacturer part numbers per item are maintained in the purchase manufacturer item data.

Physical names add t and the company number (ttcibd001100). SQL columns carry t_ on SQL Server and t$ on Oracle. Codes and fields were checked against the LN 10.x online help for each session listed. Site-specific item data and Feature Pack fields differ by release: confirm in your data dictionary before you rely on a column.

Want an item master gap report from your LN data?

We can run a read-only check of missing sales, purchase and warehouse item records and send you the list.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

Where each attribute lives

Start from tcibd001 (session tcibd0501m000): item type, item group, inventory unit, product type, lot and serial flags. Commercial data is per business process. Sales unit and sales price are in tdisa001 (tdisa0501m000), purchase unit, buyer and purchase price in tdipu001 (tdipu0101m000). Order method, order quantities and safety stock are in tcibd200 (tcibd2100m000) at item level and in whwmd210 (whwmd2510m000) per warehouse. Production settings such as phantom, scrap and backflush flags are in tiipd001 (tiipd0101m000). Customer- and supplier-specific overrides sit in tdisa010 and tdipu010.

Worked example: one row per item for a master data audit

Select item, dsca, kitm, citg and cuni from tcibd001, then left join tdisa001, tdipu001 and tiipd001 on item. A missing tdisa001 row for a sold item, or a missing tdipu001 row for a purchased item, is a common reason why order entry falls back to defaults or fails. Add tcmcs023 on citg for the group description. For warehouse-level checks, left join whwmd210 on item and cwar and flag rows where iwhs is not active or where uidt says the item ordering data is used but tcibd200 is incomplete.

Left join, never inner join, so gaps stay visible
Pad or trim item codes consistently
Read enumerations through their domains

Version differences and gotchas

Baan IV and Baan 5 kept the item in tiitm001; LN moved the general item to tcibd001 and split sales and purchase data into tdisa001 and tdipu001. Interfaces built on Baan IV need remapping, not just a rename. In LN, the same item code with a project segment is a different item, so project-pegged items appear as separate rows. Default sessions such as tdisa0502m000 and tdipu0102m000 only fill new records; changing a default does not update existing items. Unit conversions may be item-specific or group-level in tcibd003, so check both.

How to check an item attribute in the system

Open the item in Items (tcibd0501m000) and use the specific menu to jump to the sales, purchase, production or warehousing data: each opens the session listed in this table for the same item. Field help on any field shows the table and field name, which is the quickest way to confirm a column before you put it in a query or interface mapping. For a bulk check, compare row counts: every item with a sales role should have a tdisa001 row and every purchased item a tdipu001 row. Differences point to items created by an import that skipped a step.

Frequently Asked Questions

What is the Infor LN items sales session?

Items - Sales is session tdisa0501m000 and it maintains table tdisa001. It holds the sales unit, sales price and price unit, sales currency, sales price group, statistics group, default warehouse and site, minimum order quantity and tax code. Defaults for new records come from Items - Sales Defaults (tdisa0502m000).

Which session maintains item data by business partner?

For customers, Items - Sales Business Partner (tdisa0510m000) maintains tdisa010, keyed by item, sold-to and ship-to BP and effective date. For suppliers, Item - Purchase Business Partner (tdipu0110m000) maintains tdipu010, keyed by item, buy-from and ship-from BP and effective date. Both can also be set for an item group.

Where is the item group stored in Infor LN?

The item group code is the field citg on tcibd001. The list of item groups and their descriptions is table tcmcs023, maintained in Item Groups (tcmcs0123m000). Item groups are also used as a key in conversion factors and in item by business partner records, so a group can carry settings for many items.

Where are purchase settings by warehouse kept?

Purchase commercial data is in tdipu001 and per supplier in tdipu010. Warehouse-level supply settings such as order method, supply system, reorder point and supply warehouse are in whwmd210, Item Data by Warehouse (whwmd2510m000). Its Use Item Ordering Data field decides whether the item-level values in tcibd200 apply instead.

If you want planners and buyers to ask LN about item settings in plain English on your own servers, we can add a private AI layer that reads these tables.

Talk to an Expert Explore More Free Tools