IT systems · Practical guide

SAP S/4HANA Public Cloud validation: scope and releases

SAP delivers the next cloud release while your team continues using the current processes. A technical upgrade schedule leaves open which customer-specific workflows require retesting. Establish a repeatable assurance process for Public Cloud releases.

Table of contents

At a glance

How do you validate SAP S/4HANA Cloud Public Edition for GxP use?

Validate the intended business process, including configuration, data processing, extensions and integration. Assess supplier evidence, responsibilities and the risks in your process. For each release, assess which changes affect your use and the evidence for affected functions. The cloud provider delivers its agreed services. The regulated user remains responsible for deciding whether the configured use is suitable.

Public Edition is a standalone operating model.

Distinguish SAP S/4HANA Cloud Public Edition from Private Edition and On-Premise. Release pathways, expansion capabilities, and operational responsibilities may differ. Therefore, a validation concept developed for a different edition cannot be directly transferred. Document the product, landscape, business processes in use, and relevant integrations. Assess which systems, in addition to the ERP, influence quality-related decisions.

The SAP Help for Public Edition 2608 announces major upgrades in February and August. Customers will be informed six weeks in advance; initially, the test system is updated, followed by development and production systems four weeks later. Smaller, interruption-free functionalities may be deployed in between. If such features are not activated within the described six-month period, activation will occur with the next major release, provided the functionality impacts active business processes. Please align the specific dates and your system landscape with the latest announcement. This vendor-scheduled planning does not determine the overall scope of your GxP testing.

Sources: [1] [2]

Assign responsibility to specific deliverables

Develop a responsibility matrix for development, hosting, configuration, master data, interfaces, user management, and subject-matter approval. "SAP operates the cloud" is too general for this purpose. Additional implementation partners and platform services may be involved. Define the evidence you receive from each vendor, the process for communicating changes, and who evaluates open questions. Contracts and actual operational procedures must align.

The regulated user evaluates the intended use and the extent to which the requirements are met. Supplier testing may demonstrate relevant standard functions, but this does not automatically cover the specific configuration or the full process chain. Review the document version, scope, quality, and transferability. A general manufacturer certificate is not a substitute for this alignment. Similarly, it is not appropriate to reperform all standard tests without first conducting a dedicated risk assessment.

Sources: [2]

Define GxP scope along the business process

Describe the actual workflow, for example, goods receipt, quality status, inventory movement, and dispatch. Identify the relevant data and decisions. Not every ERP field is automatically equally critical. A financial report and a release-relevant batch decision may coexist within the same system but require distinct validation evidence. The rationale for the scope should be clearly understandable to functional, IT, and QA teams.

Add boundaries and external dependencies. Does quality status originate from a Quality Management System (QMS)? Is another service responsible for label or certificate generation? Which source holds precedence in case of conflicting information? A consistent process view ensures that validation does not conclude at the ERP interface, when the actual decision is made through a downstream interface. The system boundary is defined by intended use, not solely by license or project packages.

Sources: [2]

Initial validation: Configure and operate the system together.

Capture requirements, evaluated supplier documentation, and the relevant customer configuration. Assess critical functions using appropriate positive, negative, and edge cases. Use realistic user roles and controlled test data. A test conducted by an implementation administrator may reveal missing restrictions. Document the actually tested state, including relevant integrations and enhancements.

The validation scope also includes operation: changes, access, logging, data retention, incident handling, and required investigation. Assess the vendor's recovery or export capabilities and determine which technical controls remain with the end-user. A general backup description does not automatically confirm the ability to restore a specific erroneous business transaction. Evaluate the recovery scenarios and predefined capabilities required for your process.

Sources: [2] [3]

Release example: a relevant status verification

In the example, a change affects the workflow prior to release. A second release function pertains solely to an unused evaluation. The team assigns both changes to the system inventory and to the approved processes. A targeted test is planned for status verification; the unused function receives documented justification explaining why no additional process evidence is currently required.

The relevant test evaluates a released batch, a locked batch, and a batch that cannot be unambiguously assigned. Additionally, the actual interface pathway is considered. The required behavior is derived from the existing process rules and the updated functionalities. A series of screenshots from the new menu would not adequately address this question. The following matrix serves as an independent work aid. It does not represent predefined legal test classes nor any guaranteed effect of a specific SAP release.

Release example with a relevant status check
ChangeOwn relevance questionPossible evidence
System status review Does approved further processing change? Positive and negative process cases
Interface field Do the meanings or formats change? Check the mapping and expected target state
Roll function Are access rights expanded or revoked? Tests with intended uses
Function outside the intended use Can existing processes be affected? Rationalized Impact Assessment
Output Does the required document change? Compare content, recipient, and date.
Operational function Does the review or investigation change? Run a representative operational case

Sources: [2] [1]

Organize release evaluation as a recurring procedure

Start with release information and your own inventory of usage. Assign changes to relevant requirements, configurations, data paths, and operating rules. Document reasoned exclusions where applicable. The evaluation should be conducted by appropriately qualified responsible parties. An automated search for "GxP" in release notes may provide indications, but it does not reliably capture the significance of a change for your individual workflow.

Prepare a relevance assessment, reference data, and regression analysis for the four-week window as described by SAP. Incorporate automatically activated functions into the change evaluation process. Verify which functions in the test system actually align with the future production environment. Open findings require evaluation prior to their relevant use. Where risks are not adequately controlled, appropriate actions shall be clarified with the supplier and responsible parties. A technically fixed upgrade date does not justify unverified continuation of an unrepresentative process. Escalation and decision-making must therefore be formally included in the operating model.

Sources: [2]

Deploy automation deliberately and under controlled conditions

SAP designates a test automation tool for the Public Edition. Recurring test cases can be automated using this tool or other appropriate tools, provided expected results, data, and analysis are reliable. Suitable candidates should feature stable functional assertions, such as a status lock or interface comparison. An automated test should not only verify that a page is accessible; it must also detect whether the relevant target state has been achieved or an unauthorized state has been prevented.

Evaluate test tools and scripts based on their functionality within the validation process. Altered surfaces may cause technical tests to fail, without indicating a flaw in the specialist process; conversely, weak assertions may overlook a genuine defect. Assign responsibility for maintenance and result assessment. Automation reduces repetitive tasks but does not replace impact analysis. An unmanaged regression test suite with numerous green results provides limited assurance regarding newly introduced risks.

Sources: [2]

Closure and permanent demonstrability

The batch release decision encompasses relevant processes, current status, results, deviations, and required operational actions. Boundaries are explicitly defined. Following a product change, justified controls must be performed only at the relevant location. These controls are pre-planned and may not be used as a substitute for previously conducted tests. Document who has confirmed the use within the assigned scope.

Maintain process inventory and reference tests with each relevant change event. This prevents knowledge from remaining with individual employees and every release starts again at zero. For several GxP systems, joint governance with system-specific evidence is worthwhile. The scale is an executable life cycle: responsibilities, evaluated changes and reconstructable decisions. An extensive introductory dossier alone does not ensure this permanent operation.

Sources: [2]

Project experience and collaboration

Focus the release window on the business processes affected

Before a Public Edition upgrade, process owners and IT map announced changes to actual use. We prepare known critical reference cases and relevant supplier evidence for the test window. A narrow function change may need focused regression testing. Affected extensions or uncertain interactions need further investigation. We identify automatically activated functions and possible restrictions on transports. Your authorised owners decide on use based on the evidence obtained.

Frequently asked questions about SAP S/4HANA Public Cloud validation

Has SAP S/4HANA Cloud Public Edition been validated by the manufacturer?

The manufacturer provides functions and, where applicable, appropriate evidence of its capabilities. The regulated user evaluates the specific intended use, configurations, and integrations. Supplier evidence may be utilized, but must be assessed for scope and transferability. A general customer release does not follow.

Sources: [2]

Must every component be retested after each Cloud release?

The scope is determined by the assessed changes and associated risks. Targeted functional, process, and operational validations may be appropriate. Document any justified exclusions. A blanket end-to-end test is equally unjustified, and a complete test waiver based on cloud-based operation is not inherently valid.

Can the validation concept of the Private Edition be adopted?

Only upon assessment of differences. Operational models, release pathways, enhancements, and responsibilities may vary. Adopt appropriate principles and reference cases, but adapt scope and controls to the actual public edition landscape. The same product family name does not imply an identical validation strategy.

Are the Release Notes sufficient for the change evaluation?

You are a key entry point, but do not constitute a complete customer-specific evaluation. Assign changes to your processes, configurations, data, and integrations. Missing details shall be clarified with the supplier. The documented decision must justify why additional evidence is required or waived.

Can automated SAP tests replace the specialist review?

No. Automated test cases can repeatedly verify predefined assertions. The impact analysis determines which assertions remain relevant after a change. Results and error messages require appropriate evaluation. New features or modified process boundaries may lie outside the scope of the existing test suite.

What should be included in a permanent public-cloud validation concept?

At least the defined use, responsibilities, supplier evaluation, customer configuration, appropriate proofs and controlled operating processes. Complete a recurring release process with relevance assessment, tests and decision. Scope and document structure are adapted to process, risk and available evidence.

Sources and review date

As of October 14, 2026. Regulatory classification and manufacturer responsibilities are separately documented. Examples, test matrices, and templates are standalone reference tools; they are customized for actual usage purposes.

  1. SAP S/4HANA Cloud Public Edition: Upgrade TimelineRelease 2608 reference, checked on 14 October 2026. Two major upgrades are planned per year, with the test system updated first. Confirm your project's dates and system landscape.
  2. European Commission: EU GMP Annex 11, Computerised Systems (2011)Public Edition 2608: Upgrade implications and time windows, activation of smaller functions, transport limits and test automation. Align actual implementation with announced scope of the project.
  3. PIC/S: PI 041-1, Good Practices for Data Management and Integrity (2021)Inspection Guidance on Data Integrity; in particular electronic data, transmission, access, and review.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

How we can support you

Daniel Herrmann Consulting combines professional assessment with hands-on work on the specific system. During the first meeting, we clarify your intended use, existing documentation, and the next most appropriate action step.

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