Unit Test Plan

Cardinal Health MBT Project

Unit Test Plan (UTP)

UTP_OTC_PRICE_Cust_Cross_Reference_Records_Access

Document: UTP_OTC_PRICE_Cust_Cross_Reference_Records_Access Date:

10/09/2010
Owner: OTC
Subject: PRICE_Cust_Cross_Reference_Records_Access Page 1 of 7
 Unit Test Plan

Document History

Document Location
This is a snapshot of an on-line document. Paper copies are valid only on the day they are
printed. Refer to the author if you are in any doubt about the currency of this document.

Revision History

Revision Revision Summary of Changes Revised By

Number Date
10/09/2010 Venky Chad

Approvals
This document requires the following approvals:

Name Title Approved Date

Steve Johnson Process Team Lead

Distribution
This document has been distributed to:

Name Title
Kathy Jiskra Sub Team Lead

Document: UTP_OTC_PRICE_Cust_Cross_Reference_Records_Access Date:

10/09/2010
Owner: OTC
Subject: PRICE_Cust_Cross_Reference_Records_Access Page 2 of 7
 Unit Test Plan

Contents
..............................................................................................................................3
1. Unit Test Plan Overview:....................................................................................4
2. Test Plan:............................................................................................................4
3. Test Data: ...........................................................................................................5
4. Issues:.................................................................................................................6
5. Check List:.........................................................................................................6

Document: UTP_OTC_PRICE_Cust_Cross_Reference_Records_Access Date:

10/09/2010
Owner: OTC
Subject: PRICE_Cust_Cross_Reference_Records_Access Page 3 of 7
 Unit Test Plan

1. Unit Test Plan Overview:

The purpose of this UTP is to test the conversion for Partner or customer
cross reference The source data for the vendors will be supplied in an
access database called Vndr_Cust_Nbr. The conversion will be tested in the
QA client prior to execution in the production environment.. The cross
reference table is a true SAP table that will reside in ECC/Vistex. For the
conversion, the table will be populated by two types of partners: KU for
customer and LI for vendor. However for this particular CDD only vendor
(LI) customer records will be used. The conversion will be done by the
technical team and validated by Process Team/ Business SME’s.

2. Test Plan:

Test # Test Condition

PRICE_Cust_Cross_Reference_Records_Access

Step Step Description Expected Actual Results Pass / Fail Comments

Results
1 Extract Partner or Extract File is Extracted Pass
customer cross data created with 4records
from access database designated
data
2 Validate the load file File maps to Extract file Pass
for accuracy load tool contained valid
format. All data for all fields
values are
correct
3 Execute the loading of Load file Selected 4 Pass
the extract file from creates records to load
Excel file to MBT ECC Partner 0r to SAP ECC
client customer cross Vistex .
reference
4 Enter transaction Maintenance The screen is Pass
/IRM/GPXREF Partner
displayed with
Reference

Document: UTP_OTC_PRICE_Cust_Cross_Reference_Records_Access Date:

10/09/2010
Owner: OTC
Subject: PRICE_Cust_Cross_Reference_Records_Access Page 4 of 7
 Unit Test Plan

screen is the selection

displayed
criteria
5 Enter in the following if there are Empty screen is Pass
fields Partner type, already
displayed
Partner and records
Identification provided present for the
as follows and press partner type
ENTER. then those
records will
appear in the
ALV grid if not
It will display
only empty
ALV grid
6 Click on the Import All the records 4 records loaded Pass
Partners tab button, are loaded
and select the partners
XLS file
7 Validated the load file Data is The file Pass
for Accuracy. validated in contained valid
during the data.
process of
conversion.

3. Test Data:
NRAR
Ref. T KTONR IDPRV DATAB DATBI IDTYP PARVW KTONR_DET XPR
49001 10/10/20 10/10/20
1 LI 63 1 10 10 ID SP 10000130 X
49001 10/10/20 10/10/20
2 LI 63 2 10 10 ID SP 10000004 X
49001 10/10/20 10/10/20
3 LI 63 3 10 10 ID SP 10000017 X
49001 10/10/20 10/10/20
4 LI 63 4 10 10 ID SP 10000083 X

Document: UTP_OTC_PRICE_Cust_Cross_Reference_Records_Access Date:

10/09/2010
Owner: OTC
Subject: PRICE_Cust_Cross_Reference_Records_Access Page 5 of 7
 Unit Test Plan

4. Issues:
NONE

Test # Test Condition

PRICE_Cust_Cross_Reference_Records_Access

Issue # Test Step Issue Resolved (Y/N) Resolution Comments

5. Check List:

Check List:

1. Unit Test conditions cover all the input screen validations.

2. Unit Test conditions covers all the different business requirements documented in
Process Design Document or Functional specification.
3. Unit test conditions cover transformation rules and business validation documented
in mapping document for Interfaces and conversions.
4. Unit Test conditions cover negative business conditions

5. Unit Test conditions cover all variants of a transaction.

6. Unit Test Results match unit test conditions.

7. Issues are listed in issues section for not tested or failed unit test conditions.

Document: UTP_OTC_PRICE_Cust_Cross_Reference_Records_Access Date:

10/09/2010
Owner: OTC
Subject: PRICE_Cust_Cross_Reference_Records_Access Page 6 of 7
 Unit Test Plan

Document: UTP_OTC_PRICE_Cust_Cross_Reference_Records_Access Date:

10/09/2010
Owner: OTC
Subject: PRICE_Cust_Cross_Reference_Records_Access Page 7 of 7