Académique Documents
Professionnel Documents
Culture Documents
Consultin
Transforming
Enterpri
g
ses
Title
Version
1.0
Author
Pawan Dubey
Reviewed By
Santosh Prakash
Date
18.09.2015
Last changed
on:
18-Sep-2015
Tested by:
Version:
Page:
Santosh Prakash
1.0
1 of 9
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.
Case
Description
Create a 541 document.
Create a 542 document with reference to 541 document
Display RGP Report
Input DataZ11
DATA OBJECT
VALUE/CODE
Material
A811090/A811221
Batch
0000637693/0000639
539
A00014
Vendor
DESCRIPTION
COMMENTS AND
NOTES
Special
Requirements
Unique or specific requirements that need to be YES
emphasized for configuration. One to two line
description of the requirement.
Check Reference Document Field
Okay? Yes No
Copying of data in return PO from latest
Okay? Yes No
scheduling Agreement
Last changed
on:
18-Sep-2015
Tested by:
Version:
Page:
Santosh Prakash
1.0
2 of 9
Expected Results
S Explanation
1 Availability of Reference document field in MIGO for Mvt Type 542
4 RGP report should run as per expectation
Reference
Related Case
Procedures
Organizational
involvement:
Context
S
1
2
3
Object
System
Client
Company
Value/Code
SAP ECC 6.0
500
Bharat Seats Ltd
Transactional
Steps
-Input
BUSINESS PROCESS STEPS
1
Last changed
on:
18-Sep-2015
Description/Comments/Notes
TRANS.
CODE
MIGO
Tested by:
Version:
Page:
Santosh Prakash
1.0
3 of 9
Transactional
Steps
-Output
No BUSINESS PROCESS STEPS
1
Last changed
on:
18-Sep-2015
4900504180/81/82
Doc Created
TRANS. OUTPUT
OK / ERROR
CODE
DATA / RESULT
ZRGP_R Report Displayed OK
Tested by:
Version:
Page:
Santosh Prakash
1.0
4 of 9
Last changed
on:
18-Sep-2015
Tested by:
Version:
Page:
Santosh Prakash
1.0
5 of 9
Last changed
on:
18-Sep-2015
Tested by:
Version:
Page:
Santosh Prakash
1.0
6 of 9
Last changed
on:
18-Sep-2015
Tested by:
Version:
Page:
Santosh Prakash
1.0
7 of 9
Actual
Results
S Explanation
1 All the transaction executed successfully.
2 Report Run completed successfully.
Test
Approval
Date
18.09.2015
By
Santosh
Prakash
Comments
RGP Process & Reporting
EVALUATION
Last changed
on:
18-Sep-2015
Tested by:
Version:
Page:
Santosh Prakash
1.0
8 of 9
Fit to
Company
Overall fit with company
requirements
Gaps (not identified within
Business Blueprint)
Missing Data
YES
NO
NO
Missing Functionality
Future Enhancements
NO
Yes, explain:-
Last changed
on:
18-Sep-2015
By
Comments
Tested by:
Version:
Page:
Santosh Prakash
1.0
9 of 9