Infor LN Logical Table Sharing Design Worksheet
This worksheet plans multicompany table sharing in Infor LN, where a logical company reads a table physically stored in another company through Logical Tables (ttaad4120m000). Fill it in before you change the data dictionary so references, volumes and runtime conversion are agreed.
| Table code | Description | Package | Logical company (uses data) | Physical company (owns data) | Sharing method | Referenced tables to share too | Rows estimate | Risk | Converted to runtime | Owner | |
|---|---|---|---|---|---|---|---|---|---|---|---|
Logical tables are maintained in the Logical Tables session (ttaad4120m000). After saving, run Convert to Runtime and have users log on again before the change takes effect. A referenced table that is not shared leaves references unresolved and can cause errors in sessions at runtime. Example table codes are standard LN common tables; confirm package and references in your data dictionary.
Get your sharing design reviewed
Send the completed worksheet and your LN version and we will check the reference chains and runtime steps before you change the data dictionary.
Optional. The tool and every export work without this. No spam.
How to use it
List each candidate table with its code, package, the logical company that will read it and the physical company that owns it. Record the sharing method, the referenced tables that must be shared with it, a row estimate and a risk rating. Mark whether it has been converted to runtime and who owns the decision. Export to Excel for the design review. Start with low-risk common data such as units, currencies and countries, and treat items and business partners as separate decisions with their own sign-off.
- One row per table and company pair
- Write down references, not only the main table
- Agree the owner of shared data: only the physical company maintains it
Where this lives in LN
Table sharing is defined in Logical Tables (ttaad4120m000) for a package combination: you specify the table, the logical company and the physical company whose table it uses. The change only reaches users after Convert to Runtime and a fresh logon (or service restart for background processes). Infor's guide to multicompany table sharing covers the design rules; read it alongside this worksheet. Data replication between companies is a different mechanism: each company keeps its own copy, maintained by a load or integration, and is not configured in Logical Tables.
Worked example
Company 200 is a new sales company that should use the units, currencies, countries, payment terms and item groups of company 100. Those five tables are low or medium risk and small. Items (tcibd001) are high risk: sharing them means company 200 cannot hold its own item data, and every table the item record references must also resolve in the physical company. Business partners stay unshared in this design because the role tables would also need sharing decisions.
Gotchas
If you share a table but not the tables it references, reference fields cannot be resolved, descriptions go missing and sessions can fail validation or stop with errors, for example when country-of-origin data points at countries that are not visible. Sharing large transaction-heavy tables has performance effects because all companies hit one physical table. Converting to runtime without a logon restart leaves users on the old definition. Test the full set in a test environment, check key sessions in both companies, and keep the worksheet as the record of what was changed.
Frequently Asked Questions
How does table sharing work in Infor LN?
A logical company is mapped, per table, to a physical company that stores the data. When users in the logical company open a session on that table, LN reads and writes the physical company's table. The mapping is maintained in Logical Tables (ttaad4120m000) and activated with Convert to Runtime.
What happens if I forget to share a referenced table?
Fields that point to the missing reference cannot be resolved, so descriptions go missing and validations fail, which leads to errors in sessions that use those fields. Plan the reference chain for every shared table and share or align those tables at the same time.
Do I need to restart LN after changing logical tables?
After saving the logical table definitions, run Convert to Runtime. Users must log on again to pick up the new runtime data dictionary, and background jobs or services may need a restart. Schedule the change in a maintenance window.
Which tables are usually shared in LN multicompany setups?
Common reference data is the usual starting point: units, currencies, countries, payment terms and item groups. Item and business partner data can be shared but carry more risk because of their many references and their effect on company-specific processes.
If you want people in every LN company to ask questions across shared and unshared data in plain English on your own servers, we can set that up.
Related Tools
Infor LN Company and Enterprise Unit Design Worksheet
Plan LN companies, enterprise units, sites and currencies row by row, with user and volume totals, and export to Excel.
Infor LN & BaanInfor LN and Baan ERP Table List by Package
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.
Infor LN & BaanInfor LN Multi-Site Rollout Planner
Model your Infor LN global rollout: enter sites, wave size, and complexity to get wave count, total timeline, program cost, and cost per site.
Infor LN & BaanInfor LN Item Unit Conversion Factor Worksheet
List generic and item-specific unit conversions for LN 10.x with inverse factors and a test quantity check, so the factors are right before anyone types them in.
More Infor LN & Baan tools
See all- Infor LN Session and Module Code Reference
- Infor LN Production Order Status and Lifecycle Reference
- Infor LN 4GL Session Script Template
- Infor LN DAL Hook Review Checklist
- Infor LN Warehousing Order Origins and Types Reference
- Infor LN Table Name and SQL Query Builder
- Infor LN Regression Test Effort Calculator
- Infor LN and Baan Customization Inventory Worksheet
- Baan to Infor LN Data Conversion Mapping Worksheet
Keep exploring
Free tools
- Infor LN Table Name and SQL Query BuilderTurn an LN logical table such as tcibd001 into the physical SQL table name with company suffix and a ready SELECT statement.
- Infor LN New Company Creation ChecklistStep-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.
- Infor LN Company and Enterprise Unit Design WorksheetPlan LN companies, enterprise units, sites and currencies row by row, with user and volume totals, and export to Excel.
Guides
- Infor LN Printing and Report Design GuideDesign Infor LN reports and configure printing. Report session development, document output, label printing, and Crystal Reports integration for LN.
- Infor LN Multi-Company Setup and Financial StructureComplete guide to Infor LN multi-company financial structure including enterprise modeling, company creation, shared tables, and consolidation configuration.
- Infor LN Enterprise Modeling GuideDesign Infor LN enterprise structures. Company modeling, logistic entities, financial companies, and multi-site architecture for complex organizations.