ILOA table — Location and Account Assignment for Technical Objects

ILOA holds one location and account assignment record per technical object, whether that object is a piece of equipment or a functional location. SAP separated this data from EQUI and IFLOT because equipment and functional locations share the same location and account assignment structure, so rather than duplicating the fields in both master tables, both point into ILOA through a shared internal key. A row in ILOA carries the organizational placement of the object: business area, cost center, controlling area, plant section, and, where relevant, the functional location it is installed at. It does not carry the equipment number or functional location description directly as its business key; those live in the calling tables. Changes made on the 'Location' or 'Account Assignment' tab of IE02 or IL02 update this table, not EQUI or IFLOT.

ILOA is client-dependent and grows to the size of the combined equipment and functional location population, so a select without restriction on ILOAN or on a derived join from EQUI or IFLOT will scan a large table. Never query ILOA standalone by cost center or business area expecting it to be selective; those fields have very low cardinality relative to row count and force a full scan. Always start from EQUI or IFLOT, filter to the object or object list first, then join into ILOA on ILOAN. There is no secondary index worth relying on for ad hoc access by KOSTL or GSBER alone.

Symptom: a maintenance order raised against a piece of equipment settled to the wrong cost center. Pull the equipment's ILOAN from EQUI for the equipment number and date range in question, then read ILOA on that ILOAN to see the cost center recorded on the master at that time. Compare it against the account assignment actually stored on the order (AUFK or the order's account assignment table), not against ILOA alone, since the order can carry its own overridden assignment independent of the master.

ILOA continues to exist in S/4HANA in the same role, still populated from IE02, IE01, IL01, and IL02, with no known compatibility view replacing it. Fiori app equivalents for equipment and functional location maintenance write to the same underlying structure through the same class-based master data logic that existed in ECC. Consultants working purely in Fiori should still expect ILOA, not a CDS view, as the underlying persistence for this data.

Location and account assignment data on technical objects is owned by the PM/EAM master data team, since it is maintained through equipment and functional location transactions. Cost center and controlling area validity is a joint concern with FI/CO, particularly when a cost center is blocked or a controlling area is restructured, since ILOA will still show the old value until the master record is manually corrected.

EQUI and IFLOT are the two master tables that reference ILOA through the ILOAN key and are maintained via IE01, IE02, IL01, and IL02. AFIH carries the equipment and functional location reference on maintenance order headers and is where the actual order-level account assignment override should be checked against ILOA's master default. Text and classification tables around EQUI and IFLOT are unaffected by ILOA changes and must be checked separately.