What Is Multisite (Infor LN)?
Also known as: LN multisite, LN sites, multi-site LN
Definition
Multisite in Infor LN is the configuration pattern for running several plants, warehouses or legal entities in one environment using sites, enterprise units and multiple companies, with intercompany trade rules that price and post transfers between them automatically.
Multisite (Infor LN) Explained
LN gives you several structural levels and the design problem is choosing among them. A logistic company is the heaviest boundary, providing full operational separation and its own transaction data. An enterprise unit ties a logistical scope to the financial company that accounts for it. A site groups the warehouses, work centers and planning scope of one physical location. Sites let you model several plants inside a single logistic company, which is far lighter than giving each plant its own company.
Which level to use is driven by legal and reporting requirements first and operational preference second. Separate legal entities in different countries generally need separate financial companies, and often separate logistic companies. Multiple plants within one legal entity are usually best modeled as sites, because a transfer between them stays a warehouse transfer order rather than becoming a full intercompany sale and purchase with internal invoicing and elimination.
Intercompany trade is the mechanism that makes cross-boundary flows work when separation is genuinely required. Trade relationships and agreements define which entity buys from which, how the internal transfer is priced, and what documents and postings are produced. Configured well, an internal transfer generates its own invoicing and matching automatically; configured poorly, it produces reconciliation work every month for the rest of the system's life.
Planning spans the structure as well. Enterprise Planning can plan across sites and companies, with planning clusters and supply strategies defining where demand is satisfied from and how supply cascades between locations. That is a genuine strength of LN in multi-plant manufacturing, and it is also where the multisite design either pays off or exposes itself: if the structure does not reflect how goods actually flow, planning will produce results the business does not recognize.
Why It Matters
- Choosing sites over separate companies where the law allows removes a permanent burden of intercompany accounting.
- Intercompany trade configuration determines whether cross-entity transfers reconcile automatically or by hand each month.
- Planning across sites and companies is a core LN strength, but only if the structure matches real material flow.
- Restructuring companies or sites after go-live is a data conversion project, so the design must be validated up front.
In Practice
Test the enterprise structure with a full end-to-end intercompany scenario before committing: create demand in one entity, satisfy it from another, and follow the transaction all the way through internal invoicing, matching and elimination into consolidated reporting. Structural flaws that are invisible in a design workshop become obvious the first time you try to close the books on a paper transaction.
Frequently Asked Questions
What is the difference between a site and a company in LN?
A company is the top-level data boundary, with logistic companies holding operational data and financial companies holding the ledger. A site is a lighter grouping inside a logistic company that represents a physical location and its warehouses, work centers and planning scope. Transfers between sites in one company are warehouse transfers; transfers between companies are intercompany transactions.
When do I need separate companies rather than sites?
When legal, tax or statutory reporting boundaries require it, or when operations must be genuinely independent, including separate master data conventions and authorizations. Different legal entities, particularly across countries, normally need separate financial companies. Multiple plants inside one legal entity rarely justify separate logistic companies and are usually better modeled as sites.
Related Terms
Logistic Company
A logistic company in Baan and Infor LN is a company number that holds operational data such as items, warehouses, and sales, purchase, production and warehouse orders. Each logistic company is linked to exactly one financial company that carries its ledger.
Financial Company
A financial company in Baan and Infor LN is a company number that owns the general ledger: the chart of accounts, dimensions, fiscal calendars, currency setup and all financial transactions for one or more logistic companies linked to it.
Enterprise Planning
Enterprise Planning is Infor LN's supply planning engine. It runs master planning and order planning across plan items, sites and companies, generating planned orders and reschedule signals from demand, inventory, lead times and the supply strategies defined per plan item.
Go Deeper
Infor LN vs SyteLine Selector
Answer ten questions about your sites, manufacturing mode, and complexity to see whether Infor LN or SyteLine (CloudSuite Industrial) is the better fit.
Infor LN Implementation Cost: What to Budget
Infor LN implementation cost typically runs $500K to $5M+. See budget breakdowns by phase, license-to-services ratios, and the cost drivers for 2026 projects.
Infor LN to CloudSuite: Migration Playbook
Infor LN to CloudSuite migration playbook: Baan and LN version paths, extension conversion, ION integration rework, timelines, and defense compliance steps.
Working with Multisite (Infor LN) in a live environment? Our engineers do this every day - and our AI agents automate most of it.