Both formats: the Word file is the one you edit, the PDF is for reading, printing and circulating. Adapt them freely — once you download them they are yours, and there is nothing to attribute.
Download Word (.docx) · 66 KBDownload PDF · 141 KB
UAT is where the business decides whether it can do its job on the new system. In an S/4HANA program it carries an extra weight: for most users this is their first extended contact with Fiori, and their verdict is shaped as much by whether they can find things as by whether the configuration is correct.
What is inside
- 1. Purpose and boundaries
- 2. Entry criteria
- 3. Participants
- 4. Scenarios
- 5. Fiori usability feedback
- 6. Defects and change requests
- 7. Sign-off
- 8. Turning UAT into regression
How to use it
- Everything in italics is guidance and should be deleted once you have replaced it. Square brackets mark a value to fill in.
- These four documents are designed to be used together: the strategy sets the rules, and the three plans execute them at each level.
- Where your program uses different level names, keep your names and map them in section 1 rather than renaming everything.
How it ties back to Studio
Each template includes an automation candidate table: a short scoring pass over the flows you have just listed, asking how often each runs, whether its outcome is deterministic, and whether you control its data. That table is the bridge between a strategy document and an actual suite — it is what turns "we should automate more" into a list of named flows in priority order.
The rest of the set
Four documents covering the test levels an S/4HANA program actually runs:
- SAP S/4HANA Test Strategy — the program-level document
- SAP TUT and FUT Test Plan — technical and functional unit testing
- SAP System Integration Test Plan — end-to-end across modules and interfaces
- SAP User Acceptance Test Plan — business sign-off