IFLOTX table — Functional Location Description Text Table

IFLOTX is the text table attached to the functional location master table. One row represents the description of a single functional location in a single language: the functional location number and language key form the key, and the text field carries the short description that appears next to the functional location number everywhere in PM (order header, notification, IL03 display, most standard PM lists). It does not hold long text, classification data, structure indicators, or any of the technical attributes of the functional location itself - those live in the master table. If a functional location was created and a description typed in at that point, exactly one row normally exists, in the creation language. Additional rows appear only if someone explicitly maintains the description in another language, which in practice is rare outside multi-language rollouts.

MANDT first, always. After that, TPLNR is the natural restriction - the table is not large in absolute terms compared to movement or transaction tables, but it is still a full outer join risk if selected without a TPLNR range on a big installed base. SPRAS is the second most useful restriction; most shops effectively run in one or two languages, so filtering to the relevant SPRAS before joining avoids pulling duplicate description rows for the same functional location. Never assume a row exists for every TPLNR - absence of a row in the requested language is normal, not corruption, and code that does an inner join on IFLOTX will silently drop functional locations that have no description in that language.

Symptom: a functional location shows blank description in a report but has a description on screen in IL03. Select IFLOTX with TPLNR equal to the functional location and no SPRAS restriction. If a row exists only for a language other than the one the report runs in, the report's join is filtering on the wrong SPRAS, not a data gap. If no row exists at all for that TPLNR, the description was never entered in any language and the master record genuinely has no text.

IFLOTX continues to exist in S/4HANA as the standard text table for functional location descriptions; the master data model for functional locations was not restructured in the move to S/4HANA the way some other PM objects were. Reporting increasingly goes through CDS-based views that already resolve the description in the session language, so consultants writing new Fiori-based extracts are less likely to touch IFLOTX directly, but any classic ABAP report, custom program, or interface built against the older PM data model still reads it exactly as before.

Functional location descriptions are PM master data and sit with the plant maintenance functional consultant or master data team responsible for the technical object hierarchy, not with a basis or ABAP owner. A missing or wrong description in one language is a master data maintenance issue to raise with whoever owns functional location creation standards, not a table structure defect.

IFLOT is the functional location master table this text table hangs off. ILOA carries location and account assignment attributes for the same TPLNR. EQUI and EQUZ carry equipment master and equipment time-segment data, relevant when an equipment installed at the functional location needs its own description resolved through EQKT, the equipment's analogous text table. IL01, IL02, and IL03 are the transactions that create, change, and display functional locations and are the normal write path into IFLOTX; direct table maintenance outside those transactions is unsupported practice.