IL02 — Change Functional Location

IL02 opens an existing functional location for change. A functional location represents a place in a technical hierarchy such as a plant, production line, or building wing, and it carries structural data, location data, account assignment data, classification, partner data, and status. The one fact that explains most confusion: the structure indicator assigned at creation determines whether the location identifier follows a hierarchical mask (parent-child string) or an unstructured edge-based numbering. IL02 cannot change the structure indicator itself, so any change that requires re-parenting a functional location under a different branch of the hierarchy is often not a simple field edit inside IL02 but requires a dedicated reclassification or reorganization step, and users who try to force it by editing the superior location field alone get inconsistent results.

IL02 is reached whenever an existing functional location needs a data correction that does not warrant recreating the object: a new cost center, a changed maintenance planning plant, an updated address, a status change, added classification characteristics, or a partner reassignment. It sits downstream of the initial technical hierarchy build (IL01) and upstream of equipment installation, notification, and order creation, since orders and notifications inherit account assignment and location data from the functional location at the time they are created. Consultants reach for IL02 rather than IH01 (structure display) when an actual field change is needed rather than just navigation; IH01 is used to find the location first when the number is not known. On Fiori-enabled systems the equivalent app is used for the same purpose but the underlying object and constraints are identical.

To confirm a functional location's current master data, pull IFLOT filtered on the functional location field (TPLNR) and check structure indicator, superior location, and planning plant. To confirm the account assignment actually in effect, join on the ILOA key stored against that functional location and compare cost center and business area with what the change history shows. To confirm a status change actually posted, check JEST for the object with the relevant status profile and compare the active status against what the user reports seeing on screen; a mismatch usually means the change was made but not saved, or was saved against a different functional location number than the one being viewed.

The transaction itself is unchanged in S/4HANA and remains fully supported. A Fiori app exists for managing functional locations for organizations that have moved maintenance staff to the Fiori launchpad, but the underlying object model, structure indicator behavior, and account assignment rules are identical to the classic transaction. There is no structural change to the functional location object between ECC and S/4HANA that affects how IL02 behaves.

This is functional PM/EAM territory, owned by the plant maintenance or asset management configuration team, since the recurring issues are hierarchy design (structure indicator) and authorization rather than code. A good handover includes the exact functional location number, the field that failed to save, the exact error or warning text, and whether open orders or equipment exist under that location. ABAP involvement is rare and limited to custom validation logic on save, if any exists.

IL01 and IL03 are the create and display counterparts and should be read alongside IL02 to understand what can and cannot be edited after creation. IH01 is the structure display used to locate a functional location within the hierarchy before switching to IL02 to change it. IE02 and IE03 are the equipment-side change and display transactions, relevant because equipment installed under a functional location inherits location and account assignment data that IL02 changes affect. IW21, IW22, IW31, and IW32 are worth reviewing to understand how notifications and orders consume the functional location's current master data at creation time.