Table of contents
At a glance
What does SAP PM validation involve?
Demonstrate that configured maintenance and measuring equipment workflows support their intended tasks. Trace the correct equipment from the maintenance plan through the order and, where relevant, the QM calibration inspection to actual use. Distinguish order completion, the inspection result and the decision on equipment use. Data, roles, interfaces and failure consequences determine scope. This does not require blanket validation of all SAP functions.
- Edition, release, and actually used SAP functions must be aligned with the considered device process.
- Equipment, technical area, task, and inspection result must professionally and technically align correctly.
- Task completion does not constitute automatic confirmation of device suitability.
- The actual usage effect and operation after changes are part of the proof.
Classify SAP PM within the specific S/4HANA environment
SAP PM is the common theme name for maintenance in SAP. This article uses as a documented framework Maintenance Management in SAP S/4HANA 2025. The Scope Description feature is available in document version 2.3 of 31.07.2026. The additional SAP landing page describes a calibration scenario for the Fully-Activated Appliance 2025 FPS01.
This reference is intentionally more specific than a general statement covering all SAP landscapes. Appropriate documentation must be provided for ECC, S/4HANA Cloud Public Edition, or other releases. The presence of a feature described in terms of functionality does not confirm that it is licensed, implemented, or correctly integrated with other processes in your environment.
Therefore, record the edition, release, relevant organizational units, deployed applications, and enhancements. Subsequently, describe a specific process from the affected device through to its actual use. The general S/4HANA guideline remains responsible for the overall approach; here, focus is on the maintenance and testing tool chain.
The critical equipment selection determines the scope
The regulatory examples apply to human medicinal products within the EU GMP framework. Annex 11 is classified as a GMP guideline for computerised systems; the current EudraLex version cited is from January 2011. Sector-specific or industry-specific regulations must be addressed separately. For FDA-related records, the applicability of Part 11 must be assessed based on the underlying obligations and electronic usage.
Start with potential failure: an inappropriate device is used, maintenance is documented on the wrong equipment, or a overdue inspection remains undetected. These lead to required functions and controls. Cost or procurement functions may lie outside the scope of the assessment, provided they do not establish a relevant dependency. However, the absence of a spare part or a misattributed external test result may alter this boundary.
Distinguish the software's suitability from the device's suitability. A correctly configured task does not replace required maintenance or calibration. ICH Q9(R1) supports a risk-based determination of validation extent. For this, you do not need a rigid category derived solely from the module name nor the same test volume for all technical objects.
Assign equipment, installation location, and measurement values unambiguously
SAP defines technical locations for structuring the facility and equipment as individual maintenance objects. Sensors and counters document the states of technical objects in measurement records. This raises a key question for your process: Does information refer to the installation location or to the specific physical device?
Consider a device replacement. When a different measuring device is installed at the same location, previous calibration results must not be assigned to the new device without a valid technical basis. Therefore, verify equipment identifier, serial number, installation period, and its relationship to the measurement point. This check guide outlines an intended control objective and does not claim any automatic SAP protection function.
Use similar identifiers and controlled equipment changeovers as a control sample. A clean extract of the master data displays only the relevant time point; to evaluate a prior usage, you need the then-applicable equipment assignment. Document which data are pivotal and who authorizes or verifies changes to equipment identity.
Review maintenance plan, task order, and feedback separately
The described S/4HANA scope includes scheduled maintenance planning, work processes, and notifications and tasks for planned or unplanned activities. Upon feedback, information on executed activities and measurement values can be captured. Critical to the validation evidence is whether this processing accurately reflects the intended technical assignment.
First, establish the triggering deadline or condition, affected devices, and required activities. Then, assess the origin pathway, specific assignment, and a deliberately incomplete process. A response confirming completed work does not necessarily indicate that all required test results are available or that subsequent use is permissible.
The following custom matrix separates the decisions. It prevents a single status field from being interpreted simultaneously as a schedule booking, work assignment record, and equipment release. The applications and status values you use for this purpose should be included in the description of your configuration.
| Object / Step | Process question | Specific test validation |
|---|---|---|
| Equipment | Which physical device is affected? | Compare serial number and identifier with test device |
| Maintenance plan | What work is required when? | Compare the specified due date with the activity triggered |
| Assignment | Is the device and the required activities correctly assigned? | Incorrect equipment and missing activities as deviation events |
| Feedback | What was actually accomplished? | Complete and incomplete processing differ. |
| Calibration check | Does the device meet the specified requirement? | Compare result against independent target |
| Device usage | How is authorized use actually implemented? | Record usage in the subsequent process step |
Define the boundary between maintenance and quality management clearly
The SAP documentation references calibration verification of test equipment within the Quality Inspection area. The reviewed FPS01 decommissioning description links named testing or measuring devices in maintenance assignments to evaluations against predefined performance specifications. This demonstrates the technical interrelationship, but does not specify the exact type of task, transaction, or complete configuration of your installation.
Describe the characteristics and specifications that define the inspection task, who records the results, and what decision follows. When an external calibration service is utilized, the assignment of its findings to the correct device and task must be maintained. An attached certificate should not be considered a positive decision without review, especially if it contains limitations or unmet criteria.
Chapter 3 §3.41 addresses calibration and control using appropriate methods and records at defined intervals. The specific metrological evaluation remains the responsibility of the competent authority. The existing SAP-QM article enhances material testing and inventory tracking; this article remains applicable to the testing equipment. A determination of the equipment's suitability is not a decision regarding the release of a medicinal product batch.
From test result to actual device usage verify
A positive test result, a completed order, and a usable device represent distinct factual statements. The SAP status values or follow-up actions associated with them must be defined by your organization. The evaluated documentation includes follow-up actions for inspections of technical assets; it does not establish a general automatic production hold for any overdue equipment.
Therefore, specify a clear requirement: a specific test method may only be used for the intended process step if the accepted validation is current and the equipment assignment is correct. Subsequently, define the control pathway in SAP, in the linked system, or through a regulated equipment issuance process. A technical control is only meaningful if the production route actually utilizes it.
Consider expiry date, disruption in handover, and permitted exceptions. For ongoing processes, it must be clearly defined what constitutes a new negative information. Not every status issue requires the same corrective action; the response depends on the process and the associated risk. However, deliberately assess whether an existing positive information may override a new restriction decision.
Example: Pressure gauge following maintenance and inspection
This example was not executed in SAP. Equipment P-204, serial number M204, is installed at functional location L-07. Maintenance order W-410 covers this equipment. Permission to use it expires at 08:00 on 6 October 2026 (Europe/Berlin). After that point, the example test requirement calls for an accepted calibration result, the specified decision on use and confirmation that the resulting status has taken effect.
For software testing, the specialist department has predefined reference values of 0.00, 5.00, and 10.00 bar, along with a test rule specifying that the absolute difference between display and reference value shall not exceed 0.10 bar. This represents a simplified test model. It does not replace a calibration method; measurement uncertainty, normality, and actual operating conditions must be considered separately in the actual procedure.
The first data set recorded at 08:30 Uhr reads 0.02, 5.12, and 10.04 bar. Independently calculated deviations amount to 0.02, 0.12, and 0.04 bar. The mean value is not acceptable. Even after confirmation of completed maintenance activities, the example process is therefore not permitted to proceed. A new data set, obtained following the implemented action, shows values of 0.01, 5.08, and 10.03 bar, yielding deviations of 0.01, 0.08, and 0.03 bar; all three meet the test criteria.
Instead of addressing the identity error, P-205 with serial number M205 is installed at the same position. A positive result for P-204 shall not authorize the release of P-205. Prior to each independent variant, a documented initial state must be restored. The ongoing incident case, however, retains both findings and their interrelationship. Tables and invoices define only the required values; actual system behavior must be observed during the project.
| Variant / Input | Independently determined expected result | Expected evidence |
|---|---|---|
| 07:59 Uhr; existing validation evidence remains valid | Use permitted under current authorization | Demonstrate the correct device and valid status state |
| 08:00 Uhr; deadline reached | No use without new accepted proof | User testing is rejected upon control. |
| 08:30 Uhr; 0.02 / 5.12 / 10.04 bar | 0.02 / 0.12 / 0.04 bar; median point rejected | Find remains valid despite completed maintenance |
| At the 5-bar point: 5.10 or 5.11 bar | 0.10 accepted; 0.11 rejected | Includes boundary and decimal handling |
| New sentence: 0.01 / 5.08 / 10.03 bar; decision open | Acceptable values, usage decision still pending | No premature authorization based solely on measurement values |
| Positive result for P-204; installed is P-205 | No transfer of suitability to foreign equipment | Device mix-up identified and addressed |
| P-204 decided; recipient notification lost | Recipients shall not accept unchecked clearance levels | Proposed default procedure comprehensible |
| P-204 approved and status correctly carried over | Usage per example requirement possible | Order, result, decision and utilization linked |
Records and corrections beyond object boundaries are recorded.
The evidence often spans equipment history, order data, test results and supporting documents. Identify which records support the decision on equipment use. Chapter 4 covers calibration and maintenance records and logbooks for major or critical equipment, among other matters. A report must show the relevant relationships clearly.
Review a controlled data correction: A result was assigned to the correct device but with an incorrect unit. The original entry and the corrected statement must remain traceable. Who is authorized to make the correction and who evaluates the impact on a previously made decision? A correction carried out according to a defined procedure is not automatically equivalent to a change in SAP configuration.
Conversely, if a review rule, role-based permission, or interface is modified, the system change must be managed under controlled conditions. The required audit trail and review shall be based on relevant data and risk assessments. Do not assume universal SAP audit trail coverage based solely on the existence of individual change documentation. Perform and demonstrate the exact change under consideration with the intended role.
Record transfers, migrations, and restorations in the chain of custody
For external calibration services, mobile solutions, or attached production, the critical error may arise between applications. Describe which identifier and which result transfer, and which system holds the decisive decision. The manufacturer documentation for this article does not provide a universal message format. The expected behavior is derived from your interface specification.
Own control samples are a delayed result, a duplicate message, and a correction following an already accepted decision. Also verify the reconciliation following a system failure: technically retransmitted data must not generate incorrect device assignments or contradictory release statuses. For migration and restoration, values, significance, and required history must be evaluated jointly.
Evaluate changes based on relevant requirements and dependencies. A new system status or expansion may necessitate targeted revalidation checks; a comprehensive, one-off test of all SAP modules does not follow. Appropriate SAP, partner, and project documentation can be utilized when the actual scope aligns with the environment. Additionally, agree on operation, failure assessment, and periodic review of the achieved state.
Prepare an SAP-PM project with the right stakeholders involved
Maintenance and metrology should be able to demonstrate a real device workflow prior to script development. QA evaluates the evidence and control range, the SAP responsible party or partner provides explanation of the customizing, and production or laboratory demonstrates actual usage. IT and interface responsible parties clarify technical requirements. For outsourced activities, the service provider's validation pathway is included.
For SMEs, the main drivers of effort are device and process variations, mature master data, expansions, integrations, and available specialist time. An existing SAP system can provide prior operational records; however, the suitability of these records must still be assessed. Start with a clearly defined critical device chain and leverage the insights for justified planning of additional variations. A fixed project duration does not follow.
- Edition, Release, Applications in Use, and Enhancements described.
- Equipment, serial numbers, technical locations, and history traceable.
- Maintenance plan, task assignment, and required inspections technically justified.
- Calibration specifications, result types, and decision authorities clarified.
- Validity and actual control of usage is defined.
- Test environment, independent required and separate fault scenarios prepared.
- Supplier and inventory evidence evaluated for specific fit.
- Transfers, corrections, restoration, and changes scheduled.
Project experience and collaboration
Trace the maintenance order through to continued equipment use
A closed maintenance order does not by itself settle whether equipment may be used again. With Maintenance and the process owners, we identify the work, assessments and decisions required, then test how your SAP PM configuration supports them. For a familiar maintenance process, we focus on missing evidence. For a new equipment class, we also identify who assesses findings, authorises use and passes status to downstream processes.
Frequently asked questions about SAP PM
Does this guide also apply to SAP ECC or the Public Cloud?
The functions described herein apply to SAP S/4HANA 2025; SAP's accompanying calibration example references FPS01 for 2025. An identical implementation in ECC or S/4HANA Cloud Public Edition is not claimed. You may use the methodological questions provided, but you must verify the apps, data objects, status logic, and supported workflows based on the correct edition and your specific release.
Must the entire ERP be revalidated for SAP PM?
The scope results from the affected device process and its dependencies. Existing evidence for unchanged functions can remain usable. However, check whether procurement, external services or a production interface influence the critical process. Neither the flat-rate inclusion of all modules nor the flat-rate exclusion of commercial functions answers this question.
Why are equipment and technical space to be separately verified?
A device location may have contained different physical devices over time. For a device assessment, it must be demonstrable which device was actually used during a prior operation. Therefore, evaluate device changes including device identifiers and temporal assignments. A positive finding for the retired device shall not be considered sufficient evidence for the replacement device solely based on the same installation location.
Is a completed maintenance task already considered equipment release?
Completing a maintenance order also releases the equipment only if the configured process covers all the prerequisites. A confirmation can record completed work while the calibration assessment or the decision on use remains open. Specify the prerequisites and test what happens when a transaction is deliberately incomplete or unsuccessful. The observed behaviour must match the approved requirement.
Where does the boundary lie between PM and QM in calibrations?
The maintenance process organizes equipment and required activities; Quality Management (QM) can support calibration verification and its evaluation. SAP defines this linkage for testing and measuring equipment. The specific data and steps your facility utilizes must be explained separately. The inspection of a device remains distinct from a material inspection and its inventory decision.
How do we verify the usage restriction during overdue calibration?
Track the expiry of equipment status from equipment status to actual usage. Define which application or organizational control is intended to prevent usage. Also verify outdated status information and failure of technical integration. A single equipment flag alone is insufficient if the relevant process does not take it into account.
How do we verify an external calibration certificate in SAP?
Assign it unambiguously to the device, the order, and the performed procedure. Evaluate the results, limitations, and professional conclusions prior to establishing a positive usage status. Test a mock document for a similarly named device and a non-acceptable finding. A successfully uploaded document initially indicates only that a file exists.
What must be available prior to startup?
Provide a clearly defined process, reliable device data, maintenance and inspection requirements, and the technical system status. Identify the operating department, its release criteria, and the interface pathway. Supplement existing documentation and establish an appropriate test environment. If the desired behavior is not achieved, specialist decisions must be clarified first; such decisions cannot be replaced by extensive test scripts.
Who must work alongside SAP-IT and QA?
Maintenance includes operating procedures and equipment assignment; metrology or the responsible department evaluates calibration and measurement specifications. Production or laboratory confirms actual usage. The partner supports with configuration and interface setup; external service providers provide their assessment findings. Responsibilities must align, even in small companies where individual personnel may perform multiple tasks.
Sources: [4]
What factors drive effort and duration?
Crucial factors include the number and diversity of device processes, data quality, internal enhancements, external findings, and integration with intended use. Additionally, data integrity, test environment, and available specialist support must be considered. Initially assess a representative process chain, including failure cases. From this, it can be estimated which variations are transferable and which require additional evaluation. A generic weekly estimate would lack substantiation without this foundational assessment.
Sources and review date
As of 6 October 2026. Supplier reference: SAP S/4HANA 2025, Feature Scope Description Version 2.3 dated 31 July 2026, along with the reviewed Landing page for the FPS01 calibration scenario. No functional transfer to ECC or Public Edition. Tables and calculation examples are standalone review aids; a specific SAP installation was not tested.
- SAP S/4HANA 2025 — Feature Scope Description
- SAP S/4HANA 2025 FPS01: Asset Management — Calibration Processing
- European Commission: EudraLex Volume 4
- EU GMP Annex 11: Computerised Systems
- EU-GMP Chapter 3: Facilities and Equipment
- EU GMP Chapter 4: Documentation
- EMA: ICH Q9(R1), Step 5, Corr.2
- FDA: Part 11 — Scope and Application
Sources checked: .
Clarify the calibration process up to actual use.
We support you in aligning device selections, SAP configuration, and existing evidence into a justified validation scope.
- SAP S/4HANA validation →
Support an SAP go-live with evidence your team can defend at audit while keeping validation on schedule. We take a risk-based approach from the template to the interface for greenfield or brownfield projects and existing ECC systems.

