Retiring Infor LN and Baan means preserving agreed historical records and usable access before removing the source application dependency. For this scenario, prioritise financial-company context, production costs and lot evidence. Compare required reports and documents with source evidence, test permissions and obtain business acceptance before scheduling shutdown.

This guide covers the retirement questions, a mock-data ArchiveHub demonstration and the validation work needed to define a project scope.

What a read-only LN or Baan costs

Cost categories are a discovery checklist, not a guaranteed savings calculation. Verify support status, deployment, shared infrastructure and contract terms for the actual installation.

  • The application server and its database. LN and Baan run on their own application layer over Oracle, SQL Server or DB2 databases, often on Unix hosts that nobody else in IT still supports. Each of those layers needs licences, patching and skills.
  • Infor maintenance on a system that only answers questions.
  • Session knowledge. Finding a document in LN means knowing the right session, such as tfgld3509m000 or tdsls4500m000, and the right company number. Few people outside the old ERP team do.
  • Customisations. Customer-specific modules, such as an interface package for an external payroll, are understood only by the people who built them.
  • Traceability obligations. Aerospace and defence customers expect lot and certificate history to stay retrievable for a long time. That alone is often why the old system is never switched off.
  • Security exposure on an ageing stack that still holds employee, supplier and bank data.

Scope, versions and evidence

This is an illustrative workflow, not a customer case study. Confirm the source release, deployment, modules, customisations and extraction permissions before using the mappings below. Tables and report labels describe the demonstration catalogue; native-report equivalence has not been independently certified. Use agreed source reports and representative records for acceptance testing.

An archive is not a replacement for every operational feature of the retired ERP. Document required historical tasks, excluded functions and any archive-derived calculations.

Historical data to scope for Infor LN and Baan

ArchiveHub archives LN and Baan by table code, with each table's description naming the sessions that show it. Physical tables keep the familiar t prefix plus package, module and table number, for example ttfgld106.

General ledger. tfgld106 (Finalized Transactions, shown in tfgld3509m000 and tfgld1509m000), tfgld101 (Documents, the header behind Document History tfgld1504m000), tfgld100 (Batches), tfgld203 (Ledger History, where period 0 is the balance brought forward), tfgld204 (Dimension History), tfgld008 (Chart of Accounts), tfgld010 (Dimensions), tfgld005 (Financial Periods, with period 13 for the year-end close) and tfgld011 (Transaction Types).

Integration. tfgld482 (Integration Transactions: debit and credit pairs sharing one GUID) and tfgld410 (Integration Transactions by Order: one row per logistic document posted to finance). These are what let you prove how a warehouse receipt or a production order hit the ledger.

Receivables, payables, cash and tax. tfacr200 (Customer Open Entries) and tfacp200 (Supplier Open Entries), both keyed by transaction type, document number, line and the matching document; tfcmg200 (Bank Transactions), tfcmg103 (Payment Batches), tfcmg101 (Payment Advice); tfgld126 (Tax Analysis); tfbgc150 (Budget Amounts).

Logistics and manufacturing. tdsls400/401/406 for sales orders and deliveries, cisli305/310 for sales invoices, tdpur400/401/406 for purchase orders and receipts, whinh310/312 and whinh430/431 for warehouse receipts and shipments, whinr110 (Inventory Transactions, the per-item stock ledger), whwmd215 (Inventory by Warehouse and Item), whltc100 (Lots), tisfc001 and tisfc010 for production orders and operations, ticst001 (estimated and actual material costs), tihra100 (Hours Accounting), tibom010 and tirou101/102 for production BOMs and routings, and tiedm100/110 for engineering revisions and as-designed BOMs.

Master data, projects and assets. tccom100, tccom110 and tccom120 for business partners and their sold-to and buy-from roles, tcibd001 (Items - General), ticpr007 (Item Costing), tppdm600 and tppss200 for projects and elements, tffam100, tffam200 and tffam250 for fixed assets, and tccom001 with bpmdm001 for employees.

Baan stores enumerated fields as numbers. ArchiveHub carries the labels exported from the Baan data dictionary in a clearly marked helper table, so a status reads as text in queries. Field names and descriptions are kept throughout.

Explore the demonstration

Finalized Transactions list in ArchiveHub Finalized Transactions: archived LN general ledger lines from tfgld106, filterable by company, period, transaction type and document. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Finalized transaction detail page in ArchiveHub Finalized Transactions detail: a single archived LN ledger document opened from the list. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Customer Aging Analysis in ArchiveHub Customer Aging Analysis: customer open entries from tfacr200 aged at the archive cutoff. ArchiveHub demonstration using mock data; not a native ERP screen or customer implementation.

Explore the report reference catalogue

These mappings identify intended business workflows, not certified one-for-one equivalents. Confirm availability, source coverage, filters, currencies, dates and calculations for the selected release and implementation.

General Ledger

  • Finalized Transactions: reference workflow: Finalized Transactions (tfgld3509m000) with its lines (tfgld1509m000)
  • Batches and Document History: reference workflow: Transaction batches (tfgld100) and Document History (tfgld1504m000), the audit trail of who created and finalized postings
  • Integration Transactions: reference workflow: Integration transactions (tfgld482 debit/credit pairs, tfgld410) from Warehousing, Manufacturing and Sales
  • Trial Balance: reference workflow: Print Trial Balance (tfgld3402m000)
  • Dimension Analysis: reference workflow: Print Trial Balance - Ledger Account/Dimension Combinations (tfgld3409m000) and Dimension History (tfgld204)
  • Budget versus Actual: reference workflow: Budget Amounts against ledger actuals per department
  • Reconciliation Analysis: reference workflow: the reconciliation and analysis of control accounts, covering subledger, GRNI, WIP, inventory and bank against the ledger

Accounts Receivable

  • Customer Open Entries: reference workflow: open entries by customer (tfacr200), sales invoices and their receipts
  • Customer Aging Analysis: reference workflow: the aging analysis of customer open entries (tfacr200) at the archive cutoff

Accounts Payable

  • Supplier Open Entries: reference workflow: open entries by supplier (tfacp200), purchase invoices and their payments
  • Supplier Aging Analysis: reference workflow: the aging analysis of supplier open entries (tfacp200) at the archive cutoff

Cash Management

  • Bank Transactions: reference workflow: Bank transactions (tfcmg200) per company bank account
  • Payment Batches: reference workflow: Payment batches and payment advice (tfcmg103, tfcmg101)

Tax

  • Tax Analysis: reference workflow: the tax analysis register by tax code and period (tfgld126), with settlements

Master Data

  • Business Partners: reference workflow: Business Partners (tccom100) with sold-to and buy-from roles
  • Chart of Accounts: reference workflow: Chart of Accounts (tfgld008)
  • Items - General: reference workflow: Items - General (tcibd001) with costing and inventory per company

Sales

  • Sales Orders: reference workflow: Sales Orders (tdsls4100m000) and Sales Orders - Overview (tdsls4500m000)
  • Sales Invoices: reference workflow: Sales invoices (cisli305, cisli310)

Procurement

  • Purchase Orders: reference workflow: Purchase Orders (tdpur400, tdpur401) with actual receipts (tdpur406)

Warehousing

  • Inventory Transactions: reference workflow: inventory transactions by item (whinr110) with running quantity, the per-item stock ledger
  • Inventory by Warehouse: reference workflow: inventory by warehouse and item (whwmd215) at the archive cutoff

Quality

  • Lot Tracing: reference workflow: Lots (whltc100), with origin, certificate and every movement, for aerospace traceability from supplier to customer

Manufacturing

  • Production Orders: reference workflow: Production Orders (tisfc0501m000) with material (ticst001), operations (tisfc010) and hours
  • Production BOM and Routing: reference workflow: the Production BOM (tibom010) and routing (tirou101, tirou102)

Engineering

  • Engineering BOM and Revisions: reference workflow: engineering item revisions and the as-designed BOM (tiedm100, tiedm110)

Shop Floor

  • Hours Accounting: reference workflow: hours accounting on production operations (tihra100), shop floor labor

Project

  • Projects: reference workflow: Projects (tppdm600) with element budgets (tppss200), actuals from ledger dimension 2 and project pegging of orders

Fixed Assets

  • Asset Master: reference workflow: the Asset Master and book data (tffam100, tffam200) with depreciation history (tffam250)

Human Resources

  • Employees: reference workflow: Employees - General and Employees - People (tccom001, bpmdm001)
  • Payroll by Department: reference workflow: the payroll interface register (customer module tzpay, since LN has no native payroll), tied to the ledger by department

Source documents stay attached

Document types below illustrate the intended scope. Include source attachments and external repositories explicitly, and test retrieval and record linkage before decommissioning.

The archive keeps documents with their records. Purchase orders, supplier invoices and customer invoices carry their PDFs; production orders keep their shop travelers; lots keep their certificates of conformity; business partners keep their onboarding files, assets and projects their approvals, and employees their HR letters. For an aerospace customer audit, the lot, its movements and its certificate are found together.

Beyond the reports

Confirm these capabilities, configuration requirements and limits during the demonstration and scope review; the report catalogue alone does not validate them.

  • Ad-hoc query builder across the configured archived LN tables, with LN field descriptions and suggested joins (tfgld106 to tfgld101 on transaction type and document; whltc100 to whinr110 on item and lot).
  • Retention rules and purge with approval, so HR and payroll data can expire while ledger, lot and program history stays for as long as contracts require.
  • Legal hold for warranty, product liability and contract disputes.
  • Personal-data governance: agree the lawful retention, access and deletion requirements with the responsible privacy and records teams. Product features alone do not establish regulatory compliance.
  • Access controls: define and test permissions for the required companies, records and sensitive fields. Do not assume that system-level roles reproduce the original ERP permissions, particularly for payroll and HR data.
  • OData feeds into Excel, Power BI and SAP Analytics Cloud.

How an LN or Baan decommissioning runs

  1. Extract the tables for every logistic and financial company in scope, with data dictionary descriptions and enum labels.
  2. Validate. Row counts per table, then balances that tie out: tfacr200 and tfacp200 to their control accounts, whinr110 and open production orders to inventory and WIP, tfgld482 integration pairs to tfgld106, and the trial balance to tfgld203 ledger history.
  3. Parallel read access for finance, quality, program and supply chain users while LN or Baan is still available.
  4. Retire after acceptance. Obtain documented sign-off for data reconciliation, document retrieval, user access, retention and legal holds, recovery and remaining integrations. Retire only the approved components; shared infrastructure may still be needed. End or reduce subscriptions, licences and support only where the contract permits. Budget for archive operation and any residual costs.

Questions about Infor LN and Baan retirement

Can LN and Baan report mappings be reused unchanged?

Treat them as candidates, not guaranteed equivalents. Confirm release, company structure, session behaviour and customisations against the installed system before accepting the mapping.

How should a lot-history workflow be accepted?

Select representative lots and follow their source, production and shipment relationships. Verify available quality documents separately and record gaps rather than inferring traceability from finance totals.

What does this ArchiveHub demonstration prove?

The screenshots illustrate how selected records can be presented using mock data. They do not prove production completeness, customer outcomes or parity with every Infor LN and Baan report. Request a demonstration against your own approved scope and acceptance cases.

Related retirement resources

For the broader project approach, see Legacy application retirement planning. To evaluate how users will find transactions, follow relationships and retrieve documents, explore archived data reporting. These resources complement this Infor LN and Baan-specific scope rather than replace source-system validation.

Evidence and further reading

The report catalogue and screenshots originate from an internal mock-data demonstration. They are not vendor certification or customer implementation evidence.

Use Infor documentation to locate the documentation for the installed release. This is a documentation entry point, not verification of every table or report mapping in this article.

Fixed-price Infor LN and Baan retirement engagement

ArchiveHub offers a fixed-price engagement for Infor LN and Baan retirement and historical data access, based on an agreed scope, deliverables and acceptance criteria. Request a scoped proposal covering your source systems, data, documents, reporting and validation requirements. The proposal should specify included services, exclusions, ongoing platform or hosting charges, and how scope changes will be handled.

Discuss your Infor LN and Baan retirement requirements with ArchiveHub

Infor LN and Baan are trademarks of their respective owners. ArchiveHub is not affiliated with or endorsed by Infor.