Practical guides · Practical guide

How to test SAP Business ByDesign cloud updates based on risk

An SAP Business ByDesign cloud update may affect only a few approved processes. Starting with the SAP release notes, identify which functions may change, justify regression coverage and document closure. The example shows how the system owner, process team, QA and partner can turn unresolved findings into timely operating decisions.

Table of contents

At a glance

How much testing does a ByDesign update need?

Map relevant ByDesign release notes to your intended use, data flows and requirements. Assess the impact and uncertainties, then select document reviews and regression tests. Record the test conditions, results and deviations before deciding on continued use. The documented rationale justifies the scope. The update title alone does not.

  • SAP release notes serve as the starting point; the internal process assessment determines the scope of validation evidence.
  • Preview, approved change, and actual system timeline must be kept separate.
  • The test system, enhancements, and interfaces must adequately represent the to-be-validated process flow.
  • The closure ties together results, open deviations, and a responsible operational decision.

1. Clearly define the scope of the review request for each update

First, describe the subject: Which ByDesign system, which known starting state, and which target state are being considered? Does a partner package, an attached warehouse, or an independent evaluation belong to this scope? Leverage the existing system and process infrastructure. Conducting a new ERP assessment at every release would likely obscure the specific change question.

The regulatory focus of this guide pertains to GMP processes for human medicinal products. Annex 11 links risk-based justification to controlled changes. Consequently, a fixed test suite is not required for every cloud update. The key consideration is whether the change may impact the intended functions, relevant data, or effective controls. Other regulatory areas must be addressed separately depending on your specific application.

Name a responsible party for the evaluation and required contributions. Technical review and professional assessment are distinct responsibilities.

Sources: [4] [5]

2. Collect SAP information and maintain its current status

The SAP What’s New Viewer distinguishes between Required, Recommended and Info only, among other labels. These labels indicate what action SAP expects users to take for the change. Use them as an input to your own assessment. They do not classify the GxP risk to your process. Read the full change description, including prerequisites and required actions.

SAP labels preliminary indications as Preview and notes potential changes. Therefore, record title or identifier, source, retrieval date, affected area, and the assessed text version. Prior to finalization, verify whether a preliminary indication has been upgraded to a revised final description. Include relevant partner notifications and previously known internal disruptions.

Define who receives the information and assumes responsibility. A filtered subscription is practical; however, it must not inadvertently obscure cross-cutting changes to access, release, or communication. The individual overview should clearly indicate which topics have been reviewed and which have been reasonably excluded.

Sources: [1] [4]

3. From the release note to the affected process

For every potentially relevant indication, ask the same questions: Are we utilizing the function or one of its dependencies? Could requirements, documentation, or controls change? Can we reliably assess this based on existing documentation? A function name alone does not indicate whether a subsequent batch list or an external system uses the same data pathway.

The following matrix is a work proposal of its own. Its lines are accepted change types, not claimed changes to a particular SAP release. It shows how the justification leads to a concrete selection. If the effects are unclear, clarification with SAP or the partner as an open point belongs in the evaluation.

Example of a commented impact matrix
Accepted noteReference to own usageRationale next action step
Display change in an unused area No function utilized and no established dependency identified Document the exclusion with a traceable inventory reference
The criterion for selecting a relevant evaluation has changed. The analysis supports tracing an individual batch Compare open inventory and stored selection with altered result
The communication behavior of a used data path changes. A partner process requires the transferred quantities and references. Check continuous exchange together with error handling
Access rule of a used activity is affected The function separates data entry from professional judgment. Test user access permissions with the intended roles, including both authorized and unauthorized access.
Impact on own expansion is still unclear The partner has not yet been able to categorize the affected request. Hold evaluation open; request technical clarification and appropriate supporting evidence

Sources: [4]

4. Regression based on potential consequences selection

A regression test should demonstrate that a required, previously functioning property remains intact after the change. Therefore, do not simply select the most recently executed tests. Initially assign any potential error to a specific technical cause: incorrect quantity, missing batch assignment, unauthorized action, or incomplete documentation.

Leverage existing approved requirements and appropriate test cases. Supplement where a new failure path emerges or the original validation evidence does not cover the altered process flow. Particularly useful are a representative normal case, the affected boundary condition, and a plausible failure scenario. The number and depth of cases are determined by risk and available evidence.

A standalone document review may be sufficient to demonstrate a traceable, non-impacted function. However, it is less robust when the impact remains unknown or when a relevant control is altered. Ensure that the underlying rationale for not selecting an additional functional test is clearly documented; avoid generic statements such as "no relevance" without reference to the existing control environment.

Sources: [4]

5. Prepare the test system in a timely and appropriate manner

The ByDesign Library outlines the maintenance schedule in the Service Control Center for both productive and non-productive systems. Use actual system dates for your planning. A general publication of release information neither confirms the current installed version of your test nor verifies the production schedule.

For system copies, SAP identifies key limitations: during the period between test and production upgrade, no copy of the production system can be requested. Additionally, in copies, both configurations and change records are separate selection points. Therefore, a seemingly appropriate copy may lack the historical records required by your test.

Verify prior to testing the specific version, relevant configuration, roles, extensions, and test data. Document differences from production and their significance. If the test case requires prior records, proactively ensure their availability. The suitability of a test environment is derived from the testing objective, not solely from its designation.

Sources: [2] [4]

6. Explicitly include own enhancements and interfaces

Capture the dependencies of a relevant process flow even outside the visible ByDesign screen. This may include partner logic, additional fields, reports, and integrated systems. Ask the partner for the affected version, scope of changes, and available results. A general statement of compatibility provides little value if it does not specifically reference your actual data pathway.

The SAP Security Guide describes communication agreements as a configuration of electronic data exchange with a communication partner. It assigns these configurations to the customer. Therefore, when changes affect this area, it is necessary to also verify endpoints, authentication, and the authority of the respective counterpart. An accessible service does not constitute evidence of correct technical processing.

Following a system copy, additional post-processing may be required. The library specifically highlights the activation of customer-specific add-ons in the "In Development" status within the target system. Have the partner confirm the required state for the test case. Otherwise, the test could inadvertently execute a different workflow than the subsequent production.

Sources: [3] [2] [4]

7. Example: verify a changed transfer to an external warehouse

The following scenario does not describe a real SAP release change. Assume your company transfers an order with batch reference to an external warehouse. A reviewed indication relates to one component of this data pathway. Your technical instruction is: Only the intended batch and quantity may be further processed; incomplete transfers must remain detectable.

The functional area and partner jointly determine where the order becomes professionally binding and which system leads the processing status. Only thereafter are target values and documentation established. The selection below focuses on the relevant handover process. Other independent ERP areas are not re-evaluated solely due to this example.

Conduct cases with appropriate test endpoints and representative roles. A deliberately introduced error must not trigger an actual release. If a counterparty can only be simulated, document which component is covered by the simulation and which evidence of actual interaction remains missing.

Own regression tests for the accepted data pathway
Test caseExpected professional conductRecords supporting the results
Valid order for a partial quantity Batch, quantity and order purchase arrive unchanged Source record, transferred data set, and target record
Required batch assignment is missing Incomplete operation is rejected or stopped controlled Error message and observable processing status
Interruption following shipment Restart leaves the transaction in a single, understood state Sender/recipient linkage and documented continuity
Resubmission of the same procedure Undetected duplicate processing is excluded. Comparison of the business processes of both systems
Correction of an outstanding pending process Only the professionally valid version is used Version or correction reference and final assignment

Sources: [4]

8. Transfer deviations to a justified operational decision

If a test fails, you first distinguish product errors, unsuitable test conditions and false expectations. Keep track of the original result. A successful repeat test does not yet explain why the first attempt failed. Especially for unstable data paths, the cause should be sufficiently clarified before completion.

Assign any remaining deviation to the relevant process and associated risk. Identify, if applicable, an allowable temporary corrective action, responsible party, validity period, and subsequent resolution. Not every open documentation issue necessitates the same level of consequence as an unreliable material assignment.

If the SAP update schedule is outside your control, the decision on the permissible use of the affected process remains the responsibility of the relevant party. Prepare necessary restrictions or appropriate alternative workflows. This guide does not assume that the SAP update date can be arbitrarily postponed nor that immediate return to the previous version is possible.

Sources: [4]

9. Associate the closure with the actual system status

A viable update closure addresses a few key questions: What was actually implemented? What impacts were assessed? Which requirements are covered by which evidence? What deviations remain, and who authorized further use? Link release documentation, assessment, results, and decisions in a way that ensures the relationship remains clear and understandable without project-specific recall.

Compare the initial condition used in the test with the actual production environment. An unexpected additional change requires a renewed assessment of its implications, not an automatic repetition of all tests. Additionally, specify which initial routine processes following the update should be closely monitored and define how anomalies should be reported.

Update relevant operating instructions, training materials, and the system inventory. Use recurring outages or difficult-to-evaluate release notes to improve the next cycle.

Sources: [4]

10. Checklist for a planned update run-through

Determine the effort primarily based on the affected processes, in-house developments, data flows, available evidence, and testing capabilities. Missing subject-matter reference values can generate more work than the technical update itself. Therefore, plan for the involvement of the subject-matter department and partners; a free IT calendar slot is insufficient.

A system owner can coordinate the process. Process owners define the technical expectations, the partner outlines technical dependencies, and quality assurance contributes to evaluation and decision-making within its defined responsibilities. The specific task delegation should be clarified prior to the next release.

  • Record affected systems, source and target states, as well as actual dates.
  • Collect SAP and partner notifications with sources and assessed status.
  • Assign processes, relevant data, and dependencies.
  • Clarify uncertainties and justify test selection or exclusions.
  • Test system, data, roles, expansions, and counter-systems to assess suitability.
  • Document results and original deviations in a traceable manner.
  • Document remaining risks, temporary actions, and usage decisions.
  • Compare actual production status, operating records, and required post-observation.

Sources: [4]

Project experience and collaboration

Link each release note to the ByDesign process you use

With process owners and the ByDesign partner, we compare a relevant release note with the configured process. Which function changes, which data or decisions are affected, and which reference case shows the effect? An unchanged area may be covered by a justified document review. A change to a posting path or extension needs focused tests on the relevant version. Your team receives a reasoned scope decision and knows which findings require resolution before continued use.

Frequently asked questions about ByDesign updates

Must every ByDesign update be fully revalidated?

No, a blanket end-to-end test does not automatically follow from a cloud update. Assess the impact on your approved usage and existing documentation. This will determine the type and extent of additional testing required. For extensive changes, this extent can be significant. What is essential is a transparent justification, not the objective of conducting either the minimum or maximum number of tests.

Sources: [4]

Does "Info only" mean that no GxP assessment is required?

No. The SAP indication describes the expected action requirement from a product perspective. Your process may have specific dependencies, such as a relevant analysis or external further processing. Therefore, assign the note at least to your inventory. If no impact can be justified, you may document this without proactively retesting every functional area.

Sources: [1] [4]

What release information does the system owner need?

The following elements are required: the specific change, prerequisites, expected actions, and the assessed information status. Include references to internal usage, relevant partner input, and actual system timelines. SAP previews may still change. Therefore, any early assessment must be verified against the final information prior to serving as the basis for update closure.

Sources: [1] [2]

When should we prepare the test system?

So early that required data and components are available prior to the planned review period. The SAP Library excludes the need for a production copy during the upgrade period between test and production systems. Additionally, clarify required equipment and change documentation. A readily available test system is not automatically suitable for historical or ongoing process validations.

Sources: [2] [4]

May we exclude unused new features?

An exclusion may be justified if the function is actually not utilized and does not impact any relevant dependency. Additionally, assess any requirements that could automatically affect existing workflows. Maintain a clear record of the existing status and the rationale for the exclusion. Simply labeling a function as "new" on the label is neither a sufficient basis for exclusion nor an automatic trigger for testing.

Sources: [4]

Does our partner's compatibility confirmation suffice?

It can provide a significant contribution when it is clear which extension, version, and usage it covers. Assess its transferability to your process. Open requirements, customer-specific settings, and relevant interfaces may require additional validation evidence. Avoid both unverified adoption of a general assurance and the complete replication of appropriate partner documentation without a technical justification.

Sources: [4]

Why is a successful interface call not enough?

It initially displays only part of the data pathway. A technical justification must, for example, confirm that identity, quantity, and reference in the target system are processed correctly. Risk-appropriate evaluation should also include checks for interruption, repetition, and correction. In ByDesign, communication agreements are customer-specific configurations; therefore, both the local settings and the actual counterpart system must be considered.

Sources: [3] [4]

When can a documented assessment be sufficient without a new functional test?

If you can provide appropriate documentation demonstrating that the approved use and its relevant controls are not affected, identify the considered dependencies and the rationale for exclusion. Where the impact remains unclear, the assessment is still not complete. The absence of a test in such cases is not a risk-based decision but an open question.

Sources: [4]

What happens with an open defect shortly before a technical update?

Assess the impact on the specific process and escalate the required decision to the responsible parties. A limitation of usage or an appropriate alternative procedure may become necessary. The legitimacy of such measures must be justified. Do not assume any arbitrary postponement or rollback of the cloud update; verify the actual technical and operational capabilities available.

Sources: [4]

What is part of the conclusion and who needs to work for it?

The closure encompasses system status, impact assessment, selected validation evidence, deviations, and the decision on continued use. The system owner, affected department, quality assurance, and responsible partners provide their agreed contributions. Effort and duration primarily depend on the impact assessment and outstanding validation evidence. A fixed estimation based solely on the designation "ByDesign-Update" would therefore not be credible.

Sources: [4]

Sources and review date

Source date: 6 October 2026. Manufacturer information is derived from SAP documentation for ByDesign 2608; actual system statuses and schedules remain the governing factors for your processing. Preliminary release notices may be subject to change. The matrices and warehouse example are internal review proposals and do not represent any specific SAP release update. Regulatory focus: GMP processes for human medicinal products.

  1. SAP Business ByDesign 2608: How to Use the What’s New Viewer
  2. SAP Business ByDesign Library 2608, 21 August 2026: Maintenance Plan and System Backups
  3. SAP Business ByDesign Security Guide 2608, 31 July 2026: Communication Agreements
  4. European Commission: EU GMP Annex 11, Computerised Systems
  5. European Commission: EudraLex Volume 4, current GMP guidelines

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Justify the scope of the next ByDesign update cycle.

We support you in linking release indications with your processes and existing evidence, resulting in a concrete selection of tests and open decisions.

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