Infor LN Company and Enterprise Unit Design Worksheet
Getting the company and enterprise unit structure right is one of the first and most expensive decisions in an Infor LN implementation. This worksheet lets you list companies, enterprise units, sites and currencies row by row, see user and volume totals, and export a clean design for sign-off.
| Company no. | Company name | Enterprise unit | Unit type | Site | Local currency | Shares master data | Users | Orders per month | Orders per user | |
|---|---|---|---|---|---|---|---|---|---|---|
0 | ||||||||||
81.8182 | ||||||||||
21.1111 | ||||||||||
221.4286 | ||||||||||
18.4211 | ||||||||||
46.6667 |
A company number in LN is a separate set of data tables, enterprise units link logistic and financial functions inside enterprise modeling, and one company can contain several units and sites. Use this worksheet to agree the structure before configuration. Final design depends on legal entities, reporting needs and your LN version.
LN structure review
Optional: a second pair of eyes on your company, site and enterprise unit design.
Optional. The tool and every export work without this. No spam.
How to use the worksheet
Add one row per enterprise unit. Put the LN company number, the legal or functional name, the unit and its type, the site, the local currency, whether master data is shared, and expected users and orders per month. The computed column shows orders per user so you can spot a unit that is oversized or thin. Use the totals for licensing and sizing conversations, and export to Excel to share with finance and IT.
The method behind the design
In LN, a company number holds its own set of transactional and master tables, and enterprise modeling links units, sites and companies together. Typical drivers for a separate company are a separate legal entity, a different local currency or fiscal calendar, and different regulatory reporting. Drivers against it are duplicated master data and extra intercompany effort. Shared master data across companies reduces duplication but needs governance. Decide per business, not per template.
- One company per legal entity is a common starting point
- Share items and business partners only where ownership is clear
- Plan intercompany flows early, they drive effort
Common mistakes
Teams often copy the legal structure straight into LN without asking what must be separate. Others create too many companies and then fight consolidation and intercompany. Forgetting a sandbox and test company in the plan is another gap, as is not planning the numbering convention for companies. Because restructuring companies later is expensive, review the draft with finance, supply chain and IT before you configure, and record the reasons for each split in the worksheet.
Frequently Asked Questions
What is an enterprise unit in Infor LN?
It is an organizational element in enterprise modeling that groups related functions, such as financial, sales, purchase, warehousing or manufacturing, and ties them to a company and site. Units let LN route transactions to the right finance and logistics context.
How many LN companies should we have?
As few as the business and legal structure allow. A separate company is usually justified by a separate legal entity, currency, calendar or reporting. More companies means more setup, intercompany work and reconciliation, so each one should have a clear reason.
Can LN companies share master data?
Yes. LN supports sharing certain master data across companies, which cuts duplication. It needs clear ownership and change control, because an edit in one place affects every company that uses the data.
Does this replace the LN enterprise modeling configuration?
No. It is a planning and communication aid for agreeing the design. The actual structure is configured in LN enterprise modeling by your consultant, following your version's documentation.
If you are planning a multi-site LN structure or consolidating Baan companies, we can share how we help assess and document the design with an on-prem assistant.
Related Tools
Infor LN Session and Module Code Reference
Searchable list of the Infor LN / Baan package and module codes (tisfc, tdsls, whinh and others) with what each one covers.
Infor LN & BaanInfor LN Table Name and SQL Query Builder
Turn an LN logical table such as tcibd001 into the physical SQL table name with company suffix and a ready SELECT statement.
Infor LN & BaanInfor LN Regression Test Effort Calculator
Estimate test hours, defects and calendar weeks for an LN upgrade or change, and see how adding testers shortens the schedule.
Infor LN & BaanInfor LN Production Order Status and Lifecycle Reference
Lifecycle reference for LN production orders: statuses, what they allow, typical transactions and common blockers.
More Infor LN & Baan tools
See all- Infor LN 4GL Session Script Template
- Infor LN DAL Hook Review Checklist
- Infor LN Warehousing Order Origins and Types Reference
- Infor LN and Baan Customization Inventory Worksheet
- Baan to Infor LN Data Conversion Mapping Worksheet
- Infor LN User Role and Authorization Matrix Worksheet
- Infor LN Change Request Form Template
- Infor LN Session Test Script Template
- Infor LN Cutover Runbook Template