Infor LN & BaanGlossary

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.

What is Baan ERP?

Baan ERP is the ERP product line from the Dutch vendor Baan, aimed at manufacturers. In the strict sense BaanERP is the Baan V release, but the term is also used for the whole Baan family: Baan IV, BaanERP, and the later SSA ERP LN and Infor LN releases that descend from it.

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

Free Tool

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.

Talk to an Expert Browse the Full Glossary

Back to Glossary

Try it here, free

Infor LN and Baan ERP Table List by Package

Open full tool

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.

Download:

Table	Package	Description	Key fields	Notes
tccom100	tc Common	Business partners	bpid	Parent of customer and supplier roles. LN only; Baan IV used tccom010 and tccom020.
tccom130	tc Common	Addresses	cadr	Referenced by business partners, warehouses, companies and orders.
tccom010	tc Common	Customers (Baan IV and 5)	cuno	Replaced by business partner model in LN.
tccom020	tc Common	Suppliers (Baan IV and 5)	suno	Replaced by business partner model in LN.
tcibd001	tc Common	Items general	item	Central item master in LN. Item code is padded with leading spaces in the project segment.
tiitm001	ti Manufacturing	Items (Baan IV and 5)	item	Predecessor of tcibd001 in older releases.
tcmcs003	tc Common	Warehouses	cwar	Linked to an address and an enterprise unit.
tcmcs023	tc Common	Item groups	citg	Used for grouping items for planning, costing and reporting.
tcmcs080	tc Common	Carriers and freight forwarders	cfrw	Referenced by shipments and orders.
tcemm030	tc Common	Enterprise units	eunt	Part of enterprise modeling; links planning, finance and warehouses.
tdsls400	td Distribution	Sales orders	orno	Header. Order type comes from tdsls094.
tdsls401	td Distribution	Sales order lines	orno, pono, sqnb	Line quantities, prices and status.
tdsls406	td Distribution	Sales order line deliveries	orno, pono, sqnb	Delivery-level data for a line. Confirm field set in your release.
tdsls094	td Distribution	Sales order types	sotp	Controls order handling, such as which activities run.
tdsls040	td Distribution	Sales orders (Baan IV and 5)	orno	Older header table. Lines are in tdsls041.
tdsls041	td Distribution	Sales order lines (Baan IV and 5)	orno, pono	Older line table.
tdpur400	td Distribution	Purchase orders	orno	Header. Order type from tdpur094.
tdpur401	td Distribution	Purchase order lines	orno, pono, sqnb	Line item, quantity, price and status.
tdpur094	td Distribution	Purchase order types	potp	Controls purchase order processing.
tdpur040	td Distribution	Purchase orders (Baan IV and 5)	orno	Older header; lines in tdpur041.
tdpur041	td Distribution	Purchase order lines (Baan IV and 5)	orno, pono	Older line table.
whinh200	wh Warehousing	Warehouse orders	oorg, orno	Header for inbound, outbound and transfer warehouse orders.
whinh210	wh Warehousing	Warehouse order lines	oorg, orno, pono, seqn	Lines link back to source order and item.
whwmd215	wh Warehousing	Item inventory by warehouse	item, cwar	On-hand and allocated quantities. Verify column names for your release.
tisfc001	ti Manufacturing	Production orders	pdno	Status field drives the shop floor control lifecycle.
tibom010	ti Manufacturing	Bill of material lines	mitm, pono	Parent item and position. Baan IV and 5 structure.
tfacr200	tf Finance	Accounts receivable invoices and transactions	ttyp, ninv	Open and paid customer documents.
tfacp200	tf Finance	Accounts payable invoices and transactions	ttyp, ninv	Open and paid supplier documents.
tfgld410	tf Finance	General ledger transaction history	year, ptyp, ttyp, docn, lino	Posted journal lines. Column set varies by release.
ttaad200	tt Tools	Companies	ccmp	Company numbers used as the suffix on every physical table.

Keys and column names can vary between Baan IV, Baan 5 and LN releases, and customizations add fields. Always check the data dictionary in your own VRC. Physical table names in the database add a leading t and the company number, so tdsls400 in company 100 is ttdsls400100.