SAP S/4HANA validation · Pharmaceuticals · Biotech · Medical devices

SAP S/4HANA validation for pharmaceutical and medical device companies.

Plan validation around your SAP rollout.

Whether you are implementing a new system, converting an existing one or migrating selected data, we define the GxP-relevant processes with your team, plan risk-based tests and give QA the evidence it needs for release.

We base the amount of testing on the processes in scope and the risks they carry.

Regulations and platforms: GAMP 5 · Annex 11 · 21 CFR Part 11 · SAP S/4HANA · RISE with SAP · SAP BTP

At a glance

Who can help with GxP validation of an SAP S/4HANA migration?

Daniel Herrmann Consulting (DH-Consulting) specialises in computer system validation and IT GxP compliance for pharmaceutical, biotech and medical device companies and laboratories. We establish the status of systems, validate them and help client teams maintain the validated state. For SAP S/4HANA migrations, we plan validation, assess the implementation partner’s evidence and carry out agreed tests with your team. GxP-relevant processes define the scope.

From 2023 to 2026, DH-Consulting advised a top-ten pharmaceutical company on a large SAP S/4HANA implementation covering ERP and Extended Warehouse Management (EWM). The work also included local validation and test management and support for cutover tasks.

60+ systems validated · No critical findings in audits or inspections of those systems after validation

What we do

  • Define GxP-relevant processes, system boundaries and interfaces with the business, IT and QA
  • Establish requirements and risks and assess implementation partner evidence
  • Prepare the test plan and implement the agreed strategy, including data migration
  • Document the work using your SOPs and templates, hand over the records and train their owners

What your implementation partner does

  • Explain configuration, custom development, extensions and their dependencies
  • Provide technical tests and documents
  • Investigate and resolve technical causes of test deviations
  • Provide the approved system baseline for testing and operation

Where you retain responsibility

  • Operational knowledge and requirements
  • Process decisions during the project
  • Formal approval under your quality procedures

Contractual responsibilities may vary. We document them before implementation starts.

01 · Who we work with

When do you need SAP S/4HANA validation?

This is a good fit if …

  • you are implementing S/4HANA in pharmaceuticals, biotech or medical devices, moving from SAP ECC or rolling out an existing template to more sites.
  • SAP controls GxP-relevant activities such as batch status, inventory holds, release or traceability.
  • the go-live date is set and the business, IT and QA need to agree what validation requires.
  • the person who held the validation expertise has left your organisation.
  • you need validation that fits a small or medium-sized business. We have worked with both smaller companies and global enterprises.

Consider another starting point if …

  • you primarily need extra staff. Staff augmentation is rarely the right fit for our service.
  • you only want a set of documents for a deadline. We work towards a validated state your team can maintain.
  • SAP only supports commercial activities with no effect on product quality, patient safety or data integrity. We document the rationale for excluding those functions and check for dependencies on GxP processes.

02 · Scope

Let your business processes determine the testing.

What is SAP validation?

SAP validation documents whether S/4HANA or SAP ERP is fit for intended use in GxP-regulated processes. It examines workflows in which SAP influences product quality, patient safety or data integrity, such as batch status, inventory holds and traceability.

Typical areas include Quality Management (QM), Materials Management (MM), Production Planning and Process Industries (PP/PP-PI), warehouse management (EWM/WM), Sales and Distribution (SD) and Plant Maintenance (PM). Their relevance depends on how you use them. We document excluded functions and identify their dependencies on relevant processes.

We use GAMP 5 to guide our approach and assess which requirements apply, including EU GMP Annex 11 or 21 CFR Part 11 where relevant. We identify the records, audit trails and electronic signatures that matter to your process.

Guide to identifying GxP-relevant SAP modules and business processes →

More about GAMP 5 consulting →

03 · Focus areas

Three areas that need particular care in S/4HANA.

An S/4HANA migration changes more than the technical release. Migration, configuration and interfaces directly affect quality-relevant data and decisions, so we plan for all three from the outset.

01 · Data migration

A migration needs functional verification that the target system interprets the data correctly. EU GMP Annex 11 addresses preservation of value and meaning. Comparing record counts alone cannot show that units, status mappings or object relationships survived transfer.

Value and meaning · Reconciliation · Legacy records

02 · Configuration, custom code and extensions

An impact assessment identifies which workflows, data models, custom developments and extensions change during conversion. The documented change determines additional tests. Even a small code change can affect a critical status, so assess the functional consequence.

Impact assessment · Configuration · Extensions

03 · Interfaces

S/4HANA may exchange data with warehouse, manufacturing, laboratory and quality systems. Validation follows relevant data across that landscape, including middleware such as SAP PI/PO or Integration Suite on SAP BTP where used. We test successful transfers, rejected and missing messages and duplicate messages.

MES · LIMS · Warehouse management

04 · Implementation approaches

New implementation, system conversion and selective transition: what each means for validation.

SAP distinguishes several transition approaches, commonly called greenfield, brownfield and bluefield. Each raises a different evidence question: which existing processes and records remain suitable, and which configuration or migration decisions need new evidence?

New implementation (greenfield)

Target processes and configurations are designed afresh. Requirements, configuration and migration of the required data take priority. Assess which legacy evidence remains relevant. Which processes are being introduced and which data will move?

System conversion (brownfield)

An existing system baseline is converted to a new environment. Assess changes to processes, data models, custom code, extensions and interfaces. Prior validation needs review against the documented change, which determines additional tests. Which existing processes and extensions have changed?

Selective data transition (bluefield)

Selected configurations and data move while others are intentionally excluded. Document selection, transformation and continued use of historical records. Which configurations and records will move or stay behind?

Rollout of the same template at additional sites

Compare central evidence with local use. A site-specific rule or interface may need its own testing. A global test might establish the main workflow without covering local access roles. Reuse or repeat each test according to its applicability.

The system context determines the approach. For each option, establish how staff will access historical records after go-live.

Decommissioning SAP ECC after moving to S/4HANA → GxP system decommissioning →

Send an enquiry

05 · Client testimonial

Coordinating validation across SAP projects.

Daniel Herrmann supported validation across several SAP rollouts. His role included responsibility for individual project workstreams and coordination with other validation managers.

Jens Fuellbier

“Daniel brings tremendous value through his expertise and commitment to validation and compliance.”

Jens Fuellbier · Head of GBS Governance, Enablement & Strategy · Boehringer Ingelheim · Translated from German

This recommendation concerns Daniel Herrmann’s own project work.

SAP rollouts · Validation management · Pharmaceuticals

An SAP implementation needs clear responsibilities across the business, IT, QA and the implementation partner. We make that coordination part of the project plan.

Read all client testimonials →

06 · Process

Four steps to a validated SAP system in operation.

Our Integrated Validation Execution approach combines project coordination and validation. We align both with your implementation partner’s plan, starting with the overall scope and then the detail.

01 · Scoping and project planning

We define the GxP-relevant processes, data and interfaces with the business, IT and QA during scoping, then develop a detailed project plan. Deliverable: agreed scope and project plan

02 · Specification

We document user and functional requirements and assess risks. Requirements follow the business process and the decisions it supports. Deliverable: specification and risk assessment

03 · Implementation and testing

The implementation partner configures SAP. We plan the tests and perform them with your team. Risk determines test depth, and we assess whether partner tests are suitable evidence. Deliverable: documented tests and assessed deviations

04 · Go-live

Cutover brings S/4HANA into operation. Beforehand, we agree which findings would prevent go-live and the latest point at which a controlled fallback remains feasible. We provide close support during hypercare. Deliverable: a validated system in operation

Cutover: planning GxP release and fallback →

After two weeks

Depending on scope and preparation, the first two weeks establish scope and an outline plan. We then refine it, allocate resources and responsibilities and hold the kick-off.

At completion

A validated system with testing proportionate to risk and operating procedures that maintain its validated state.

Estimated effort

We estimate effort after scoping. Key drivers are the processes involved, transition approach, custom developments and extensions, interfaces and migration.

Planning SAP validation effort and cost →

Send an enquiry

07 · A typical project

Working together on your SAP project.

The SAP implementation is underway and the go-live date is fixed. The business, IT and QA need to agree what validation requires, or the person who held that knowledge has left.

We start by defining scope with the process owners. Where does SAP support a quality decision, such as batch status or an inventory hold? QA identifies how the project fits existing procedures. IT and the implementation partner explain configuration, extensions, custom developments and interfaces. Management decides priorities and resources.

Reusing earlier screenshots after moving to S/4HANA is insufficient if workflows or risks have changed. Review the relevance of existing documents, then reassess processes, risks and tests.

Process owners know the expected rules and can judge whether SAP processes data correctly. The implementation partner investigates and resolves technical causes of deviations. We assess their impact with QA.

After go-live, your team maintains the validated state. Where useful, training videos and self-study materials remain available to staff and future role holders.

Sustaining validated operation reduces the cost of repeated work.

08 · Quality framework

Every project follows the same quality framework.

Daniel Herrmann provides technical oversight on every project. The team uses consistent procedures, templates and quality checklists so that quality does not depend on one individual.

Once scope is agreed, we assign roles across our team, your organisation and the implementation partner.

Daniel Herrmann has over 17 years’ experience validating computerised systems, from work in medium-sized businesses and at Boehringer Ingelheim to leading validation projects. Our work draws on more than 60 systems validated in pharmaceuticals, biotech, contract manufacturing and laboratories. None of those systems subsequently received a critical finding in an audit or inspection.

Daniel Herrmann has led project management and validation management in global SAP programmes involving teams across multiple countries.

Our clients include Boehringer Ingelheim, Johnson & Johnson and many small and medium-sized companies. We introduce proportionate compliance frameworks smaller businesses can run and defend in an audit.

For documentation, we use GxPsuite. It brings together your sources and prepares drafts from your templates. Our experts review the drafts. Your designated owners confirm applicability to the system and approve them under your quality procedures. GxPsuite is a product of traqx GmbH, co-founded and managed by Daniel Herrmann.

Meet our team → Selected projects led by Daniel Herrmann → GxPsuite →

Elements of our quality framework

Technical oversight

Provided by Daniel Herrmann on every project.

Consistent procedures

The same procedures and templates across projects.

Quality checklists

Defined checks on every project.

Continuous improvement

We incorporate proven improvements into our procedures and checklists.

09 · Common questions

Questions about SAP S/4HANA validation.

Do we need to revalidate everything when moving to S/4HANA?

The documented change determines what needs retesting. For a brownfield conversion, assess the impact on processes, data models, custom code, extensions and connected applications. Existing validation evidence must be reassessed against those changes. For a greenfield implementation, the focus is requirements, configuration and migration. Existing documents can help, but processes, risks and tests need to be reviewed.

How long does SAP validation take?

After scoping, we estimate effort and duration and align both with the implementation partner’s schedule. The main drivers are in-scope processes, implementation approach, custom code and extensions, interfaces and migration. We then plan testing, approvals and milestones through go-live.

How much does SAP validation cost?

We estimate effort after scoping. The processes in scope have more influence than the number of modules. We can offer a fixed price for a defined scope or a day rate for targeted advice. Our cost guide describes the main effort drivers. Send us your project details for advice specific to your situation.

What does the systems integrator do, and what do you handle?

The systems integrator configures SAP and understands the technical setup. Your process owners explain its business implications. We plan validation, assess whether the partner’s tests and records are suitable evidence and perform agreed tests with your team. Your organisation retains approval. We record the division of responsibilities in the project plan.

How soon can you join our SAP project, and what can we expect after two weeks?

Include your SAP rollout date in your enquiry so we can confirm when we can start. Ideally, scoping begins before configuration and migration. If the project is underway, we assess its actual state and existing records. Depending on scope and preparation, the first two weeks establish scope and an outline plan.

How much staff time should we plan, and which records do you need?

Process owners, IT and QA are needed at the outset to establish scope. We then schedule your contribution explicitly. Process owners supply expected business rules, reference data and decisions. QA aligns validation with your procedures. IT explains the technical setup. Information on edition, deployment, transition approach, affected processes, existing validation records and your implementation partner’s proposal helps us get started.

Do you validate SAP cloud deployments, including RISE and BTP?

Yes. Our scope includes RISE with SAP and SAP Business Technology Platform (BTP). Validation covers the intended business process, configuration, extensions and integration. We establish which services SAP delivers under your edition and contract and what evidence is available. We assess release impact and affected functions. Your organisation decides whether the system is suitable for regulated use.

How do you verify data migration to S/4HANA?

EU GMP Annex 11 says validation should check that transfer preserves the value and meaning of the data. Record counts alone cannot establish that. We connect the source, transformation rule, target and verification method and plan separately for access to historical data.

How do you validate roles and authorisations?

We test permitted and prohibited activities for each role. Effective access to objects, organisational units and critical status changes matters more than which apps are visible. Tests cover assigned roles, prohibited actions, alternative access routes and role combinations. A successful authorised transaction alone does not establish that access is restricted correctly.

How do you handle transports, releases and changes after go-live?

Change assessment and periodic evaluation help maintain the validated state. Each transport is linked to an approved change. Check contents, dependencies, import order and target system. The effect of the change determines testing. Apply the same approach to role changes and new releases. We agree procedures before go-live so your team can operate them independently.

What will we have after go-live, and what can our team do independently?

A validated SAP system in operation, with specifications, a risk assessment, documented tests, assessed deviations and a recorded release decision. Your team has operating procedures to assess transports, changes to roles and releases and to evaluate the system periodically. Where appropriate, training videos and self-study materials remain available to current and future role holders.

Sources

Sources and review dates

Author: , founder and managing director of DH-Consulting. · German source text dated

The regulatory references concern computerised systems used in GMP activities under EU GMP Annex 11 and, where applicable, 21 CFR Part 11 and medical device manufacturers’ quality management systems. Our checklists and workflows are practical tools. SAP describes the transition approaches. The validation implications are our interpretation. Technical details depend on the edition and documentation version.

  1. European Commission: EU GMP Annex 11, Computerised Systems, 2011 revision. Principle and section 1 on scope and risk, section 2 on personnel, section 3 on suppliers, section 4 on validation and migration, section 5 on data exchange, section 7 on storage and access during retention, section 9 on audit trails, sections 10–12 on change, periodic evaluation and access, section 14 on electronic signatures and section 17 on archiving.
  2. eCFR: 21 CFR Part 11, Electronic Records; Electronic Signatures. Section 11.1 defines scope. Applicability depends on use within FDA jurisdiction.
  3. EUR-Lex: Regulation (EU) 2017/745 on medical devices, consolidated text of 19 July 2026. Article 10(9) on manufacturers’ quality management systems.
  4. ISPE: GAMP 5, Second Edition. Industry guidance on risk-based validation.
  5. European Commission: EU GMP Chapter 7, Outsourced Activities. Suitability, responsibilities and agreements for outsourced activities.
  6. ICH Q9(R1): Quality Risk Management. Risk-based decisions and proportionate formality.
  7. SAP Learning: Customer Transition Paths to SAP S/4HANA Cloud Private Edition. Supplier guidance on transition approaches for the Private Edition.

Tell us about your project

Tell us about your SAP project, your target date and the support you need.

Send an enquiry

Project enquiry · Reply by email