# Infor LN Logical Table Sharing Design Worksheet > Source: https://netray.co/tools/infor-ln-logical-table-sharing-design-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Plan which LN tables a logical company reads from a physical company, including the reference tables that must be shared with them, before you touch Logical Tables. ## Category infor-ln ## Erp Infor LN ## Audience - LN administrator - LN functional consultant - ERP architect ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Table code **Key:** table **Type:** text #### Description **Key:** desc **Type:** text #### Package **Key:** package **Type:** text #### Logical company (uses data) **Key:** logical **Type:** text #### Physical company (owns data) **Key:** physical **Type:** text #### Sharing method **Key:** method **Type:** select **Options:** - Direct sharing (logical table) - Data replication - Not shared #### Referenced tables to share too **Key:** refs **Type:** text #### Rows estimate **Key:** rows_est **Type:** number **Format:** integer #### Risk **Key:** risk **Type:** select **Options:** - Low - Medium - High #### Converted to runtime **Key:** runtime **Type:** select **Options:** - Yes - No #### Owner **Key:** owner **Type:** text **Rows:** **Table:** tcmcs001 **Desc:** Units **Package:** tc **Logical:** 200 **Physical:** 100 **Method:** Direct sharing (logical table) **Refs:** Check unit sets that use these units **Rows est:** 120 **Risk:** Low **Runtime:** No **Owner:** LN admin **Table:** tcmcs002 **Desc:** Currencies **Package:** tc **Logical:** 200 **Physical:** 100 **Method:** Direct sharing (logical table) **Refs:** Review rate tables separately **Rows est:** 40 **Risk:** Low **Runtime:** No **Owner:** Finance **Table:** tcmcs010 **Desc:** Countries **Package:** tc **Logical:** 200 **Physical:** 100 **Method:** Direct sharing (logical table) **Refs:** Tables referencing countries, e.g. country of origin data **Rows est:** 250 **Risk:** Medium **Runtime:** No **Owner:** LN admin **Table:** tcmcs013 **Desc:** Terms of payment **Package:** tc **Logical:** 200 **Physical:** 100 **Method:** Direct sharing (logical table) **Refs:** Related payment term detail tables **Rows est:** 60 **Risk:** Low **Runtime:** No **Owner:** Finance **Table:** tcmcs023 **Desc:** Item groups **Package:** tc **Logical:** 200 **Physical:** 100 **Method:** Direct sharing (logical table) **Refs:** Default data referenced by item groups **Rows est:** 300 **Risk:** Medium **Runtime:** No **Owner:** Master data **Table:** tcibd001 **Desc:** Items - general **Package:** tc **Logical:** 200 **Physical:** 100 **Method:** Direct sharing (logical table) **Refs:** tcmcs001, tcmcs023 and other item references **Rows est:** 85000 **Risk:** High **Runtime:** No **Owner:** Master data **Table:** tccom100 **Desc:** Business partners **Package:** tc **Logical:** 200 **Physical:** 100 **Method:** Not shared **Refs:** Role tables (sold-to, buy-from) would need a decision too **Rows est:** 12000 **Risk:** High **Runtime:** No **Owner:** Sales and purchasing **Totals:** #### Total rows in scope **Key:** rows_est **Agg:** sum **Format:** integer **Summary:** #### Tables listed **Key:** tables **Expr:** count **Format:** integer #### Average rows per table **Key:** avg_rows **Expr:** sum_rows_est / count **Format:** integer **Notes:** 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. ## Content **Intro:** 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. **Sections:** #### How to use it **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### How does table sharing work in Infor LN? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms infor ln table sharing, infor ln user guide for table sharing, ln logical tables, ttaad4120m000, ln multicompany table sharing, ln logical company physical company, convert to runtime ln --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json