Week 8 of 12
SIT and UAT that hold up
Integration testing proves the processes work across modules and systems. User acceptance proves the business will accept them. Both fail in the same ways: transaction-by-transaction scripts, test users with SAP_ALL, expected results like "screen appears", and no agreed exit criteria.
Everything from the last seven weeks feeds this: the strategy’s exit criteria, the process library’s critical list, the test data rules and the interface inventory.
This week: make SIT and UAT end-to-end, role-based and signable
- Write SIT scenarios as end-to-end chains, e.g. EDI order → credit check → delivery → goods issue → billing → invoice to EDI → bank statement clears the payment.
- Every expected result must be checkable: a document number, a posted amount, a status. Never "screen appears".
- Run UAT with production business roles, one test user per tester, and never SAP_ALL.
- Agree the UAT sign-off route and escalation now: process owner, functional lead, test manager, program director.
Number of the week
1
test user per tester is the rule that removes lock conflicts and makes UAT results trustworthy.
Source: The Sign-Off Table UAT planUse this week
- SAP UAT Plan (Word) →
19 process variants, day-in-the-life scripts, entry criteria and the sign-off route.
- UAT Sign-Off Form (Word) →
Results, accepted defects, controls tested and signatures, for each process owner.
- SAP Test Script Template →
A 10-step SAP GUI order-to-cash script and a Fiori procure-to-pay script, ready to copy.
Next week: the data you migrate is under test too. We set up mock conversions and reconciliation.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.