What Is Baan IV?
Also known as: Baan 4, Baan IVc, Baan IVc4
Definition
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.
Baan IV Explained
Baan IV was released by the Dutch software company Baan in the mid-1990s as the successor to Triton 3, and it went through a long series of maintenance releases, of which Baan IVc and its later service packs are the versions still most often found in production. It ran on UNIX and Windows servers against Oracle, Informix, DB2 and Microsoft SQL Server, and users reached it through a character-mode terminal interface or the later Windows client that wrapped the same underlying screens.
Architecturally, everything in Baan IV is a session: a coded screen, report or batch program defined in the Tools data dictionary and executed as pseudo-code by the bshell. The platform-specific pieces live in a separately versioned porting set, so the same application code runs across operating systems and databases. Source code is layered in VRCs (version, release, customer), which is how standard code, patches and site-specific customizations are kept apart while still compiling into one runtime picture.
Functionally the suite is organized into packages: tc for common master data, td for distribution, ti for manufacturing, tf for finance, tp for project, ts for service and tt for tools. Dynamic Enterprise Modeling sits above them, letting an implementation describe its processes and generate role-based menus. Multiple companies coexist in one environment, with table sharing controlling which master tables are physically common and which are kept separate for each company.
Today Baan IV is well past mainstream vendor support, and the practical risks are operational rather than functional: the software still works, but the operating systems, databases and hardware under it are aging out of certification, and the pool of developers who can read 4GL scripts written twenty years ago keeps shrinking. Many aerospace, defense and industrial manufacturers still run it because their program lifecycles are measured in decades, which makes a deliberate migration path to Infor LN or CloudSuite the real decision to make.
Why It Matters
- Running unsupported ERP shifts every security patch, OS upgrade and database certification issue onto your own team, with no vendor backstop.
- The scarcity of Baan IV 3GL/4GL developers drives up both hourly rates and the elapsed time to make any change.
- Baan IV data structures carry hard limits, such as short item and order code fields, that constrain modern part numbering and EDI requirements.
- Understanding what is genuinely standard versus customized in your Baan IV VRCs is the single biggest driver of migration cost to Infor LN.
In Practice
The most common surprise on a Baan IV assessment is customization sprawl nobody can inventory. Sites routinely find hundreds of modified standard sessions sitting in a derived VRC, with no source control history and no documentation of why. Before estimating any upgrade, extract the full list of customized objects per VRC and classify each one as still used, obsolete or replaceable by standard LN functionality.
Frequently Asked Questions
Is Baan IV still supported?
Baan IV is long past Infor's mainstream support window. Some third-party and Infor sustaining arrangements exist, but you should assume no new functionality, no regulatory updates and no certification of new operating systems or database versions. Most organizations still on Baan IV are effectively self-supporting, relying on internal knowledge and specialist partners to keep the environment running.
What is the difference between Baan IV and Baan V?
Baan V, marketed as BaanERP, restructured the application: warehousing moved out of distribution into its own package, planning was rebuilt as Enterprise Planning instead of the older MPS and MRP modules, and the client and component architecture were modernized. Baan IV code does not simply upgrade in place; the move to Baan V or Infor LN is a data and process migration project.
Related Terms
BaanERP (Baan V)
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.
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.
Bshell
The bshell is the Baan and Infor LN virtual machine. It loads compiled pseudo-code for sessions, scripts and reports, executes it, and translates the application's database calls into native SQL through porting set drivers - one bshell process typically serves one user session.
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.
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 Baan IV in a live environment? Our engineers do this every day - and our AI agents automate most of it.