Infor LN & BaanFree generatorPDF, Excel, Word exportInfor LN

Infor LN Table Name Builder (Logical to Physical SQL Name)

Infor LN and Baan show tables as logical names such as tcibd001, but the database stores them with a prefix and a company suffix. This builder converts a package, module, table number and company into the physical table name and gives you ready read-only SQL to start from.

Fill in

Package (2 letters)

Module (3 letters)

Table number (3 digits)

Company number

Database schema or owner

First column

Second column

Generated code

Download:

Name parts

-- Logical table : tcibd001
-- Package       : tc
-- Module        : ibd
-- Table number  : 001
-- Company       : 100
-- Physical table: ttcibd001100
-- Column pattern: t_<fieldname>

Sample read-only SELECT

SELECT t_item, t_dsca
FROM baandb.ttcibd001100
ORDER BY t_item;

Row count check

SELECT COUNT(*) AS row_count
FROM baandb.ttcibd001100;

LN physical tables are the logical name prefixed with t and suffixed with the three digit company number, and fields are prefixed t_. Defaults use tcibd001 (items) as an example, so check column names such as item and dsca in your data dictionary. Case, schema name and quoting depend on your RDBMS and driver. Run read-only queries against a reporting copy rather than production, and never write to LN tables directly, use the DAL or BDE.

Read-only LN reporting layer

Optional: see how table and enum mapping can be handled for you in a natural-language layer.

Optional. The tool and every export work without this. No spam.

How to use the builder

Enter the package and module letters, the three digit table number and the company number, plus the schema name your DBA uses. The first block shows each part and the resulting physical name. The second and third blocks give a SELECT and a row count you can paste into your SQL client. Fill the column fields with the logical field names, without the t_ prefix, and the builder adds it for you.

The naming convention

A logical LN table is five letters plus three digits: the first two letters are the package, the next three the module, and the digits the table within the module. In the database the name becomes a leading t, then the logical name, then the company number, so tcibd001 for company 100 is ttcibd001100. Fields are stored with a t_ prefix, for example t_item. LN tables also carry reference counter columns such as t_Refcntd and t_Refcntu that you normally ignore in reports.

Package plus module equals the five letter module code
Company number is part of the physical name
Enumerated fields store numbers, not text, so map them in reports

Common mistakes

People query the wrong company by forgetting the suffix, or assume enumerated fields hold text when they hold a numeric code that must be translated with the domain definition. Others run heavy reports on the production database during business hours or try to update LN tables directly, which bypasses business rules and the DAL and can corrupt data. Use a reporting copy, filter on indexed fields, and use supported interfaces for any write.

Frequently Asked Questions

What is the physical name of tcibd001 in the database?

It is t, then the logical name, then the company number. For company 100 that is ttcibd001100. The company suffix means each LN company has its own copy of the table.

Why do LN columns start with t_?

It is the database naming convention for LN fields. The logical field item in table tcibd001 is the column t_item in the physical table. Use the logical name in tools and add the prefix in SQL.

Can I update LN tables with SQL?

You should not. Direct updates skip the DAL, validations and reference counters and can leave inconsistent data. Use the supported interfaces such as DAL based sessions, BDE or integration objects, and keep SQL for reading.

Where do I find column names and enum values?

In the Tools data dictionary of your LN environment: table definitions list fields and domains, and domain definitions list enumerated values with their numeric codes. Check there rather than relying on generic documentation.

If your analysts keep translating LN table names and enums by hand, we can show how a natural-language layer over a read-only copy of LN answers it directly.

Talk to an Expert Explore More Free Tools

Related Tools

Infor LN & Baan

More Infor LN & Baan tools

See all

Back to All Tools