IL01 — Create Functional Location
IL01 creates a functional location master record, the fixed point in a technical hierarchy where equipment is installed and maintenance work is planned. It captures the location label, structure indicator, organizational data (plant, planning plant, cost center) and the superior functional location link. The label's format and the superior location field are maintained independently, which is the main source of hierarchy inconsistencies.
This page covers IL01, the transaction for creating functional location master data in Plant Maintenance and Enterprise Asset Management. It focuses on the gap between label structure and the actual superior-location link, the tables the save writes, and the failure patterns that show up later as broken hierarchies, blocked order creation, or classification errors.
Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 1,119 words
Purpose
IL01 creates a functional location, the master record representing a fixed technical position in a plant structure, as opposed to equipment, which represents the physical item installed there. Each functional location gets a label built according to a structure indicator that defines how many hierarchy levels the label encodes and what characters separate them. The structural fact that causes most confusion: the hierarchy shown in structure reports is driven by a separate superior functional location field, not purely by parsing the label string. A label can look nested (matching its parent's prefix) while the superior field points somewhere else entirely, or vice versa. IL01 lets both be set independently, and nothing forces them to agree.
When it is used
IL01 sits at the start of technical object structuring, typically during plant commissioning, a new production line build, or extension of the maintenance hierarchy to a new area. A consultant reaches for IL01 when creating a single location manually with full control over structure indicator, class assignment and organizational data. For bulk creation, LSMW, a BAPI-based load, or a Fiori app for managing functional locations is used instead, since IL01 has no mass-upload mode. Compared to IE01, IL01 is used when the object is the fixed installation point rather than the physical asset, and when the object needs to persist even after the equipment installed at it is exchanged.
How to use it in practice
- Call IL01 and enter the functional location label, either typed directly or generated against a reference structure indicator template
- Select the object category (for example technical or maintenance object) that determines which screens and fields apply
- On the general data screen fill plant, maintenance planning plant, cost center and other organizational assignments
- On the location and organization tab, explicitly set the superior functional location field, do not rely on the label alone to establish the hierarchy link
- Maintain classification data if the category requires characteristics, and check status defaults before saving
- Save and confirm the location appears correctly in a structure list, not just as an isolated record
Key data objects
- IFLOT - the functional location master record itself: label, structure indicator, category, superior functional location, plant and planning data
- IFLOTX - long text and additional description entries linked to the functional location
- ILOA - shared location and account assignment table used by functional locations, equipment and orders; holds the account assignment and location data actually referenced by orders and notifications
- JEST and JSTO - object status management, tracking the current and history of status values (created, deletion flag, locked)
- Classification tables (class assignment and characteristic value tables) - populated when the object category requires characteristics
How to prove it in the data
In SE16 on IFLOT, filter on TPLNR for the label and pull STRNO and the superior functional location field for that record. Compare the superior field's value against what the label's leading segments imply under the structure indicator's coding rules; a mismatch confirms a broken hierarchy link even though the record displays fine in isolation. Cross-check ILOA on the same TPLNR for the organizational and account assignment values that downstream orders and notifications actually inherit, since those come from ILOA, not directly from IFLOT.
ECC vs S/4HANA
The functional location data model is unchanged on S/4HANA; IL01 still writes IFLOT, IFLOTX and ILOA the same way. A Fiori app for managing functional locations is available for display and edit scenarios and is commonly used by non-key-user roles, but structural creation involving structure indicator design is still normally done through the classic transaction. There is no functional redesign of the hierarchy mechanism to be aware of.
Common pitfalls and how to diagnose them
- Structure indicator mismatch - the label entered does not conform to the length and separator rules of the chosen structure indicator, producing a save error or, worse, a label that saves but sorts incorrectly in every hierarchy report; check the structure indicator's definition before troubleshooting the record itself
- Superior location out of sync with the label - the label suggests one parent but the superior functional location field points to another or is blank; this shows up as an object missing from its expected branch in a structure list while still existing as a standalone record; always check the superior field directly rather than trusting the label's appearance
- Missing organizational data - planning plant or maintenance planning plant left blank at creation surfaces later as an inability to create a maintenance order or notification against the location, with an error that does not obviously point back to IL01
- Status blocking - a deletion flag or locked status set on the functional location silently blocks equipment installation or order creation with a generic authorization-looking error; check JEST for the object before assuming a permissions problem
- Classification save failures - a required characteristic left empty causes a save error that reads as a classification problem but is really a configuration mismatch between the object category and the class assigned to it
- The common reflex fix that makes it worse: deleting and recreating a functional location under the same label to force the hierarchy to look right. This orphans installation history in the equipment-to-location link and breaks any order or notification history that referenced the old internal record; correcting the superior field or the structure indicator assignment on the existing record is almost always the safer path
Whose problem this is
This is a functional PM/EAM consultant's object: structure indicator design, category selection and hierarchy layout are functional decisions. Basis involvement is limited to plant and planning plant authorization objects. ABAP gets involved only if customer-specific fields have been added to the functional location screens. A good handover states the label, the structure indicator used, the intended superior location, and whether the issue is a save error or a hierarchy display error.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/il01ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.