IT systems · Practical guide

Validating SAP QM: from inspection plan to effective material block

When SAP QM contributes to a material-use decision, follow the inspection plan and recorded result through to the stock production or dispatch can actually use. The examples are based on SAP S/4HANA Cloud Public Edition 2608. Verify the corresponding functions for other editions and releases.

Table of contents

At a glance

What does SAP QM validation involve?

Link SAP QM inspection planning, results recording, usage decisions and subsequent material movements to justified requirements and test evidence. Include failures, permissions and interfaces. A successful SAP transaction or positive usage decision alone does not demonstrate that a material block is effective or that a batch has received any legally required certification.

  • Edition, release, source of inspection and apps used determine the technical scope of inspection.
  • Test results, intended use, inventory type, and batch status are separate test objects.
  • Exception pathways and recalls warrant separate testing, including their logistical implications.
  • LIMS data transfers and ongoing operation are part of the validation of the specific process.

SAP QM specifically define: Edition, Release, and Process

SAP QM refers to the quality management functions within an SAP environment. The evaluated guidance applies to SAP S/4HANA Cloud Public Edition 2608. It covers, among other features, the app Usage Decisions Manage, F2345. This does not entail an equivalent function for SAP ERP or ECC, S/4HANA Private Edition, or earlier Cloud releases. Within a given edition, the actually implemented processes are decisive.

Therefore, hold the following points firmly: Which release is currently being processed productively? Which test results, facilities, and materials are involved? Is result capture performed in SAP or in the laboratory? Which application determines onward release? The general S/4HANA validation approach remains as described in the linked foundational article; here, the focus is on the technical QA chain and its interconnections.

A useful scope description might include the incoming material inspection of a specific raw material type, using external laboratory results and controlled transfer from the inspection inventory. This approach is more demonstrable than the blanket requirement to validate the entire quality management module.

Sources: [1] [6]

Further reading:

GMP requirements relate to the actual use of the system.

The regulatory examples of this article relate to the production of medicinal products for human use in the EU-GMP environment. Annex 11 treats computerised systems in GMP regulated activities as a GMP guideline and describes a well-founded, risk-based approach. The European Commission continues to include the January 2011 version in the relevant list. For medical devices, veterinary medicinal products or other industries, the respective basis should be defined separately.

FDA Part 11 is an additional scope question: Which required records do you create or use electronically, and which FDA requirements apply? Neither SAP nor the term Quality Management generically fulfills the same set of requirements.

Specify your requirements based on potential decision errors: incorrect specifications, use of a foreign inspection lot, premature conclusion, or use of material despite an unresolved test result. Map existing SAP, implementation, and test documentation to these requirements. Gaps in coverage remain visible; a comprehensive manufacturer’s manual does not replace this alignment.

Sources: [10] [9] [12]

The inspection plan and master inspection characteristic must be compatible with the batch.

SAP Help describes master inspection characteristics as reusable master data with a plant, version, status and qualitative or quantitative type. They can also specify limits, methods and control indicators. Validation must establish whether the limit is applied correctly in the actual inspection lot. A correct value on screen alone cannot show this.

Verify material and site assignments, planned release, cut-off date, and professionally approved attribute specifications. If a plan change is implemented: Which status applies to a newly produced batch, and how is the previous status of an ongoing or completed process maintainable and traceable? Define the desired behavior prior to testing.

For missing inspection plans, SAP identifies a significant exception: In the case of a mandatory goods receipt inspection, a goods receipt and a batch may occur even though the usage decision has not yet been feasible. Therefore, a recorded goods receipt does not constitute evidence of a fully prepared quality inspection.

Own decision support for inspection planning
Item under testDecision to makeSuitable evidence
Materials and manufacturing processes Which approved plan applies on the inspection day? Lots with documented planning and material assignment
Quantitative Attribute What units and limits are approved? Target comparison as well as values at and beside the limit value
Qualitative Attribute Which attribute expressions are acceptable? Accepted and rejected example batch result
Change plan Which existing lots are affected? Comparison before and after controlled switch
Missing plan How is an incomplete process identified? Treatable failure scenario with designated responsible party

Sources: [3] [4]

Properly capture and correct results in a technically accurate manner

The app for tabular result capture can aggregate multiple batch attributes across different batches. It supports various data entry methods; evaluation may be performed manually or automatically depending on the sampling procedure. This creates independent audit risks related to misclassification and inappropriate evaluation rules.

Use deliberately similar batches of the same material for testing. Verify that the value appears at the correct batch and attribute, that the unit is unambiguous, and that the configured evaluation mode produces the intended decision. Also check for missing values, invalid inputs, and a plausible correction scenario. A cleanly filled form still does not fully reveal these boundaries.

Annex 11 addresses additional accuracy checks for critical manual entries. It does not require a second-person check for every field. Suitable validated electronic checks are another option. Assess the consequences of error, then identify which control covers the specific result type and what evidence you need.

Sources: [5] [9]

Intentionally evaluate usage decisions and exception pathways

F2345 can capture and modify usage decisions. The help text also describes a forced feature closure without captured results. Therefore, your test planning must not conclude that missing results technically prevent any closure. Determine who is authorized to use such exceptions and what technical justification or additional controls are required.

Particularly important is the reversal: According to SAP, when a usage decision is reversed, the stock postings are not automatically reverted. Therefore, a corrected decision does not automatically restore the previous logistical state. Review the complete correction procedure, including already transferred quantities, and notify the relevant process owners.

A usage decision is not automatically equivalent to the legally mandated batch certification. For human medicinal products, Annex 16 distinguishes between the evaluation of manufacturing and control, certification by a qualified person, and transfer to marketable stock. If SAP supports these steps, roles, records, and transfers must be explicitly designed to cover them. The QM app alone does not constitute evidence of this implementation.

Sources: [1] [11] [9]

Further reading:

Connect stock type and batch status to the restriction the system actually enforces

SAP provides stock postings prior to, during, or after the usage decision for stock-relevant batches, as long as quantities remain open. Booking suggestions can be linked to decision codes. A non-stock-relevant batch does not offer this booking option. Therefore, verify the actual batch type and the configured quantity flow.

Treat pending stock, locked stock, and batch status as distinct entities. For recurring batch inspections, SAP provides separate options for booking into pending stock or for changing the batch status, each triggered by time-dependent events. The mechanism within your workflow that prevents usage must be derived from the configuration.

Attempt the relevant material withdrawal, transfer, or shipment handover using the respective involved role in the test. A lock mark alone is insufficient as a verification result if the material can still be further processed under a different application. Document all permitted exceptions and incorporate linked storage solutions. According to SAP Help, transaction F2345 cannot be used for usage decisions regarding partial quantity postings in SAP EWM. Define the intended handling procedure for such stocks and independently verify it.

Sources: [2] [7] [1]

External results require a traceable path for review and verification.

SAP provides a workflow for the Inspection-Lot-API comprising inspection process, event, retrieval of attributes, handover to a subsystem, and subsequent result feedback. The described variant explicitly does not cover result capture for inspection points. This represents a system interface boundary that you should clarify prior to utilizing an existing integration component.

Define the lead system for raw data, technical evaluation, and SAP feedback. As a standalone audit tool, a message comprising batch, process, attribute, unit, and result status is recommended. Intentionally vary: foreign attribute, repeated message, delayed correction, missing response, and interrupted connection. The expected behavior arises from your interface specification, not solely from a successful API call.

Particularly address the reprocessing: Who identifies a pending process, who is authorized to resubmit, and how do you prevent conflicting processing in the laboratory and SAP? Also verify the professional readability of the result as well as the technical transmission. Annex 11 explicitly includes appropriate controls for electronic data exchange.

Sources: [6] [9]

Further reading:

Example: Raw material batch with unresolved result

This fictional test scenario has not been executed in SAP. At goods receipt, an inspection lot is created for a raw material batch. Quality control records a positive identity result, but a second required result is still missing. The defined requirement is that the material must not be issued to the intended manufacturing order until the quality decision is resolved.

Conduct the process using realistically separated test batches: Laboratory, Quality Release, and Storage. Maintain control over opening inventory, planned status, and authorizations. Subsequently, verify both normal processing and a potential exception closure. The actual blocking effect must be demonstrable within your environment; this example does not assume a fixed SAP standard configuration.

The test is only completed after evaluation of the open points. An unexpected removal possibility is a finding to be examined, no reason to formulate the target appropriately afterwards. The proof package includes the target and the actual, relevant data sets, deviation decision and, if necessary, the justified repetition test.

Own test matrix for the inventory receipt example
VariationTested behaviorEvidence
Required result is missing Predefined control prevents unauthorized further use Status, decision and sample take
Result outside specification Evaluation and subsequent decisions align with the release policy. Result, Evaluation Rule and Documented Decision
Unauthorized role attempts exception Exception closure is prevented or strictly controlled. User role and observed system behavior
Decision is withdrawn Existing booking is recognized and processed accordingly. Material charge, residual quantity and correction decision rationale
Labor resubmits results Duplicate or conflicting communications remain under control Event log and final business state

Sources: [9] [1] [2]

Configuration, releases, and traceability ensured

A new selection set, modified permissions, or revised interface assignments can likewise impact the quality management (QM) chain, just as a software update can. Therefore, evaluate changes based on affected requirements and processes. A justified regression test focuses on altered functionalities and relevant dependencies; a blanket, comprehensive test of all SAP modules does not follow from this.

For automated acceptance decisions, SAP specifies prerequisites and exclusions. The function evaluated here is not intended for batches with inspection points; for specific production batches, SAP directs to other applications. When using automated decisions, deliberately test the triggering conditions and cases that should not result in an automated acceptance.

Additionally, specify how relevant result changes, decision corrections, and rights modifications will be traced and evaluated, and identify who is responsible for such evaluations. A material document is a record of a transaction, but does not automatically represent the complete history of all quality-related data changes. Assess the required documentation, its availability, and review requirements based on the specific process. Supplement with provisions for system recovery, incident handling, and periodic evaluation of the system.

Sources: [8] [2] [9]

Start with a robust initial foundation for implementation

For SMEs, unnecessary effort often arises from unclear master data or inconsistent release rules. Before concluding tests, QA, Quality Control, SAP responsibility holders, and warehouse or production personnel should jointly walk through a selected process. The implementation partner will explain the configuration; subject matter experts will determine the required process behavior.

Plan the scope and timelines based on actual dependencies: number of process variants, data quality, individual customizations, LIMS/EWM integration, and available test environment. Accepted evidence can save effort when it is relevant to the version and intended use. However, open technical decisions cannot be replaced by additional test scripts.

  • Edition, release, works, batch origins and applications clearly documented.
  • Approved test protocols, attributes, units, and decision codes available.
  • the types of stock, batch status and permissible material movements.
  • Normal case, missing result, recall and unauthorized action planned.
  • Point of contact for interfaces, fault handling, and test data assigned.
  • Appropriate test environment and traceable configuration state provided.
  • Deviation evaluation, final decision, and handover to operations are governed.
  • Change process, data access, recovery and ongoing responsibilities defined.

Sources: [9]

Project experience and collaboration

Verify the effect of an SAP usage decision on logistics

With Quality, we select an inspection lot and trace its result to the material movement. Production and Logistics demonstrate what a positive, negative or reversed usage decision actually does. We map existing SAP QM evidence to those transitions. A single open stock rule may need a focused test. For several inspection lot origins or a LIMS interface, we plan cases across system boundaries to assess the quality decision and its effect together.

Frequently asked questions about SAP QM

Must the entire SAP system be revalidated for SAP QM?

The scope follows the affected process and its dependencies. For a new quality management (QM) procedure, existing validation evidence for routine operations or unchanged functions may remain applicable, provided their suitability is assessed. Additionally, evaluate which master data, user roles, material movements, and interfaces are impacted by the new procedure. A blanket revalidation of all modules is therefore not warranted.

Sources: [9]

Do these QM functions also apply to SAP ECC or S/4HANA Private Edition?

The specific functional evidence applies to S/4HANA Cloud Public Edition 2608. Similar naming does not permit unverified transfer to ECC, Private Edition, or other releases. Use the appropriate vendor documentation and document the actual workflow in those environments. Technical questions regarding the correct audit plan, accurate results, and effective blocking remain valid as standalone audit support.

Sources: [1] [3]

Why is creating an inspection lot successfully insufficient evidence?

A batch may be released even if a required inspection plan is missing. SAP documents this scenario for mandatory incoming goods inspection: goods receipt and batch generation are possible, but the usage decision has not yet been made. Therefore, verify plan availability, release status, material traceability, and processability. Supplement the documentation up to the point of actual permissible further use of the material.

Sources: [4] [2]

Is a positive usage decision already equivalent to pharmaceutical batch certification?

No, this cannot be derived solely from the decision code. Annex 16 specifies certification by a qualified person and the subsequent transfer to marketable stock as separate components of batch release. If your system captures these activities, verify the specific role, documentation, and technical linkage. A routine quality management (QM) decision does not establish these requirements.

Sources: [11] [9]

Is the inventory automatically relocked after revocation of the usage decision?

The help for F2345 explicitly states that reversing the decision does not reverse stock postings. Check the actual stock position after the correction. The follow-up process must account for quantities that have already moved. The person correcting the usage decision should be able to agree any required stock action with those responsible.

Sources: [1] [2]

Which test cases are particularly important for automated usage decisions?

Verify the established prerequisites and any breaches thereof: missing results, rejected attributes, or recorded errors. The evaluated SAP function also identifies exclusions, for example, for batches with inspection points, and refers to other applications for specific production batches. Therefore, a positive automated test is insufficient. The specific scope of automation must align with your release and intended quality processes.

Sources: [8]

How is integration of a LIMS into SAP-QM validation addressed?

Consider the professional assignment and the full feedback workflow: Batch, Process, Attribute, Unit, Value, and Processing Status. Test not only successful transfer but also repetition, interruption, and a contradictory correction. The evaluated SAP-API example does not include result capture for test points. For such workflows, you require the appropriate integration justification instead of unverified transfer.

Sources: [6] [9]

What must be available prior to the initiation of a QM validation project?

You require a clearly defined target process, available master data, the actual system configuration, and an appropriate test environment. Particularly useful are approved specifications and a clear presentation of inventory and release rules. Address open process decisions early. Otherwise, although the project may generate numerous test results, it will not be able to reliably assess their technical validity.

Sources: [9] [3] [4]

Who must work alongside IT and QA in SAP QM?

Quality control explains inspection characteristics and result evaluation. Warehouse and production staff assess the consequences for material movements. SAP owners and the implementation partner explain configuration and technical limits. Include the owners of connected laboratory or warehouse systems and, where batch certification is involved, the responsible Qualified Person. Assign each decision and record to its proper owner.

Sources: [9] [11]

What factors determine effort and duration for SAP QM?

Pipelines are primarily process variations, quality of the inspection planning, individual enhancements, interfaces, and unclarified exception pathways. The availability of qualified inspectors and representative test data also influences the workflow. Existing, relevant evidence can reduce the need for additional validation. A robust planning approach emerges following a limited scope and gap assessment; it cannot be derived from the product name or the number of users.

Sources: [9]

Sources and review date

The functional documents refer to SAP S/4HANA Cloud Public Edition 2608, as of October 6, 2026. Edition, apps, configuration and interfaces of your environment are to be compared separately. The test aids are own recommendations; a concrete SAP installation has not been tested for this. Complementary targeted source comparison on October 18, 2026: SAP help F2345, visible cloud reference number 2608,500, to the limit for EWM subset bookings.

  1. SAP: Manage usage decisions, F2345
  2. SAP: Stock postings
  3. SAP: Display Master Inspection Characteristic, F2219
  4. SAP: List of missing inspection plans
  5. SAP: Tabularly record inspection results
  6. SAP: Example: Recording Inspection Results in an External System
  7. SAP: Periodic inspections of batches
  8. SAP: Automatic usage decision
  9. EU GMP Annex 11: Computerised Systems
  10. European Commission: EudraLex Volume 4
  11. EU GMP Annex 16: Certification by a Qualified Person and Batch Release
  12. FDA: Part 11 — Scope and Application

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Clarify the critical transition points in your Quality Management process

Daniel Herrmann Consulting supports you in aligning professional release criteria, 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.

Send a project enquiry Customer testimonials →