Infor LN & BaanFree referencePDF, Excel, Word exportInfor LN

Infor LN Session Code Reference: Package and Module Codes

Every Infor LN and Baan session code starts with a five character module code: a two letter package and a three letter module, such as tisfc or tdsls. This reference lists the most-used modules so you can read a session name in a ticket, log or authorization list and know where it lives.

Download:

Module code	Package	Functional area	What it typically covers	Typical users
tcibd	tc Common	Item base data	Item master: general item data, item groups, item type, unit sets	Master data team, planners
tccom	tc Common	Common data	Business partners, employees, addresses, contacts	Master data team, sales, purchasing
tcmcs	tc Common	General masters	Units, currencies, countries, general reference tables, warehouses setup in common data	Application administrators
tcemm	tc Common	Enterprise modeling	Companies, enterprise units, sites and the links between them	Implementation consultants
tibom	ti Manufacturing	Bill of material	Manufactured item BOMs, components, effectivity	Engineering, planners
tirou	ti Manufacturing	Routing	Routing, operations, task and work center links	Manufacturing engineering
tisfc	ti Manufacturing	Shop floor control	Production orders, material and operation reporting, order status	Production control, shop floor
ticst	ti Manufacturing	Costing	Standard and actual cost calculation for manufactured items	Cost accountants
tdsls	td Order Management	Sales control	Sales quotations, sales orders, order lines, deliveries	Sales administration
tdpur	td Order Management	Purchase control	Purchase requisitions, purchase orders, schedules, receipts	Buyers
tdinv	td Order Management	Inventory control	Inventory transactions and inventory by item and warehouse	Inventory controllers
tdilc	td Order Management	Inventory location control	Location-level inventory, where location control is used	Warehouse supervisors
whwmd	wh Warehousing	Warehousing master data	Warehouse definitions, locations, item data per warehouse	Warehouse administrators
whinh	wh Warehousing	Inventory handling	Warehouse orders, order lines, inventory transactions and handling units	Warehouse staff, logistics
whinr	wh Warehousing	Inbound	Inbound receipts and inbound goods processing	Receiving
whout	wh Warehousing	Outbound	Outbound picking, shipping and outbound order processing	Shipping
tfgld	tf Financials	General ledger	Ledger accounts, journal entries, periods, financial statements	Accountants
tfacp	tf Financials	Accounts payable	Purchase invoices, supplier payments	AP clerks
tfacr	tf Financials	Accounts receivable	Sales invoices, customer receipts	AR clerks
tfcmg	tf Financials	Cash management	Bank accounts, payments, bank reconciliation	Treasury
ttadv	tt Tools	Application development	Sessions, tables, domains, scripts and forms in the data dictionary	LN developers
ttaad	tt Tools	Application administration	Users, authorizations, companies, session parameters and queues	LN administrators

Module codes are the first five characters of a session code (two letter package plus three letter module). Verify against the Tools data dictionary in your own VRC, because customized and added modules are common. Session names and numbers vary by LN version.

Ask LN questions in plain English

Optional: see how a read-only assistant over your LN data answers questions like which sessions or tables hold a value.

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

How to read an LN session code

A full session code is the module code plus a four digit number, a one letter session type and a three digit suffix, for example tisfc0501m000. The first two letters are the package (ti is manufacturing), the next three are the module (sfc is shop floor control). The letter after the digits is the session type: m for main, s for subsession, f for form or display, and so on. The same code appears in the Tools data dictionary, in user authorizations and in the table names, which is why a table such as tcibd001 belongs to the tc package and the ibd module.

How to use the table

Type a code, package or keyword in the search box to filter. Use the table when you read a support ticket, an audit finding, a BDE or log file, or a role design workbook and need to place a session quickly. Export to Excel to add your own columns, such as owner, custom sessions and risk. The reference deliberately lists modules, not individual session numbers, because session numbers differ between LN versions and customized VRCs.

Search by package (td) to see every order management module
Search by a business word (invoice, cost, location) to find the module
Export the list as a starting point for an authorization review

Common mistakes and ERP notes

The most common mistake is assuming the module code equals the menu name. Menus are role based and renamed, but the code is stable. A second mistake is treating a table prefix as a session: tdsls400 is a table, not a session. Finally, customized VRCs add modules with the same pattern, so do not use an unknown code to infer standard behavior. Always confirm in the session's About or Zoom information inside LN, and with the Tools application development tables, before you change authorizations or write extensions.

Frequently Asked Questions

What does tisfc stand for in Infor LN?

tisfc is the shop floor control module in the ti manufacturing package. It holds production orders and their reporting, including material issues and operation completion. The ti prefix is manufacturing and sfc is shop floor control.

What is the difference between tdsls and tdpur?

Both are in the td order management package. tdsls is sales control, covering quotations, sales orders and deliveries. tdpur is purchase control, covering requisitions, purchase orders and receipts. Their tables follow the same pattern with their own module code.

What does whinh cover in Infor LN warehousing?

whinh is the inventory handling module in the wh warehousing package. It covers warehouse orders and order lines, inventory transactions and handling. Master data is in whwmd, and inbound and outbound processing sit in whinr and whout.

Are these codes the same in Baan IV?

The package and module naming pattern is the same lineage, and many codes carry over, but sessions, numbers and some modules differ between Baan IV, Baan 5 and LN. Treat the list as orientation, then verify in your own data dictionary.

If your team spends time hunting sessions and tables across LN companies, we can show how a read-only natural-language layer over LN data answers these questions directly.

Talk to an Expert Explore More Free Tools

Related Tools

Infor LN & Baan

More Infor LN & Baan tools

See all

Back to All Tools