EQUI table — Equipment Master General Data

EQUI holds one row per physical equipment master record: a single piece of maintainable technical equipment such as a pump, vehicle, instrument, or serialized asset. It is time-independent - the row does not change when the equipment is reinstalled elsewhere or reassigned to a different functional location; that movement history lives in EQUZ. EQUI carries the identifying and classifying attributes of the equipment: its category, manufacturer data, serial and inventory numbers, acquisition data, and the object number that ties it into status management, notifications, and orders. Short descriptions live in EQKT, not in EQUI. Deleted equipment is flagged, not physically removed, so a row existing in EQUI does not guarantee the equipment is still active in the plant - check the deletion flag and status before treating a hit as live.

EQUI is a large, un-partitioned master table spanning every plant and equipment category in the client. Restrict by client implicitly and add EQTYP or a plant filter (reachable through ILOA) before running an open-ended selection; filtering only on HERST or TYPBZ across a full client is slow and rarely selective. EQUNR is the primary key and the fastest access path when known; treat it as a character string, not a number - the internal numbering is zero-padded, and losing leading zeros in an extract or spreadsheet round-trip breaks every downstream join. Filter on LOEKZ explicitly, and check status through the object number rather than assuming a returned row means the equipment is currently in service.

To confirm a specific serial number was ever created as equipment, select EQUI where SERNR equals the serial number and MATNR equals the material; no row returned means the serial number was never converted to equipment, regardless of what a field report claims. To confirm equipment is not scrapped, check that the row's LOEKZ is blank and cross-check its status through the object number against status management rather than assuming an EQUI hit alone proves the equipment is active.

EQUI remains the underlying equipment master table in S/4HANA EAM; there has been no wholesale replacement with a compatibility view for this table, and its structure carried over largely unchanged from ECC. Equipment maintenance is now also exposed through Fiori apps and API-based creation and change services, but those still write to EQUI and EQUZ underneath. Consultants working with newer asset management extensions such as predictive maintenance or IoT integration should not expect a separate master table - equipment identity still resolves back to EQUNR in EQUI.

Equipment master data quality is owned jointly by the plant maintenance functional consultant who configures equipment categories and number ranges, and by the site's maintenance planning or master data team that actually creates and retires records. Where equipment ties to a capitalized asset, FI-AA shares responsibility for keeping acquisition data aligned.

EQUZ carries the time-dependent installation and superior-equipment history for each EQUNR; EQKT carries short texts; IHPA carries partner assignments keyed by OBJNR; ILOA carries location and account assignment data keyed by ILOAN; VIQMEL and AFIH reference the equipment from the notification and order side by EQUNR. Equipment master records are created, changed, and displayed through the standard equipment master transactions in Plant Maintenance.