SAP UAT Template

UAT stands for User Acceptance Test. UAT is an important activity in the  ASAP Methodology used for SAP Implementation. It is a very tense and intense activity as the key users and some experienced end users mostly raise their objections on the TO BE Design agreed upon in the Business Blueprint. It often witnesses unpleasant moments between the Implementation Team and the Client. The script for the scenario is prepared tested and then given to the key users to test along with their observations. Mostly the reason of conflict is the lack of complete knowledge of the Business process owners while explaining their business requirements and deep transactional knowledge of the Key users due to their experience in running the business. The following Template will help you to visualize and learn more about the Test scenarios used in the UAT.

 

Test Scenario No. TS-SD-0051 Sales Order (Complete Cycle)

 

Case Description
Create a Sales Order
Reference to customer PO
Issue Bonus for two order lines
Create two lines without bonus
Do the manual allocation for two lines and automatic allocation for rest of the lines
Create a delivery note
Revise quantities after delivery
Create Invoice

Setup Data
DATA OBJECT		VALUE/CODE	DESCRIPTION	COMMENTS AND NOTES
Material		102166, 101194
Sold Qty		50, 100
Bonus Qty		5, 10
Customer		11311

Special Requirements
Unique or specific requirements that need to be emphasized for configuration. One to two line description of the requirement. Reference can be made back to the Business Blueprint for further detail		Okay? Yes No
Check Credit limit for customer		Okay? Yes No
Check Stock Availability		Okay? Yes No
Batch determination based on first expiry first out		Okay? Yes No
		Okay? Yes No
		Okay? Yes No

Expected Results
S	Explanation
1	Financial and Controlling entries should be created by the system
2	Stock should be reduced
3
4

Reference
Related Case Procedures
Organizational involvement:		FI CO SD MM PP ____________ (specify)

Approval
Date	By	Comments

Configuration Section - “n” (To be filled by Project Team)

Context
S	Object		Value/Code	Description/Comments/Notes
1	System
2	Client
3	Company
4
5
6

Transactional Steps
	No	BUSINESS PROCESS STEPS		TRANS. CODE	OUTPUT DATA / RESULT	OK / ERROR
	0
	1
	2
	3
	4
	5
	6
	7
	99

Actual Results
S	Explanation
1
2
3
4

Test Approval
Date	By	Comments

E V A L U A T I O N

Fit to Company
Overall fit with company requirements		Low Medium High
Gaps (not identified within Business Blueprint)
· Missing Data		Yes, explain:
· Missing Documents or Reports		Yes, explain:
· Missing Functionality		Yes, explain:
· Missing Interface		Yes, explain:
· System Mods (screens, tables or data)		Yes, explain:
· Other		Yes, explain:
Future Enhancements		Yes, explain:

Approval
Date	By	Comments