Equipment Missing From Functional Location Structure

A planner or technician reports that a piece of equipment does not show up when they pull the equipment list for a functional location, even though the equipment clearly belongs there physically. Sometimes the complaint is the reverse: the equipment master says it sits at a location, but the location's structure display does not list it. Notifications raised against the functional location do not pick up the equipment automatically, or a preventive maintenance plan built on the functional location skips a piece of equipment the planner expected to be included. Reliability or plant engineering usually notices this first, during a walkdown reconciliation or when a report used for statutory inspection scheduling comes back short.

Pull the equipment master field (IE03, Location tab) alongside every row in the installation history table for that equipment number (SE16N on EQUZ), sorted by valid-from date. If the flat field disagrees with the history, or the history has no row covering today's date, that is the proof. Cross-check by running the functional location's structure or usage list (IH03/IE05) for the same date and confirming the equipment is absent despite the master field showing that location.

If the flat field was updated without a formal install, run the install function from equipment change mode (IE02) to create a proper time-dependent installation record; this is a data fix, done equipment by equipment, no transport needed. If the equipment was legitimately dismantled and needs to be reinstalled, use the install function again with the correct start date rather than editing the field. If the functional location category does not allow installation, the category configuration must be changed in the IMG and transported; this affects every location built on that category, so check for other locations relying on the current restriction before changing it. If the block is a maintenance plant mismatch, decide whether the equipment plant is wrong (data fix) or whether cross-plant installation should be permitted generally (configuration change, transported, with wider impact). If a load tool wrote the field directly, correct the load program to call the install function module instead of updating the table, and reprocess the affected population.

The reflex fix is to open the equipment in change mode and simply retype the functional location field, or run a mass change (MASS transaction, LSMW) across a batch of equipment to push the field value again. This updates the flat field a second time but still does not create or correct the underlying installation history record. The equipment master now shows the right location, so the immediate complaint looks solved, but usage-list reports, warranty and cost history, and any downstream report keyed off the installation history still show gaps or the wrong installation date, and the problem resurfaces at the next audit or dismantle.

PM master data maintenance owns the correction, usually within the plant maintenance or asset management team responsible for equipment and functional location records. The handover note should carry the equipment number, the expected functional location, how the discrepancy was found (report, walkdown, audit), the installation history rows pulled from EQUZ, and whether the field was likely set by manual entry, LSMW, or an interface load.