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

Infor LN New Company Creation Checklist

This checklist walks an LN administrator through creating an additional company on an on-prem Infor LN 10.x system. It follows the Infor setup sequence and adds the planning and validation steps that the procedure assumes you already know.

0%

0 of 29 items complete

9 critical items still open - these are the highest-risk gaps.

Download checklist:

Plan

Create

Share tables

Initial data and users

Validate

Critical items in Plan and Create cannot be fixed cheaply later: the first weekday, the package combination and table sharing decisions all affect data. Do not hand the company to users until every critical item is checked.

Get your new company design checked before you create it

Send us your planned company number, package combination and table sharing list and we will review it against your existing enterprise structure.

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

Was this tool useful?

How to use it

Fill in the Plan group with the functional consultant before anyone logs on as bsp. Most of the expensive mistakes are decided there: which tables are shared, which package combination the company runs on and whether the first weekday matches the rest of the structure. Then work through Create, Share tables and Initial data in order, ticking each item. The Validate group is what you show the project lead before handing over. Export the list to PDF and file it with the enterprise structure design so the next company is created the same way.

Where this lives in LN

Company definition and table creation are Tools sessions run in company 000 context: Companies (ttaad1100m000), Create Tables (ttaad4230m000) and Logical Tables (ttaad4120m000). Create Tables also relies on the database definitions that tell LN which database holds the company tables, so check those with your DBA before running it. Once the tables exist you switch company and continue in the Common package: Initialize Parameters (tcmcs0295m000), then the COM parameters, the general company data and Implemented Software Components. User access is granted through User Data (ttams1100m000).

Table sharing decisions

Logical tables make one company read and write another company's physical table. Typical candidates are master data you want maintained once, such as items, business partners or currencies, but every shared table also shares its parameters and its behaviour, so share by module design rather than table by table. The safest moment to define sharing is before Create Tables runs. If a table already exists physically in the new company and you then link it logically, the physical table is no longer used and any data in it is effectively hidden. Make sharing a written decision signed by the functional lead.

Gotchas

Forgetting Convert to Runtime after creating the company is the classic one: Create Tables then reports that the company is unknown. The second is BOD publishing. A new company connected to ION can start publishing master data as soon as records are entered, and once BODs reach ION that publication cannot be undone. Set Prevent BOD Publishing in BOD Parameters (tcbod0100m000) while you configure, then clear it and run the initial load. The third is user access: users who cannot see the company in their company list usually need their User Data changes converted to runtime.

Frequently Asked Questions

What is admin mode in Infor LN when creating a company?

There is no separate admin mode for company creation. You log on as a Tools administrator such as bsp or baan, run the Tools sessions in the system context, and lock regular users out while tables are created. Some sites run these steps during a maintenance window so no user session holds the old runtime data.

Why does Create Tables say the company does not exist?

Usually the company was saved in Companies (ttaad1100m000) but not converted to runtime, or the bshell was not restarted after conversion. Run Convert to Runtime from the Companies session, log off and on, and run Create Tables (ttaad4230m000) again.

Can I share tables after the company is in use?

Technically yes, through Logical Tables (ttaad4120m000) and convert to runtime, but data already in the company's own physical table is no longer visible once the link is active. Plan a data migration or cleanup for the affected tables and test it in a copy first.

Where is this in the Infor LN administrator guide?

The company setup user guide on docs.infor.com covers creating the first company and creating additional companies, and the session help for ttaad1100m000, ttaad4230m000 and ttaad4120m000 explains each field. This checklist adds planning and validation steps around those procedures.

If you want admins and consultants to ask your LN system in plain English which tables are shared between companies, we can set that up on your own servers.

ArchRay builder
Design the on-prem AI stack for Infor LN and Baan: model, GPUs, RAG pipeline, guardrails
See memory, speed and cost as you swap parts, then export the diagram. Free, in your browser.
Open the builder

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP

Integrations

Comparisons

Software