Technical structure and objects in SAP S/4HANA (functional location & equipment)

The technical structure is how SAP represents the physical world you maintain — what exists, where it sits, and how the parts relate. It is built from two core objects: the functional location (the place where maintenance happens) and the equipment (the individual object that is maintained), arranged in a hierarchy that carries cost assignment, history, and planning responsibility.

The two core objects

• Functional location. A business object that represents a place in your operation — a site, building, production line, zone, or position in a system. It is the stable reference point: equipment comes and goes, but the functional location remains, so the maintenance history of a location is preserved over time.
• Equipment. An individual, physical object that has to be maintained in its own right — a machine, vehicle, tool, measuring instrument, building-services unit, IT asset, and so on. Equipment can be installed into a functional location or into a higher-level (superior) equipment, and moved or dismantled later.

Building the hierarchy

Technical objects are arranged in a parent-child structure. Functional locations form a hierarchy (site → area → line → position), and equipment is installed underneath. A common pattern is a main equipment at the lowest location level with subordinate equipments beneath it.

Two things flow through that hierarchy:

• Cost assignment. Each object carries a cost center (and other organizational data such as planning plant, planner group, and main work center), so maintenance cost lands where it is caused.
• Inheritance. Subordinate objects can inherit organizational and reference data from the object above them, which keeps a large structure consistent without re-entering data on every node.

Why it matters

The technical structure is the foundation everything else hangs off. Notifications and orders are written against a functional location or equipment, so getting the structure right determines whether your maintenance history is meaningful, whether cost reporting is trustworthy, and whether planning responsibilities (planner group, work center) route correctly. It is the first master-data decision in any SAP EAM rollout — designed once at the right level of detail, neither too flat to be useful nor so deep it becomes unmaintainable.

Setting it up

Functional locations are created and maintained with transactions IL01 / IL02 / IL03, and equipment with IE01 / IE02 / IE03 (with Fiori equivalents in S/4HANA). Mass creation is typically done from templates and spreadsheet uploads rather than one record at a time. The structure indicator controls how functional-location labels are coded into hierarchy levels.

Common questions

What is the difference between a functional location and equipment? A functional location is a fixed place (it stays put); equipment is a moveable object installed at a place. History on the location survives equipment changes.

Can equipment be installed under other equipment? Yes — equipment can sit under a functional location or under a superior equipment, which is how main/subordinate equipment structures are built.

Why model functional locations at all if I have equipment? Because the location preserves history and cost continuity independently of which specific equipment is installed there at any given time.

---

Related: equipment master · maintenance notifications · SAP EAM scope items. Designing your S/4HANA Asset Management structure? Explore our SAP PM training.