Purchasing Test Script

TE.040 System Test Script - Fixed Assets

Doc Ref: TE.040 System Test ScriptXXX 0, 0000

AIM

TE.040 System Test Script

Global Pharmacuitical IndustrialPayblesAuthor:Joseph FawzyCreation Date:Jul 27, 2015Last Updated:July 27, 20155Document Ref:1Version:DRAFT 1A

Note: Title, Subject, Last Updated Date, Reference Number, and Version are marked by a Word Bookmark so that they can be easily reproduced in the header and footer of documents. When you change any of these values, be careful not to accidentally delete the bookmark. You can make bookmarks visible by selecting Tools->OptionsView and checking the Bookmarks option in the Show region.Approvals:

Note: To add additional approval lines, press [Tab] from the last cell in the table above.

Copy Number_____

Note: You can delete any elements of this cover page that you do not need for your document. For example, Copy Number is only required if this is a controlled document and you need to track each copy that you distribute.

Document Control

Change Record

1DateAuthorVersionChange Reference

27-Jul-15Joseph FawzyDraft 1aNo Previous Document

Reviewers

NamePosition

Distribution

Copy No.NameLocation

1

2

3

4

Note: The copy numbers referenced above should be written into the Copy Number space on the cover of each distributed copy. If the document is not controlled, you can delete this table, the Note To Holders, and the Copy Number label from the cover page.

Note To Holders:

If you receive an electronic copy of this document and print it out, please write your name on the equivalent of the cover page, for document control purposes.

If you receive a hard copy of this document, please write your name on the front cover, for document control purposes.

Contents

iiDocument Control

Overview1Payable Test Sequences2Open Period3Enter Invoice Batch4Enter Standard Invoice / Currency5Enter Matched invoice / with varience6Enter Credit and debit memo invoice7Enter Prepayment Invoice8Enter Payment9Prepayment Appling10Run create account program11Run transfer journal to GL12Review Journal13Print cheques Report14Cancel invoice15Voided checks16Period close17Data Profile - 18Defect Log19Open And Closed Issues For This Deliverable20Open Issues20Closed Issues20

Note: To update the table of contents, put the cursor anywhere in the table and press [F9]. To change the number of levels displayed, select the menu option Insert>Index and Tables, make sure the Table of Contents tab is active, and change the Number of Levels to a new value.

Overview

This System Test Script documents the steps needed to test the integration of application extensions with the target application system with respect to the process.

System testing measures the quality of the entire application system, using system test sequences and scripts. You must create scripts for all business processes based on the Mapped Business Requirements (BR.030). You should be able to reuse the test scripts you created during Test Business Solutions (BR.080); however, the focus of business solution testing is confirming individual business processes, while business system testing focuses on confirming the collective application system. For more information, refer to Business Mapping Test Results (BR.080) as a basis for business system test specifications.

This system test will include the following types of testing:

Integrated Business Processes

Manual Procedures

Support Procedures

Security Testing

Initial System Documentation Inspection

Manual Data Inspection

Database Journaling

Converted Data Load Testing

Converted Data Inspection

Interface Testing (limited to processing data as input from another system, or creating data for use by another system)

Data/Transaction Reconciliation to the legacy system

Job Stream Testing (if there is a batch component)

Back-Up and Recovery Testing

Data Archival Testing

Lock Testing Simulating User Load (executing identical scenarios)

Batch Window Test (on full converted data volumes)

Payable Test Sequences

Note: The tables in this deliverable contain sample data that should be used as an example only. Remove all sample data before completing your final deliverable.

Sequence #DateTimePayable Test NameDescriptionTesterTest StatusPass/FailNotes

PA10Open PeriodOpen Period

PA20Standard InvoiceEnter Invoice Batch

PA30Standard InvoiceEnter Standard Invoice / Forgin

PA40Standard InvoiceEnter Matched invoice / With varience

PA50Debit /Credit InvoiceEnter Credit /Debit Memo Invoice

PA60Prepayment InvoiceEnter Prepayment Invoie

PA70PaymentEntre Payment / Pay in full

PA80ApplyingApply prepayment

PA90Create AccountRun Create Account

PA100Transfer to GLRun Transfer Journal to GL

PA110ReportReview Journal

PA120ReportPrint Check Report

PA130Cancel InvoiceCancel Invioce

PA140Cancel PaymentVoid Payment

PA150Period closeClose period

Open PeriodNote: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete

ScenarioStepTest StepRoleAction or PathExpected ResultsActual ResultsExpectedCycle TimeActualCycle TimeStatus

PA1010.1Open Payble periodPaybles ( Accounting (Control payable periodOpen Control payable periods form> 1 min.> 1 min.Active

PA1010.2Choose Peiod you need then select Open.

PA1010.3Save and close

Enter Invoice BatchScenarioStepTest StepRoleAction or PathExpected ResultsActual ResultsExpectedCycle TimeActualCycle TimeStatus

PA2020.1Invoice (Entry (Invoice BatchOpen Invoice Batch form> 1 min.> 1 min.Active

PA2020.2Enter Batch Name in English or arabic.

PA2020.3Select operating unit

PA2020.4Enter control count and control amount

PA2020.5For defaulting , Enter invoice currency , GL Date , Payment term

PA2020.6Press on Invoice ButomOpen Invoice form

Enter Standard Invoice / CurrencyNote: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete


PA3030.1From Invoice type Select Standard > 1 min.> 1 min.Active

PA3030.2Select supplier name from Trading partner or supplier number from supplier number

PA3030.3Select supplier site

PA3030.4Enter Invoice date , Invoice Number , invoice amount , GL Date

PA3030.5Select invoice currency

PA3030.6Select Term and Payment method

PA3030.7Press on Line Tab

PA3030.8Select Line Type (Item,Freight, Misc.,Tax and withholding tax

PA3030.9Enter line amount

PA3030.10Optional , Enter defult distribution account

PA3030.11From Invoice Withholding tax , Select withholding tax percentage

PA3030.12Press on distribution , to review and modify

PA3030.13From Action ( press validate

PA3030.14From Action ( Create account


Enter Matched invoice / with varienceNote: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete


PA4040.1From Invoice type Select Standard > 1 min.> 1 min.Active

PA4040.2Enter PO Number

PA4040.3Enter Invoice date , Invoice Number , invoice amount , GL Date , Term and Payment method

PA4040.4Press On Match Buttom ( Find

PA4040.5Select Inventory Items and enter Qty and price

PA4040.6Press match

PA4040.7Review distribution




Enter Credit and debit memo invoice Note: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete


PA5050.1From Invoice type Select Debit Memo or Credit Memo > 1 min.> 1 min.Active





PA5050.6Select Term and Payment method


PA5050.8Select Line Type (Item,Freight, Misc.,Tax and withholding tax



PA5050.11From Invoice Withholding tax , Select withholding tax percentage

FA5050.12Press on distribution , to review and modify

FA5050.13From Action ( press validate

FA5050.14From Action ( Create account

FA5050.15Save and close

Enter Prepayment InvoiceNote: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete


PA6060.1From Invoice type Select Prepayment > 1 min.> 1 min.Active





PA6060.6Select Term , Prepayment Type and Payment method


PA6060.8Select Line Type (Item,Tax and withholding tax)



PA6060.11Press on distribution , to review and modify



PA6060.14From Action ( Pay in full

PA6060.15Select Bank and Bank account then press Validate and crate account


Enter PaymentNote: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete


PA7070.1Enter PaymentPayable ( Payment ( Entry ( PaymentsPayment form open> 1 min.> 1 min.Active

PA7070.2Select supplier , supplier site ,payment date , payment amount , bank account , Payment process profile and Anticipated date

PA7070.3Press Enter/Adjust Invoice buttom

PA7070.4Select invoice and enter payment amount

PA7070.5Press Save

PA7070.6From Action ( Validate

PA7070.7From Action (Create Account

Prepayment Appling Note: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete


PA8080.1Apply prepayment to invoiceInvoices ( entry ( Invoices ( FindOpen Invoice form> 1 min.> 1 min.Active

PA8080.2From Action (Apply/Unapply prepaymentOpen apply/Unapply prepayment form

PA8080.3Check apply check box , then select prepayment ,enter amount apply and GL Date

Then Press apply/unapply buttom


Run create account programNote: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete


PA9090.1Run creat account programView ( Request ( submit new request ( Report Name ( Create account> 1 min.> 1 min.Active

PA9090.2Paramter (Select Leadger

Enter End date

Select Mode (Final, Draft)

Transfer to General Leadger

Post in General Leadger

PA9090.3Press submit

PA9090.4Review Report

Run transfer journal to GLNote: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete


PA100100.1Run creat account program

View ( Request ( submit new request ( Report Name ( Transfer Journal to GL> 1 min.> 1 min.Active

PA100100.2Paramter (Select Leadger

Select process categoryEnter end date

Post in General Leadger



PA100100.5

Review Journal

Note: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete


PA110110.1From Invoice/Payment formReport ( View Accounting > 1 min.> 1 min.Active

Print cheques ReportNote: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete


PA120120.1Run Print cheques Report

View ( Request ( submit new request ( Report Name ( GNP Print check Bank Name> 1 min.> 1 min.Active

PA120120.2Paramter (Check Number

Vendor

Supplier Name



Cancel invoiceNote: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete


FA130130.1Cancel invoicePayable ( Invoice ( Entry ( Invoice> 1 min.> 1 min.Active

FA130130.2From Action ( Cancel Invoice

Voided checksNote: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete


FA140140.1Void payment

Payable ( Payment ( Entry ( Payments> 1 min.> 1 min.Active

FA140140.2From Action ( void

FA140140.3Enter void date , Void GL Date

FA140140.4From Invoice action select (None,Hold and cancel) (OK

Period closeNote: A Test Specification defines test script execution. You can have several specification line items per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Test Step: the series of procedural steps that must be taken for the scenario step in order to properly perform the test3) Role: Step/Sequence owner4) Action or Path: descriptive of action to be taken by the primary resource or role during the test; either navigation, location or directive information5) Expected Results: anticipated outcomes or outputs described in measurable terms6) Actual Results: actual outcomes or outputs described in measurable terms7) Expected Cycle Time: anticipated elapsed time for processing the Step/Sequence8) Actual Cycle Time: actual elapsed time consumed during processing the Step/Sequence9) Status: Active, Pending Active, Pending Obsolete, or Obsolete


FA150150.1Open Payble period

Paybles ( Accounting (Control payable period> 1 min.> 1 min.Active

FA150150.2Choose Peiod you need then select Open

FA150150.3Save and close

Data Profile -

Note: A Data Profile describes the business conditions that are needed in order to test the application system. You can have several Data Profiles per process task. Follow these guidelines:1) Scenario Step: unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario2) Business Object: the name of a particular data element that must be present (like Customer or Master Demand Schedule)3) Data Condition: actual values or reference to some other document containing valuesor even a screen shot4) Business Rule: the policy or decision drivers that influence the process step5) Type: the entity type.6) Status: the entity state.

ScenarioStepBusinessObjectDataConditionBusinessRuleTypeStatus

Defect Log

Defect ID NumberTest Step ReferenceModule NameDefect DescriptionResolutionRe-Test ByRe-Test DatePass/FailStatus (open, closed, in process)

Open And Closed Issues For This Deliverable

Note: Add open issues that you identify while writing or reviewing this document to the open issues section. As you resolve issues, move them to the closed issues section and keep the issue ID the same. Include an explanation of the resolution.

When this deliverable is complete, any open issues should be transferred to the project- or process-level Risk and Issue Log (PJM.CR.050) and managed using a project level Risk and Issue Form (PJM.CR.050). In addition, the open items should remain in the open issues section of this deliverable, but flagged in the resolution column as being transferred.

Open Issues

IDIssueResolutionResponsibilityTarget DateImpact Date

Closed Issues

IDIssueResolutionResponsibilityTarget DateImpact Date

Enter Credit and debit memo invoice 3 If > 1 7 of 23 = - Sec1 22 iii 7 of 22

PayableFile Ref: Payables (v. DRAFT 1A)

Purchasing Test Script

Documents

Transcript of Purchasing Test Script