# Measuring Point Limit Breaches Without Follow-Up Notification Report

> 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.

- Type: Report, Custom development, ALV report
- Module: PM
- Estimated effort: M (3–5 working days)
- Last updated: 2026-11-17
- URL: https://nekuhub.com/en/reports/measuring-point-limit-breach-report/


## 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.

### Closest standard alternatives

- IK17: Lists measurement documents; does not compare with limits or check for a follow-up notification.

## Tables used

| Table | Role | Access | Join | System |
|---|---|---|---|---|
| IMRG | Measurement documents: reading, date, time, valuation code (driving table) | Read | - | ECC + S/4 |
| IMPTT | Measuring point: description, lower/upper limit, object number | Read | IMPTT-POINT = IMRG-POINT | ECC + S/4 |
| EQUI | Equipment the measuring point belongs to | Read | EQUI-OBJNR = IMPTT-MPOBJ | ECC + S/4 |
| EQUZ | Current time segment and location link of the equipment | Read | EQUZ-EQUNR = EQUI-EQUNR AND EQUZ-DATBI = '99991231' | ECC + S/4 |
| ILOA | Maintenance plant and functional location | Read | ILOA-ILOAN = EQUZ-ILOAN | ECC + S/4 |
| QMIH | Check for a notification on the same equipment after the breach | Read | QMIH-EQUNR = EQUI-EQUNR | ECC + S/4 |
| QMEL | Date of the follow-up notification | Read | QMEL-QMNUM = QMIH-QMNUM | ECC + S/4 |
| EQKT | Equipment description | Read | EQKT-EQUNR = EQUI-EQUNR AND EQKT-SPRAS = SY-LANGU | ECC + S/4 |

## Selection screen parameters

| Parameter | Description | Type | Reference field | Required |
|---|---|---|---|---|
| S_SWERK | Maintenance plant | Range / multiple | ILOA-SWERK | Yes |
| S_EQUNR | Equipment | Range / multiple | EQUI-EQUNR | No |
| S_POINT | Measuring point | Range / multiple | IMRG-POINT | No |
| S_PSORT | Measurement position | Range / multiple | IMPTT-PSORT | No |
| S_IDATE | Reading date range | Range / multiple | IMRG-IDATE | Yes |
| P_FUDAYS | Days allowed for a follow-up notification | Single value | - | No |
| P_NOFU | Only breaches without follow-up | Checkbox | - | No |

## Output columns

| Column | Source |
|---|---|
| Measuring point | IMRG-POINT |
| Point description | IMPTT-PTTXT |
| Equipment | EQUI-EQUNR |
| Equipment description | EQKT-EQKTX |
| Reading date | IMRG-IDATE |
| Time | IMRG-ITIME |
| Recorded value | IMRG-RECDV |
| Unit | IMRG-RECDU |
| Lower limit | Calculated: IMPTT-MRMIN converted to the recording unit |
| Upper limit | Calculated: IMPTT-MRMAX converted to the recording unit |
| Breach direction | Calculated: Upper when READG > MRMAX, lower when READG < MRMIN |
| Deviation | Calculated: Reading − upper limit for an upper breach, lower limit − reading for a lower breach |
| Valuation code | IMRG-VLCOD |
| Follow-up notification | Calculated: From IMRG-WOOB1 or the QMEL-QMNUM found on the same equipment within the window |
| Days without follow-up | Calculated: Today − IMRG-IDATE when there is no follow-up |

## 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.

## Authorization objects

- I_SWERK: Display technical objects and measurement documents by maintenance plant
- I_QMEL: Display 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.

---
Let us build this report for your system: https://nekuhub.com/en/request-a-quote/?report=pm-measuring-point-limit-breaches
