Table of contents
At a glance
What does SAP Business ByDesign validation involve?
SAP Business ByDesign validation demonstrates that the configured system is fit for its intended GxP use. Define the scope from the processes, data and risks involved. Supplier documentation can support the assessment. Evaluate your own configuration, roles, extensions and interfaces, then use change control to maintain the validated state during operation.
- The intended use determines the scope; the product name alone is insufficient.
- Batch status, authorized user rights, and data transfers are verified during actual operation.
- SAP records and internal process records have different responsibilities.
- Cloud updates are part of the planning process right from the start.
When is SAP Business ByDesign GxP relevant?
The first question is whether the decision is based on ByDesign data. Are batches identified there, are quality-relevant stocks controlled, or are data provided for manufacturing and release processes? If so, this workflow warrants a technical evaluation. A purely commercial process has a different basis than the decision regarding which materials are authorized for production.
EU-GMP Annex 11 applies to computerised systems used in GMP-controlled activities. It is therefore not a general legal framework for the use of ERP software. Whether additional requirements, such as US regulations on electronic records, are applicable is determined by the specific activity, market, and nature of the records.
As a working aid, a process overview with four elements per step is appropriate: required data, decision derived from that data, potential consequences of erroneous processing, and existing controls. Dependencies are then added. An initially unchallenged master date may be relevant if it controls a quantity conversion, a status, or an assignment within a quality-critical process.
Sources: [1]
Which evidence originates from SAP, the partner, and the end user?
ByDesign is operated as a cloud-based ERP system. This results in a clear division of responsibilities: provider operation, system setup, and usage within a regulated process represent distinct tasks. A clear responsibility matrix prevents any party from assuming that the other is responsible for audits or evaluations. The following assignment serves as a conceptual example; the actual contractual agreements and duties prevail.
Do not accept general certificates alone. What matters is whether specific information is available for your intended use and whether it supports a valid conclusion. A technical description explains a function. A test report verifies specific tests conducted at a particular site. Both must be evaluated for relevance and applicability to your specific purpose.
| Topic | Typical contribution | To be clarified with the user |
|---|---|---|
| Supplier operation | SAP Documentation on Operations, Safety, and Release Procedures | What services are covered under the agreement? |
| Configuration | Partner documentation for scoping, fine-tuning, and expansions | Does the documented configuration match the tenant in use? |
| Business process | Company requirements, work instructions, and process knowledge | What controls and acceptance criteria are required? |
| Testing and Operation | Evaluated existing evidence plus additional testing | Who evaluates deviations and decides on their use? |
Check batches, decay data and inventory status in the flow of goods
SAP describes batches and lots in ByDesign under "Identified Stock". The identification is linked to a product; this may include, for example, production and expiry data. For validation, it is important to understand how these information elements are utilized within the configured material flow.
A status name does not yet indicate whether a specific movement is prohibited. The SAP documentation differentiates the usage across various workflows and also identifies movements that may still occur with blocked or expired inventory. Therefore, a requirement regarding usage or dispatch is evaluated based on this specific action.
Prepare a concise check table comprising starting status, user role, desired action, and expected outcome. Include authorized exceptions, such as controlled recall or destruction. For an external warehouse, monitoring is conducted at the system boundary: which status information leaves ByDesign, and which decision is made by the warehouse?
- Batch identification and product assignment during data capture, partial quantities, and reversal comparisons.
- Record expiry date including relevant edge cases in test data.
- Perform authorized and unauthorized actions using the intended user permissions.
- Tracking from incoming goods to use or delivery.
Sources: [3]
Evaluate user rights and change histories separately
ByDesign uses Business Roles with Work Centers, Views, and access restrictions. For multiple roles, a user's permissions may be extended. Therefore, evaluating each role individually does not automatically reflect the actual combined permissions. For critical actions, representative users with their actual role combinations provide more relevant and reliable evidence.
A second control point is the traceability of changes. "Configuration Change History" relates specifically to changes in system configuration; it does not constitute a general proof of a complete change history for all business data. At the relevant data object, assess the available information, who has access to it, and how it remains accessible during the required retention period.
Concrete audit questions include: Who is authorized to modify an expiration date? Is a prior indication clearly traceable when updated later? How is a change in personnel assigned? How does a responsible party evaluate suspicious modifications? An existing history only fulfills its purpose when integrated with the intended review and work processes.
Interfaces: Verify professional handling up to the destination
SAP documents communication scenarios and web services for integration with ByDesign. The specific installations utilizing these are derived from the established connections. This includes partner expansions, custom fields, and technical users. A successful call confirms initial technical communication; the final business state requires a separate reconciliation.
Track individual data records at a quality-related interface from origin to destination. Compare identifiers, values, units, status, and timestamp. Particularly insightful are rejected messages, retry transmissions, and interruptions. Who identifies the error, who is authorized to correct it, and how is duplicate processing prevented or detected?
A useful traceability link connects the source data, the identifiable message, and the result in the target system. Screenshots lacking a common reference point hinder this comparison. Additionally, document any changes to a mapping, field, or connected system that trigger a re-evaluation.
Example: Test a batch-related process in a comprehensible way
The following example illustrates a possible test design; no assurance is given regarding the standard behavior of a ByDesign configuration. Assume a facility wishes to prevent the use of material with an unapproved status for a specified production step. The department first defines the exact rule and its permitted exceptions.
Test data are prepared using comparable batches with different status values. An authorized production user performs the same procedure on these batches. The expected outcome is described prior to execution. In the test protocol, tenant, system version, roles, data used, and actual system responses are documented.
Subsequently, the status is modified by a designated user, and the process is repeated. Additional cases involve unauthorized attempt at modification and status transfer to an associated system. If a response does not align with the specified requirement, the result is evaluated. The desired response is not retrospectively adjusted to match the observed behavior.
ByDesign - Integrating Updates into the Validated Operation
SAP describes quarterly tenant upgrades with an earlier update of the test tenant. The specific schedule and available test time must be confirmed by the company for its landscape. Different version statuses are also relevant: according to SAP, the consolidation of a change project requires that test and production environments be running identical versions.
For the evaluation of an update, a reusable workflow is recommended: review release information, assign affected processes and enhancements, assess risks, select testing activities, and determine findings. An existing catalog of key process validations facilitates this work. It is updated when new interfaces, roles, or subject-matter changes occur.
A full repetition of every previous inspection is not a prudent automation. Similarly, assuming SAP will only provide non-critical changes is insufficient. Documented impact assessment justifies the selection. For a relevant open finding, the team must designate a specific responsible party and establish an escalation pathway prior to the production update.
What documentation and decisions are required?
The documentation is intended to make the system used and the decisions made comprehensible. An appropriate structure combines system description and scope, requirements, risk assessment, used supplier documents, tests, deviations and the final evaluation. Names and divisions are based on the company's quality management.
For an existing ByDesign system, work commences from the current state. Existing documentation is reviewed for currency and reliability. Missing evidence is identified, assessed for significance, and addressed with appropriate actions. A newly signed documentation does not retrospectively validate a previously unexamined state.
The effort depends in particular on process scope, extensions, interfaces and available documents. In addition, test accesses and the availability of department, QA and partners. A reliable plan specifies these prerequisites before appointments are promised. For operation, change procedures, access management, fault handling and the regular evaluation of the system status should be connected.
Sources: [1]
Checklist for the Start of ByDesign Validation
With these points, an initial meeting can be prepared. The list serves as a starting guide and does not replace an assessment of your specific process.
- GxP-related processes, locations, and responsible departments are identified.
- Test and production tenants, system status, and the next upgrade window are known.
- Scope, fine-tuning, expansions, and interfaces are clearly documented and traceable.
- Critical batch, status, and master data possess professionally defined rules.
- User roles and existing histories can be verified in the test system.
- Supplier documentation and existing test evidence are available or specifically requested.
- Variations, open actions, and decisions regarding usage are the responsibility of designated individuals.
Project experience and collaboration
Plan ByDesign validation evidence around the batch process
For SAP Business ByDesign, we agree with your process owners, IT team and implementation partner who will provide each item of evidence. A batch status change followed by a stock movement is one possible starting point. We establish which requirements existing SAP or partner documentation covers and where your configuration needs additional testing. If only a few gaps remain, a targeted evidence package may suffice. If the process itself is unclear, we first work through it with your team.
Frequent Questions on ByDesign Validation
Has SAP Business ByDesign already been validated by SAP?
No, not for your specific use case. Manufacturer assessments and documentation can provide part of the evidence. Evaluate which of these actually cover your configuration, roles, extensions, and processes, and identify which additional assessments are required.
Sources: [1]
Must the entire ByDesign system be validated?
Not all functions need to be validated to the same depth. The scope aligns with the intended use and a documented risk assessment. Relevant functions, including their interdependencies, are evaluated. This may also include data, interfaces, or shared settings outside of an initially selected module, as appropriate.
Sources: [1]
How is ByDesign operated following a Cloud update?
The company evaluates changes with respect to its processes and establishes required assessments and actions. SAP outlines an accelerated upgrade of the test tenant. Specific available timelines, roles, and test data should be pre-organized. Test results and decisions regarding required actions are documented.
Does ByDesign provide an adequate audit trail for each GxP process?
Not automatically. The various ByDesign histories and protocols serve different purposes. Whether they meet your GxP documentation requirements must be assessed at the relevant business object: Can changes be clearly traced with respect to personnel, timestamp, and prior value? The Configuration Change History alone does not establish a complete history of all business data.
Can an already productive ByDesign system be retrospectively assessed?
Yes. The starting point is the current system status and existing documentation. Gaps and their significance are assessed, actions are prioritized, and additional evidence is obtained. This work must not be presented as retrospective validation of a previous unexamined state.
Sources: [1]
How long does validation of SAP Business ByDesign take?
The duration is primarily determined by the number and variations of relevant processes, expansions, and interfaces, as well as existing documentation and available specialist, QA, and partner resources. The next cloud update may also influence the sequence. Therefore, a robust scheduling plan requires coordinated planning of technical decisions, test preparation, execution, and review.
Sources: [1]
Sources and review date
Manufacturer specifications describe functions and processes as currently documented. They do not confirm any specific customer configuration. Inspection checklists, checklists, and example workflows are professional support tools; the regulatory alignment is to be determined for the intended use.
- European Commission: EU-GMP Annex 11, in particular the General Principle as well as Sections 1, 3, 4 and 9–12
- SAP Help Portal: SAP Business ByDesign
- SAP Help: Identified Stock Management
- SAP Help: Working with Business Roles
- SAP Help: Configuration Change History
- SAP Help: Communication Scenarios
- SAP KBA 3368337: Tenant Upgrades and Version Differences in Change Projects
Sources checked: .
Support with your ByDesign validation
Daniel Herrmann Consulting provides support in defining scope, evaluating existing documentation, and implementing an agreed validation scope. Professional judgments and approvals remain embedded within your quality process.
- 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.

