IE01 — Create Equipment Master
IE01 creates an equipment master record, the standalone technical object used to track a physical asset (pump, vehicle, motor) through its maintenance life. The structural fact that causes most confusion: equipment category is fixed at creation and cannot be changed later, and the installation link to a functional location is stored as a separate time-dependent record, not as a permanent attribute of the equipment itself.
This page covers IE01, the transaction for creating equipment master records in Plant Maintenance and Enterprise Asset Management. It focuses on the entry sequence, the tables the save actually writes, and the recurring diagnostic failures around category lock-in, duplicate creation, and time-dependent installation data.
Reviewed by an ERPClimb SAP consultant on 15 Sept 2026· 1,117 words
Purpose
IE01 creates an equipment master, a technical object representing a physical, individually tracked asset with its own number, maintenance history, warranty and (optionally) serial number. Equipment is deliberately independent of functional location: the equipment record itself carries organizational data (plant, cost center, company code) while the physical installation position is stored as a separate, time-sliced record. This separation is the single fact behind most equipment confusion — an equipment record can exist perfectly validly with no current installation, or with an installation history that does not match what the equipment master's own valid-from date suggests. Equipment category, chosen on the initial screen, fixes the field selection and screen layout for the object's lifetime and cannot be changed after save without a formal category conversion, which is not part of this transaction.
When it is used
IE01 is used whenever a physical, individually identifiable asset needs its own maintenance history separate from the location it sits in — a pump that gets swapped between skids, a vehicle, a rotable spare. It is reached for during initial master data load, when a newly purchased or commissioned asset arrives, or when a serialized spare part is dismounted and needs to be tracked independently going forward. It is not used for objects that never move and never get individually tracked — those stay as functional location attributes only. On S/4HANA a Fiori app exists for creating and managing technical objects, but IE01 remains common for detailed or bulk entry, especially during data migration or when copying from a reference equipment.
How to use it in practice
- Select the equipment category on the initial screen; this cannot be changed after save
- Optionally enter a reference equipment or use 'copy from' to prepopulate class, characteristics and organizational data
- Enter a description and the valid-from date for the equipment record
- On the Location tab, set functional location, maintenance plant, planning plant and planner group if known at creation
- On the Organization tab, set company code, business area and cost center
- On the Structure tab, set a superior equipment if this object is installed inside another piece of equipment
- Save; the system assigns the equipment number (internal number range) or accepts the number entered (external range)
Key data objects
- EQUI - equipment master general data: equipment number, category, valid-from and valid-to dates
- EQUZ - time-dependent installation data: functional location assignment, superior equipment, installation and de-installation dates as time slices
- ILOA - location and account assignment: plant, maintenance plant, cost center, business area, valid for the location record referenced by the equipment or its installation slice
- EQKT - short text and long text for the equipment description in multiple languages
- Classification tables (if a class was assigned at creation) linking the equipment number to class and characteristic values
How to prove it in the data
Start in SE16 on EQUI filtered by equipment number to confirm category and that valid-to date is 31.12.9999 (active record). Then query EQUZ on the same equipment number to see every installation time slice — look for gaps, overlaps, or a slice with no functional location, which explains why an order or notification pulled the wrong location. Cross-check ILOA using the location key referenced from the relevant EQUZ or EQUI record to see the plant and cost center that were actually assigned at that point in time, not the current one.
ECC vs S/4HANA
The underlying data model for equipment (EQUI, EQUZ, ILOA) is unchanged on S/4HANA. A Fiori app exists for creating and managing technical objects with a more guided layout, but IE01 is still fully supported and is generally preferred for bulk creation, copy-from workflows, or data migration where field-level control matters. No category, numbering, or installation-history behavior changed between ECC and S/4HANA.
Common pitfalls and how to diagnose them
- Category locked in - the category chosen on the initial screen cannot be edited afterward. If the wrong category was picked, IE01 gives no way back; the object needs a formal category conversion or a new equipment record and manual history transfer. Check EQUI-EQTYP before assuming the record can simply be corrected.
- Duplicate equipment for the same physical asset - technicians create a new equipment record instead of searching for an existing one, usually because serial number or manufacturer data was not checked first. Search EQUI (or the equipment list) by serial number and manufacturer part number before creating; duplicates fragment maintenance history across two equipment numbers.
- Installation history gaps or overlaps - the equipment's own valid-from date does not align with the first EQUZ installation slice, so orders and notifications inherit no location, or inherit a stale one. Diagnose by listing EQUZ rows chronologically and checking for missing or overlapping date ranges.
- Organizational data mismatch - cost center, plant or business area entered on the Organization tab does not match the user's authorization or the intended settlement object, surfacing later as settlement or authorization errors on orders raised against the equipment. Confirm ILOA values against the intended maintenance and planning plant before the record goes live.
- Conflict with automatic equipment creation - if the material is serial-number managed with an equipment-creation profile, equipment gets created automatically at goods movement, and a parallel manual IE01 creation produces a second, unlinked record. Check the material's serial number profile before manually creating equipment for a serialized part.
Whose problem this is
This is a functional PM/EAM consultant's transaction end to end; ABAP involvement is limited to custom fields added through user exits or enhancement spots on the equipment screens, and Basis is only relevant for number range configuration. A clean handover names the equipment number, category, whether it was copied from a reference object, and any custom field or enhancement notes attached to the category.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/ie01ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.