Table of contents
At a glance
Which tests do GxP-relevant approvals in SAP Fiori need?
For GxP-relevant approvals in SAP Fiori, test approver selection, triggering conditions, delegated authority and behaviour after a record changes. A completed Fiori task alone is insufficient. The process should retain the approved content, the identity of the decision-maker and the meaning of the decision.
Scope and Applicability
SAP describes flexible workflow, including for procurement documents in S/4HANA Cloud Public Edition. This does not imply a general statement regarding batch release or any SAP edition. Review the specifically implemented workflow and its integration with the business object.
What a release should professionally validate
A Fiori app is initially a user interface. Describe the decision made upon performing an action: approval of a procedure, confirmation of a review, or legally binding electronic signature. These functions may be interrelated but are not equivalent. A button labeled "Release" does not demonstrate appropriate function segregation nor compliance with all signature requirements.
Retain the App, Backend, Workflow, and Identity Services. For the flexible workflow in the Public Edition 2608 purchasing area, SAP defines start and step conditions, assignee rules, deadlines, and exception handling. Process experts model the workflow in "Manage Workflows"; approvers review tasks in "My Inbox". Verify these settings as well as the actually transferred production status. This specific product description does not constitute validation evidence for any other Fiori workflow or edition.
State the decision as a professional statement: An authorized individual confirms a clearly designated procedure in a specific version and with a discernible intent. This generates concrete testing questions regarding identity, content, timing, and unaltered assignment. If an electronic signature is required, the applicable requirements for such a signature must additionally be assessed.
Link process, version, and decision significance
Check whether the decision-maker actually sees the relevant information. A title and a document number may be insufficient if approval-relevant data changes between display and decision. A proper linkage must exist between the reviewed content and the confirmed status. The technical implementation of this linkage depends on system configuration.
Define the approach to handling changes during an ongoing workflow. A modification to critical data may necessitate a re-evaluation. A purely editorial adjustment may be treated differently. The process should clearly indicate which decision applies to which version. A general statement such as "workflow completed" obscures this distinction.
| Assessment question | Evidence to produce | Potential error |
|---|---|---|
| Who decides? | Users and actual authorizations | Representation has unjustifyedly broad access |
| What is being validated? | Unique process and data status | Decision relates to obsolete display |
| What applies? | Visible decision type | Technical knowledge acceptance is interpreted as quality release. |
| What happens next? | Actual resulting state | Status changes, but the required follow-up process remains incorrect |
| How can it remain traceable? | Relationship between content, person, and time point | The protocol leaves the verified version open. |
Example: critical change after start of release
A request for a quality-related material parameter is under review. While the decision-maker is evaluating the request, another role modifies the proposed value. The original reviewer subsequently clicks on "Release." The own requirement stipulates that any relevant change must be identified and the updated status must be re-evaluated.
Prepare a known starting process and document its content. Open it using the decision-maker role. Then, in the controlled test environment, alter the critical value via the intended alternative pathway. Execute the decision and monitor status, notification, and subsequent process. The expected reaction shall be predefined, not adjusted to the observed standard behavior.
A suitable result can be an prevented decision, a new check or another comprehensible control per architecture. It is crucial that no unchecked changed content is considered to be released unnoticed. The test report should combine the old and new status as well as the actual reaction. A screenshot of the green workflow status alone is not enough for this.
| Test case | Action | Expected process outcome |
|---|---|---|
| Unaltered process | Authorized person decides | The correct status is verifiable. |
| Critical change | Change value after start of inspection | Selected change and re-evaluation control applies |
| Unauthorized user | Attempt the same decision | Authority limit remains valid |
| Rejection | Rationale for rejection of the procedure provided | Invalid subsequent process does not start |
| Representation | Use the deputy arrangement within the specified period | Responsibility is assigned to the actually acting authorized person. |
Representation, mobile usage and alternative options review
Representation may be necessary, but should be clearly defined as specific authorities. Document the start, end, scope, and types of decisions involved. Representation for commercial activities does not automatically include quality-related decisions. Verify that the configuration appropriately enforces this boundary and that the responsible individual remains identifiable thereafter.
When mobile or multiple interfaces are used, consider the scope of information available. The decision-maker must be able to access the required data from those locations. A condensed display may facilitate user experience but should not compromise professional assessment. Evaluate representative devices and the actual approved usage pathway.
Capture background jobs, interfaces, and administrative pathways that may alter the same status. A formally correct decision workflow does not prove that every other status change has been controlled. Document authorized exceptions and required records. The actual architecture determines which pathways are relevant.
Evaluate electronic signature specifically additionally.
If the decision is to be used as an electronic signature, verify the applicable requirements relating to identity, intent, and association with the record. The existence of an existing enterprise login does not automatically satisfy all the requirements for a signature action. Similarly, every internal authorization is not necessarily required to be classified as a Part 11 signature. The scope shall conform to the applicable records and guidelines.
For EU GMP, Annex 11 addresses electronic signatures, among other aspects, regarding enterprise-wide impact, persistent linkage to the data set, and date and time. For US applications, additional Part 11 requirements may apply. Do not confuse this framework with a general eIDAS classification. The specific implementation must be assessed in relation to the intended use.
Document what the user confirms in the action and how the connection becomes visible later. An exported report should not lose the required context. Also check a historical search after a subsequent change. The proof must be able to explain the decision in its context at that time.
Workflow changes and ongoing operations maintained
A modified decision rule may activate other personnel, conditions, or follow-up actions. Therefore, assess not only the technical transfer but also ongoing processes. Define whether these processes end under the previous rule or are controlled and transitioned into the new one. An unclear mixed operation complicates the determination of which authority was in effect at any given time.
Critical positive, negative, and change cases are suitable for regression testing. Add failure and restart scenarios if they may influence the decision status. A double notification does not automatically constitute a dual professional release; however, a technical retry must not generate an uncontrolled second business transaction. Assess the actual impact.
Provide regulatory status, responsible parties, representation, and audit trail access. The internal team should be able to explain why a specific action was assigned to a particular individual and which content was confirmed. This ensures the workflow is traceable during audits and in subsequent changes.
Also check for missing approvers and overdue tasks. An alert or reassignment must not replace a required conscious decision through automatic approval. The actually confirmed content must remain linked to the version of the business object.
Worksheet for deputy cover with clear limits on authority
Another independent testing scenario involves a temporally and professionally limited representation. Prepare a process both within and outside the authorized scope. The SAP help documentation outlines representation rules for the specified Public Edition context in "My Inbox"; their suitability for your specific decision-making process will be assessed separately.
Verify access, the actual responsible person, available content, and downstream impact. Upon expiry or revocation of authority, any previously authorized action is attempted again. The historical record must capture the truly responsible individual. If the process additionally generates an electronic signature, the specific requirements for such signatures must be evaluated.
| Phase | Test case | Evidence needed |
|---|---|---|
| Start | Activate the designated deputy. | Person, scope and time reference are clear. |
| Within | Edit approved process. | Required content is accessible; authorized decision takes effect. |
| Outside | Attempt to edit a transaction outside the role's permitted scope. | The specified authority limit remains valid. |
| Content | Review the annex and current status. | No decision shall be made without appropriate basis. |
| Ende | Verify access after expiry or revocation. | Additional power does not remain unnoticed. |
| History | Investigate closed decisions. | The signer, signed content and meaning of the signature can be identified. |
Next steps
- State the decision and legal significance of approval.
- Document conditions, roles, and alternates.
- Review data modifications and exception routes with specific test cases.
- Assess the result at the business object and in the available protocol jointly.
Project experience and collaboration
Bind the decision to the content the user actually confirmed
Your process owners select a specific Fiori approval and define what the person is confirming. We change a value under controlled conditions between display and approval to test whether the action remains tied to the content. Depending on the process, we also test deputies, mobile views or an alternative status path. QA and IT distinguish an internal approval from a regulated electronic signature. We identify the actual person, the version confirmed and the downstream effect.
Frequently asked questions about Approvals in SAP Fiori
Is a Fiori release click automatically a Part 11 signature?
No. First assess the significance and applicable scope of the action. An internal approval may have different requirements than an electronic signature for a regulated record. Thereafter, the actual technical and organizational implementation, along with the necessary evidence, must be evaluated. Neither the product name nor the button text alone confirms the signature function.
Must reminders also be tested?
Can email approval be considered equivalent?
Must all open workflows be restarted upon a rule change?
Not at all. Evaluate the content, persons and decision-making rules. Set a comprehensible transition path. A continuation under the previous rule may be appropriate if it is still technically acceptable. In case of a faulty authority or critical content change, however, a reassessment may be required.
How can we test delegation in an approval workflow?
Use a clearly identified process both within and outside the authorized scope of representation. Verify the actual individual, authority, time period, and subsequent impact. Notification to the representative does not constitute sufficient evidence of their appropriate decision-making capability. Historically, the actual individual acting must remain identifiable.
What should be particularly verified in mobile releases?
The decision-maker must be able to access and understand the information required for their responsibilities. Verify the actual display, version, and critical components on the approved usage pathway. A condensed mobile presentation must not undermine the technical evaluation without notice. The appropriate controls shall be determined based on the specific process.
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.
- European Commission: EU GMP Annex 11, Computerised Systems (2011)Sections 4.4, 10, 12, and 14: Requirements, Changes, Access and Electronic Signatures. Current version as of EudraLex on 14.10.2026; no universal project or deadline stipulation.
- eCFR: 21 CFR Part 11 – Electronic Records; Electronic SignaturesCurrent regulatory text. Applicability and additional documentation obligations must be assessed on a process-by-process basis.
- SAP: Flexible Workflow in 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: .
Review decision, content, and workflow impact together
Starting from a specific batch release, we consider the current status, authorisation, downstream impact, and required history. Separate evaluation is provided for simple approval and electronic signature.
- 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.

