Table of Contents
  1. Introduction
  2. SAP PM Overview
  3. Creating Equipment
  4. Functional Locations
  5. Creating Measuring Points
  6. Recording Measurements
  7. Automated Data Entry
  8. Running ZPM_MP_ANAL
  9. Understanding the Output
  10. Best Practices
  11. Troubleshooting
  12. TCode Reference
SAP Plant Maintenance

Measuring Point Analysis
User Guide

A complete step-by-step guide to the SAP Plant Maintenance module and the ZPM_MP_ANAL comparative analysis report — written for beginners. By the end of this guide, you'll know how to create equipment, set up measuring points, record measurements, and analyse the data using charts.

TCode: ZPM_MP_ANAL System: SAP S/4HANA 2022 Author: Charaka Janith Client: Lanka Tiles PLC Updated: January 2024

01 Introduction

The ZPM_MP_ANAL transaction is a custom ABAP report developed for Lanka Tiles PLC on SAP S/4HANA 2022. Its purpose is to provide a daily comparative analysis of measuring point data across multiple pieces of equipment, giving maintenance teams actionable insights for operational efficiency.

This guide assumes you have no prior experience with the SAP Plant Maintenance module. We'll start from the very beginning — understanding what Plant Maintenance is — and work through each step until you can confidently run the report and interpret the results.

What you'll learn: Equipment creation, functional locations, measuring points, measurement documents, running the ZPM_MP_ANAL report, understanding charts and ALV output, and best practices for data quality.

What is ZPM_MP_ANAL?

This report consolidates data from multiple measuring points and presents it in a single ALV grid (tabular view) alongside two interactive charts. It compares two characteristics (e.g., motor temperature vs. ambient temperature) side-by-side across multiple equipment, helping you spot trends, anomalies, and correlations quickly.

The report is accessed via SAP GUI transaction code ZPM_MP_ANAL (Development Request #21701).

02 SAP Plant Maintenance Overview

The SAP Plant Maintenance (PM) module is designed to support the full maintenance lifecycle — from planning and execution to settlement and analysis. It helps organisations manage physical assets, schedule maintenance activities, track equipment condition, and reduce downtime.

Key Concepts

Before you can use the ZPM_MP_ANAL report, you need to understand four fundamental objects:

ObjectDescriptionExample
EquipmentA physical asset that needs maintenance (machine, vehicle, building)Packing Machine #3
Functional LocationWhere equipment is installed — defines the organisational hierarchyPlant 1 > Packaging Area > Line 3
Measuring PointA specific checkpoint on equipment where readings are takenMotor Temperature Sensor
Measurement DocumentA record of an actual reading taken at a measuring point85.5 °C on 14-Jan-2024
📖
The flow: Create Equipment → (Optional) Create Functional Location → Create Measuring Point → Assign to Equipment → Record Measurements → Run ZPM_MP_ANAL

Prerequisites for This Guide

  • You have SAP GUI installed and a user account with access to the PM module
  • You have authorisation for the following transactions: IE01, IK01, IK11, and ZPM_MP_ANAL
  • Basic familiarity with SAP GUI navigation (menu paths, transaction codes, screen fields)

03 Creating Equipment

Equipment is the central object in SAP PM. Think of it as the digital representation of a physical asset. Every measuring point must be linked to a piece of equipment, so this is your first step.

What is Equipment?

Equipment represents any physical object you want to maintain independently. In a manufacturing plant, this could be a conveyor motor, a compressor, a pump, a forklift, or even an entire production line treated as a single equipment.

Step-by-Step: Creating Equipment (TCode IE01)

STEP 1
Navigate to TCode IE01

In the SAP GUI command field (top-left), type IE01 and press Enter. This opens the Create Equipment: Initial Screen. If you need to change existing equipment later, use IE02. To display equipment, use IE03.

STEP 2
Enter Equipment ID or Use Internal Numbering

If your system uses internal number assignment, leave the Equipment field blank — SAP will assign a number automatically. If you use external numbering, enter a meaningful ID (e.g., MTR-003-PKG). Check with your SAP Basis team to know which method your system uses.

STEP 3
Select the Equipment Category

The equipment category determines which fields are visible and what processes apply. Common categories include:

CategoryCodeUse Case
MachineMProduction machinery, motors, pumps, compressors
VehicleVForklifts, trucks, company cars
BuildingEFactory buildings, warehouses, offices
Production Resource/ToolPMoulds, dies, jigs, fixtures
Customer EquipmentCEquipment owned by a customer but on your premises
STEP 4
Fill in the Equipment Master Data

Press Enter to go to the detail screen. Navigate between tabs and fill in:

General Tab:

  • Description: A clear, descriptive name — e.g., "Main Conveyor Motor — Packaging Line 3"
  • Manufacturer: OEM name (e.g., Siemens, ABB, local supplier)
  • Model Number: The specific model identifier
  • Serial Number: The manufacturer's serial number (critical for traceability)
  • Year of Construction: Helps with lifecycle analysis

Location Tab:

  • Plant: The plant where the equipment operates (e.g., LT01)
  • Cost Center: The cost centre charged for maintenance (e.g., 1000-301)
  • Work Center: The maintenance work centre responsible for this equipment
  • Functional Location: If you have functional locations set up, assign one here

Organization Tab:

  • Planner Group: The group responsible for maintenance planning (e.g., M01 — Mechanical)
  • Main Work Center: Default work centre for maintenance tasks
  • ABC Indicator: Criticality classification — A = High criticality, B = Medium, C = Low

Structure Tab:

  • Superior Equipment: If this equipment is part of a larger assembly
  • Installation Date: When the equipment was installed (start of depreciation)
STEP 5
Save the Equipment

Press Ctrl+S or click the Save icon (diskette). SAP will display a confirmation message with the new equipment number. Write this number down — you'll need it when creating measuring points.

Example: Creating a Cooling Tower Pump

Scenario: You need to monitor a cooling tower pump at the Lanka Tiles main plant.

FieldValue
Equipment(blank — internal numbering)
CategoryM (Machine)
DescriptionCooling Tower Pump — CT-01
ManufacturerGrundfos
PlantLT01
Cost Center1000-301
Planner GroupM01
ABC IndicatorA (High criticality — cooling system failure stops production)

Result: SAP creates equipment 10000001 (example number). This equipment is now ready to have measuring points assigned.

💡
Best Practice: Use consistent naming conventions for equipment. Consider including location codes in the external ID. For example: LT01-PKG-MTR-003 = Lanka Tiles Plant 1, Packaging area, Motor number 3.

04 Creating Functional Locations

Functional locations represent the hierarchical structure of your plant. They define where equipment is installed. While not strictly required for ZPM_MP_ANAL (you can assign measuring points directly to equipment), they are essential for larger organisations with complex plant layouts.

Step-by-Step: Creating Functional Locations (TCode IL01)

STEP 1
Navigate to TCode IL01

Type IL01 in the command field and press Enter.

STEP 2
Design Your Location Structure

Functional locations use a hierarchical coding system. A well-designed structure makes navigation and reporting easier. Example structure for a tile manufacturing plant:

LT01              Lanka Tiles Plant 1
LT01-PKG         Packaging Area
LT01-PKG-L03     Packaging Line 3
LT01-PKG-L03-S02 Station 2 (on Line 3)

Enter your functional location code in the field. Use a character to separate levels (typically a hyphen - or forward slash /).

STEP 3
Complete the Master Data

Press Enter and fill in:

  • Description: A meaningful name for the location
  • Plant: The plant this location belongs to
  • Cost Center: Default cost centre for maintenance at this location
  • Planner Group: Responsible planner group
  • Category: Typically T for technical location
STEP 4
Save

Press Ctrl+S. The functional location is created and its full hierarchy path is displayed.

💡
Planning your hierarchy: Keep the structure no more than 4-6 levels deep. Too many levels makes navigation cumbersome. Common structure: Plant → Area → Line → Station.

05 Creating Measuring Points

A measuring point is a specific location on equipment where a measurement is taken. It can measure temperature, pressure, vibration, flow rate, runtime hours, or any other quantifiable value. This is the most critical object for the ZPM_MP_ANAL report — without measuring points, there is nothing to analyse.

Understanding Characteristics

Measuring points are linked to characteristics (defined in SAP using TCode CT04). A characteristic defines what is being measured (e.g., "Motor Temperature", "Outlet Pressure"). The ZPM_MP_ANAL report requires two characteristics per measuring point — this is how it generates the comparative analysis.

Step-by-Step: Creating a Measuring Point (TCode IK01)

STEP 1
Navigate to TCode IK01

Type IK01 in the command field and press Enter.

STEP 2
Enter Measuring Point ID

Enter a unique identifier for the measuring point. Similar to equipment, this can be internal or external. Use a meaningful code if external — e.g., CT01-MOTOR-TEMP for "Cooling Tower 1 Motor Temperature".

STEP 3
Enter Description and Basic Data

On the General tab:

  • Description: e.g., "Motor Winding Temperature — Cooling Tower CT-01"
  • Unit of Measurement: e.g., °C for temperature, Bar for pressure, kW for power
  • Decimal Places: typically 1-2 for most industrial measurements
  • Category: M (Measurable Value) — this is the standard option
STEP 4
Assign Characteristics

Navigate to the Characteristics tab (or equivalent depending on your SAP version). Here you assign the characteristics that define what values this measuring point records:

  • Characteristic 1: The primary measured value (e.g., MOTOR_TEMP)
  • Characteristic 2: The secondary value for comparison (e.g., AMBIENT_TEMP)

Characteristics are pre-defined in the system using TCode CT04 and grouped into Class 002 (Measuring Points). If you don't see the characteristics you need, ask your SAP Basis team or create them via CT04.

Important for ZPM_MP_ANAL: The report's selection screen asks for two characteristics. The report groups data by Characteristic 1 for the top chart (horizontal bars) and Characteristic 2 for the bottom chart (vertical bars). Both must be assigned to your measuring points for the report to work.
STEP 5
Assign to Equipment

Navigate to the Object Assignment tab:

  • Object Type: Choose Equipment (or Functional Location if applicable)
  • Object Number: Enter the equipment number you created in Step 3 (e.g., 10000001)
STEP 6
Set Validation Limits (Optional but Recommended)

On the Limits tab, you can set acceptable ranges for your measurements:

  • Lower Limit: Minimum acceptable reading (e.g., 0 °C)
  • Upper Limit: Maximum acceptable reading (e.g., 120 °C)
  • Tolerance: Acceptable deviation beyond limits (e.g., 5%)
  • Entry Medium: Manual, Automatic, or Calculated

When limits are set, SAP will warn users if a reading falls outside the acceptable range — this is a powerful quality control feature.

STEP 7
Save

Press Ctrl+S. The measuring point is created and linked to your equipment.

Example: Measuring Point for Cooling Tower Pump

Continuing from the equipment example above:

FieldValue
Measuring PointCT01-MOTOR-TEMP
DescriptionMotor Winding Temperature — CT-01
UoM°C
CategoryM (Measurable Value)
Characteristic 1MOTOR_TEMP
Characteristic 2AMBIENT_TEMP
Assigned ToEquipment 10000001 (Cooling Tower Pump CT-01)
Lower Limit0 °C
Upper Limit120 °C
Entry MediumManual

Now, every time someone records a measurement at this point, the ZPM_MP_ANAL report will be able to read and analyse it.

Example: Vehicle Mileage vs. Fuel Consumption

Scenario: A company forklift (FKL-001) needs its daily mileage and fuel consumption tracked to monitor efficiency and schedule maintenance. This is a classic PM use case for vehicle equipment.

Step 1 — Create the Equipment (IE01):

FieldValue
Equipment(blank — internal numbering)
CategoryV (Vehicle)
DescriptionDiesel Forklift — FKL-001
PlantLT01
ABC IndicatorB (Medium criticality)

Step 2 — Create the Measuring Point (IK01):

FieldValue
Measuring PointFKL001-DAILY-USE
DescriptionDaily Mileage & Fuel — Forklift FKL-001
Characteristic 1DISTANCE_KM (Unit: KM)
Characteristic 2FUEL_LITRE (Unit: L)
Assigned ToEquipment 10000010 (Diesel Forklift FKL-001)
Entry MediumManual

How the analysis works here: Each day you record the distance driven (KM, Characteristic 1) and the fuel consumed (L, Characteristic 2). The ZPM_MP_ANAL report then compares these side by side — a sudden increase in fuel consumption without a corresponding increase in distance signals engine trouble or worn components, making it easy to spot efficiency drops before they become breakdowns.

The report's unit conversion logic also applies: since RECDU = 'KM' triggers a ÷1000 conversion, large cumulative readings are automatically scaled down for chart display. For fuel in Litres, no conversion is applied.

06 Recording Measurement Documents

Once your equipment and measuring points are set up, you need to record measurement readings. A measurement document is the actual record of a reading taken at a specific date and time for a specific measuring point.

Step-by-Step: Recording a Measurement (TCode IK11)

STEP 1
Navigate to TCode IK11

Type IK11 in the command field and press Enter. This opens the Create Measurement Document screen.

STEP 2
Enter the Measuring Point

Type the measuring point identifier (e.g., CT01-MOTOR-TEMP) in the Measuring Point field and press Enter.

STEP 3
Enter the Reading

The screen displays the characteristics defined for this measuring point. Enter:

  • Reading (Characteristic 1): The actual value (e.g., 85.5)
  • Reading (Characteristic 2): The second value if required (e.g., 32.0)
  • Measurement Date: When the reading was taken (defaults to today)
  • Measurement Time: When the reading was taken
  • Document Text: Any remarks about the reading (e.g., "Routine morning check")
STEP 4
Save

Press Ctrl+S. A confirmation message shows the measurement document number.

Example: 7 Days of Temperature Readings

Below is a sample data set recorded for Cooling Tower CT-01 over one week. You can record these readings daily using IK11 to build up data for the analysis report.

DateTimeMotor Temp (°C)Ambient Temp (°C)Notes
08-Jan-202408:0078.229.5Morning shift — normal
09-Jan-202408:0080.130.2Normal
10-Jan-202408:0085.532.0Hot day, motor running warm
11-Jan-202408:0088.331.5Slightly elevated — monitoring
12-Jan-202408:0095.730.8Warning level — schedule inspection
13-Jan-202408:0092.429.0Cooler day but still high
14-Jan-202408:0097.130.5Critical — inspection needed

This dataset will be used in the Walkthrough Example section when we run the ZPM_MP_ANAL report.

💡
Pro Tip: To view existing measurement documents for a measuring point, use IK13 (Measurement Document List).
Example: 7 Days of Mileage & Fuel Readings

Below is a sample data set recorded daily for Forklift FKL-001. The odometer reading (KM driven each shift) is recorded alongside the fuel filled (Litres). This lets the ZPM_MP_ANAL report compare distance against consumption — a powerful way to detect efficiency problems.

DateShiftDistance (KM)Fuel (L)Notes
22-Jun-2024Day42.58.2Regular operations
23-Jun-2024Day38.17.5Light day
24-Jun-2024Day45.09.0Heavy load day
25-Jun-2024Day40.29.8Fuel consumption up — monitoring
26-Jun-2024Day44.811.5Efficiency dropping
27-Jun-2024Day39.512.2Poor efficiency — schedule maintenance
28-Jun-2024Day41.013.8Critical — air filter clogged, serviced next day

Analysis: From 22-Jun to 24-Jun the forklift averaged ~5.1 KM/L, which is normal for this model. By 26-Jun this dropped to ~3.9 KM/L, and by 28-Jun it was down to ~3.0 KM/L — a 40% efficiency loss in one week. The ZPM_MP_ANAL report's chart view would show the distance bars staying roughly equal while the fuel bars grew, making the problem immediately visible. The cause was a clogged air filter, which was replaced after the 28-Jun reading restored normal efficiency.

07 Automated Data Entry (Optional)

For organisations with PLC (Programmable Logic Controller) or SCADA systems, measuring points can be automatically updated via interfaces, eliminating manual data entry entirely.

How Automation Works

  1. PLC/SCADA collects readings from sensors in real-time (e.g., every 5 minutes)
  2. An interface program (RFC, Web Service, or BDC) sends the readings to SAP
  3. SAP creates measurement documents (IK11 equivalent) automatically via BAPI or BDC
  4. ZPM_MP_ANAL reads this data the same way as manually entered data
Setting up automated interfaces requires ABAP development and the involvement of your SAP Basis and Automation teams. This is typically done during the PM implementation project.

08 Running the ZPM_MP_ANAL Report

Now that you have equipment, measuring points, and measurement documents set up, you can run the comparative analysis report. This is the core functionality that brings all the data together.

Accessing the Report

STEP 1
Open the Report

Type ZPM_MP_ANAL in the SAP GUI command field and press Enter. Alternatively, if the TCode is not available, run it via SE38 using program name ZPM_MP_ANAL.

Understanding the Selection Screen

The selection screen is divided into four blocks. Here's what each block does:

Block 1: Main Selection Criteria

FieldTCode/ParamRequiredDescription
Characteristic 1so_char1YesSelect the primary characteristic (e.g., MOTOR_TEMP). Only single value allowed — no intervals or multiple values.
Characteristic 2so_char2YesSelect the secondary characteristic (e.g., AMBIENT_TEMP). Only single value allowed.
Equipment Numbersso_equiNoSelect one or more equipment numbers. Leave blank to include all equipment (may slow performance).
Datep_dateYesThe base date for your analysis. Defaults to yesterday (system date - 1). Cannot be today or a future date.

Block 2: Period Type

Choose how the report groups your data. This affects the date range and the number of comparative periods:

OptionCodeDate Range LimitUse When
Day
(Default)
p_dayMax 14 days backShort-term troubleshooting. Best for tracking daily variations and recent changes.
Weekp_weekMax 7 weeks (49 days)Weekly trend analysis. Good for reducing data noise while keeping medium-term context.
Monthp_monthMax 4 months backLong-term strategic analysis. Use for capacity planning, budgeting, and lifecycle tracking.

Including Last (p_last): This field determines how many additional periods to include for comparison. Default is 13. For example, in Day mode with p_last = 13, the report shows 14 days (base date + 13 additional days). In Month mode with p_last = 2, it shows 3 months total.

Validation Rules: Day mode: Max 14 days back, cannot be today. Week mode: Max 7 weeks (49 days) back. Month mode: Max 4 months back with p_last ≤ 3 (max 3 additional months).

Block 3: Display Options

OptionDefaultEffect
Sort by DateONSorts the ALV grid by date in ascending order. Enables date-level subtotals.
Sort by EquipmentONGroups and sorts by equipment number. Enables equipment-level subtotals.
Sort by MPONGroups and sorts by measuring point. Enables measuring point subtotals with SUM aggregation of reading values.

Block 4: Information / Help

This block displays validation rules and constraints for the selected period type. Read it carefully before executing the report.

Walkthrough Example: Running the Report

Complete Walkthrough

Scenario: You've been recording motor winding temperature and ambient temperature for Cooling Tower CT-01 for the past week. You want to see the trend.

Step 1: On the selection screen, fill in:

FieldValue
Characteristic 1MOTOR_TEMP
Characteristic 2AMBIENT_TEMP
Equipment10000001 (Cooling Tower Pump)
Date14.01.2024

Step 2: Select period type:

FieldValue
Period TypeDay
Including Last6 (gives 7 days total — matching the sample data)

Step 3: Display options:

OptionValue
Sort by DateON
Sort by EquipmentON
Sort by MPON

Step 4: Click Execute (F8) or navigate to Program → Execute.

The report processes the data and displays the output screen with the ALV grid and charts.

Walkthrough: Forklift Fuel Efficiency Analysis

Scenario: You've been recording daily distance and fuel consumption for Forklift FKL-001 and noticed the fuel bill seems higher than usual. Run ZPM_MP_ANAL to investigate.

Step 1: On the selection screen, fill in:

FieldValue
Characteristic 1DISTANCE_KM
Characteristic 2FUEL_LITRE
Equipment10000010 (Diesel Forklift FKL-001)
Date28.06.2024

Step 2: Period type — select Day with Including Last: 6.

Step 3: Leave all sort options ON.

Step 4: Execute (F8).

What the charts show: The horizontal bar chart (Characteristic 1 — DISTANCE_KM) shows the total KM driven over the week with a moderately sized bar. The vertical bar chart (Characteristic 2 — FUEL_LITRE) shows the total fuel consumed with a bar that's disproportionately large relative to the distance. This disproportion is the key insight — the forklift's fuel efficiency (KM per Litre) has degraded significantly. The ALV grid confirms the trend: distance readings stayed in the 38-45 KM range, while fuel rose from 8.2L to 13.8L.

09 Understanding the Output

The report presents a split-screen layout — the left side shows the tabular ALV grid and the right side shows two charts.

ALV Grid (Left Panel)

The ALV (SAP List Viewer) grid displays all measurement records in a structured table. Depending on your sort options, the grid will show:

ColumnDescription
DateThe date the measurement was recorded
EquipmentEquipment number
Equipment DescriptionDescription of the equipment (from EQKT table)
Measuring PointThe measuring point identifier
MP TextMeasuring point description text
MD Value (READG)Measuring document value for Characteristic 1
MD Value (READG2)Measuring document value for Characteristic 2
Unit (RECDU)The unit of measurement
📈
ALV Toolbar: You can use the standard ALV toolbar to sort, filter, find values, export to Excel (local file icon), and print. The Export to Excel function is particularly useful for further analysis.

Subtotals: With "Sort by MP" enabled, the grid shows subtotals per measuring point with the SUM of all reading values. This gives you aggregated values for each point.

Charts (Right Panel)

The right side of the output screen contains two charts generated using SAP's GFW (Graphical Framework):

Top Chart: Horizontal Bar Chart (Characteristic 1)

  • Type: Horizontal bars
  • Data: Aggregated readings for Characteristic 1, grouped by equipment
  • X-Axis: Reading value (total)
  • Y-Axis: Equipment identifier
  • Each bar represents one piece of equipment
  • Bar length represents the total reading value for that characteristic

Bottom Chart: Vertical Bar Chart (Characteristic 2)

  • Type: Vertical bars
  • Data: Aggregated readings for Characteristic 2, grouped by equipment
  • X-Axis: Equipment identifier
  • Y-Axis: Reading value (total) — labelled "2nd char val"
  • Each bar represents one piece of equipment
  • Bar height represents the total reading value
💡
Quick interpretation: Compare the two charts side by side. If you see an equipment that ranks high in both charts, it may indicate a correlation — for example, high motor temperature and high ambient temperature could suggest the equipment is in a hot location rather than having a mechanical fault.

Interpreting Results: A Practical Example

Interpreting the Cooling Tower CT-01 Data

Using the 7-day sample data from Section 6:

What the ALV grid will show:

DateEquipmentMPValue 1 (°C)Value 2 (°C)
08-Jan10000001CT01-MOTOR-TEMP78.229.5
09-Jan10000001CT01-MOTOR-TEMP80.130.2
10-Jan10000001CT01-MOTOR-TEMP85.532.0
11-Jan10000001CT01-MOTOR-TEMP88.331.5
12-Jan10000001CT01-MOTOR-TEMP95.730.8
13-Jan10000001CT01-MOTOR-TEMP92.429.0
14-Jan10000001CT01-MOTOR-TEMP97.130.5

What to look for:

1. Upward Trend: The motor temperature rose steadily from 78.2°C to 97.1°C over 7 days. This is a clear warning sign — the motor is overheating and trending worse.

2. Ambient vs. Motor Correlation: Notice that ambient temperature stayed fairly stable (29-32°C) while motor temperature increased significantly. Since the motor temp is rising independently of ambient conditions, the issue is likely internal to the motor (worn bearings, failing insulation, cooling fan problem) rather than environmental.

3. Action Trigger: At 97.1°C, the reading is approaching or exceeding the upper limit (120°C depending on your setting). Speed the reading increase suggests action is needed within days, not weeks. Schedule a maintenance inspection.

Chart View: In the horizontal bar chart (Characteristic 1 — MOTOR_TEMP), you'd see a single long bar for equipment 10000001 (total of all daily readings = 617.3). In the vertical bar chart (Characteristic 2 — AMBIENT_TEMP), you'd see a single shorter bar for the same equipment (total = 213.5). The ratio between the bars tells the story.

Interpreting the Forklift Mileage vs. Fuel Data

Using the Forklift FKL-001 sample data from Section 6:

What the ALV grid shows:

DateEquipmentMPDistance (KM)Fuel (L)
22-Jun10000010FKL001-DAILY-USE42.58.2
23-Jun10000010FKL001-DAILY-USE38.17.5
24-Jun10000010FKL001-DAILY-USE45.09.0
25-Jun10000010FKL001-DAILY-USE40.29.8
26-Jun10000010FKL001-DAILY-USE44.811.5
27-Jun10000010FKL001-DAILY-USE39.512.2
28-Jun10000010FKL001-DAILY-USE41.013.8

What to look for:

1. Stable distance, rising fuel: The distance readings fluctuate normally between 38-45 KM per day (routine operations). However, fuel consumption rises steadily from 8.2L to 13.8L — a 68% increase — while the workload stayed the same. This is the classic pattern of mechanical degradation.

2. Efficiency calculation: 22-Jun: 42.5/8.2 = 5.18 KM/L. 28-Jun: 41.0/13.8 = 2.97 KM/L. The forklift's fuel efficiency dropped by 43% in one week, meaning nearly half the fuel was being wasted.

3. Action taken: The air filter was inspected on 29-Jun and found to be severely clogged. After replacement, efficiency returned to normal (verified in the following week's readings). Without the ZPM_MP_ANAL report, this gradual degradation could have gone unnoticed until the engine suffered damage.

Chart View: The horizontal bar chart (DISTANCE_KM) shows a moderately sized bar (total = 291.1 KM across 7 days). The vertical bar chart (FUEL_LITRE) shows a bar that's proportionally very tall (total = 72.0 L). The visual disproportion between the two bars is the report's most powerful feature — it makes efficiency problems instantly obvious without needing to calculate anything.

Unit Conversion Logic

The report automatically converts certain units for consistency:

Original UnitConversion AppliedExample
KM (Kilometres)Divided by 1000 → displayed as thousands of KM45,000 KM → 45.00
L (Litres)Multiplied by 1000 → displayed as millilitres0.5 L → 500.00
Other unitsDisplayed as recorded (no conversion)°C, Bar, kW, etc.
📈
Unit conversion in action — Forklift example: If your forklift odometer records cumulative KM and the RECDU field is set to KM, the report divides by 1000 and displays the value in thousands. For Litres, a reading of 0.5 L gets multiplied by 1000 and displays as 500.00. Check the original unit on your measurement documents in IK12 if the displayed values seem off.

10 Best Practices

Follow these guidelines to ensure your data is accurate and your analysis is meaningful:

Data Quality

  • Consistent units: Always use the same unit for the same measuring point. Mixing °C and °F for temperature readings makes analysis meaningless.
  • Timely recording: Record measurements at the same time each day/shift for comparable data. Morning readings after equipment warm-up are a standard practice.
  • Document anomalies: Always fill in the Document Text field when a reading seems unusual. Note the circumstances (e.g., "After bearing replacement" or "During peak load").
  • Regular calibration: Ensure measurement instruments (sensors, gauges) are calibrated regularly. Faulty sensors produce misleading trends.

Report Usage

  • Day mode for troubleshooting specific problems (looks at daily fluctuations)
  • Week mode for routine trend monitoring (reduces day-to-day noise)
  • Month mode for strategic analysis, capacity planning, and lifecycle tracking
  • Limit equipment selection: Don't use '*' to select all equipment if you have hundreds — the report will be slow. Select only the equipment you need.
  • Export to Excel: Use the ALV export function to download raw data for pivot tables, conditional formatting, or sharing with team members who don't have SAP access.

Equipment Setup

  • Standardise naming conventions across your organisation. A documented naming standard prevents confusion.
  • Use ABC indicators to classify equipment criticality. This helps maintenance planners prioritise resources.
  • Set measuring point limits for all critical equipment. SAP's automatic validation catches data entry errors and provides early warnings.

11 Troubleshooting

ProblemLikely CauseSolution
No data in the ALV grid Measuring points not assigned to the selected equipment, or no measurement documents exist for the date range Verify equipment-measuring point assignment using IK03 (display measuring point). Check IK13 for existing measurement documents in the date range.
Chart appears empty Selected characteristics don't match any measuring point data in the date range Verify that the characteristics used in the selection screen match the ones assigned to your measuring points. Both Characteristic 1 and 2 must match.
Incorrect reading values Unit conversion applied unexpectedly, or wrong reading recorded Check the original unit (RECDU) in the measurement document. Use IK12 to view the document details.
ALV subtotals look wrong Measuring point sort option is disabled Enable "Sort by MP" on the selection screen. Subtotals and aggregation only work when this option is ON.
Date validation error Date is today, in the future, or beyond the allowed range Day mode: ensure the date is not today and within 14 days back. Week mode: within 7 weeks. Month mode: within 4 months.
Report is very slow Too much equipment selected without date filtering Reduce the equipment selection to only necessary equipment. Narrow the date range if possible.
"No data selected" error gt_sequnce generated dates that fall outside available data range Reduce the p_last value or select a more recent p_date. The report's date range construction is inverted (most recent = low, oldest = high).
Measuring point not listed in F4 help Characteristic not linked to the measuring point Check IK02 (change measuring point) and verify the characteristic assignment on the Characteristics tab.

12 Related Transaction Codes

TCodeFunctionSection
IE01Create EquipmentEquipment Master
IE02Change EquipmentEquipment Master
IE03Display EquipmentEquipment Master
IE05Equipment ListEquipment Master
IL01Create Functional LocationFunctional Location
IL02Change Functional LocationFunctional Location
IL03Display Functional LocationFunctional Location
IK01Create Measuring PointMeasuring Point
IK02Change Measuring PointMeasuring Point
IK03Display Measuring PointMeasuring Point
IK11Create Measurement DocumentMeasurement Recording
IK12Change Measurement DocumentMeasurement Recording
IK13Measurement Document ListMeasurement Recording
IK14Delete Measurement DocumentMeasurement Recording
IK31Measuring Point List by EquipmentReporting
CT04Create CharacteristicMaster Data
CL02Create Class (for characteristic grouping)Master Data
IQ01Create Maintenance NotificationMaintenance Process
IW31Create Maintenance OrderMaintenance Process
IW32Change Maintenance OrderMaintenance Process
IW33Display Maintenance OrderMaintenance Process
MCI1PM Information SystemReporting
ZPM_MP_ANALMeasuring Point Analysis ReportThis Guide

The data processing flow of ZPM_MP_ANAL: The report generates date sequences from the selected period type, retrieves equipment from EQUI table, finds linked measuring points from IMPTT (filtered by characteristics), fetches measurement documents from IMRG, and then populates the ALV grid and chart data tables. Characteristic 1 readings go to the horizontal bar chart (READG column), while Characteristic 2 readings populate both the READG2 column and the vertical bar chart.