Practical guides · Practical guide

Choosing an SAP validation partner for a regulated implementation

Ask a prospective CSV partner what your S/4HANA implementation changes in one quality-relevant business process and what evidence the change needs. Their answer reveals more about their SAP experience than a list of projects. Use the subsequent questions to examine implementation paths, operating models, project phases, roles and test tools for SAP in EU GMP manufacture of human medicinal products.

Table of contents

At a glance

How can you assess an SAP validation partner before award?

Ask the proposed team to walk through a relevant business process in your landscape and trace the data to the resulting decision. Examine how they would evaluate configuration, custom code, roles, transports, interfaces and historical records. Ask for a sample deliverable and a plan that assigns work to your team, the implementer and the validation partner at the right project milestones.

  • A new implementation, a system conversion and a selective data transition each raise different questions.
  • The SAP project plan and the GMP evidence must refer to the same system version.
  • Ask the candidate about authorisations, SAP transports and test tools.
  • Contract and personnel requirements also apply to outsourced SAP validation activities.

Which SAP transition path should the partner understand?

For S/4HANA Cloud Private Edition, SAP describes new implementation, system conversion and selective data transition. A new implementation starts with a new installation. A conversion builds on the existing ERP system. Selective data transition transfers and transforms selected content. First establish which path your edition and architecture support and which your project intends to use.

Use the comparison to connect the SAP transition path with your CSV plan. Ask the partner to explain which requirements and risks remain open for your chosen path and how they would address them.

Every path needs a plan for continued access to the historical information you need. A successful target-system implementation leaves that archiving and decommissioning decision open.

Comparing SAP transition paths in the selection interview
Transition pathQuestion for the candidateWhat the answer should explain
New implementation Which processes will you configure from scratch and which data will you migrate? How new requirements, configuration and migration relate
System conversion Which existing processes and custom developments will change? Which existing evidence remains usable and why additional regression tests are needed
Selective data transition Which configuration and data will you include or exclude? How to trace selection, transformation and subsequent use of historical data
Upgrade or limited change Which previous conclusions could the change affect? How the impact of the change determines what additional evidence is needed

Sources: [1] [2]

Further reading:

Establish what the operating model and service actually cover

Identify whether your system runs on premises, in a private cloud or in a public cloud, and which services you use. Ask who owns the infrastructure, configuration, technical changes and release information. A general claim of SAP cloud experience leaves those responsibilities open.

Annex 11 section 3.1 requires formal agreements defining the responsibilities of third parties involved. Section 3.2 addresses competence, reliability and the risk-based need for a supplier audit. Ask what supplier and hosting information the candidate can obtain for your engagement and what remains for your team to investigate.

Sources: [2]

Further reading:

How does validation fit into SAP Activate?

SAP Activate describes six phases, Discover, Prepare, Explore, Realize, Deploy and Run. The SAP learning material places fit-to-standard work in Explore and iterative implementation and testing in Realize. Deployment and operation follow. An implementation plan alone does not demonstrate suitability for GMP use.

Ask the partner to show where their work belongs in your actual project plan. The CSV mapping below is our planning method. It illustrates how work can fit together and prescribes neither regulatory phases nor a universal document sequence.

If the partner waits until technical testing is over to ask about requirements, ask how they will link and assess the existing results. When they cite user acceptance testing (UAT), ask them to identify the requirements those tests actually cover.

Mapping validation work to SAP Activate
Project phaseQuestion about the validation workEvidence to discuss
Prepare How will you define the intended use, responsibilities and evidence strategy? A shared view of the system and project tasks
Explore How will you record process gaps and critical business rules? A link between a process decision and its requirement
Realize How will you keep the configuration, changes and tests linked? An execution record identifying the version tested and the assessment of findings
Deploy and Run How will you assess the final data state and decide whether to proceed to operation? A link to cutover, the boundaries of use and the responsibilities handed over

Sources: [3] [2]

Further reading:

Agree responsibilities with the implementation partner, CSV partner and customer

The technical partner knows the configuration. The process owner determines what it means for the business process. The CSV team links requirements and risks to suitable evidence. Authorised people within the customer organisation assess the results and intended use. If each of two partners assumes the other will approve the result, the allocation of responsibilities needs work.

EU GMP Chapter 7 sections 7.5–7.8 address prior assessment, provision of information, oversight and review of results for outsourced GMP activities. Section 7.11 covers subcontracting. Sections 7.14–7.17 cover the contract, responsibilities, records and provision for audits. For the consultants who will perform the work, Chapter 2 section 2.23 also addresses suitable qualifications and the records that support them.

Use the table to identify who produces each result and who evaluates it. As a quality recommendation, we suggest basing the final assessment on more than the configurator's unchecked assertion. Relevant evidence from the implementation partner can support that assessment.

Who produces the evidence and who assesses it?
SubjectTechnical contributionBusiness assessment
Status logic Explain configuration and dependencies Define permitted use
Custom development Identify affected logic and changes Determine relevance and suitable evidence
Test finding Investigate the observed behaviour and its cause Assess the impact and whether use can continue
Handover Make the current system version available Accept responsibility for operation and changes

Sources: [4] [5] [2]

Ask about authorisations, SAP transports and local differences

Give the candidate a specific case. One role can change a quality-relevant status and another can only read it. Ask which effective permissions, dependent roles and exceptional access rights they would examine. Testing the authorised user alone leaves the restriction on unauthorised users untested.

Ask how a changed version will move to the next environment. Which configuration was tested and which actually reaches the target? Annex 11 section 10 provides the framework for controlled system and configuration changes. The technical procedure must fit your SAP landscape.

For a global template, assess central evidence against local use and known differences. An additional site rule or a different interface can create a need for local evidence. Ask the candidate to work through one example and justify which central tests can be used and which need further work.

Sources: [2]

Further reading:

Check that migration and interfaces preserve values and their meaning

When data move to another format or system, Annex 11 section 4.8 calls for checks that the value and/or meaning of the data have not changed. In practice, consider the mappings, relationships and intended use. Matching record counts alone do not answer these questions.

For example, follow a material and batch with a relevant status from source through mapping to target. Who assesses an unknown source status? How does the team handle the final change after a dress rehearsal? Your process determines the expected results. Ask the candidate to explain and test what that status actually blocks in your configuration.

For interfaces that remain in operation, consider what triggers each transfer and how errors are handled. A technical acknowledgement of receipt does not establish that the receiving system reached the correct business state. Our data migration article covers reconciliation rules and suitable reference cases.

Sources: [2]

Further reading:

A work sample for the selection interview

Use an anonymised case or a clearly scoped hypothetical example. Ask the candidate to identify missing information and explain their reasoning. The exercise below is a proposed interview task and has not been run as a product test.

Ask for a suitable example of a decision or evidence record. An anonymised or hypothetical record is sufficient. Judge the explanation given by the person who would do the work, as well as the sales team's presentation.

An interview exercise for prospective SAP validation partners
Scenario or promptWhat a substantiated answer coversAn answer that leaves the question open
System conversion with a change to custom code The affected function, existing evidence and regression tests needed “The core product stays the same.”
Material status received from the LIMS The source, mapping, error path and business process that uses the status “The interface has been technically tested.”
A transport after testing is complete How the tested version relates to the deployed version “The transport job showed green.”
A site with a local rule Whether central tests apply and what the site needs to add “The template applies everywhere.”
A historical record after ECC shutdown Required data, context and retrieval method “The database is backed up.”
Further reading:

What the quotation should say about tools and handover

Identify which tools the project will use for requirements, tests and findings. Annex 11 section 4.7 requires a documented assessment of the suitability of automated testing tools and test environments. A product name or an automatically generated report does not establish that suitability.

A suitable quotation identifies the processes, system versions, data flows and deliverables in scope. The handover should allow operations to trace a later authorisation, transport or interface change. Use the linked guides to compare suppliers and pricing models alongside your SAP-specific requirements.

Sources: [2]

Further reading:

Define what your SAP validation partner will deliver

With Daniel Herrmann Consulting, distinguish the validation work from the work your implementation partner and internal team will do. We discuss the processes involved, who owns each decision and which decision your project needs next.

Start with our computer system validation guide →

Discuss SAP projects and roles

We discuss why you are getting in touch, where your system stands and which decision comes next.

Project experience and collaboration

Use one SAP process to evaluate prospective partners

To evaluate potential SAP partners, choose a quality-relevant business process. Which steps will change? Which data will transfer? What can the implementation partner already demonstrate? Use that example to prepare questions for the selection interview. An established global template needs a different assessment from a newly configured process chain. We agree the division of work with your process owners, QA and IT.

FAQ on selecting an SAP validation partner

How does CSV expertise differ between a conversion and a new implementation?

For a conversion, the partner needs to understand existing processes, custom developments, changes to data models and which evidence remains suitable. A new implementation places more emphasis on newly configured processes and data migration. The actual edition and architecture matter in both cases.

Sources: [1]

Can our implementation partner contribute to CSV?

Yes, where the partner is suitable and the responsibilities are clear. The contract giver evaluates the results under Chapter 7 section 7.8. As a quality recommendation, we suggest that the final assessment goes beyond the configurator's unchecked assertion. This does not establish a general requirement to use separate companies.

Sources: [4]

Does an SAP certification establish suitability for our GMP project?

It can support the person's qualifications. Suitability depends on the work you intend to assign. Ask the proposed consultant to explain the transition path, impact on the process and evidence required. Chapter 2 section 2.23 and Annex 11 section 3.2 provide relevant regulatory references.

Sources: [5] [2]

What else should we clarify for a public cloud engagement?

Identify the service in scope, your configuration and who owns changes and operation. Ask which information and testing options will be available and which tasks remain with your team. Check how experience with another SAP operating model applies to this service.

Does a test management tool need the same validation as the ERP system?

What you need to examine depends on the tool's function and how you use it. Annex 11 section 4.7 requires a documented suitability assessment for automated testing tools and test environments. Use that assessment to determine which evidence is necessary for the intended use.

Sources: [2]

Which question reveals a gap between the two partners' responsibilities?

Ask who investigates a test finding, who makes the technical correction and who evaluates the result for continued use. Look for named roles and defined handovers. If each party refers the decision to the other, agree a workable joint process before proceeding.

Sources and review date

Primary sources were checked on 17 October 2026. SAP describes the transition paths and SAP Activate. We explain how they can inform CSV planning. The regulatory scope is EU GMP for human medicinal products. The specific engagement depends on the SAP version, edition and actual landscape.

  1. SAP Learning: Customer Transition Paths to SAP S/4HANA Cloud Private EditionSAP describes the transition paths for Private Edition. The article's assessment of CSV implications and work packages is our own.
  2. European Commission: EU GMP Annex 11, Computerised Systems, January 2011 revisionGMP for human medicinal products. The relevant provisions include sections 1–4, 7, 10–13 and 16–17, as identified in the article.
  3. SAP Learning: Describing the Methodology Structure – SAP ActivateSAP describes its project phases. The mapping to GMP evidence is our own method and does not imply GMP approval by SAP.
  4. European Commission: EU GMP Chapter 7, Outsourced ActivitiesOutsourced GMP activities, suitability, responsibilities, agreements and oversight.
  5. European Commission, EU GMP Chapter 2, Personnel, effective 16 February 2014Personnel, role-specific training and evaluation of practical effectiveness. The official EudraLex entry links to the original chapter.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Bring your implementation path and a critical business transaction

Bring the edition, operating model, proposed transition path and one relevant data or status flow. Use that example to identify the questions a suitable validation partner will need to answer.

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