IL03 — Display Functional Location Master Record

IL03 opens the display view of a functional location, the object type used in Plant Maintenance to represent a fixed position in a technical or organizational hierarchy - a building, a production line, a measuring point, a system boundary. The record carries a structure indicator that defines the coding mask of the location's identifier, a superior location reference that places it in the hierarchy, plus organizational, classification and partner data. The structural fact that causes most confusion: the hierarchy visible in IL03 is only as correct as the superior-location field on each record. Nothing enforces that the technical hierarchy matches the organizational or cost hierarchy, and IL03 will happily display a location with no superior, or one whose superior was reassigned, without warning that reporting rollups above it are now broken.

IL03 is reached for whenever someone needs to confirm what a functional location actually is before creating a notification or order against it, before installing equipment at it, or before trusting a cost report that rolls up through it. It sits upstream of IW21/IW31 (notification and order creation reference the location) and downstream of IL01/IL02 (create and change). Consultants use IH01 instead when the task is browsing or restructuring the tree itself; IL03 is the tool for inspecting one record's full detail - classification values, partner assignments, address, status - which the tree view in IH01 does not show. It is also the fastest way to confirm whether a location exists at all when a user reports it missing from a search.

In SE16, pull IFLOT filtered on the functional location number (TPLNR) to confirm structure indicator, superior location, and plant assignment. Cross-check IFLOTX on the same object number for the description shown on screen. To confirm what equipment sits or sat at the location, query EQUZ filtered on the location field with the validity dates, since a blank result there - despite IL03 showing a location that looks populated - is normal and does not mean the location is faulty. Check JEST against the object number for any locking or deletion status before assuming the record is simply corrupt.

IL03 is unchanged in S/4HANA and remains available in the classic GUI alongside the newer Fiori-based functional location apps. The underlying tables and structure indicator logic are the same as in ECC. Organizations doing hierarchy cleanup or classification-heavy work increasingly use the Fiori manage functional locations app for bulk edits, but IL03 stays the fastest single-record display and is still the transaction most consultants reach for during ticket triage.

Functional PM/EAM consultant territory: hierarchy design, structure indicator setup, classification and partner assignment all belong here. ABAP is only involved for custom fields added to the location screen. Basis matters only for authorization object scoping. A good handover includes the functional location number, the specific tab where the discrepancy shows, and whether the issue is master data, hierarchy, or a downstream order/notification symptom.

IL01 and IL02 are the create and change counterparts and are the natural next stop when IL03 reveals a data gap. IH01 is the structure and hierarchy browser, useful for tracing superior-location chains that IL03 shows one link at a time. IE02 and IE03 cover the equipment side, needed whenever the question shifts from 'what is this location' to 'what is installed here.' IW21 and IW31 are where the location number gets consumed downstream in notifications and orders, worth reviewing to understand why a bad master record surfaces as a creation error there instead of in IL03 itself.