# Infor LN New Company Creation Checklist > Source: https://netray.co/tools/infor-ln-new-company-creation-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Step-by-step checklist for adding a company to an on-prem Infor LN 10.x system, from planning the company number and table sharing to validating the first transactions. ## Category infor-ln ## Erp Infor LN ## Audience - LN system administrator - LN technical consultant - LN application consultant ## Tool **Kind:** checklist **Groups:** #### Plan **Items:** **Text:** Choose a four-digit company number that is not already used and fits your numbering plan **Critical:** true **Text:** Decide the package combination (VRC) the company will use; it must be one that is installed **Critical:** true Choose the company currency and confirm it is defined consistently with the other companies in the structure **Text:** Use the same first weekday as the other companies in the multicompany structure **Critical:** true **Text:** Decide which tables are shared with other companies through logical tables, before any tables are created **Critical:** true Check database space for a full set of company tables and their indexes #### Create **Items:** Log on as user bsp (or baan) on the target environment Create the company in Companies (ttaad1100m000) with number, first weekday, currency and package combination **Text:** Run Convert to Runtime from the Companies session before closing it **Critical:** true Log off and on again so the bshell picks up the new runtime company data Run Create Tables (ttaad4230m000) for every package the company uses; logically linked tables are not created physically **Text:** Check the Create Tables report for errors before continuing **Critical:** true #### Share tables **Items:** Define table sharing in Logical Tables (ttaad4120m000) per table or module, pointing to the owning company Convert the logical table definitions to runtime and restart the bshell If a table was created physically before you defined sharing, resolve it deliberately rather than leaving two copies Document every shared table and its owning company in the enterprise structure design #### Initial data and users **Items:** Switch to the new company (LN Options, Change Company) **Text:** Run Initialize Parameters (tcmcs0295m000) to check required tables and insert default records **Critical:** true Set the COM parameters for the new company, including number groups Enter the general company data and select the packages in Implemented Software Components Define the home currency setup and the company address **Text:** Give users access to the new company in User Data (ttams1100m000) and convert user changes to runtime **Critical:** true Assign roles and text group authorizations for the new company #### Validate **Items:** Open key sessions for each implemented package and confirm no table-missing errors Check $BSE/log for errors written during table creation and first logons **Text:** If the company will publish BODs, select Prevent BOD Publishing in BOD Parameters (tcbod0100m000) until setup is complete **Critical:** true Clear Prevent BOD Publishing only after integration setup, then run the initial load sessions Post a test transaction per package and reverse it, or use a test company first Record the company number, VRC, shared tables and setup date in the system register **Scoring Note:** 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. ## Content **Intro:** 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. **Sections:** #### How to use it **Body:** 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 **Body:** 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### What is admin mode in Infor LN when creating a company? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms infor ln admin mode, infor ln administrator guide, infor ln create company, infor ln table sharing, ttaad1100m000 companies, ttaad4230m000 create tables, infor ln logical tables, infor ln multicompany setup --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json