IT systems · Practical guide

Testing SAP QM inspection plan changes and open inspection lots

An inspection plan has changed. An inspection lot that already exists may still be governed by an earlier version. Establish which version applies at that transition before using the new limits or characteristics in routine operation.

Table of contents

At a glance

How does an inspection plan change affect inspection lots in SAP QM?

Define the intended effective date and test new, open and already decided inspection lots separately. Record which specification version was assigned and whether reassignment occurs. The outcome depends on SAP edition, release, inspection type, lot status and configuration. Test the configured behaviour before concluding that a change reaches every existing lot.

  • Distinguish the inspection plan, the inspection setup in the material master and the specification assigned to the actual lot.
  • Define which rule applies to new lots, open lots and lots with a completed decision.
  • If reassigning a lot, account for any sample size already calculated and any results already recorded.
  • Keep historical limits and the decisions based on them traceable.

What do the inspection plan, inspection setup and inspection lot control?

An inspection plan defines planned operations and characteristics. The inspection setup in the material master influences how inspection lots are created and processed. Each lot holds the context of a particular inspection. A change to one of these elements does not automatically make the same change to the others.

For example, SAP documents that changes to the inspection setup affect new lots, not existing ones. Check how the mechanism works in your system before extending that statement to an inspection plan change or a custom enhancement.

The product references cover SAP ERP 6.0 EHP8 and S/4HANA On-Premise 2025 FPS01. Cloud editions can differ. Record your release, inspection type, relevant master data and extensions before executing the tests.

Sources: [1] [2] [3]

Agree the transition rule before changing the plan

A new specification needs an effective date and a rule for applying it. Does it apply to lots created from a certain date, specified batches or all open inspections? Establish the rule from the reason for change and the quality system. The date someone saves a change does not determine its business effect.

Consider previous decisions. Correcting an error in the old specification can require a different lookback from introducing a prospective change. Knowing that old lots technically remain unchanged does not settle how to deal with them.

Assign responsibility for changing, checking and approving the plan and for handling open lots. Implement the agreed rule. When a manual procedure is needed, make sure users can identify and process all affected lots.

Sources: [4] [5]

Document validity and the specification actually assigned

Record the inspection plan ID, validity, change number or revision information where used, status and critical characteristics. SAP documents these validity and change attributes for inspection plans. For the test, establish which version the actual lot used as well.

Determine when the specification is selected or adopted and whether reassignment is allowed. SAP ERP documentation gives the example of resetting a completed sample calculation before assigning another inspection specification. Check the prerequisites for the release and lot status in use.

Displaying the current plan does not demonstrate historical inspection conditions. A later reviewer must be able to identify which limit applied to a given result. Preserve the link between inspection lot, characteristic, result and decision.

Sources: [3] [2] [4]

Example of lowering an upper limit from 10.0 to 9.5 mg

Inspection plan A permits values up to and including 10.0 mg. Plan B sets an upper limit of 9.5 mg. In this example, new lots use B after the effective time. Open lots are assessed individually under a documented rule. Completed decisions remain historically traceable.

Create inspection lot L-A before the change and record the assigned version. Create L-B after the change. A test value of 9.8 mg falls below the old limit but above the new one. It distinguishes the two versions. Also test exactly 9.5 mg and 9.6 mg against the new rule.

Compare the actual lot characteristics and decisions with the transition rule. If controlled reassignment is allowed, test that separately. Assess existing results, permitted status transitions and history. Do not assume a lot can be reassigned in every status.

Example matrix for inspection plan versions and effective dates
Inspection lot or caseExpected result in the exampleEvidence needed
L-A created before the change The previous assignment remains identifiable. Apply the transition rule. Actual version and assessment of outstanding work
L-B created after the change takes effect Version B applies. A result of 9.8 mg is outside the limit. Lot characteristic, result valuation and status
Boundary value of 9.5 mg under B Passes because the limit is inclusive. Display formatting does not change the outcome.
Reassign an open lot Only under a permitted, controlled procedure. Prerequisites, existing results and history
Decision already completed The historical decision can still be understood. The version applicable at the time can be traced.

Sources: [4] [2]

Select open lots at different processing stages

An open lot before sample calculation differs from one with a calculated sample, partially recorded results or a nearly completed inspection. Select representative states from the process you actually use. One newly created lot cannot cover these differences.

Check which actions are allowed in each state and what they do to existing results. If the procedure prevents a version change, the block may be the expected result. If it permits a controlled change, preserve the relationship between that change and its effect on the inspection.

Test relevant exceptions such as another inspection type, an added characteristic or a changed unit. Select cases by the impact of the change. You need not repeat the same full matrix for every plan change, but do include differences that can affect results.

Sources: [2] [4]

Test result valuation and the usage decision separately

Start with the characteristic and its result valuation. Follow the subsequent workflow through the usage decision, stock effects and interface transfers where in scope. Displaying the correct limit does not establish that every downstream step works.

A SAP usage decision is not automatically the regulatory certification or release of a medicinal product batch. Describe its role in your process. Otherwise a technical status can suggest a broader decision than your evidence supports.

For automated steps, test invalid status combinations and transfer errors. In this example, a lot that fails under B must not be sent as passed because an interface retains an old status. Follow the expected state to the required point in the target process.

Sources: [4] [5]

Historical traceability and closure criteria

Link the reason for change, approved version, transition rule, selected lots, results and unresolved findings. Show what each system display demonstrates about the actual process. A screenshot of the new plan cannot explain what happened to existing records.

Check permissions and change history for critical master data. Who may change limits, reassign a lot and assess the consequences? Verify that the actual audit trail or a supplementary controlled procedure provides the necessary context.

Before going live, identify any lots that still need action. A searchable transition list can show each owner and decision status. At closure, verify that no affected transaction remains unresolved.

Checklist for closing an inspection plan change
CheckEvidenceDecision
When the change takes effect Approved transition rule Which lots use which version?
New inspection lots Boundary and normal cases Does the intended version apply?
Open inspection lots Representative processing states Are changes permitted and traceable?
History Link between the result and the specification in force at the time Can a reviewer still understand earlier decisions?
Routine operation Roles, outstanding actions and instructions Can the team apply the transition rule?

Sources: [4] [5]

Further reading:

Project experience and collaboration

Test the new inspection plan with lots at different stages

With your QM and laboratory owners, we prepare new, open and already decided inspection lots for a defined inspection plan change. We specify the applicable specification version for each state. Existing traceable assignments can be tested directly. If an assignment must be made or changed, we also assess its effect and data context. With IT, we trace the version actually used through to the decision on the result. Changing the inspection plan does not automatically change every lot.

Questions about inspection plan changes, open lots and approvals

Does a new inspection plan automatically change existing inspection lots?

Existing lots may retain their previous version. For changes to inspection setup in S/4HANA 2025 FPS01, SAP explicitly states that only new lots are affected. When changing an inspection plan, check the actual assignment on each selected lot. Identify the lots that need the new version and whether reassignment is permitted and necessary.

Sources: [1]

Why test a result between the old and new limits?

It shows how the inspection conclusion changes. In this example, 9.8 mg is below 10.0 mg and passes. It is not below 9.5 mg and fails that limit. A result of 8.0 mg would pass under both versions and could conceal a wrong assignment. Include boundary cases and the decision rule actually used.

Can we reassign the specification on every open inspection lot?

No. Certain conditions apply. In SAP ERP 6.0 EHP8, an existing sample determination must be reversed before another inspection specification is assigned. Check the permitted procedure for your release and its effect on existing results. The intended change must be possible in the inspection lot’s current status.

Sources: [2]

Must we reassess historical results after every limit change?

Assess the reason for the change and its impact. A prospective change to a specification and a correction to a previously incorrect rule can require different decisions about historical results. Document the justification and preserve the original records.

Sources: [4]

Is a SAP usage decision the GMP batch release?

No. A usage decision is part of the SAP inspection process. Regulatory certification and release of a medicinal product batch involve additional prerequisites and responsible roles. Record which step the usage decision performs and test the relevant functions and handovers.

How can QA trace the change later?

Link the reason, transition rule, inspection plan version, actual lot assignment and result. Test access to the relevant history using the intended role. The plan valid today does not identify the specification that applied earlier.

Sources: [4] [5]

Sources and review date

Sources were checked on 14 October 2026. The regulatory interpretation and product capabilities are supported separately. Adapt our examples, test matrices and templates to your intended use.

  1. SAP S/4HANA: Editing the Inspection SetupS/4HANA On-Premise 2025 FPS01. Changes to inspection setup affect new inspection lots. Check the mechanism separately for inspection plan changes.
  2. SAP ERP: Assigning an Inspection Specification ManuallySAP ERP 6.0 EHP8. Prerequisites for assigning another inspection specification. Other editions may behave differently.
  3. SAP: Editing Inspection OperationsValidity, change number and revision level in the inspection plan.
  4. European Commission: EU GMP Annex 11, Computerised Systems (2011)EudraLex listed this edition as current on 14 October 2026. It covers applications, risks, operation and the data lifecycle. The proposed tests are our own examples.
  5. PIC/S: PI 041-1, Good Practices for Data Management and Integrity (2021)Inspection guidance on data integrity, including electronic data, transfer, access and review.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Discuss your SAP QM change

We assess the process with your team and test it in the actual system. Tell us the intended use, the evidence you have and the next step you are considering.

  • 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 →