IT systems · Practical guide

SAP S/4HANA: testing GxP roles and authorisations

“QA” is too broad to define access. Specify whether someone may enter, change or assess test results or release a batch, and for which plants. Those decisions give you observable expected results. A successful login proves little about the separation of these permissions.

Table of contents

At a glance

How do you validate GxP permissions in SAP S/4HANA?

Test GxP-relevant permissions in SAP S/4HANA against the activities a role may and may not perform. Check effective access to objects, organisational units and critical status transitions beyond the apps visible on screen. Use representative test roles to attempt prohibited actions, alternative access paths and combinations of roles.

Scope and Applicability

The focus lies on professional access control within the approved S/4HANA process. A general security concept or a segregation-of-duties analysis can provide valuable foundations, but it does not replace the evidence of specific GxP application.

Sources: [1]

Distinguish the edition, user interface and business activity

The S/4HANA permission concept must fit the edition and architecture. For the public edition, SAP describes IAM apps, application catalogs, limitations and application roles; the IAM information system shows its assignments. Which smallest unit is usable also depends on support for IAM apps. Do not transfer this guide unchecked to on-premises or private edition. Include Fiori, background processing and connected systems in your specific review.

Begin with the technical action: Who is authorized to modify a quality-related material parameter, set a status, or perform a release step? Supplement with organizational boundaries such as plant or company, as applicable within the process. Only thereafter should the technical implementation be assessed. A visible tile or a role with an appropriate name does not prove authorization for the action.

Capture actual user combinations. An employee can get access via multiple roles, groups or technical ways. Therefore, the concept should distinguish between approved task, assigned permission and actually effective action. Individual exceptions and administrative approaches are visibly evaluated instead of hidden as insignificant special cases.

Sources: [1] [2]

A functionality matrix with verifiable boundaries

For each critical action, specify one positive and one negative scenario. For example, an authorized user should be able to change a planned status. A read-only user should not be able to perform the same action. Add an unauthorized organizational area if this boundary is relevant. Review the business object and its downstream impact.

The following matrix serves as an example of a planning scenario. It does not prescribe a universal function separation for every company. Inappropriate combinations arise from your process and its associated risks. Document accepted exceptions and the controls in place for those exceptions, rather than asserting an ideal separation that is technically unimplementable.

Own work aid: A functionality matrix with verifiable boundaries
Critical actionPositive caseNegative case
Change material parameters Primary master data user within the authorized scope Production users without change responsibilities
Set the batch status Named professional responsibility Read-only access
Perform release step Procedure of authorized decision-makers Unauthorised requester
Describe the interface Technical identity designation Access to objects the role does not need
Maintaining Roles Authorized Administration Standard business user

Sources: [1]

Example and inspection table: Access via multiple technical pathways

A user is not permitted to modify a quality-relevant setting within the Fiori app. The negative test result is observed in the interface. However, an additional technical or background authorization may enable an alternative write path. Whether such a path exists must be verified within the specific environment; the article does not assume the presence of a specific standard gap.

Capture all intended and achievable paths to the critical object. Test representatively surface, relevant interface and, if necessary, background processing. The detection designates user, role, system level, object, action and actual result. A test report should make clear which paths were deliberately not included in the scope and why.

If an unauthorized access is identified, assess its origin and usage. The removal of a role may impact additional required tasks. Therefore, after correction, evaluate both the intended restriction and the authorized business process. A blanket suspension of all users may technically terminate a system, but it does not constitute a sufficient and sustainable operating model.

Use the matrix to test the defined business activity through the actual entry points. For each path, record the identity, role and effective boundary. Assess the reach of a shared role if the test fails. Repeat both permitted and prohibited actions after correction.

Internal Work Aid: Specialist Action, Access Path and Actual Authorization
Area to assessExample entryAcceptance question
Professional Responsibility Reading of a specified material parameter. The required work remains feasible.
Action not allowed Change due to pure production role. The limit is actually enforced.
User interface Fiori app is accessed in the correct area. The test aligns with the later user pathway.
Alternative Relevant job or interface call. No unknown additional write path.
Exception Preferred maintenance access with intended use. Usability and data integrity traceability.
Status Edition, Release, Roles and Key Restrictions. Traceability is assigned to the actual configuration.

Sources: [1]

Evaluate privileged accesses and function segregation

Administrators may require extensive technical capabilities. Identify purpose, assignment, and control. Distinguish the implementation of a system from its routine use in the process. Granting administrative access as a permanent standard role for approvals undermines a clear separation of duties.

If a contingency access is provided, describe triggers, duration, documentation, and subsequent evaluation. Solely demonstrating validity does not prove the appropriateness of the implemented changes. The review should take into account the actual critical activities performed and their impact on the process. The specific technical solution employed remains architecture-dependent.

Function separation is derived from specific risks. A general conflict matrix can assist but does not replace the evaluation of your process. SAP provides a regularly ISAE 3000-verified report on the access model of the Public Edition, with a focus on application catalogs and function separation. An accessible and relevant report can be considered as supplier evidence; however, the internal role combination must still be independently assessed. Verify that creation, modification, review, and approval are sufficiently separated such that improper self-verification is prevented or adequately controlled. Documented exceptions must have clear justifications and effective corrective actions.

Technical accounts are assigned a dedicated validation pathway with defined interface scope, responsible party, and controlled administration. They must not be used as a convenient substitute for human decision-making.

Sources: [1] [2]

Changes to the role model are controlled through takeover.

A new app, a transport change, or a modified interface can alter the required authorization scope. Therefore, link role changes to a systems impact assessment. Identify affected users and critical actions. Testing a single modified role does not automatically address interactions with existing assignments.

Obtain a clear and understandable status report. It should demonstrate which roles, organizational restrictions, and exceptions were in effect at the time of the review. A later export may reflect a different state. Link the test date and configuration state to ensure the report can genuinely be associated with the approved usage.

In normal operation, role changes, resignations, and substitutions are considered. A periodic review should align actual authorizations with actual responsibilities. Signing off on a lengthy and obscure list of roles is less effective than a targeted evaluation of critical role combinations. Training and clear accountability support this assessment.

Sources: [1]

Next steps

  • Derive critical activities and organizational boundaries from the process.
  • Invent real role combinations and technical users.
  • Perform positive and negative tests using defined accounts.
  • Awarding, modifications, revocation, and regular review in operations.
Further reading:

Project experience and collaboration

Test a critical action with the actual combination of roles

For a defined SAP business action, we compare what users should and should not be able to do. We consider assigned roles, organisational boundaries and all available access paths. One user case may represent others where their equivalence is justified. Special roles or alternative write paths need separate negative tests. With IT, we determine the extent of findings and tests for the correction. The evidence should demonstrate actual authority to act, beyond the visibility of a Fiori tile.

Frequently asked questions about S/4HANA access authorisations

Must each authorized object be individually tested?

Not automatically. Prioritize activities and failure consequences relevant to the intended use. Technical analyses complement traceable process validations.

Sources: [1] [2]

Is a hidden tile or blocked Fiori access sufficient?

You do not confirm complete authorization for yourself. A hidden tile does not prove a locked backend function. Even an audited front-end path does not automatically cover other relevant interfaces, jobs or administrative paths. Capture and check the actual entrances for the critical specialist action.

Sources: [1] [2]

Who should approve the test?

The responsible party designated within the quality and authorization system. The QA and IT departments bring different areas of expertise; accountability should be clearly defined prior to testing.

Sources: [1] [2]

Can a standardized conflict matrix replace our own role review?

It can assist in the selection of critical combinations. However, appropriateness stems from your processes, data, and responsibilities. Also assess local extensions and accepted exceptions. A formally conflict-free catalog does not automatically demonstrate that a quality-relevant action is appropriately scoped to the intended personnel.

How do we select representative SAP users for the test?

Consider actual role and group combinations, organizational areas, and exceptions. Select cases that cover different critical authorizations. An idealized single role may fail to capture real-world combinations. Document which user groups are represented by each test and where individual assessment remains necessary.

Must administrative controls be completely excluded?

Not every necessary administration can or need to be completely excluded. Specify purpose, authorization, and appropriate controls. It is essential that privileged actions do not be treated as routine operational processes without detection. Assess relevant data impact and traceability within the actually used operating model.

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: Authorization Model, S/4HANA Cloud Public EditionSupplier source for product functionalities. Availability and behavior depend on version, edition, license, and configuration; no general compliance certification.

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Verify the active SAP authorization at the specialist process level

With your responsible parties, we assign critical activities to actual roles and access paths. A surface test remains distinguishable from the broader access statement.

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