MHIS table — Measuring Point History Table in Plant Maintenance

One row in MHIS represents a historical value entry recorded against a single measuring point or counter, captured at a point in time. It exists to support the consumption based (performance based) maintenance planning function, which needs a rolling history of readings to calculate the annual estimate, the projected average consumption figure used to schedule the next maintenance call for a counter driven strategy. MHIS is not where a technician's reading lands when a measurement document is posted, that is IMRG. MHIS is a secondary, largely internal table that the estimate and forecast logic reads and refreshes as measurement documents accumulate or as the annual estimate is recalculated. Because of this, its population depends entirely on whether the measuring point is actually used in a counter based maintenance plan, not on whether readings exist at all.

Only two fields on this table can be stated with confidence; the remaining columns (the historical value itself and its associated date or period marker) exist but their exact technical names are not asserted here and should be confirmed in the data dictionary before being used in a query or extract.

The practical join always starts from the measuring point number and moves outward to the owning technical object. From MHIS the join to the measuring point master is direct; from there the standard PM linkage table resolves the object the measuring point is attached to, whether equipment or functional location.

Always restrict by client first, then by the specific measuring point number, never scan MHIS without a POINT filter in a live system, especially one with long history retention or many counter based plans, since the table accumulates one row per historical value per measuring point over years. Resolve the measuring point to its owning equipment or functional location through MPLA and ILOA before pulling history, otherwise the numbers are meaningless out of context. Do not expect a consistent row per calendar period; entries are only written when the estimate logic actually runs or a relevant measurement document triggers a recalculation.

Symptom: a counter based maintenance plan is scheduling calls too early or too late, and the annual estimate on the measuring point looks wrong. Resolve the equipment to its measuring point via MPLA (matching on the equipment's ILOA installation number), take that POINT value, then select MHIS for that POINT and compare the historical values it holds against the actual posted readings in the measurement document table for the same period. A mismatch points to a stale or unrefreshed estimate rather than bad input readings.

The measuring point and counter data model in Plant Maintenance has not been a focus of the S/4HANA simplification effort, and no compatibility CDS view specific to MHIS is documented. It is reasonable to expect the table's shape and role are unchanged from ECC. Reporting and forecast display for counter based maintenance continue to run through the standard measuring point and maintenance plan transactions rather than through direct table access, which remains a diagnostic step rather than a supported reporting path in either release line.

The recurring mistake is treating MHIS as a document or audit table rather than a derived support table for scheduling logic.

This is a PM/EAM functional consultant's table, specifically whoever configures counter based (performance based) maintenance strategies and measuring points. A data or basis team gets involved only if table growth or archiving of historical measurement data becomes a volume concern; they do not own the interpretation of what the history values mean for a given plan's scheduling.

MPLA and MPOS are the measuring point master data tables that MHIS extends with history; ILOA is the shared PM location and account assignment table used to resolve a measuring point to its owning equipment; EQUI is the equipment master reached that way. Measurement documents themselves are created and changed through the standard measuring point document transactions, not through direct edits to MHIS.