# Testing Category/ Testing Case Description

Scenario
1 Access management Tester can log into tool successfully

2 Access management Access management process is clear to tester

3 User Interface Tester check if user interface is easy to navigate to different

function/process?
4 Master Data availability Material master data, material structure
''Admin'' tab

5 Cost center

6 Process/function

7 Storage mapping

8 Detection point

9 Root cause analysis

10 Symptom (scrap reason)

11 Shift Pattern

12 Material price
13 Scrap Entry Case 1
''Scrap'' tab Case 2
Case 3
Case 4
14 Approval function Each scrap entry can be approved
15 XML file XML file can be generated sucessfully for all testing cases

XML file can be stored into local hard driver in XMLtoSAP

16 XMLtoSAP XML file can be read and RFC can be called successfully

Read XML file can be deleted from main table and stored to
2nd folder
17 SAP 4.6 TO can be automatically created from storage ID to HSM

FI, CCA postings can be generated properly

Expected result Tester Testing Result

Tester's access are added in tool and it works during UAT

Tester knows how to handle access (add/remove access

from tool)
User can easily find and move to needed processes

Material master data is available for testing case

When part number entered, PN description, type can be
automatically mapped

All valid cost centers are available, add/remove function is

workable
All valid Process/function are available, add/remove
function is workable
All valid storage are available, add/remove function is
workable
All valid Detection point are available, add/remove function
is workable
All valid Root cause are available, add/remove function is
workable
All valid Symptoms are available, add/remove function is
workable
All valid shift pattern are available, add/remove function is
workable
Material price is available for testing case

Approval function is workable for each testing case

XML file can be generated sucessfully

XML file can be stored into local hard driver in XMLtoSAP

XML file can be read and RFC can be called successfully

Read XML file can be deleted from main table and stored to
2nd folder
TO can be automatically created from storage ID to HSM

FI, CCA postings can be generated properly

Testing Status Testing Date Notes
Testing Scenario Testing purpose/ expected result Testing Case EMRR Type Material code

Case 1
Case 2
Case 3
Case 4
Case 5
Case 6
Quantity Material Type Product Cost Center Process/function Shift Patten Account Detection point
Scrapping Reason Detailed failure category Scrap decision Stock Type Source Type Destination Type
RMA (Return material Approval TO number MM doc # FI document CCA document
authority number) authority
?
?
?
?
?
?
?
?
?
?

do we need master data for approver?

Comment

Manual input
Material uploading function
Material uploading function
Manual input
Manual input
Manual input
Manual input
Manual input
Manual input
Manual input
OneScrap testing scope:
HHB OPs enter reason, detection point in tool
Get Approval from MF GL
Check Data and OneScrap entry
Perform Security check

XML file testing scope

XML file can be generated sucessfully and content is correct
XML file can be stored into local hard driver

XMLtoSAP testing scope

XML file can be read and RFC can be called successfully
Read XML file can be deleted from main table and stored to 2nd folder

SAP 4.6 testing scope

Auto TO create from Source storage type to HSM
Auto writing OFF will be perfomed
Open question from meeting:
1 What SAP environment will be used in UAT testing?
2 What's the frequency that new OneScrap tool sends data to SAP?
3 Material MD update system solution. If not available, what's the E2E process should be
4 Offer URL to tester before UAT
ess should be