SAP transaction codeObjectIE03ModulePM_EAM

IE03 — Display Equipment Master Record

IE03 displays an equipment master record: technical data, location and cost center assignment, structure links to functional locations or superior equipment, classification and status. It is read-only. The confusion it generates almost always comes from its time-dependent segment: installation location, cost center and functional location assignment live in date-bound slices, so the same equipment number can show different assignments depending on the date being displayed.

Covers what IE03 shows and why its output depends on a hidden date parameter most consultants forget exists. Focuses on diagnosing missing data, wrong time slices, and classification gaps rather than repeating the screen layout.

Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 1,053 words

Purpose

IE03 is the display-only counterpart to IE01 (create) and IE02 (change) for the equipment master. It shows general data, the location and account assignment tab, the structure tab (superior equipment, functional location, bill of material links), classification, and status. The structural fact that explains most confusion: equipment master data splits between a header (fixed attributes like equipment category and object type) and a time-dependent segment carrying installation location, functional location assignment, cost center, and maintenance plant, each valid for a date range. IE03 always resolves to one time slice, usually today's, so a display that looks 'wrong' is frequently just showing the wrong period rather than bad data.

When it is used

Used constantly during incident triage: before creating a notification or order against a piece of equipment, a consultant checks IE03 to confirm current location, cost center, and functional location assignment, and to see whether the equipment is currently installed or in stock. Also used to review installation history when a breakdown pattern needs correlating with a location change, and to check classification values before running a technical object search. IH01 or IH03 is the better starting point when the equipment number is not yet known; IE03 is for when the number is already in hand and full detail is needed, including tabs that list views omit.

How to use it in practice

  • Enter the equipment number directly, or use the match code to search by material, serial number, or functional location.
  • Open the general data tab to confirm equipment category, object type, and deletion flag status.
  • Check the location tab for current installation location, functional location, cost center, and maintenance plant.
  • Open the structure tab to see superior equipment, sub-equipment, or bill of material assignment if relevant.
  • Check the classification tab for characteristic values if the object participates in measuring points or search by class.
  • Use the installation history function on the location tab when the question is about a past assignment rather than the current one.

Key data objects

  • EQUI - equipment header: internal equipment number, equipment category, object type, deletion indicator.
  • EQUZ - time-dependent segment: installation location, functional location, cost center, maintenance plant, valid-from and valid-to dates.
  • EQKT - equipment short text descriptions by language.
  • ILOA - location and account assignment data shared across equipment, functional locations, and orders.
  • JEST and JSTO - system and user status records linked via the object number.
  • AUSP and CABN - characteristic values and characteristic definitions assigned via the object's internal number and classification type.

How to prove it in the data

In SE16, pull EQUI filtered on the equipment number to confirm it exists and check the deletion flag. Then pull EQUZ for the same equipment number sorted by valid-from date, and check which row's valid-from/valid-to range brackets the date being questioned; this is the row IE03 actually displays. Cross-check the functional location and cost center fields in that row against ILOA if the location tab looks inconsistent. For status questions, take the object number from EQUI and filter JEST to see active status entries, cross-referencing against the status profile if a user status is expected but not showing.

ECC vs S/4HANA

IE03 exists on S/4HANA with no change to the underlying model; EQUI, EQUZ, and the status tables are unchanged. A Fiori app for viewing technical objects exists as an alternative front end and reads the same tables, but the GUI transaction remains fully usable and is still the faster path for consultants checking installation history or classification detail, since those views are not always exposed identically in the Fiori equivalent.

Common pitfalls and how to diagnose them

  • Equipment not found: usually a typo, a deletion flag set, or an authorization group on the equipment master restricting display by planning or maintenance plant. Check the deletion flag in EQUI before assuming a data problem, and check the user's authorization for the equipment's plant before assuming it does not exist.
  • Wrong time slice displayed: the equipment shows a location or cost center that does not match what the business expects because the visible EQUZ segment is not the one relevant to the incident date. Common after a dismantle-install cycle where the old assignment is still 'valid' in the system on paper for a date range that overlaps the query date. Always check the valid-from/valid-to on the EQUZ row before treating the field as wrong.
  • Missing classification values: the classification tab is empty or incomplete because no class is assigned, or characteristic values were never maintained after class assignment. Confirm via the classification tab whether a class exists at all before assuming the search by characteristic will work.
  • Structure tab shows no superior equipment or functional location: either the assignment was genuinely never made, or the equipment was created independently of a functional location and the link exists only through a maintenance order, not the master record itself.
  • Location fields blank on the location tab: equipment exists in stock, not installed anywhere, which is valid and not a data error; check the equipment's installation status before treating a blank functional location field as a defect.

Whose problem this is

Functional PM/EAM issue in almost every case: missing or incorrect master data, wrong time slice, authorization group setup. ABAP involvement is limited to custom fields or enhancements on the master record screens. A clean handover states the equipment number, the date being investigated, which tab shows the discrepancy, and the relevant EQUZ valid-from/valid-to range already checked.

Related SAP objects

Reviewed pages this object connects to in the ERPClimb knowledge graph.

Source: ERPClimb — https://erpclimb.com/sap-tcodes/ie03ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.