PM Report Custom development ALV report

Measuring Point Limit Breaches Without Follow-Up Notification Report

Short answer: A custom ALV report that compares measurement documents with the lower and upper limits of the measuring point and lists readings that crossed a limit, with the size and direction of the deviation. It checks whether a notification was created on the same equipment after the breach; breaches without follow-up are flagged separately.

Estimated effort
M · 3–5 working days
System
ECC and S/4HANA
Tables
8
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

Why is the standard not enough?

IK17 lists measurement documents, but it does not compare the reading with the limits of the measuring point, filter the breaches or show whether a notification followed. When vibration, temperature or pressure readings are entered every day, values above the limit stay in the list unnoticed. The custom report gives the breach, the deviation and the follow-up status on the same line.

Who uses it? Condition-based maintenance teams, maintenance planners, energy and process safety owners.

Closest standard alternatives

  • IK17 Display Measurement Documents (List). Lists measurement documents; does not compare with limits or check for a follow-up notification.

Tables used

The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.

TableRoleJoinSystem
IMRGMeasurement DocumentMeasurement documents: reading, date, time, valuation code (driving table)—ECC + S/4
IMPTTMeasuring PointMeasuring point: description, lower/upper limit, object numberIMPTT-POINT = IMRG-POINTECC + S/4
EQUIEquipment Master DataEquipment the measuring point belongs toEQUI-OBJNR = IMPTT-MPOBJECC + S/4
EQUZEquipment Time SegmentCurrent time segment and location link of the equipmentEQUZ-EQUNR = EQUI-EQUNR AND EQUZ-DATBI = '99991231'ECC + S/4
ILOAPM Object Location and Account AssignmentMaintenance plant and functional locationILOA-ILOAN = EQUZ-ILOANECC + S/4
QMIHNotification Maintenance DataCheck for a notification on the same equipment after the breachQMIH-EQUNR = EQUI-EQUNRECC + S/4
QMELNotification HeaderDate of the follow-up notificationQMEL-QMNUM = QMIH-QMNUMECC + S/4
EQKTEquipment Short TextsEquipment descriptionEQKT-EQUNR = EQUI-EQUNR AND EQKT-SPRAS = SY-LANGUECC + S/4

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_SWERKMaintenance plantRange / multipleILOA-SWERKYes1000
S_EQUNREquipmentRange / multipleEQUI-EQUNRNo10004512
S_POINTMeasuring pointRange / multipleIMRG-POINTNo300125
S_PSORTMeasurement positionRange / multipleIMPTT-PSORTNoRULMAN-ON
S_IDATEReading date rangeRange / multipleIMRG-IDATEYes01.11.2026 – 17.11.2026
P_FUDAYSDays allowed for a follow-up notificationSingle value—No2
P_NOFUOnly breaches without follow-upCheckbox—NoX

Output columns

#ColumnSource
1Measuring pointIMRG-POINT
2Point descriptionIMPTT-PTTXT
3EquipmentEQUI-EQUNR
4Equipment descriptionEQKT-EQKTX
5Reading dateIMRG-IDATE
6TimeIMRG-ITIME
7Recorded valueIMRG-RECDV
8UnitIMRG-RECDU
9Lower limitCalculated IMPTT-MRMIN converted to the recording unit
10Upper limitCalculated IMPTT-MRMAX converted to the recording unit
11Breach directionCalculated Upper when READG > MRMAX, lower when READG < MRMIN
12DeviationCalculated Reading − upper limit for an upper breach, lower limit − reading for a lower breach
13Valuation codeIMRG-VLCOD
14Follow-up notificationCalculated From IMRG-WOOB1 or the QMEL-QMNUM found on the same equipment within the window
15Days without follow-upCalculated Today − IMRG-IDATE when there is no follow-up

Sample output

Measuring pointPoint descriptionEquipmentEquipment descriptionReading dateTimeRecorded valueUnitLower limitUpper limitBreach directionDeviationValuation codeFollow-up notificationDays without follow-up
300125Bearing vibration front10004512Compressor K-1211/14/202607:30:007.90MM/S06.30Upper1.603
300131Oil temperature10004718Hydraulic press P-311/15/202614:00:0078°C3070Upper810028155
300140Line pressure10004630Conveyor belt B211/16/202606:15:004.10BAR58Lower0.901
A view built with fictional sample data; not real system data.

How does the report work?

  1. Measurement documents that are not cancelled (CANCL blank) are read from IMRG for the date range and measuring points on the selection screen.
  2. From IMPTT the measuring point description, position (PSORT), lower limit (MRMIN), upper limit (MRMAX) and object number (MPOBJ) are added; points without limits and counter-type points (INDCT) are left out.
  3. The comparison runs in the internal unit: IMRG-READG is compared with IMPTT-MRMIN and MRMAX. For display the reading and the limits are converted to the recording unit (RECDU). Deviation = reading − upper limit (upper breach) or lower limit − reading (lower breach).
  4. MPOBJ is matched to EQUI-OBJNR to find the equipment; maintenance plant and functional location come through EQUZ and ILOA.
  5. Follow-up check: when a notification was created directly from the measurement document, IMRG-WOOB1 is filled; otherwise a notification on the same equipment within the selected days after the reading date is searched in QMEL/QMIH. When none is found, a ’no follow-up’ flag is set and the days from the reading to today are calculated.

Performance notes

IMRG grows very quickly; keep the date range short and narrow by measuring point or equipment. Read IMPTT first and fetch IMRG records only for points with limits. Evaluating only the last day's readings in a daily background job is the most efficient use.

Features

  • ALV list (sort, filter, subtotals)
  • User-specific layout variants
  • Double-click drill-down to the document The measuring point opens IK13, the equipment opens IE03, the follow-up notification opens IW23.
  • Export to Excel
  • Runs as a background job
  • Send the result by email Breaches without follow-up can be sent every morning to the responsible maintenance planner group.

Authorization objects

  • I_SWERKDisplay technical objects and measurement documents by maintenance plant
  • I_QMELDisplay follow-up notifications by notification type

Frequently asked questions

Can a notification be created automatically when a limit is crossed?

The report only reads. If required, a button that creates notifications for the 'no follow-up' lines in mass can be added, or a separate background job can create them; this extension adds about two days.

Why is the comparison done in the internal unit?

The limits of the measuring point and the internal value of the reading are stored in the same unit, while the recorded value may be in the unit the user entered. Comparing in the internal unit avoids false alarms, and the screen shows the unit the user knows.

Are code-based readings evaluated too?

The base version evaluates measuring points with numeric limits. For readings entered as codes (for example a 'bad' valuation code), filtering by a list of valuation codes can be added.

Related reports

PM Report Custom ALV report

Repeat Breakdowns by Equipment Report

A custom ALV report that shows breakdown notifications repeating on the same equipment within a selected window of days, with the previous …

QMEL · QMIH · QMFE · QMUR

Let us build this report for your system

Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.

Related report: Measuring Point Limit Breaches Without Follow-Up Notification Report