What Is BaanERP (Baan V)?
Also known as: Baan V, Baan 5, BaanERP 5.0c
Definition
BaanERP, also called Baan V, is the late-1990s successor to Baan IV. It introduced a separate Warehousing package, Enterprise Planning, and a component-based Windows architecture, and it is the direct code ancestor of SSA ERP LN and today's Infor LN.
BaanERP (Baan V) Explained
BaanERP shipped at the end of the 1990s and was numbered as Baan V, with the 5.0 line and its service packs being the versions most commonly deployed. It arrived during a turbulent commercial period for the vendor, and the product passed from Baan to Invensys and then to SSA Global in 2003. That ownership chain matters because it explains why the same codebase later appears under the names SSA ERP LN, Infor ERP LN and finally Infor LN.
The biggest structural change from Baan IV was the split of warehouse execution out of distribution into a dedicated Warehousing package with its own order types, inbound and outbound procedures, and inventory handling. Planning was likewise rebuilt: the older master production scheduling and MRP modules were replaced by Enterprise Planning, which introduced plan items, master plans, order planning and planning clusters as a single engine spanning several companies.
Under the covers, Baan V kept the familiar platform: sessions defined in Tools, 3GL and 4GL scripts, pseudo-code executed by the bshell, porting sets for each operating system and database, and VRC layering for customizations. What changed was the amount of business logic pushed into DAL objects, so that validation and defaulting are enforced regardless of which session, exchange scheme or interface writes the record.
For organizations still on Baan V, the upgrade story is materially better than it is from Baan IV. The data model, session codes and business object structure of Baan V are recognizably those of Infor LN, so migration is largely an upgrade path with data conversion and customization remediation rather than a rebuild. The two things that usually decide effort are the volume of modified standard code and how much of the customization can be reimplemented as LN extensions.
Why It Matters
- Baan V is the pivot version: its data model is close enough to Infor LN that upgrade, rather than reimplementation, is realistic.
- The Warehousing and Enterprise Planning packages introduced here define how inventory and supply planning still work in LN today.
- Business logic centralized in DAL objects means interfaces and data loads inherit validation instead of bypassing it.
- Knowing whether you are on Baan IV or Baan V changes migration cost estimates by a wide margin, so it is the first fact any assessment should establish.
In Practice
A frequent gotcha on Baan V estates is customizations that duplicate functionality Infor later shipped as standard, such as bespoke shipping documents or homegrown intercompany postings. During upgrade scoping, map every customization against standard LN capability first. Teams that skip this step routinely pay to port code that LN already replaces, and then carry the maintenance forever.
Frequently Asked Questions
Is Baan V the same product as Infor LN?
They share a direct lineage. SSA Global acquired Baan and released the next major version as SSA ERP LN, which Infor then continued as Infor LN. Session codes, table names and the underlying Tools platform carry forward, so a Baan V developer recognizes LN immediately. The functional scope, user interface and extensibility model, however, have moved on considerably.
Can Baan V be upgraded directly to Infor LN?
Yes, a technical upgrade path exists and is the normal route. The work concentrates on converting data into the newer LN structures, retiring or reimplementing customizations, retraining users on the modern web interface, and revalidating integrations. Most of the schedule risk comes from customized standard code and undocumented interfaces rather than from the base data conversion itself.
Related Terms
Baan IV
Baan IV is the mid-1990s release of Baan Company's ERP suite, built on the bshell runtime with 3GL and 4GL development tools, package-based modules such as td, ti and tf, and multi-company table sharing.
Infor LN
Infor LN is Infor's enterprise ERP suite for complex discrete manufacturers, descended from Baan IV and Baan V. It is deployed as on-premises LN 10.x or as an Infor CloudSuite edition, and covers manufacturing, warehousing, projects, service and multi-company finance.
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
Baan to Infor LN Migration Readiness Assessment
Score your organization's readiness to migrate from Baan IV or Baan V to Infor LN across ten dimensions, from data quality to executive sponsorship.
Baan ERP: History, Versions, and Modern Migration Paths
Baan ERP history from Triton to Baan IV, Baan V, and Infor LN, plus practical migration paths for manufacturers still running Baan today. Get a proven roadmap.
Baan 4GL Modernization: Strategies for Legacy Code
Baan 4GL modernization strategies: inventory legacy sessions, retire dead code, convert customizations to LN extensions, and de-risk your Baan installed base.
Working with BaanERP (Baan V) in a live environment? Our engineers do this every day - and our AI agents automate most of it.