IH01 — Functional Location Structure Display

IH01 renders the technical object hierarchy - functional locations nested under other functional locations, with equipment installed at various points in the tree - as a single expandable structure. It exists because functional location master display (IL03) and equipment master display (IE03) only show one object plus its immediate parent; IH01 shows the whole plant or system context at once. The structural fact that explains most confusion: IH01 is a display and navigation tool, not the master transaction. It reads the hierarchy as of a chosen key date, and equipment installation records are time-sliced. An object that is not visible in the tree is very often correctly assigned but outside the date window being queried, rather than actually missing or misassigned in the master data.

IH01 is reached for whenever someone needs to see structure rather than a single record: confirming where a piece of equipment sits before raising a notification or order, checking that a new functional location was created under the correct parent, or scanning a plant section for orphaned or duplicated equipment before a mass change. It is used instead of IL03 or IE03 when the question is about position within the hierarchy, not the content of one master record. It is used instead of a Fiori hierarchy app when speed matters more than a modern UI - IH01 can select and expand a large plant tree in one shot, which is still faster for bulk visual scanning than most app-based equivalents, even on S/4HANA.

To confirm a missing-node symptom, pull EQUZ for the equipment number in question and look at the installation start and end fields for that functional location assignment; compare that range against the key date used in the IH01 selection screen. If the equipment's valid installation record does not cover the key date, that is the whole explanation - no data is broken. Separately, check IFLOT for the functional location's superior functional location field to confirm the parent actually matches what the tree is expected to show, and rule out a typo in the structure indicator being used for selection.

IH01 is still available and functions the same way on S/4HANA; the underlying tables and the time-dependent installation logic in EQUZ are unchanged. SAP's Fiori catalog offers app-based alternatives for browsing technical object hierarchies, but many teams continue to use IH01 for bulk structural review because it handles large trees and mixed functional-location-plus-equipment selections in one screen more efficiently than app-based navigation. No functional behavior of the classic transaction was removed.

This sits with the PM/EAM functional team, usually the master data or maintenance planning group that owns functional location and equipment structuring. Basis involvement is limited to genuine performance timeouts on very large selections. A good handover includes the exact selection screen used (starting object, structure indicator, key date), a screenshot of the tree branch in question, and the expected parent-child relationship so the receiving analyst does not have to reconstruct the selection from scratch.

IL03 and IE03 are the natural next stops to inspect a single functional location or equipment master once it has been located in the IH01 tree. IL02 is where superior functional location reassignments are actually made, since IH01 only navigates there. IW28 and IW29 are useful once an equipment or functional location has been identified, to check what open notifications already exist against it before raising a new one.