Infor LN & BaanFree referencePDF, Excel, Word exportInfor LN / Baan

Infor LN Table List (Baan ERP Tables by Package)

Infor LN, and Baan before it, names every table with a package code, a module code and a three digit number. This list gives the commonly used tables by package, with key fields and the Baan IV equivalents where they differ.

Download:

Table	Package	Description	Key fields	Notes
tccom100	tc Common	Business partners	bpid	Parent of customer and supplier roles. LN only; Baan IV used tccom010 and tccom020.
tccom130	tc Common	Addresses	cadr	Referenced by business partners, warehouses, companies and orders.
tccom010	tc Common	Customers (Baan IV and 5)	cuno	Replaced by business partner model in LN.
tccom020	tc Common	Suppliers (Baan IV and 5)	suno	Replaced by business partner model in LN.
tcibd001	tc Common	Items general	item	Central item master in LN. Item code is padded with leading spaces in the project segment.
tiitm001	ti Manufacturing	Items (Baan IV and 5)	item	Predecessor of tcibd001 in older releases.
tcmcs003	tc Common	Warehouses	cwar	Linked to an address and an enterprise unit.
tcmcs023	tc Common	Item groups	citg	Used for grouping items for planning, costing and reporting.
tcmcs080	tc Common	Carriers and freight forwarders	cfrw	Referenced by shipments and orders.
tcemm030	tc Common	Enterprise units	eunt	Part of enterprise modeling; links planning, finance and warehouses.
tdsls400	td Distribution	Sales orders	orno	Header. Order type comes from tdsls094.
tdsls401	td Distribution	Sales order lines	orno, pono, sqnb	Line quantities, prices and status.
tdsls406	td Distribution	Sales order line deliveries	orno, pono, sqnb	Delivery-level data for a line. Confirm field set in your release.
tdsls094	td Distribution	Sales order types	sotp	Controls order handling, such as which activities run.
tdsls040	td Distribution	Sales orders (Baan IV and 5)	orno	Older header table. Lines are in tdsls041.
tdsls041	td Distribution	Sales order lines (Baan IV and 5)	orno, pono	Older line table.
tdpur400	td Distribution	Purchase orders	orno	Header. Order type from tdpur094.
tdpur401	td Distribution	Purchase order lines	orno, pono, sqnb	Line item, quantity, price and status.
tdpur094	td Distribution	Purchase order types	potp	Controls purchase order processing.
tdpur040	td Distribution	Purchase orders (Baan IV and 5)	orno	Older header; lines in tdpur041.
tdpur041	td Distribution	Purchase order lines (Baan IV and 5)	orno, pono	Older line table.
whinh200	wh Warehousing	Warehouse orders	oorg, orno	Header for inbound, outbound and transfer warehouse orders.
whinh210	wh Warehousing	Warehouse order lines	oorg, orno, pono, seqn	Lines link back to source order and item.
whwmd215	wh Warehousing	Item inventory by warehouse	item, cwar	On-hand and allocated quantities. Verify column names for your release.
tisfc001	ti Manufacturing	Production orders	pdno	Status field drives the shop floor control lifecycle.
tibom010	ti Manufacturing	Bill of material lines	mitm, pono	Parent item and position. Baan IV and 5 structure.
tfacr200	tf Finance	Accounts receivable invoices and transactions	ttyp, ninv	Open and paid customer documents.
tfacp200	tf Finance	Accounts payable invoices and transactions	ttyp, ninv	Open and paid supplier documents.
tfgld410	tf Finance	General ledger transaction history	year, ptyp, ttyp, docn, lino	Posted journal lines. Column set varies by release.
ttaad200	tt Tools	Companies	ccmp	Company numbers used as the suffix on every physical table.

Keys and column names can vary between Baan IV, Baan 5 and LN releases, and customizations add fields. Always check the data dictionary in your own VRC. Physical table names in the database add a leading t and the company number, so tdsls400 in company 100 is ttdsls400100.

Planning reporting or AI over Infor LN or Baan data?

Optional: share your release and database and we will suggest a read-only approach that stays on your network. The list is free without it.

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

How the Baan and LN table naming works

A table name such as tdsls400 breaks down into a two letter package (td for distribution), a three letter module (sls for sales) and a three digit table number (400). In the database, the physical table gets a leading t and a three digit company suffix, so tdsls400 in company 100 becomes ttdsls400100. Fields carry the table prefix in SQL, for example t_orno. That is why a query for every sales order in all companies has to loop over the company suffixes, or use a union.

How to use the list

Filter by package to see only distribution, finance, warehousing or common tables, or type a business word such as invoice or warehouse. The notes column flags where Baan IV and 5 used a different table than LN. Export the filtered rows to Excel to hand to a migration analyst or report writer. For session names that open these tables, use the session code reference linked below.

tc holds shared master data such as business partners and items
td holds sales and purchase documents
ti covers manufacturing; tf covers finance; wh covers warehousing
tt holds the tools and data dictionary layer

Relationships worth knowing

Sales and purchase orders join header to line on the order number and then position. Warehouse orders link back to their source order. Items are keyed by item code, which in LN may include a project segment padded with spaces, so comparisons from outside the system must handle that. Finance documents use a transaction type and document number pair. Always confirm joins against the data dictionary rather than assuming, since customization and release differences are common.

Common mistakes when querying LN tables

Do not run heavy ad hoc queries on the production database during business hours. Do not forget the company suffix, or you will read the wrong company or no data at all. Enumerated fields store a number, with the label in the domain definition, so a status shows as an integer in SQL. Finally, avoid writing directly to tables; use the application, a DAL or a supported integration so hooks and validations run.

Frequently Asked Questions

How are Baan and Infor LN tables named?

A table name is package, module and number, such as tdsls400. The two letter package and three letter module identify the area, and the three digits identify the table. The database adds a leading t and a company number suffix.

What is the Infor LN customer and supplier table?

LN uses business partners in tccom100 with role records for sold-to, ship-to and similar roles. Baan IV and 5 used tccom010 for customers and tccom020 for suppliers. Check your release before writing joins.

Where is the sales order table in Baan?

In LN, sales order headers are in tdsls400 and lines in tdsls401. In Baan IV and 5 they are tdsls040 and tdsls041. Add the company number to get the physical table name.

Can I read Infor LN tables directly with SQL?

Often yes for read-only reporting, depending on the database and your policy, but check the data dictionary, avoid peak hours and never write directly. Use the application or integration layer for changes.

If you want to ask an LN system questions in plain language from your own servers, Netray builds read-only, on-prem AI layers over LN data. The table list works on its own.

Talk to an Expert Explore More Free Tools