# Infor LN Table List (Baan ERP Tables by Package) > Source: https://netray.co/tools/infor-ln-baan-table-list-by-package-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Filterable list of commonly used Infor LN and Baan tables by package, with the naming convention, key fields and where a Baan IV table differs from LN. ## Category infor-ln ## Erp Infor LN / Baan ## Audience - LN developer - Data migration analyst - BI report writer ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Table **Key:** table **Type:** text #### Package **Key:** package **Type:** select **Options:** - tc Common - td Distribution - ti Manufacturing - tf Finance - wh Warehousing - tt Tools #### Description **Key:** description **Type:** text #### Key fields **Key:** keys **Type:** text #### Notes **Key:** notes **Type:** text **Rows:** **Table:** tccom100 **Package:** tc Common **Description:** Business partners **Keys:** bpid **Notes:** Parent of customer and supplier roles. LN only; Baan IV used tccom010 and tccom020. **Table:** tccom130 **Package:** tc Common **Description:** Addresses **Keys:** cadr **Notes:** Referenced by business partners, warehouses, companies and orders. **Table:** tccom010 **Package:** tc Common **Description:** Customers (Baan IV and 5) **Keys:** cuno **Notes:** Replaced by business partner model in LN. **Table:** tccom020 **Package:** tc Common **Description:** Suppliers (Baan IV and 5) **Keys:** suno **Notes:** Replaced by business partner model in LN. **Table:** tcibd001 **Package:** tc Common **Description:** Items general **Keys:** item **Notes:** Central item master in LN. Item code is padded with leading spaces in the project segment. **Table:** tiitm001 **Package:** ti Manufacturing **Description:** Items (Baan IV and 5) **Keys:** item **Notes:** Predecessor of tcibd001 in older releases. **Table:** tcmcs003 **Package:** tc Common **Description:** Warehouses **Keys:** cwar **Notes:** Linked to an address and an enterprise unit. **Table:** tcmcs023 **Package:** tc Common **Description:** Item groups **Keys:** citg **Notes:** Used for grouping items for planning, costing and reporting. **Table:** tcmcs080 **Package:** tc Common **Description:** Carriers and freight forwarders **Keys:** cfrw **Notes:** Referenced by shipments and orders. **Table:** tcemm030 **Package:** tc Common **Description:** Enterprise units **Keys:** eunt **Notes:** Part of enterprise modeling; links planning, finance and warehouses. **Table:** tdsls400 **Package:** td Distribution **Description:** Sales orders **Keys:** orno **Notes:** Header. Order type comes from tdsls094. **Table:** tdsls401 **Package:** td Distribution **Description:** Sales order lines **Keys:** orno, pono, sqnb **Notes:** Line quantities, prices and status. **Table:** tdsls406 **Package:** td Distribution **Description:** Sales order line deliveries **Keys:** orno, pono, sqnb **Notes:** Delivery-level data for a line. Confirm field set in your release. **Table:** tdsls094 **Package:** td Distribution **Description:** Sales order types **Keys:** sotp **Notes:** Controls order handling, such as which activities run. **Table:** tdsls040 **Package:** td Distribution **Description:** Sales orders (Baan IV and 5) **Keys:** orno **Notes:** Older header table. Lines are in tdsls041. **Table:** tdsls041 **Package:** td Distribution **Description:** Sales order lines (Baan IV and 5) **Keys:** orno, pono **Notes:** Older line table. **Table:** tdpur400 **Package:** td Distribution **Description:** Purchase orders **Keys:** orno **Notes:** Header. Order type from tdpur094. **Table:** tdpur401 **Package:** td Distribution **Description:** Purchase order lines **Keys:** orno, pono, sqnb **Notes:** Line item, quantity, price and status. **Table:** tdpur094 **Package:** td Distribution **Description:** Purchase order types **Keys:** potp **Notes:** Controls purchase order processing. **Table:** tdpur040 **Package:** td Distribution **Description:** Purchase orders (Baan IV and 5) **Keys:** orno **Notes:** Older header; lines in tdpur041. **Table:** tdpur041 **Package:** td Distribution **Description:** Purchase order lines (Baan IV and 5) **Keys:** orno, pono **Notes:** Older line table. **Table:** whinh200 **Package:** wh Warehousing **Description:** Warehouse orders **Keys:** oorg, orno **Notes:** Header for inbound, outbound and transfer warehouse orders. **Table:** whinh210 **Package:** wh Warehousing **Description:** Warehouse order lines **Keys:** oorg, orno, pono, seqn **Notes:** Lines link back to source order and item. **Table:** whwmd215 **Package:** wh Warehousing **Description:** Item inventory by warehouse **Keys:** item, cwar **Notes:** On-hand and allocated quantities. Verify column names for your release. **Table:** tisfc001 **Package:** ti Manufacturing **Description:** Production orders **Keys:** pdno **Notes:** Status field drives the shop floor control lifecycle. **Table:** tibom010 **Package:** ti Manufacturing **Description:** Bill of material lines **Keys:** mitm, pono **Notes:** Parent item and position. Baan IV and 5 structure. **Table:** tfacr200 **Package:** tf Finance **Description:** Accounts receivable invoices and transactions **Keys:** ttyp, ninv **Notes:** Open and paid customer documents. **Table:** tfacp200 **Package:** tf Finance **Description:** Accounts payable invoices and transactions **Keys:** ttyp, ninv **Notes:** Open and paid supplier documents. **Table:** tfgld410 **Package:** tf Finance **Description:** General ledger transaction history **Keys:** year, ptyp, ttyp, docn, lino **Notes:** Posted journal lines. Column set varies by release. **Table:** ttaad200 **Package:** tt Tools **Description:** Companies **Keys:** ccmp **Notes:** Company numbers used as the suffix on every physical table. **Notes:** 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. ## Content **Intro:** 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. **Sections:** #### How the Baan and LN table naming works **Body:** 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 **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### How are Baan and Infor LN tables named? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms infor ln table list, baan erp tables, infor ln tables, baan tdsls400 table, tccom100 business partner table, infor ln table naming convention, baan iv table names, infor ln data dictionary tables --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json