Calibration SAP
Calibration SAP
Manage Test
Test Equipment Calibration
Processes with SAP Plant Maintenance and
Quality Management
by Gaetano Altavilla, Senior SAP Practice Manager
October 27, 2017
Learn how to manage the calibration processes for a plant’s test equipment using the Plant
Maintenance (PM) and Quality Management (QM) functionalities with options available in the SAP
system. In particular, find out how to manage your calibration activities to complete business
transactions using master data from integrated modules and configuration done based on a
company’s business processes and strategies using standard options available in the SAP
system.
Key Concept
In a company, the test equipment (i.e., measurement tools) should be checked regularly. Planning and
execution are performed using a maintenance plan that automatically generates an inspection lot. In the
SAP Quality Management (QM) component, the measurement readings for the characteristics Length
and Diameter of a test probe pin are entered for this inspection lot. A test probe pin is
pin is a physical device
used to connect electronic test equipment to a device under test (DUT). Usually these devices are used in
case of electronic test requirements. If measurement readings lie outside of the tolerances, for example,
and adjustment is necessary, the status of the gauge is changed accordingly and a malfunction report is
generated with the appropriate error code. The integration of Plant Maintenance (PM) and QM is divided
into two areas: test equipment management
management (calibration inspection) and
inspection) and enhanced measurement
reading entry.
entry.
To ensure that specified performance criteria are always met, the test equipment being used must be
regularly checked and calibrated. You can use the functions of test equipment management to perform
The business transactional flow for the calibration activities is managed mainly by the Plant Maintenance
(PM) and Quality Management (QM) modules, as shown in Figure 1. 1.
Figure 1
Work center: The task list usage is important here so that the
relevant test equipment can be used in maintenance-specific task Display PM Notification
lists.
Table 1
Figure 2
Create an MIC
The QM department can create an MIC by using transaction code QS21 or by following menu path SAP
Menu > Logistics > Quality Management > Quality Planning > Basic Data > Inspection Characteristic >
Create. This path takes you to the screen in Figure 3.
Create. 3. For my example, you use an already existing
characteristic as shown in the screen in Figure 3.
3.
Figure 3
Click the
Here, for Quant. (quantitative)you
your characteristic, data button
can in the
define Figure 3 andmain
3 and
following the system
options:shows the places,
Decimal screen unit
in Figure 4.
4.
of measure,
lower and upper limits, Target value, and lower and upper plausibility limits. In Figure 3,
3, the MIC is ZERO
because in this example it is the name for the characteristic to define zero point deviation during the
equipment test procedures.
Figure 4
Figure 5
Lower specif. limit: If set, you must enter a lower specification limit for the inspection
characteristic.
Upper specif. limit: If set, you must enter an upper specification limit for the inspection
inspection
characteristic.
Sampling procedure:
procedure: If set, a sampling procedure must be assigned to the characteristic in the
task list.
Required char. (characteristic): If set, the inspection characteristic must be inspected, which leads
to the fact that a UD can only be posted if you have confirmed the inspection results for this
inspection characteristic.
Classed recording: If set, the inspection results for the inspection
inspection characteristic
characteristic are recorded as
classed values.
Defects recording: If set, an inspection characteristic is rejected. During results recording, the
function for recording defects for a characteristic is automatically called up and a recording
procedure can either be initialized by the user or performed in the background.
Figure 6
Fixed scope
scope:: If set, the number of inspected units must correspond to the precalculated number
of units to be inspected for results recording.
Test-equi assignment:
assignment: If this indicator is set, y
you
ou can assign test equipment to the inspe
inspection
ction
characteristic in the task list.
Docu. if rejected: If set, additional text has to be entered in case the characteristic has been
rejected during the results recording.
RR change docs docs (create change documents during results recording): If set, change documents
are created for this inspection characteristic when results are recorded based on characteristics.
Record measured vals: If set, measured values for this quantitative characteristic have to be
inspected and confirmed.
Print: If set, the inspection characteristic is printed on the inspection instruction.
Figure 7
Figure 8
In the
is Figure 9, of
9,
name you can
the find the details
characteristic of thefull-scale
to define General Data screen
deviation related
during the to the characteristic
equipment FULL. FULL
test procedures.
Figure 9
In Figure 10,
10, you can view the details of the Quantitative Data screen related to the characteristic FULL.
Figure 10
Figure 11
Figure 12
Figure 13
To create a task list, you can either use the transaction code IA05 or follow menu path Logistics > Plant
Maintenance > Preventive Maintenance > Work Scheduling > Task Lists > General Maintenance Task
Lists > Create. This action displays the screen in Figure 14.
14. For my example, you display a Task list that
was already created in the demo system, as shown in the Figure 14. 14.
Figure 14
Figure 15
Figure 16
To do so, either use the transaction code IP40 or follow menu path Logistics > Plant Maintenance >
Preventive Maintenance > Maintenance Planning > Maintenance Plans > Create > Single Cycle Plan.
This path takes you to Figure 17.
17.
Figure 17
In the Maint. plan cat. (maintenance plan category) field in Figure 17,
17, select Maintenance Order from the
options and then press Enter. The system then displays the screen in the Figure 18.18.
Figure 18
Cycle/Unit
Planning plant
Order Type: Enter PM06 for calibration
Main WorkCtr (work center)
Priority
Maint. (maintenance) Planner Group
MaintActivity Type (maintenance activity type)
Business Area
In the Task List section, enter the data that you entered in Figure 15.
15. After you press Enter the system
opens the screen shown in Figure 19 in19 in which you can select the Yes radio button and enter a date to
specify the cycle start date. Click the enter icon (the green check mark) to save the record.
Figure 19
Transactional
I now walk you through the stepsData
for main transactional data listed in Table 1.
1.
Figure 20
Figure 21
In the initial screen (not shown), specify the maintenance plan created in Figure 15 and
15 and press Enter. The
system then opens the screen shown in Figure 21
21 in which you click the display icon . The system
then opens a screen with the details shown in Figure 22.
22.
Figure 22
The system then displays the UD data. Select the Equipment tab to view the details shown in Figure 23.
23.
Figure 23
Select the line item and then click the choose object’s details icon to display the inspection point data,
as shown in the pop-up screen in Figure 23.23.
Based on this data, enter the inspection results using transaction code QE51N or by following menu path
SAP Menu: Logistics > Quality Management > Quality Inspection > Worklist > Results Recording.
Expand the relevant operation in the dialog structure (left column) and double-click the corresponding
equipment for the inspection lot. Then, you can evaluate the characteristics.
In
andmy example,
rejected theyou have
rest. accepted
Save theThe
your data. results record
system fordisplays
then the Equipment 10003540
the details shown and operation
in Figure 24. 0020
24.
Figure 24
Record the UD
You can record the UD either by using transaction code QA11 or by following menu path Logistics >
Quality Management > Quality Inspection > Inspection Lot > Usage Decision > Record. The screen
in Figure 25 then
then appears.
Figure 25
One response to the valuation of equipment 10003541 could be, for example, a reduction of the cycle
modification factor, which results in the maintenance cycle being shortened. A malfunction report
(category MQ) was generated with two items (zero point error and end of scale error) and corresponding
error codes. (I discuss the malfunction report for category MG in the next section.) Measurement
documents were still generated for all the measurement readings.
Note that after you save the UD, the system displays the details of the status change for objects or
equipment, as shown in the Figure 26. 26. You can also view these details by using transaction code IE03
and verifying that the status of the equipment has been updated to NPRT PRT, which is not ready for
use.
Figure 26
Figure 27
Display PM Notifications
Usually, you can display the PM notifications either by using transaction code IWS3 or by following menu
path Logistics > Plant Maintenance > Maintenance Processing > Notification > Display.
In my example, however, use transaction code QA13 and in the initial screen (not shown) enter the
Inspection Lot document number and press Enter. The system opens the screen shown in the Figure 28.
28.
Figure 28
Figure 29
Figure 30
Personnel no.:
no.: The
The employee ID for the person who actually performed the work
Actual Work:
Work: The
The number of hours spent to complete the work
Reason: The reason for variance
Reason:
Confirm. (Confirmation) text:
text: Any
Any reasonable text to justify the work done
Then, check that the rest of the defaulted entries are appropriate and save the data. The system displays
a confirmation message as shown in Figure 30. 30.
To update the PM Order as technically complete, you can either use transaction code IW32 or follow
menu path Logistics > Plant Maintenance > Maintenance Processing > Order > Change. In the initial
screen (not shown) enter the calibration order and operation in the selection screen and press Enter. The
system displays the screen in Figure 31.
31.
Figure 31
Run Reports
All affected and authorized departments
departm ents can display the details of the QM and PM documents related to
the calibration processes (for example, Quality Notification, Inspection Lot, and PM Orders) using the
information system reports available under the QM and PM modules.
These two menu paths can be used to retrieve transaction documents created in the QM and PM
modules:
In QM, follow Plant Maintenance > Information System > Report Selection > Information Systems
Information Systems system reports available under the QM Centers Capacity/Maintenance.
In PM, follow Processing/Maintenance Planning/Maintenance Task Lists Quality Management > Test
Equipment Management > Information System > Equipment/Maintenance/Calibration Inspection.
Customizing Activities
Now I describe the most important customizing activities that you need to check or complete to enable the
external processes.
Figure 32
Figure 33
Assign the calibration order type to the inspection type
In Figure 33,
33, you can see that the plant 1000 and calibration order type PM06 combination has been
assigned to inspection type 14 (inspection in PM).
Inspection Point
In QM Customizing, you need to define an inspection point of category Equipment or Functional location.
The inspection point is entered in the task list header. To complete this step, follow menu path Quality
Management > Quality Planning > Inspection Planning > General > Define Identifier for Inspection Points.
This path displays the screen shown in Figure 34. 34. In the Fields tab populate the fields as shown
in Figure 34.
34.
Figure 34
Figure 35
To complete this step, you can either use IMG transaction code OPJ8 or follow menu path Tools >
Customizing > IMG
Control > Master > Edit
Data ProjectData
> Routing (SPRO) Pushbutton:
> Define SAP In
control key. Reference IMG.use
my example, Production > Shop
the control keys Floor
QM01
and PM01. These are standard SAP control keys and are displayed in Figures 36 and
36 and 37.
37. Make sure that
the check boxes enclosed in a red border in Figures 36 and
36 and 37 have
37 have been set in your system.
Figure 36
Figure 37
Follow-Up Actions
In QM Customizing, follow-up actions can be defined that can then be linked to the codes for UDs. If a
particular code is assigned when the UD is made, the assigned follow-up actions (for example, updating
measurement readings, status changes, and so on) are executed automatically. To complete this step,
follow menu path Tools > Customizing > IMG > Edit Project (SPRO) Pushbutton: SAP Reference IMG.
Quality Management > Define Follow-Up Actions. Then select in the pop-up screen (not shown) the
activity’s option Follow-Up
Follow-Up Actions. This action opens the screen in Figure 38.
38.
Figure 38
I now describe the follow-up actions for the three function modules shown in Figure 39:
39:
Figure 39
Figure 40
To complete this step follow menu path Tools > Customizing > IMG > Edit Project (SPRO) Pushbutton:
SAP Reference IMG. Quality Management > Quality Inspection > Inspection Lot Creation > Maintain
Inspection Lot Origins and Assign Inspection Types. This path takes you to the screen in Figure 41.
41.
Figure 41
Figure 42
With these entries, the system automatically creates an inspection lot upon the scheduling of a
maintenance plan.
To do so, follow menu path Tools > Customizing > IMG > Edit Project (SPRO) Pushbutton: SAP
Reference IMG. Quality Management > Quality Inspection > Inspection Lot Creation > Define Default
Values for Inspection Type. Then, double-click the line item containing the Inspection Type 14. This
action opens the screen in Figure 43.
43.
Figure 43
Default values for inspection type 14
In the inspection lot, with inspection type 14, enable the usage of Inspect by task list, Record
characteristic results, and Automatic usage decision indicator. Leave the rest of the fields as defaulted. In
an SAP system, the data is always saved using the save icon.
Figure 44
02 as Notification origin. It defines the screen sequence control for a Notification Type.
1000_QM as Catalog profile. It restricts the list of values for the information contained in the
quality notification based on your business requirements.
26 as Update group statistics. It is used to determine the fields that will be created for the
statistics in the Logistics Information System (LIS).
Gaetano Altavilla
Dr. Gaetano Altavilla is a senior SAP practice manager. His focus is on pre-sales, delivery of SAP
application solutions for large international corporations, and SAP knowledge management in Europe, the
Middle East, and Africa (EMEA).
In his 18 years of SAP application experience working for many multinational companies, such as Procter
& Gamble and Hewlett-Packard, he has covered a wide range of ERP logistic areas, focusing on the MM,
WM, SD, LES, PP, PP-PI, PLM (QM, PM, PS) modules, as welll as CRM (TFM), SRM (EBP), SCM (SAP
APO), and MES (ME) components.
com ponents.
Dr. Altavilla holds a degree with first-class honors in mathematics from the University of Naples and is
certified in many SAP modules: SAP Logistics Bootcamp, SAP MM, SD, LE (SHP/WM/LE), PP, PLM (PM,
QM, PS), SRM, CRM, SCM (APO), SCM (TM), FI, CO, and Solution Manager. He also has experience in
ABAP/4 and application link enabling (ALE) and IDocs. He has participated in numerous industry
conferences, such as the SAP Skills Conference in Walldorf at SAP SE.
If you have comments about this article or publication, or would like to submit an article idea, please
the editor .
contact the