Professional Documents
Culture Documents
Author: Creation Date: Last Updated: Document Ref: Version: December 31, 2003 April 29, 2014
Approvals:
Document Control
Change Record
4
Date
Author
Version
Change Reference
Reviewers
Name
Position
Distribution
Copy No.
Name
Location
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.
Document Control ii
Contents
Document Control ........................................................................................................ ii Overview ....................................................................................................................... 1 Century Date Compliance ...................................................................................... 1 System Test Sequences ................................................................................................. 2 01 - System Test Specifications < Opening Payable Periods > ...................................... 4 02 - System Test Specifications < Defining Banks > ...................................................... 5 03 - System Test Specifications < Defining Distribution Sets > ..................................... 7 04 - System Test Specifications < PO Invoice for Goods > ............................................ 8 05 - System Test Specifications < Prepayment (Supplier / Employee Advances) > .... 10 6 - System Test Specifications < Prepaid Expenses, Rent & Other Advances > .......... 13 7 - System Test Specifications < Employee Expense Reports > .................................. 17 8 - System Test Specifications < Debiting Suppliers Liability > ................................... 21 9 - System Test Specifications < Create Invoice Not Matched To PO > ...................... 23 10 - System Test Specifications < Supplier / Employee Refund > ............................... 26 11 - System Test Specifications < Entering Payments > ............................................. 28 12 - System Test Specifications < Cancel Unpaid Invoices > ....................................... 29 13 - System Test Specifications < Invoice Distribution Correction > .......................... 31 14 - System Test Specifications < Void Payment > ..................................................... 33 15 - System Test Specifications < Payables Month-End Processing > ........................ 34 16 - System Test Specifications < Payables Close Period > ......................................... 38 Defect Log ................................................................................................................... 39 Open And Closed Issues For This Deliverable ............................................................. 41 Open Issues .......................................................................................................... 41 Closed Issues ........................................................................................................ 41
Document Control iv
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 Payables 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 Security Testing
Century Date Compliance In the past, two-character date coding was an acceptable convention due to perceived costs associated with the additional disk and memory storage requirements of full four character date encoding. As the year 2000 approached, it became evident that a full four character-coding scheme was more appropriate. In the context of the Application Implementation Method (AIM), the convention Century Date or C/Date support rather than Year2000 or Y2K support is used. It is felt that coding for any future Century Date is now the modern business and technical convention. Every applications implementation team needs to consider the impact of the Century Date on their implementation project. As part of the implementation effort, all customizations, legacy data conversions, and custom interfaces need to be reviewed for Century Date compliance. Testing activities need to make sure that all interfaces and application extensions are coded for Century Date compliance. System test scripts should include steps for testing Century Date compliance.
Overview 1 of 41
Payables Test Opening Payable Periods Defining Banks Defining Distribution Sets PO Invoice for Goods Prepayment (Supplier / Employee Advances) Prepaid Expenses, Rent & Other Advances Employee Expense Reports Debiting Suppliers Liability Create Invoice Not Matched To PO Supplier / Employee Refund Entering Payments Cancel Unpaid Invoices Invoice Distribution Correction Void Payment Payables Month-End Processing Payables Close Period
Description Opening Payable Periods Defining Banks Defining Distribution Sets PO Invoice for Goods Prepayment (Supplier / Employee Advances) Prepaid Expenses, Rent & Other Advances Employee Expense Reports Debiting Suppliers Liability Create Invoice Not Matched To PO Supplier / Employee Refund Entering Payments Cancel Unpaid Invoices Invoice Distribution Correction Void Payment Payables Month-End Processing Payables Close Period
Tester
Test Status Active Active Active Active Active Active Active Active Active Active Active Active Active Active Active Active
Pass/Fail
Notes
Scenario Step
Event
Test Step
Role
Action or Path
Test Step Details - Enter in the Last Used: (the last payment document number you used on a payment document) - Enter in the Last Available: (the last payment document number available for a payment document) Save your Work
Expected Results
Actual Results
Status
Scenario Step
Event
Role Invoice
Test Step Details - (B) Invoices and Query on the Required Standard Invoice - Review the Standard Invoice - (B) Actions: Validate the Standard Invoice
Actual Results
Status
DR. Asset Acc 1000 - (B) Actions: Create Accounting DR. Asset Acc 300 CR. LC Account 300 CR. Supplier Lib. Acc 1000
Scenario Step
Event
Test Step
Role
Action or Path
Expected Results
Actual Results
Status
5.2
AP Invoice
- Query on the Required Batch - (B) Invoices and Query on the Required Prepayment
- Review the Prepayment - (B) Actions: Validate the Prepayment DR. Supplier Prepay. Acc 1000 - (B) Actions: Create Accounting CR. Supplier Lib. Acc 1000
5.3
AP Invoice
- Choose Single Request, then (B) Ok - Select Report Name from LOV: (Invoice Register) - Enter the mandatory report parameters and specific your report by using the optionally parameters - (B) Press Ok - (B) Press Submit - (M) View > Requests > (B) Find to review your request status and the view the output
Role AP Payment
Action or Path (N) Invoices > Entry > Invoice Batches > (B) Actions > Pay in full
Test Step Details - Enter Payment Information: - Payment Type: Quick - Payment Bank Account: Select Bank Account - Payment Document: Select Payment Doc.
Expected Results - The Payment saved - The GL Accounting Created and correct
Actual Results
Status
DR. Supplier Lib. Acc 1000 - Document Number: Last available document CR. Bank cash clearing Acc 1000 - Payment Date: - Supplier Name: Appears by default - Supplier Site: Appears by default. Save the Payment - (B) Actions: Choose Format - (B) Actions: Choose Create Accounting - (M) Tools: View Accounting
6 - System Test Specifications < Prepaid Expenses, Rent & Other Advances >
Scenario Step 6.1 Event Receiving Request for Prepayment to Supplier Test Step Enter Prepayment to Supplier Role AP Invoice Action or Path (N) Invoice> Entry> Invoice Batch Test Step Details - Enter Batch Name (All Rent Prepayments will be entered in one batch in the beginning of each year using Macro Upload Excel sheet, which will be designed by Oratech) - Enter Prepayment Header Information: - Type: Prepayment - Supplier Name: - Supplier Site: - Prepayment Date: - Prepayment Amount: - Description: Prepaid expenses for 12 Months from MMM-YY to MMM-YY - Enter Prepayment Distribution Information: - Type: Item - Line Amounts: - Line Account: Prepaid Expense Account. Save the Prepayment 6.2 Validate Prepayment & Create AP Invoice (N) Invoice> Entry> Invoice Batch Query on the Required Batch Query on the Required Prepayment Prepayment Saved Prepayment Status Expected Results Prepayment Saved Prepayment Status Never Validated Actual Results Status
6 - System Test Specifications < Prepaid Expenses, Rent & Other Advances > 13 of 41
Scenario Step
Event
Role
Action or Path
Test Step Details Review the Prepayment (B) Actions: Validate the Prepayment (B) Actions: Create Accounting Enter Payment Information: Payment Type: Quick Payment Bank Account:
Actual Results
Status
6.3
Payment to Supplier
AP Payment
(N) Invoice> Entry>Invoice Batch > (B) Actions > Pay in full
Payment Document: Payment Date: Supplier Name: Appears by default Supplier Site: Appears by default.
Save the Payment 6.4 Recurring Invoice Creation AP Supervisor (N) Invoice > Entry > Recurring (B) Choose Actions: Format (B) Choose Actions: Create Accounting Enter Supplier Name / Number: Enter Supplier Site: Payment Method Recurring Calendar: No of periods: Recurring Invoices Template saved with no error
6 - System Test Specifications < Prepaid Expenses, Rent & Other Advances > 14 of 41
Scenario Step
Event
Test Step
Role
Action or Path
Test Step Details First Period: Invoice Number: Alphanumeric (The invoice number generated will contain this number concatenated with the period name) Distribution Set: Rent Expenses Enter the invoice Currency & Payment Term: Enter the First Amount:
Expected Results
Actual Results
Status
Save your Work 6.5 Recurring Invoice Periodical Settlement AP Supervisor (N) Invoice > Entry > Recurring Inquiry on your Recurring Invoice Enter Number of Invoices to be created: (One) (B) Press Create Recurring Invoices Name your Batch (B) Ok No of remaining Periods in the Recurring Invoices Template decreases by one The Recurring Invoices created
Save your Work 6.6 Invoicing AP Invoice (N) Invoice> Entry> Invoice Batch Inquiry on the Batch Name (the one previously named during the recurring Invoice Creation) Review the Invoice Created The Invoice Created Correctly
Save the Invoice 6.7 Validate the Invoices AP Supervisor (N) Invoice> Entry> Invoice Batch Query on the Required Batch Query on the Required Invoices Payables Implementation File Ref: Document1 The Accounting The Invoices Validated
6 - System Test Specifications < Prepaid Expenses, Rent & Other Advances > 15 of 41
Scenario Step
Event
Test Step
Role
Action or Path
Test Step Details Review the Invoices (B) Actions: Validate the Invoices (B) Actions: Create Accounting If there is a number of invoices you can select more than invoice and (B) Press Actions, Choose Validate & Choose Create Accounting for the number of invoices at once Query on the Required Batch Query on the Required Invoice
Actual Results
Status
6.8
Payment Due
AP Payment
The Invoice is Fully Paid The Prepayment Invoice is Partially Applied The Accounting Created and correct
(B) Actions: Choose Apply/Unapply Prepayment Mark the Check Box then enter the amount you want to Match. Then (B) press Apply button (B) Actions: Create Accounting
6 - System Test Specifications < Prepaid Expenses, Rent & Other Advances > 16 of 41
Scenario Step
Event
Test Step
Role
Action or Path
Test Step Details - (B) Actions: Validate - (B) Actions: Create Accounting
Actual Results
Status
7.3
Payments to Employee
AP Payment
(N) Invoice > Entry > Invoice Batch (B) Actions > Pay in full
- Query on the Required Batch - Query on the Required Prepayment - (B) Actions: Pay in Full - Enter Payment Information: - Payment Type: Quick - Payment Bank Account: - Payment Document number: - Payment Date: - Supplier Name: Appears by default - Supplier Site: Appears by default. Save the Payment - (B) Actions: Format - (B) Actions: Create Accounting
7.4
AP Invoice
Enter the Employee Name or Number Enter the GL Account: Defaulted from the HR setup for employees, this account combination used to default the missing segments for your expense report template Cost Center
Scenario Step
Event
Test Step
Role
Action or Path
Test Step Details Enter the invoice Number, Date & Currency: Enter the invoice Description: Optionally enter the Prepayment Number to be applied to this invoice (limited to the exp. Report amount) Select the Expense Template: Travel Exp Select Meals: Enter Amount & Select Account Transportation: Enter Amount & Select Account Hotel: Enter Amount & Select Account
Expected Results
Actual Results
Status
Save your work 7.5 Employee Expense Reports create AP Supervisor (N) Others > Requests> Run 7.6 Validate the Invoice AP Supervisor (N) Invoice > Entry > Invoice Batches > (B) Actions Select Request Name: Expense Report Import Enter Report Parameters: Batch Name: Source Payables Expense Reports GL Date: (B) Ok, (B) Submit Query on the Required Batch Query on the Required Invoice Review the Invoice (B) Actions: Validate Invoice The Invoice Validated The Accounting Entry Created Expense report converted to invoice correctly
Scenario Step
Event
Test Step
Role
Action or Path
Test Step Details (B) Create Accounting (M) Tools > View Accounting Enter Payment Information: Payment Type: Quick Payment Bank Account: Payment Document: Payment Date: Supplier Name: Supplier Site: (B) Press Enter / Adjust Invoices Select the required Invoices to be paid Only the Remaining unpaid Amount Appears for this Employees invoices
Expected Results
Actual Results
Status
7.7
Payment Due
Payments to Employee
AP Payment
Save the Payment (B) Press Actions: Format (B) Press Actions: Create Accounting
Save the Invoice 8.2 Validate Credit Memo & Create Accounting AP Supervisor (N) Invoice > Entry > Invoice Batches 8.3 Payment Payments to AP Payment (N) Payments > Entry > Query on the Required Batch Query on the Required Credit Memo Review the Credit Memo (B) Actions: Validate the Credit Memo (B) Actions: Create Accounting (M) Tools > View Accounting Enter Payment Information: The Payment Amount will be the Net of the 8 - System Test Specifications < Debiting Suppliers Liability > 21 of 41 The Accounting Entry Created The Credit Memo Validated
Scenario Step
Event Due
Role
Expected Results Invoice and the Credit Memo The Payment saved The Accounting Entry Created
Actual Results
Status
Payment Document: Payment Date: Supplier Name: Supplier Site: (B) Press Enter / Adjust Invoices Select the required Standard Invoices with the Credit Memo to be paid (the Net Amount will be paid) Save the Payment (B) Actions: Format (B) Actions: Create Accounting (M) Tools > View Accounting
Scenario Step
Event
Role Invoice
Action or Path
Test Step Details - (B) Invoices and Query on the Required Standard Invoice - Review the Standard Invoice - (B) Actions: Validate the Standard Invoice, if there are any holds you have to release the hold before the revalidation. If the invoice amount is not equal to the total of invoice lines, the invoice will be hold until you both equal - (B) Holds to release the invoice hold, select from LOV the reason and save - (B) Actions: Validate Invoice, the invoice will be validated successfully - (B) Actions: Create Accounting
Actual Results
Status
9.3
AP Invoice
- Choose Single Request, then (B) Ok - Select Report Name from LOV: (Invoice Register) - Enter the mandatory report parameters and specific your report by using the optionally parameters - (B) Press Ok - (B) Press Submit - (M) View > Requests > (B) Find to review your request status and the view the output
9.4
Payment Due
AP
- The Invoice is Fully Paid - The Prepayment is Fully 9 - System Test Specifications < Create Invoice Not Matched To PO > 24 of 41
Scenario Step
Event
Role Payment
Action or Path
Test Step Details - (B) Invoices and Query on the Required Invoice - Review the Standard Invoice - (B) Actions: Choose Apply/Unapply Prepayment - Select the prepayment you want to use (in case there is more than one prepayment) - Choose the Check Box then enter the amount you want to apply to invoice - (B) Press Apply - (B) Actions: Create Accounting
Actual Results
Status
DR. Supplier Lib. Acc 1000 CR. Supplier Prepay. Acc 1000
Save the Invoice 10.2 Validate Credit Memo & Create Accounting AP Supervisor (N) Invoice > Entry > Invoice Batches Query on the Required Batch Query on the Required Credit Memo Review the Credit Memo (B) Actions: Validate the Credit Memo The Accounting Entry Created The Credit Memo Validated
Scenario Step
Event
Test Step
Role
Action or Path
Test Step Details (B) Actions: Create Accounting (M) Tools > View Accounting Query on the Required Batch Query on the Required Credit Memo
Expected Results
Actual Results
Status
10.3
Payment Due
AP Payment
(N) Invoice > Entry > Invoice Batches > (B) Action > Pay in Full
The Payment Amount is Defaulted The Supplier is Defaulted The Payment Saved The Accounting Entry Created
(B) Press Action: Choose Pay in Full Enter Payment Information: Payment Type: Refund Payment Bank Account: Payment Document Number: Payment Date: Save the refund (B) Actions: Create Accounting (M) Tools > View Accounting -
DR. Supplier Lib. Acc. 500 CR. Expense Acc 500 12.2 Print Invoice Register Standard Report AP Supervisor (N) Other > Requests > Run - Choose Single Request, then (B) Ok - Select Report Name from LOV: (Invoice Register) - Enter the mandatory report parameters and specific your report by using the optionally parameters - (B) Press Ok - (B) Press Submit - (M) View > Requests > (B) Find to review your request status and the view the output - The Invoice register printed
12.3
End of Period
Payables Transfer to
AP
- GL Accounting Entries
Scenario Step
Event (Month)
Role Supervisor
Test Step Details Select Request Name: (Payable Accounting Process) Enter the Request Parameters: Enter the Period From & To Period Select Document Class: (All) Submit Transfer to GL: Yes Submit Journal Import: Yes Validate Accounts: Yes Summarize Report: Yes (B) Ok to return to main form (B) Submit to run the request (N) View > Requests (review the request status)
Expected Results created for all invoices - All AP transactions for the period range specified posted successfully to the General ledger
Actual Results
Status
13.4
AP Invoice
Scenario Step
Event
Test Step
Role
Action or Path
Expected Results
Actual Results
Status
15.2
AP Supervisor
- Select Request (Payables Accounting Entries Report) - Enter the request parameters - GL Transfer Status (All Accounting Entries not transferred to GL) - (B) Ok > (B) Submit
- Reviews invoice distributions before posting. Flag any accounts needing correction.
15.3
AP Supervisor
Choose Single Request Select Request Name: (Payable Accounting Process / Payables Transfer to General Ledger) Enter the Request Parameters: Enter the Period From & To Period Select Document Class: (All) Submit Transfer to GL: Yes Submit Journal Import: Yes
- GL Accounting Entries created for all invoices and payments - All AP transactions for the period range specified posted successfully to the General ledger
Scenario Step
Event
Test Step
Role
Action or Path
Test Step Details Validate Accounts: Yes Summarize Report: Yes (B) Ok to return to main form (B) Submit to run the request (N) View > Requests (review the request status) Choose Single Request Select Request Name: (Payables Transfer to General Ledger) Enter the Request Parameters: (B) Submit Request Select Another Request Name: (Mass Additions Create) to transfer AP Assets lines from Oracle Payables to Oracle Assets Enter the Request Parameters: GL Date: Select Asset Book Name: (B) Submit Request Select Another Request Name: (Mass Additions Create Report) to review the result of Mass addition you previously submitted Enter the Request Parameters:
Expected Results
Actual Results
Status
15.4
AP Supervisor
Scenario Step
Event
Test Step
Role
Action or Path
Test Step Details Select Asset Book Name: (B) Submit Request (N) View > Requests (review the request status) Select the book you want to query lines in Select NEW in the queue field If you want to check some specific lines, enter other criteria to limit your search Invoice Number: Line Number: Supplier Name: Supplier Number: Source Batch: Creation Date: Invoice Date: (B) Press Find to your asset lines - Select Request (All Month End Reports) - Enter the request parameters (B) Ok > (B) Submit
Expected Results
Actual Results
Status
15.5
FA Supervisor
15.6 Submit Month-End Reports AP Supervisor Other > Requests > Run
- The Reports Printed and available for Reviewing in report set for errors
Scenario Step
Event
Test Step
Role
Action or Path
Test Step Details 123Posted Invoice Register Posted Payments Register Accounts Payable Trial Balance
Expected Results
Actual Results
Status
16.2
AP Manager
Other > Requests > Run (N) Setup > Calendar > Accounting > AP Accounting Periods
- Run The Unaccounted Transactions Sweep Program, use this program to redate accounting date of the open transactions to the first day of the next open period, that in case your business allow to change the transaction date (the opened transactions couldnt be transfer to GL because there is unrealizable hold)
16.3
AP Manager
- The previous period has a status of Closed - The New opened period has a status of "Open" - Payables Transactions entry and posting should be allowed to the open accounting period
Defect Log
Defect ID Number Test Step Reference Module Name Defect Description Resolution Re-Test By Re-Test Date Pass/Fail Status (open, closed, in process)
Defect Log 39 of 41
Defect ID Number
Module Name
Defect Description
Resolution
Re-Test By
Re-Test Date
Pass/Fail
Defect Log 40 of 41
ID
Issue
Resolution
Responsibility
Target Date
Impact Date
Closed Issues
ID
Issue
Resolution
Responsibility
Target Date
Impact Date