Infor LN Database Growth by Table Calculator
This calculator projects how much the high-volume transaction tables of Infor LN 10.x grow each year from your sales, purchase and production volumes. It covers sales order lines, purchase order lines, production orders, inventory transactions and finalized finance transactions, which together usually explain most of the growth.
Your numbers
Rows in tdsls401.
Rows in tdpur401.
Rows in tisfc001.
Rows written to whinr110 per sales line, purchase line or production order (receipts, issues, transfers).
Rows written to tfgld106 per sales line, purchase line or production order, from integration postings and invoices.
Assumption. Measure it from your database for these tables.
Total table plus index space divided by data space.
Companies with similar volume. For uneven companies, run the calculator per company.
Your results
Rows per order line and row size are assumptions; LN writes to many more tables than the four modelled here. Calibrate against row counts and sizes measured in your own database.
Cumulative growth (GB) over years
Sweeps Years from 1 to 10, holding your other inputs fixed.
Get a reviewed growth and archiving plan
Send us row counts for one closed year and we will review growth and an archiving order for your LN companies.
Optional. The tool and every export work without this. No spam.
Tables modelled and why
Most LN data growth comes from transactions, not master data. Each sales order line is a row in tdsls401 and each purchase order line a row in tdpur401; production orders live in tisfc001. Each of these generates several inventory transactions in whinr110 (inventory transactions by item and warehouse) and several finalized finance transactions in tfgld106. The physical table name adds the company number, so tdsls401 in company 100 is ttdsls401100 in the database.
- tdsls401: sales order lines
- tdpur401: purchase order lines
- tisfc001: production orders
- whinr110: inventory transactions by item and warehouse
- tfgld106: finalized transactions (general ledger)
How to measure your real row size and ratios
Do not keep the 1,200 byte default. On SQL Server run sp_spaceused on ttdsls401100, twhinr110100 and ttfgld106100 and divide data size by row count; (data + index_size) divided by data gives the index factor. On Oracle, compare USER_SEGMENTS bytes for the table and its indexes with the row count from statistics. For the per-line ratios, count rows in whinr110 and tfgld106 for one closed year and divide by the order lines of the same year. Those two ratios drive most of the result, so measure them first.
Worked example
With the defaults, 215,000 order lines and production orders per year create 645,000 whinr110 rows and 1,290,000 tfgld106 rows, about 2.15 million rows in total. At 1,200 bytes and an index factor of 1.6 that is about 4.1 GB per year for one company, and about 20.6 GB after five years. Finance postings are 60 percent of the rows, which is typical when integration postings are detailed per transaction.
Which tables to archive first
Look at the biggest growers in your own measurement, usually tfgld106 and whinr110, then at history tables of sales and purchase. LN has archiving sessions per package that move closed data to an archive company and keep integrity; use them rather than deleting rows in SQL, which breaks reference counters and audit trails. Before archiving finance, confirm retention rules with your auditors and the fiscal periods that must stay online for reporting.
Frequently Asked Questions
Where do I find the full Infor LN table list and data dictionary?
Use the table definition sessions in LN Tools (Application Development, under the package VRC) or the table definitions published on docs.infor.com and in Infor's LN table reference documents for your release. Tables are named by package and module, such as tdsls for sales or whinr for inventory reporting.
Why is tfgld106 so large?
tfgld106 holds finalized general ledger transactions. Every integration posting from sales, purchase, warehousing and production lands there after finalization, often several lines per business transaction. Detailed integration mapping and frequent finalization runs increase its row count. It is usually the first finance table to consider for archiving.
Does the company number change table names?
Yes. In the database the logical table code gets a 't' prefix and the company number suffix, so whinr110 in company 100 is twhinr110100. Shared tables via logical table linking are stored once in the physical company, so do not count them for each logical company.
Is this growth estimate accurate?
It is a planning model with five tables and averaged ratios. It is accurate when you replace the defaults with ratios and row sizes measured from one closed year in your own database. Add a margin for other tables, audit trails and temporary tables.
If you want people to ask LN questions in plain English against these tables without writing SQL, we can set that up on your own servers.
Related Tools
Infor LN Bshell Application Server Memory and CPU Sizing Calculator
Estimate peak bshell count, RAM and CPU cores for an LN 10.x application server from your own measured bshell memory and concurrency.
Infor LN & BaanInfor LN and Baan ERP Table List by Package
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.
Infor LN & BaanInfor LN SQL Query Generator
Fill in the table, company number and key range to get read-only SQL for the LN database, with the physical table name built for you.
Infor LN & BaanBaan IV to Infor LN Data Copy Downtime Calculator (bdbpre/bdbpost)
Plan the downtime window for a bdbpre/bdbpost data copy from your measured throughput, parallel table lists and reorganize time.
More Infor LN & Baan tools
See all- Infor LN Session and Module Code Reference
- Infor LN Production Order Status and Lifecycle Reference
- Infor LN 4GL Session Script Template
- Infor LN Company and Enterprise Unit Design Worksheet
- Infor LN DAL Hook Review Checklist
- Infor LN Warehousing Order Origins and Types Reference
- Infor LN Table Name and SQL Query Builder
- Infor LN Regression Test Effort Calculator
- Infor LN and Baan Customization Inventory Worksheet
Keep exploring
Free tools
- Infor LN SQL Query GeneratorFill in the table, company number and key range to get read-only SQL for the LN database, with the physical table name built for you.
- Infor LN Integration Methods ReferenceA comparison table of the main ways to move data in and out of Infor LN, with typical use, direction and cautions.
- Infor LN AI Assistant Sizing and Value CalculatorSize the GPUs and estimate the monthly value and payback of a private, on-prem AI assistant for Infor LN.
ERP fixes and how-tos
- Infor LN General Table Maintenance: Finding and Editing Tables SafelyWhere general table maintenance sits in Infor LN, how to find the right session for a table, and how to change table data safely, no direct DB edits.
- How to close a financial period in Infor LNClose a financial period in Infor LN: process outstanding integration transactions, reconcile subledgers, run period-end reports, then close in Periods and Fiscal Years.
- Infor LN error 205: how to diagnose and fix itDiagnose Infor LN error 205: common triggers, the log and bshell trace to check, how to find the table and record involved, and a safe fix sequence.
Guides
- Extending Standard Infor LN Tables: Developer GuideExtend standard Infor LN tables safely with custom fields, triggers, and validation logic. Avoid upgrade conflicts with proven extension patterns for BAAN/LN.
- Infor LN Support: Alternatives When Infor Cannot Help Fast EnoughFrustrated with Infor LN support response times? Explore alternative support options including consultants, user groups, and AI-powered assistance.
- Infor LN Performance Tuning GuideTune Infor LN for optimal performance. Database optimization, session server tuning, batch processing acceleration, and bottleneck diagnosis.
AI on your ERP
- AI for Infor LN: Sessions, BODs, and Engineer-to-Order WorkAdd grounded AI to Infor LN 10.x or CloudSuite: natural-language answers over sessions and BODs, agents for project and engineer-to-order work, on-prem options.
- AI for Infor LN in Aerospace and Defense ManufacturingAI grounded on Infor LN project, contract, and configuration management data for aerospace and defense manufacturers, with on-prem deployment for ITAR.
Integrations
- How to connect Power BI to Infor LNHow to connect Power BI to Infor LN: direct database, ION and Data Lake options, on-prem data gateway, key manufacturing dashboards and adding natural-language Q&A.
- How to add AI agents to Infor LNHow to add AI agents to Infor LN: a tool layer over ION API and BODs, read-only reporting first, approval before writes, and fully on-prem model hosting.