IT systems · Practical guide

SAP Business ByDesign: testing GxP access rights

In ByDesign, a single view says little about a user's effective access. Additional views and organisational restrictions work together. Define the role, activity and data scope, such as permission to view a site's stock without changing a quality status, then test that boundary in the process.

Table of contents

At a glance

What should you test for ByDesign roles in a GxP environment?

For GxP use, test SAP Business ByDesign roles against specific permitted and prohibited activities. SAP describes access through work centres, views and their access contexts. Verify that effective permissions are limited to the intended data and organisational units. Visible menu entries alone do not demonstrate that boundary.

Scope and Applicability

This article elaborates on the role review in ByDesign. The limitations possible within a view must be determined based on the product documentation and the actual configuration; identical capabilities across all views are not assumed.

Sources: [1]

Critical business activities as starting point

First, define the actions the organization wishes to control. This may include changes to batch information, material balances, quality-related parameters, and release procedures. Supplement with organizational boundaries: site, company, department, or other actual usage-based restrictions. The name of a business role does not yet fully address these functional considerations.

In ByDesign, roles, work centers, views, and access restrictions are configured. The appropriate assessment considers the actual combination of these elements as used by the end-user. Verify the deployed tenant and release, as well as partner expansions. This article does not describe a universal role library that would be suitable without modification for every life sciences organization.

Capture exceptions, waivers, and temporary project access. A user may perform their regular duties correctly, yet still possess unwanted change rights through an additional role. Therefore, effective authorization should be verified based on actual assignments and real-time actions, not solely on an approved role list.

ByDesign checks during the assignment of multiple views the previously defined requirements for functional segregation and displays conflicts with descriptions and recommended solutions. Verify that your critical combination is indeed captured; if it is missing from the catalog, it requires a separate evaluation and appropriate testing. Additionally, consider views that are automatically assigned in combination with other views.

Sources: [1] [2]

Align the role matrix with actual work performed

Describe, for each critical function, the permitted activity, the affected data, and the expected boundary. For example, an employee may view information on an identified inventory balance but is not authorized to modify a quality-relevant attribute themselves. The positive case demonstrates required functionality; the negative case illustrates the intended restriction.

When a separation between creation and release is intended, verify both steps using the respective designated roles. A hidden button alone is not sufficient evidence. Consider existing import interfaces or extensions, where applicable, especially if they could alter the same data. The test selection should align with your specific authorization model.

Internal Work Aid: A role matrix aligned to actual work responsibilities
Activity in the exampleAuthorized userTest limit
Show batch data Production role Required information available
Change expiry date Named master data owner Modification by production role is not possible
Perform release step Responsible technical role Selected separation remains effective
Edit another area Only appropriately authorized roles Organizational access restrictions are in effect
Use technical import Designated Integration No unjustify ed access to other objects

Sources: [1]

Example: two individually plausible roles result in excessive privileges

An employee holds a production role and temporarily assumes master data responsibilities. Each assignment is individually traceable. However, together they enable modification and subsequent use of the same critical parameter, despite the internal procedure requiring an additional subject-matter approval. Therefore, the assessment must consider the combined effect. The extended access arises from the role assignments; this example does not describe a SAP Business ByDesign defect and is not a completed product test.

Simulate this combination using controlled test data. Verify display, editing, subsequent usage, and the intended decision pathway. Predefine the expected system response. If the system fails to implement the desired technical separation, assess whether an alternative appropriate control pathway is feasible or whether the role structure needs to be adjusted. A mere procedural instruction is not automatically sufficient.

Upon end of delegation, the additional assignment will be removed. Verify the actual revocation of rights and obtain a traceable justification. An approved email confirming removal does not constitute proof of implementation. Additionally, assess whether any interim critical changes have been appropriately addressed in accordance with the procedure.

Own work aid – Example: two individually plausible roles result in excessive privileges
PhaseIn-house verificationExpected result
Normal operation Use production role exclusively Permitted use without unauthorized modifications
Representation Combining both roles Additional scope is visible and evaluated
Critical workflow Attempt to perform the change and subsequent steps Selected control rule applies
End of representation Remove rights and reverify Extended access is no longer available
Review of the evidence Link the assignment to the specific action Authority and actual use demonstrable

Sources: [1]

Do not confuse access and change history.

A valid authorization restricts who is permitted to perform an action. A change history enables explanation of what actions were taken. These functions complement each other but do not replace one another. A fully logged unauthorized access remains an access event. Stringent access restrictions alone do not address all questions regarding the traceability of authorized changes.

At the specific business object, verify which history is actually available. A configuration history is not automatically a complete record of all business data. Required information, access, and retention are derived from the respective process. During testing, implement a specific change and attempt to retrospectively trace it using authorized access.

Maintain clear definitions of who is authorized to view audit data or change records and who is responsible for evaluating unusual changes. An existing report without a designated reviewer may remain underutilized in daily operations. The required review should be risk-based; the document does not assume a universal frequency or identical protocol coverage across all ByDesign objects.

Sources: [1]

Manage role changes, releases and partner access

Link personnel and task changes to an assessment of existing access rights. Existing roles should not remain unreviewed when an employee takes on a new area of responsibility. Obtain a clear overview of justified exceptions and their duration. This facilitates future audits and prevents project-based access from becoming a permanent standard.

When assessing releases or changes to extensions, evaluate whether new views, actions, or data pathways are affected. Recompute appropriate critical access scenarios. A full test of every screen is not automatically required; however, a justified selection must cover the relevant impacts. Maintain traceability between test environment and production tenant.

Provide the internal team not only with role exports, but also with the professional context and rationale behind them. A system owner should be able to explain which responsibilities are justified by a role assignment and which test defines the boundary. This ensures that role management remains understandable and traceable even after the implementation project has concluded.

Sources: [1]

Draft: Review organizational boundary definitions

As a second example, an organizational boundary is assessed: A specialist role shall be permitted to read within area A and perform a specified action, but shall not be allowed to do so in area B. Define two clearly assigned test objects and the expected rights. The specific restrictions on viewing privileges supported by the respective system must be verified at the actual ByDesign instance.

Perform the same action with the actual role combination in both areas. Visibility and change authorization are evaluated separately. Also check for export or any other actually used pathway. An inappropriate boundary effect is assessed prior to assuming that an additional organizational control pathway is sufficient.

Own work aid: positive and negative area access
Area to assessTest caseExpected finding
Scope The task is limited to Area A. Authority has been defined for the business activity.
Permitted area Edit object A with intended use. Required activity functions.
Not allowed area Attempt the same action on object B. The selected boundary works.
Roll combination Include actual issued views. No unexplained additional access.
Next step Check the used export or other entry point. The required limitation remains justifiable.
Configuration version Users, views, and restrictions are documented. The result is consistent with the verified status.

Sources: [1]

Next steps

  • Define activities and specify allowable data areas.
  • Assign Work Center, Views, and actual rights combination.
  • Verify permitted and prohibited actions performed with test accounts.
  • Document issuance, withdrawal, and operational review.
Further reading:

Project experience and collaboration

Test the effective combination of views and access scopes

With process owners and administrators, we compare the ByDesign views actually assigned with a critical task. A delegated role or automatically linked view can give users more access than an individual role suggests. We test permitted and prohibited actions. Unwanted combinations need revised assignments or an additional control with demonstrated effectiveness. We also examine subsequent revocation. An export of user assignments supports the evidence, but the ability to perform the action must still be tested.

Frequently asked questions about ByDesign access rights

Are standard reels already considered valid GxP evidence?

No. They can serve as a starting point, but must align with their actual rights in relation to the respective process. Consider combinations, linked views, organizational boundaries, and expansions. Only after configuration, appropriate action checks, and controlled management can the intended usage be justified.

Sources: [1] [2]

Can QA verify all roles individually?

For the meaning in the process, QA requires the technical department; for the technical impact, the administration is responsible. Authority and release should be clearly defined.

Sources: [1] [2]

When will it be retested?

When changes may affect relevant access, such as new views, modified roles, or organizational structures, the impact assessment determines the scope.

Sources: [1] [2]

Is every additional role automatically a risk?

Additional roles may be required for representation or new responsibilities. The effective overall scope and professional implications are critical. Special attention should be given to critical combinations, organizational boundaries, and the duration of temporary arrangements. A documented justification should be linked to actual implementation and subsequent withdrawal.

How do we verify organizational access restrictions?

Use data from an authorized and a non-authorized area. Perform the relevant action using the actual role combination. Document the configuration and results. Visibility settings alone do not confirm any change authorization; the specific business process should demonstrate the intended boundary.

Why is user export alone not a complete test?

It describes assignments at a specific point in time. It does not automatically reflect their full technical impact, alternative formulations, or the correct function within a specific workflow. Link export, task description, and appropriate action checks. Thus, it remains a useful standing record within a comprehensive evaluation.

Sources and review date

The sources provide the technical foundation. Tables, checklists, and examples are derived methodological tools, not verbatim regulatory requirements. Manufacturer information must be referenced to the specific version and configuration in use.

  1. European Commission: EU GMP Annex 11, Computerised Systems (2011)Current version as per EudraLex inventory as of 14.10.2026. Application, risks, operation, and data lifecycle; specific testing proposals are derived independently.
  2. SAP: Business ByDesign – Access RightsSAP Business ByDesign, August 2026: Work Centers and Views, Restrictions on read/write access, automatically linked views, and function-level access reviews. The specific GxP role combination requires individual assessment.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Review ByDesign access to specific activities

Bring with you actual views, role combinations and organizational limits. From this you can derive suitable permitted and not allowed action cases.

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