Table of contents
At a glance
What does a risk-based SAP S/4HANA validation cover?
For SAP S/4HANA validation, scope the processes and data that affect GxP decisions. Assess requirements and risks, then obtain evidence for the configuration, roles, extensions, interfaces and any data migration. Public cloud, private cloud and on-premises deployments have different operating and change controls. The release decision covers the specified system version and intended use.
- The edition and implementation approach set the technical conditions.
- Derive requirements from business processes and decisions that affect quality.
- Plan migration, access to historical data and legacy system decommissioning as separate tasks.
- Link individual test results to the overall evidence for intended use.
Why the choice between Public Cloud, Private Cloud and On-Premise matters
“S/4HANA” alone is too broad for a validation plan. SAP deployment models differ in configuration, extensibility and how changes reach production. Record the edition, release and relevant components. Include integration platforms and external warehouse systems where they handle relevant data.
The objective is to demonstrate suitability for intended use. The responsibilities can differ substantially. Who operates each component, who applies changes and what evidence is available? Cloud deployment does not transfer every task to the supplier. Release arrangements vary by edition.
| Deployment model | Question for the project | Action to plan |
|---|---|---|
| Public Cloud | Which standard processes, extensions and scheduled releases affect your use? | Assign test owners and schedule the work within the available window. |
| Private Cloud | Which configuration, custom development and operating services are included? | Record the customer landscape and responsibilities of SAP, partners and your organisation. |
| On-Premise | Who owns the application, infrastructure, operation and maintenance? | Assign the evidence for the application and its supporting infrastructure. |
Plan a new implementation and a system conversion separately
A new implementation establishes target processes and configures them. Validation therefore focuses on requirements, configuration and transfer of the necessary data. Legacy evidence can describe business needs. Assess whether it applies to the new process.
A system conversion moves an existing system into a new technical and functional environment. Assess changes to processes, data models, extensions and connected applications. Calling a project “brownfield” does not carry the original validation forward. Document the changes and derive the additional work.
SAP documents different implementation paths and prerequisites. Agree the technical path with the implementation partner and maintain a list of relevant changes. Use it to connect project planning and validation and update it when scope changes.
Derive requirements from business processes
A list of applications or transactions describes the interface. A requirement explains what needs to happen. For example, a material batch that has not been released must not be used in the specified manufacturing process. Describe the functions that collectively enforce this in the solution design.
For GMP use, Annex 11 calls for a documented, risk-based rationale for the extent of validation. Link the requirement, possible failure, control and evidence. An unintended status change or incorrect quantity conversion can have different consequences from a commercial display error.
Include shared master data, organisational units, access rights, printed outputs and interfaces. Important business dependencies can cross module boundaries. Explain which risks the tests cover, which existing records you can use and which areas need further work.
Sources: [1]
Data migration to S/4HANA: values, meaning and historical access
A migration assessment needs to show that users can interpret and use the required data correctly in the target. Annex 11 addresses preserving value and meaning in a transfer. Matching record counts alone cannot establish that units, statuses and relationships survived.
SAP describes the Public Edition 2608 migration cockpit as a tool for loading initial operating data, including master data, open transactions and balances, including historical account balances. It excludes historical transactions from closed or long-running processes and orders with follow-on documents. Partially delivered sales orders and partially open purchase orders require the source-system handling described in SAP Help. Plan continued access to historical records separately. These limits apply to this Public Edition tool.
For quality-relevant data, link the source, transformation, target and verification method. Document how rejected, unusual or excluded records are handled. Define how the organisation will access records subject to retention. A successful go-live cannot justify shutting down the only usable source of historical evidence.
| Data area | Question | Possible evidence |
|---|---|---|
| Batches and materials | Are identity, assignments and relevant dates preserved? | Compare the specified fields and relationships between source and target. |
| Quantities and units | Does conversion preserve the correct amount of stock? | Reconcile individual values and meaningful totals, including exceptions. |
| Status information | Does the target status have the intended effect on the process? | Check the mapping and perform a targeted functional test after migration. |
| Historical evidence | Can users still find and read the required records in their original context? | Test the designated archive or retained access to historical data. |
Assess interfaces and extensions across the whole process
S/4HANA may exchange data with warehouse, production, laboratory and quality systems and with external service providers. Follow the relevant data across that landscape. Available integration options depend on edition and release. SAP documents the interfaces and conditions of use for selected Public Edition processes.
For each interface identify sender, receiver, trigger, data content, mapping and error handling. Test rejected, missing and repeated messages as well as the successful transfer. Establish which target result belongs to the original message.
For custom extensions, identify who specifies and tests the logic and how changes are controlled. Which standard functions can change as a result? What evidence covers the version in use? An isolated extension test cannot establish that the complete quality-relevant process works.
Test authorisations and traceability for critical actions
A role called “Quality” does not demonstrate suitable access. Specify actual tasks and prohibited actions, such as changing master data, setting a status, modifying critical settings or exporting data. Execute the cases with representative users and their actual roles.
Evaluate change documents and logging on the object that matters. Standard objects, custom fields and extensions can have different capabilities. SAP's RAP-based change document example illustrates a logging function that requires activation. Do not assume the example applies to every S/4HANA object.
Test the recorded content, link to user and business object, access to history, retention and the intended review. When assessing Public Edition upgrades, include changes to business catalogs, restrictions and role templates.
Example of an end-to-end test across systems
Suppose a laboratory result determines whether a batch may be used in a defined S/4HANA process. Start with a known state in the laboratory system and end with an action in S/4HANA. Specify the implementation and expected behaviour before testing. This example describes neither a product defect nor an executed S/4HANA test.
Transfer a valid result. Check that the correct batch is assigned, the right status is processed and the intended action is permitted. Then test a rejected result, an interrupted transfer and repeat processing of the same message. An authorised user handles the error through the designated procedure. Link the states across both systems using unique IDs.
The test brings together data assignment, the effect of status, access rights and error handling. Use it alongside the component tests. Assess separately whether other batch types, sites or process variants need further evidence.
Sources: [1]
Control changes and releases after go-live
SAP documents two major Public Edition upgrades each year, in February and August, with the test system upgraded first. Record the applicable dates and responsibilities for your own landscape. Private Cloud, On-Premise and connected components have their own arrangements.
Link each technical change to its effects on requirements, processes, roles, interfaces and existing evidence. Select tests accordingly. Changes to master data rules or an external application may affect the process even when S/4HANA itself is not upgraded.
At handover, agree a reusable set of tests and identify outstanding actions. Include significant incidents, changes and their outcomes in periodic evaluation. This shows which evidence still covers current use and where new work is needed.
What should be clear before approving go-live?
A count of passed tests cannot establish readiness on its own. Decision-makers need a coherent view of the scope, results, deviations and residual risks. Use the checklist to prepare the decision.
- Document the edition, target release, sites and intended use.
- Link significant requirements to their tests and results.
- Assess deviations and outstanding issues and assign owners.
- Reconcile the migration. Document exclusions and access to historical records.
- Test authorisations and critical processes using appropriate user roles.
- Prepare operating responsibilities, change and incident procedures and training.
- Make the decision on intended use under the organisation's quality procedures.
Project experience and collaboration
Test the SAP process across project boundaries
With the process owners, we start at one quality-relevant SAP decision and trace the data, roles and system handovers it requires. Public Edition, Private Edition and on-premises implementations involve different responsibilities and change paths. Suitable existing evidence may remain applicable. Changed use, extensions and migration need appropriate additions. With the process team, IT and QA, we agree scope and dependencies. The authorised decision concerns the complete configuration in use.
Frequently asked questions about SAP S/4HANA
Does every S/4HANA module require validation?
Determine scope from intended use, applicable requirements and risk. Module names alone cannot settle it. Consider shared master data, relevant dependencies and interfaces.
Does validation differ between S/4HANA Public Cloud and Private Cloud?
Both need evidence of suitability for intended use. The configuration, extensions, operating responsibilities and release processes can differ. Define supplier contributions, internal checks and scope for the actual edition and landscape.
Can we reuse the validation of an existing SAP system?
Yes, where individual records are traceable and cover the new use. For a conversion or a new implementation, assess what changes. An old approval does not automatically cover new data models, processes, roles or extensions.
Does the migration cockpit transfer all historical data?
No. The S/4HANA Public Edition migration cockpit covers the initial operating dataset, including master data, open transactions and balances. Historical account balances can be migrated. SAP excludes historical transactional data from closed or long-running processes and orders with follow-on documents. Plan historical access or another suitable migration route separately. The restriction applies to this tool.
Must IQ, OQ and PQ always be separate documents for S/4HANA?
Keep the required evidence traceable. Annex 15 section 2.5 permits combining appropriate qualification documents, for example IQ and OQ. Justify the structure in your quality procedures. Annex 11 remains relevant to computerised systems. Three document titles alone do not establish complete validation.
What drives the effort to validate S/4HANA?
Key factors include process scope, implementation approach, edition, custom development, interfaces and migration. Also assess the quality and currency of existing evidence and the availability of test environments and process experts. Establish the boundaries before estimating the effort.
Do we need to repeat every test after an S/4HANA update?
Use the documented impact assessment to choose additional checks. Consider the affected processes, risks and existing evidence. Neither automatic full retesting nor skipping all tests reflects that assessment.
Sources and review date
Technical details depend on the edition and documentation version. The tables, checklist and example workflow support project planning. Assess the actual landscape and determine which requirements apply within your organisation.
- European Commission: EU-GMP Annex 11, specifically Sections 1, 3–5, 9–12 and 17
- European Commission: EU-GMP Annex 15, Principle and Section 2.5 on Summary of Qualification Documents
- SAP Learning: Introducing SAP S/4HANA – Editions and Operating Models
- SAP Learning: Describing Implementation Types and Clean Core
- SAP Help: Public Edition – What Data Can Be Migrated?
- SAP Learning: Migrating Data to SAP S/4HANA Cloud Private Edition
- SAP Help: Available Interfaces for Your Selected Scope
- SAP Help: Log RAP-based Change Documents, Public Edition 2602
- SAP KBA 2868559: Changes to Business Roles after a Public Edition upgrade
- SAP Help: Public Edition – Upgrade Timeline
Sources checked: .
Discuss your SAP S/4HANA validation
We help with requirements, risks, migration and the evidence your project needs. We can deliver defined project tasks or help your team build an approach it can maintain.
- 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.

