Lesson 1 of 6
UAT is a business decision
10 min
Listen to this lesson
Most SAP programs plan user acceptance testing (UAT) as the last test cycle before cutover, and many of them run it as a re-run of system integration testing (SIT) with different people pressing the buttons. That misses the point. SIT asks a technical question: does the configured solution work end to end, across modules and interfaces, as designed? UAT asks a business question: can our people run our business on this, in the way we actually work, and are we willing to accept it? The answer to the second question is a decision, and the people who make it are process owners and business leaders, not the test team.
That framing changes almost everything about how you plan UAT. The testers are business users, not consultants. The scripts follow a working day, not a configuration object. Success is measured by whether each process owner is prepared to sign, not by a pass rate alone. And the output is a sign-off pack that a finance director or a head of sales can read in ten minutes and put their name to.
How UAT differs from SIT
| Dimension | System integration testing (SIT) | User acceptance testing (UAT) |
|---|---|---|
| Question answered | Does the solution work as designed, end to end? | Can the business run on it, and will it accept it? |
| Who executes | Project testers and functional consultants | Business users and key users from each process area |
| Basis for scripts | Design documents, interfaces, configuration | Business processes, roles and real working scenarios |
| Users and access | Often broad test access to keep moving | Production-like business roles per tester |
| Exit | Test lead confirms exit criteria are met | Process owners sign acceptance, with risks named |
The two overlap in content. Contoso Motor Co.'s order-to-cash flow (sales order, delivery, goods issue, billing, payment) will be tested in both cycles. In SIT the project tests it with every interface live and checks that the accounting documents post correctly. In UAT Maria, the order-to-cash key user, runs the same flow with her own sales role, her own customer Great Lakes Fleet Services, and the paperwork she would hand to the warehouse on a Monday morning. If she cannot find the delivery block she relies on, or the invoice layout confuses customers, SIT would never have caught it. UAT should.
Where UAT sits in SAP Activate
In SAP Activate, testing happens in the Realize phase. SAP Learning's test strategy material describes informal unit and string tests during configuration, formal end-to-end, integration and data migration tests in the test system, and then UAT by customer line-of-business experts. It recommends that the experts who took part in the Fit-to-Standard workshops run UAT, because they saw the processes demonstrated and asked for the changes. Issues from UAT should be resolved and recorded before the project moves into Deploy, where the final cutover rehearsals, end-user training and go-live happen.
- ExploreFit-to-StandardBusiness experts see standard processes and agree gaps and changes
- Realize, earlyUnit and string testsInformal checks as configuration and extensions are built
- Realize, midSIT and data migration testsFormal, documented end-to-end and interface testing with migrated data
- Realize, lateUATBusiness users run their processes with real roles and record results
- DeployCutover and go-liveOnly after UAT issues are resolved or formally accepted
Operational acceptance runs in parallel
Business acceptance is not the only acceptance. Operational acceptance testing (OAT) asks whether IT and support can run the system: batch jobs and job chains complete on schedule, output reaches printers and email, interfaces recover after a failure, backups restore, monitoring raises alerts, and the support desk can take a ticket and route it. At Contoso, Luis (cutover manager) and the RISE service team own most of this. OAT runs alongside UAT, often in the same test client 100, and its results go into the same go-live decision.
Keep the two streams separate in scope and reporting, but join them at the decision. A business process that passes UAT but whose overnight credit-check job fails in OAT is not ready. Grace, the PMO lead, should see both streams on one page in the go-live readiness review.
What would you do?
Two weeks before UAT, the systems integrator proposes to save time by having its consultants execute the UAT scripts and send Contoso's process owners a summary for signature. Dan, the finance process owner, is tempted because his team is busy with quarter-end. What should Priya, the test lead, recommend?
- UAT answers a business question: can we run on this, and will we accept it?
- SIT proves the design works; UAT uses business testers, real roles and real working scenarios.
- In SAP Activate, UAT runs late in Realize, and its issues are resolved or accepted before Deploy.
- Operational acceptance runs in parallel and feeds the same go-live decision.
- Process owners own the acceptance decision; the test lead runs the process that supports it.
Check your understanding · not graded
Lesson check
1. Which question is UAT designed to answer?
2. In SAP Activate, in which phase does UAT normally run?
3. What does operational acceptance testing check that UAT usually does not?
4. According to SAP's test strategy guidance, who ideally executes UAT?