EQUZ table — Equipment Time Segment Table

One row in EQUZ represents a single validity period for one piece of equipment, describing the functional location, cost center, planning plant, planner group and location that applied to that equipment during that period. A new segment is written whenever the equipment is installed at or dismantled from a functional location, or when one of the historized organizational fields changes through the equipment master transactions. The active segment at any point in time is the one whose validity window covers that date; the current, still-open segment carries the standard SAP high-date as its valid-to value. General, non-historized attributes of the equipment such as equipment category, serial number and manufacturer data live in EQUI, not here.

Always restrict on the client field MANDT implicitly through the transaction layer, and never query without an EQUNR restriction; on an installed base with a long history this table grows one row per organizational change per piece of equipment and a full scan is expensive. To find the segment active on a given date, filter on EQUNR and select the row with the smallest DATBI that is greater than or equal to the reference date; do not assume the row with the latest DATAB is the answer, because segments can be entered out of chronological order when history is corrected retroactively.

Symptom: a plant maintenance report shows an equipment at its old functional location for a date after it was supposedly relocated. Selection: read EQUZ for the equipment number, order the result set by DATBI ascending, and pick the first row where DATAB is less than or equal to the reference date and DATBI is greater than or equal to it. The TPLNR on that row is the functional location the system considers correct for that date, independent of what the current master record shows.

EQUZ continues to exist as a transparent table in S/4HANA and the time-slice concept for equipment organizational data is unchanged. Equipment master maintenance in S/4HANA, whether through the classical transactions or the Fiori equipment apps, continues to write history into EQUZ in the same way. Consultants relying on custom reports built directly against EQUZ should expect them to keep working after a conversion, but should verify behavior against any Fiori app used as a functional replacement rather than assuming identical field-level output.

The plant maintenance functional consultant owns questions about how equipment installation history is structured and why a segment exists or does not. Cost center and controlling-relevant fields carried in EQUZ are usually agreed with FI or CO, since those values feed cost collection on maintenance orders. Basis is only relevant if the table itself is growing unexpectedly large or causing performance issues.

EQUI holds the general, non-historized equipment master data that EQUZ segments extend over time. EQKT carries the equipment's language-dependent description. IFLOT and IFLOTX describe the functional location that EQUZ-TPLNR points to. AFIH and VIQMEL reference the equipment on maintenance order headers and notifications respectively, and both are populated based on the equipment's current EQUZ segment at the time of creation. Segments are written by the standard equipment master transactions for create, change and display, and by functional location installation and dismantling actions.