SAP S/4HANA· Testing and UAT
OverviewMCP server
Pre-implementation
  1. Implementation plan
  2. Discovery
  3. Data assessment
  4. Solution design
Implementation
  1. Configuration
  2. Data mapping
  3. Data migration
  4. Testing and UAT
  5. Cutover
Post go-live
  1. Hypercare
  2. Handover
Step 8 of 11 · Implementation · Updated October 26, 2026

SAP S/4HANA testing and UAT

Testing shows that the configured SAP S/4HANA runs the client's processes from end to end. In UAT, client users confirm it with their own data and their own roles. superglue's agent writes the test scripts from the signed requirements, runs the system tests in the sandbox, and tracks UAT results and defects with the client.

Start an SAP S/4HANA projectTalk to us

How this step works

What the agent does

  • Writes test scripts per process from the requirements and the design.
  • Runs system tests with test transactions in the sandbox, and records the results.
  • Shares a UAT tracker with the client testers and collects their results.
  • Links each defect to the requirement and the setting it affects.

What you decide and approve

  • Which processes go through UAT, and who tests them.
  • Which defects block go-live.
  • When the client signs off UAT.

What the client gets

  • Test scripts with the results of each run.
  • A UAT sign-off per process.

What makes SAP S/4HANA testing and UAT work

  1. 01

    Check the Universal Journal line

    Run each process to the posting and check the profit center, segment, cost center and functional area on each ACDOCA line. A posted document can still carry the wrong assignment.

  2. 02

    Test with production roles

    Each tester uses the business role or PFCG role they will have in PRD. Missing authorizations only appear with the real role.

  3. 03

    Trace tests to scope items in SAP Cloud ALM

    Link each test case to its requirement and scope item, and log defects against it. This traceability is what the client signs at the end of UAT.

  4. 04

    Rerun regression tests after imports and upgrades

    A transport into QAS can change a process that already passed. In Public Edition, the test system gets each release upgrade before production, so rerun the regression set there too.

Frequently asked questions

How do you test a SAP S/4HANA implementation before go-live?

Check the Universal Journal line; Test with production roles; Trace tests to scope items in SAP Cloud ALM; Rerun regression tests after imports and upgrades. The agent writes the scripts from the signed requirements and runs the system tests in the sandbox.

Do client testers need a superglue account?

No. The agent shares the UAT tracker as a link. Testers record their results there, and the agent sees them in the project.

How does superglue work with our consultants?

superglue works alongside your team. The agent takes on the repetitive work, such as reading documents, drafting, mapping, loading and reconciling. Your consultants keep the client relationship and the decisions, and they approve every change to a client system.

Can we use our own implementation method?

Yes. Write your firm's method as a playbook, and every consultant and every session follows it. The documents the agent produces carry your firm's branding.

Which systems can we migrate from into SAP S/4HANA?

Common sources are SAP ECC, Oracle E-Business Suite, Microsoft Dynamics AX, JD Edwards and spreadsheets. The agent also reads Excel, CSV and XML exports and most systems with an API or a database.

Is client data safe?

superglue holds a SOC 2 Type 2 report and works under GDPR. Credentials are encrypted with AES-256. On the Enterprise plan, superglue can run on your own infrastructure.

How do we start?

Start with one live SAP S/4HANA project. Connect the client's systems, give the agent the statement of work, and run the first steps together with us.