How-toInfor LNTools / Common Data / Table Maintenance

Infor LN General Table Maintenance: Finding and Editing Tables Safely

Question
infor ln general table maintenance

Also searched as

  • general table maintenance infor ln
  • infor ln edit table data
  • infor ln find session for table
  • infor ln maintain table contents

Short answer

LN code and data tables are named by package and module (for example tc for Common, td for Distribution, ti for Manufacturing), and nearly every table has a maintenance session. Find the session that owns the table, edit through it so validation and audit apply, and avoid direct SQL updates except under a controlled procedure.

Applies to: Infor LN 10.x and Baan 5 style data dictionaries. Session codes depend on your release and installed packages.

How to find and change table data

  1. 1Identify the table code. LN table names follow a pattern of package, module and number, such as a tc table for common data.
  2. 2Use the Web UI session search or the Tools data dictionary sessions to find which session maintains that table.
  3. 3Open the session in a test company first and check the fields, domains and any dependent tables.
  4. 4Make the change through the session so LN runs its validation, authorization and audit logic.
  5. 5For bulk changes use an import or a documented conversion program, not manual edits.
  6. 6Record who changed what and why, and move the change through test, acceptance and production.

How LN names tables and sessions

Tables carry a package prefix, a module code and a number. The package tells you the area, so a tc table is shared master data and a td table belongs to distribution. Sessions follow the same pattern with a suffix that indicates the type, for example a maintain or display session.

The data dictionary in Tools lists tables, fields and domains, and cross references to the sessions that use them. It is the reliable way to answer which session edits this table.

Why not edit the database directly

Direct updates skip validation, dependent records, authorizations and audit. LN also keeps its own logic about companies and table sharing, so a direct update in one company table can silently miss another. For read-only investigation a query is fine. For writes use the application.

If a vendor or consultant proposes a direct fix, ask for a backup, a test run and a rollback plan before you agree.

Safe-change practices

Change in a test company first, take a copy of the affected rows before and after, and keep a short change log. Check the effect on running transactions: changing a code used by open orders can leave inconsistent documents. Schedule risky changes outside business hours.

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.

Common pitfalls

  • !Updating tables with SQL because it is faster.
  • !Editing production data without a test run.
  • !Forgetting that table sharing means a change can affect several companies.
  • !Changing codes used by open orders.

How an ERP-grounded AI assistant handles this

An AI assistant over the LN data dictionary can answer which session maintains a table and which fields reference it, and can read table data without write access. Netray's agents stay read-only by default; any change is a proposal for a human to execute through the normal session.

Frequently asked questions

How do I find which session maintains a table?

Use the data dictionary in Tools to see where the table is used, or search sessions by the package and module of the table code. Then open the maintain session.

Is it ever fine to update LN tables with SQL?

Only under a controlled procedure with a backup, a test run and agreement from the application owner. For normal changes use the session.

What does the tc prefix mean?

It marks the Common package, which holds shared master data such as items and business partners.

How do I change many records at once?

Use an import session or a conversion program with validation, tested in a non-production company.

Related

How-to

Infor LN item sales session, item purchase session and site data: where each lives

In Infor LN the item master is split by business function. General data sits in the Items - General table (tcibd001), sales data in Item - Sales (tdisa001) and purchase data in Item - Purchase (tdipu001). Site-dependent data such as ordering and planning parameters is held per item and site, so one item can behave differently in each site.

How-to

Conversion Factor Session in Infor LN: Setup and Common Errors

Infor LN converts between units using conversion factors, either general factors between units of the same physical dimension or item-specific factors that override them. When an item is bought in one unit and stocked in another, LN needs a factor for that pair. A missing factor is the usual cause of a conversion error on purchase orders, receipts or sales lines.

Error fix

DB Error 100 in Infor LN and Baan: Record or End of Set Not Found

DB error 100 in Infor LN and Baan is a not-found condition from the database layer: a read, find or next-record operation found no record matching the key, or reached the end of the result set. It is often harmless control flow in well-written 3GL code, but it becomes a visible error when a script does not test for it.

Error fix

Infor LN bshell Process Stuck at 100% CPU: How to Diagnose and Fix It

A bshell process pinned at 100% CPU on the Infor LN application server almost always means one session is stuck in a 4GL loop, scanning an unindexed table, or waiting on a database lock. End the session from the Sessions Monitor first, then kill the OS process only if that fails, and check for a blocking database transaction before assuming it is a bug.

Error fix

Infor LN Not Authorized to Run This Session: How to Fix It

Infor LN refuses to open a session with a not authorized message when the logged-in user's assigned role does not include that session, or when the session is blocked for the company they are logged into. Grant the session through Common > Authorization Management > Roles, or check the user's role and company context, and the session opens on retry. In most cases this is a permissions configuration issue, not a bug.

Error fix

Infor LN DAL Out of Sync After a Custom Field: Cause and Fix

Infor LN throws a DAL, or table, out of sync error, or simply drops a new custom field silently, when a table's dictionary definition is changed but the generated DAL and dependent forms are not regenerated afterward. Running the standard sequence, table compile, DAL generation, then session/form compile, in Tools > Development after every dictionary change resolves it. Skipping any one of the three steps is what causes the mismatch.

AI for ERP

AI for Infor LN: Sessions, BODs, and Engineer-to-Order Work

Add 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 ERP

AI for Legacy Baan IV/V: Capture the Knowledge Before It Walks Out the Door

Use AI to capture knowledge from ageing Baan IV/V systems, document undocumented customisations, and de-risk a future migration to LN or CloudSuite.

Stuck on Infor LN?

Talk to engineers who work inside Infor LN every week, and who build private AI that answers these questions from your own ERP data.

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

Guides

AI on your ERP

Integrations

Comparisons

Software