0x00000e6f6

8/8/2019 0x00000e6f6

1/21

AIM FF

TE.040 AR S YSTEM TEST SCRIPT RECEIVABLES

Author:

Creation Date: July 20, 1999

Last Updated: July 20, 1999

Document Ref:

Version: DRAFT 1A

Approvals:

8/8/2019 0x00000e6f6

2/21

TE.040ar System Test Script Receivables

Document Control

Change Record

4

Date Author Version Change Reference

20-Jul-99 Draft 1a No Previous Document

Reviewers

Name Position

Distribution

CopyNo.

Name Location

1 Library Master Project Library2 Project Manager34

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 documentcontrol purposes.

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

File Ref: 41164415.doc (v. DRAFT 1A )

Company Confidential - For internal use only

Data Profile -

Doc Ref: July 20, 1999

8/8/2019 0x00000e6f6

3/21

TE.040ar System Test Script Receivables

Contents

Document Control.......................................................................................ii

Century Date Compliance...........................................................................1

Accounts Receivable Test Sequences.........................................................2

Test Specification - Enter and Maintain Customer Records........................3

Test Specification - Enter and Process Receivables Transactions ..............4

Test Specification - Enter and Process Credit Memos.................................6

Test Specification - Enter and Process Adjustments...................................7

Test Specification - Enter and Process Receipts.........................................9

Test Specification - Perform Receivables Inquiry......................................11

Test Specification - Customer Call Processing..........................................12

Test Specification - Receivables Print Statements and Dunning Letters...13

Test Specification - Receivables Month End Process - Run AR Reports.....14

Data Profile - ...........................................................16

Defect Log.................................................................................................17

Open and Closed Issues............................................................................18

Open Issues.........................................................................................18Closed Issues.......................................................................................18

File Ref: 41164415.doc (v. DRAFT 1A )

Company Confidential - For internal use only

Data Profile -

Doc Ref: July 20, 1999

8/8/2019 0x00000e6f6

4/21

Century Date Compliance

In the past, two character date coding was an acceptable convention dueto perceived costs associated with the additional disk and memorystorage requirements of full four character date encoding. As the year2000 approached, it became evident that a full four character codingscheme was more appropriate.

In the context of the Application Implementation Method (AIM), theconvention 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 nowthe 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 theimplementation effort, all customizations, legacy data conversions, andcustom interfaces need to be reviewed for Century Date compliance.

File Ref: 41164415.doc (v. )Company Confidential - For internal use only

Data Profile -

Doc Ref:

8/8/2019 0x00000e6f6

5/21

Accounts Receivable Test Sequences

Sequence#

Date Time Accounts Receivable TestName

Description Tester Test Status Notes

10 Enter and Maintain CustomerRecords

20 Enter and ProcessReceivables Transactions

30 Enter and Process CreditMemos

40 Enter and Process

Adjustments50 Enter and Process Receipts60 Perform Receivables Inquiry70 Customer Call Processing80 Receivables Print Statements

and Dunning Letters90 Receivables Month End

Process - Run AR Reports100110120130140150160


Data Profile -

Doc Ref:

8/8/2019 0x00000e6f6

6/21

Test Specification - Enter and Maintain Customer Records

Scenario Step

TestStep

Role Action or Path Expected Results Actual Results ExpectedCycleTime

ActualCycleTime

Status

10.1 Add a customerprofile.Customers ->Profile Class

Customer profile saved withouterror.

10.2 Add several newcustomers withdifferent profile

classes.Customers ->Standard

System will automaticallynumber the address and Bill_tosite.

Verify customer profileinformation defaults arecorrect.

10.3 View a customerCustomers ->Summary

Verify data entered in 10.1 iscorrect.

10.4 Update a CustomerrecordCustomers ->Standard

Update saved without error.

10.5 Maintain IndividualCustomers Profile- Query up thecustomer entered in10.2Go to any one of theProfile Alternativeregion and changeany informationCustomers ->Standard

You are allowed to override thecustomer profile informationfor individual customer.


Data Profile -

Doc Ref:

8/8/2019 0x00000e6f6

7/21

Test Specification - Enter and Process Receivables Transactions

Scenario Step

TestStep


ActualCycleTime

Status

20.1 Enter a Debit Memo.- Use "Manual -Other" as BatchSource- Use "Debit Memo"for transaction classand type.- In the Lines window,QuickPick line name,and enter other linerelated information.- Make sure all theaccount codecombinations arethere.Transactions ->Transactions

This debit memo should beable to complete without anymissing data (click on"Complete" checkbox tocomplete a transaction).

20.2 Enter a Credit Memothat does notassociate to anyinvoice- Use "Manual -Other" as BatchSource- Use "Credit Memo"for transaction classand type.- In the Lines window,QuickPick line name,and enter other linerelated information(Use negativeamount).Enter a couple morecredit memosTransactions ->Transactions

This credit memo should beable to complete without anymissing data (click on"Complete" checkbox tocomplete a transaction).

20.3 View transactionsbalances and detail.Transactions ->Transactions ->(B)Balances

The transaction balance shouldbe the same as originaltransaction amount since noreceipt has been applied.

20.4 Enter transactionswith transaction type

All invoices saved withouterror.


Data Profile -

Doc Ref:

8/8/2019 0x00000e6f6

8/21

Scenario Step

TestStep


ActualCycleTime

Status

"Invoice"Transactions ->Transactions ->


Data Profile -

Doc Ref:

8/8/2019 0x00000e6f6

9/21

Test Specification - Enter and Process Credit Memos

Scenario Step

TestStep


ActualCycleTime

Status

30.1 Enter Credit Memos- Query up any one of the debit transactionsentered above asCredited Transaction- Enter a credit memoto fully credit thisdebit transaction.Transactions ->CreditTransactions

This credit memo shouldcomplete successfully.

30.2 Reapply CreditMemos- Query up one of thecredit memosentered above.- Match this credititem to a debit item.Transactions ->TransactionsSummary -> (B)Applications

Items should be matchedwithout error

30.3 View transactionbalances for bothcredit memo andcredited transaction.Repeat steps.Transactions ->TransactionsSummary -> (B)Open ->(B)Balance

All transactions should show abalance.

30.430.530.6


Data Profile -

Doc Ref:

8/8/2019 0x00000e6f6

10/21

Test Specification - Enter and Process Adjustments

Scenario Step

TestStep


ActualCycleTime

Status

40.1 - select invoice/debitmemo to be adjusted- Click on Adjustbutton- QuickPick anyactivity name. Enteradjustment amountless than theadjustment limit of the person who isdoing thisadjustment.Transactions ->TransactionSummary (B)Adjust

The adjustment should have"Approved" status

40.2 - Select invoice/debitmemo to be adjusted- Click on Adjustbutton- QuickPick anyactivity name. Enteradjustment amountmore than theadjustment limit of the person who isdoing thisadjustment.Transactions ->TransactionSummary (B)Adjust

The adjustment should have"Pending Approval" status

The adjustment number is: ______

40.3 - Login as anotheruser as approver- Enter theadjustment numbernoted down aboveand click Find button- QuickPick on Statusfield, select"Approved" and saveControl ->Adjustments ->Approve

The adjustment status shouldbe changed to "Approved" if the approvers approval limit ismore than the adjustmentamount; otherwise theapprover is not allowed toapprove the adjustment andthe adjustment status will staythe same.


Data Profile -

Doc Ref:

8/8/2019 0x00000e6f6

11/21

Scenario Step

TestStep


ActualCycleTime

Status

Adjustments40.440.540.6


Data Profile -

Doc Ref:

8/8/2019 0x00000e6f6

12/21

Test Specification - Enter and Process Receipts

Scenario Step

TestStep


ActualCycleTime

Status

50.1 - Enter a checkreceipt for one of theinvoices enteredabove.- Apply the fullreceipt amount tothis invoiceReceipts ->Batches

Record saved without error.

50.2 View invoicebalancesTransactions ->Transactions -> (B)Balances

The invoice balance should be0.

50.3 Reverse the receiptentered aboveReceipts ->Receipts -> (B)Reverse

Reversal saved without error.

50.4 View invoicebalancesTransactions ->Transactions -> (B)Balances

The invoice should show abalance after reversal.

50.5 - Enter a checkreceipt for theinvoice enteredabove and leave this

receipt unapplied.Enter the receiptamount same asinvoice amountRun UnappliedReceipt RegisterReportReceipts ->Batches -> (B)Receipts

The first run of UnappliedReceipt Register Report shouldshow the receipt

50.6 Apply the receiptagainst this invoiceRun UnappliedReceipt RegisterReportReceipts ->

The second run of the reportshould not show the receipt


Data Profile -

Doc Ref:

8/8/2019 0x00000e6f6

13/21

Scenario Step

TestStep


ActualCycleTime

Status

Receipts Summary-> (B)Application

50.7 - Enter a Misc receipt.- Click on Distributionbutton to enterdistribution account- Transmit to GLReceipts ->Batches -> (B)Receipts

Verify accounting entriescreated as a result of thismiscellaneous receipttransaction.


Data Profile -

Doc Ref:

8/8/2019 0x00000e6f6

14/21

Test Specification - Perform Receivables Inquiry

Scenario Step

TestStep


ActualCycleTime

Status

60.1 View CustomersCustomers ->Summary

60.2 View Invoice ImageTransactions ->TransactionsSummary

->(B)Open->(B)Balance60.3 View Receipts

BatchesReceipts ->Batches Summary

60.4 View Receipts byCustomer/BatchReceipts ->Receipts Summary

60.5 View TransactionHistoryCollections ->Account Details ->(B) Activity

60.6 View CustomerAccount DetailCollections ->Account Details

60.7 View CustomerAccount Summary

Collections ->Account Overview60.8 View Customer

Account Summary:AgingCollections ->Aging


Data Profile -

Doc Ref:

8/8/2019 0x00000e6f6

15/21

Test Specification - Customer Call Processing

Scenario Step

TestStep


ActualCycleTime

Status

70.1 - Record a customercall regarding one of the open invoicesentered above- Click Topic button torecord the topic- Click on Actionbutton to record thecall actionsCollections ->Customer Calls

Customer call informationsaved without error.

70.2 View customer callhistoryCollections ->Correspondence

The Customer Call should showup in View Customer CallHistory window.

70.370.4


Data Profile -

Doc Ref:

8/8/2019 0x00000e6f6

16/21

Test Specification - Receivables Print Statements and Dunning Letters

Scenario Step

TestStep


ActualCycleTime

Status

80.1 - Submit a statementfor the customer of the invoices enteredabove- View StatementGeneration Programin ConcurrentRequest window- View Statement on-line once theconcurrent programis complete- Print the statementPrint Documents-> Statements

The statement should containall the invoices, debit memos,credit memos, receipts andadjustment activity to yourcustomer. This statementshould also include unappliedreceipts which are associatedto a bill_to site.

80.2 - Enter a fewinvoices, use the firstday of last monthsdate as invoice dateand "30 Net" aspayment terms.- Print a dunningletter for thiscustomer, use "DaysOverdue" as dunningmethodPrint Documents-> Dunning Letters

The overdue invoices for thiscustomer should show up inthe dunning letter.

80.380.480.580.6


Data Profile -

Doc Ref:

8/8/2019 0x00000e6f6

17/21

Test Specification - Receivables Month End Process - Run AR Reports

Scenario Step

TestStep


ActualCycleTime

Status

90.1 Run the followingreports beforeposting:- Deposited CashReport- Other ReceiptsReport- Unposted JournalEntries ReportControl ->Requests -> Run

Verify data in reports isaccurate.

90.2 Posting to GL, use thefollowing parameters:- Post in Summary- Use Period End dateas GL Posted Date- Use first day of thecurrent period for GLStart Date, use thelast day of thecurrent period as GLEnd Date- Set "Yes" for JournalImportInterfaces ->General Ledger

Verify the Unposted JournalBatch created in GL.

90.3 - Close currentaccounting period

- Attempt Entry of anInvoice to the ClosedPeriod- Open the nextaccounting periodControl ->Accounting ->Open/Close Periods

Oracle AR will reject the GLdate for the closed period.

Next month will be availablefor invoice entry in AR

90.4 Run Month-endreportsControl -> Request-> Run

Verify data in month endreports is accurate


Data Profile -

Doc Ref:

8/8/2019 0x00000e6f6

18/21

Scenario Step

TestStep


ActualCycleTime

Status


Data Profile -

Doc Ref:

8/8/2019 0x00000e6f6

19/21

Data Profile -

Scenario Step

Business Object Data Condition Business Rule Type Status


Data Profile -

Doc Ref:

8/8/2019 0x00000e6f6

20/21

Defect Log

Defect IDNumber

Test StepReference

Module Name Defect Description Resolution Re-Test By Re-Test Date Status (open,closed, inprocess)

Oracle Receivables


Data Profile -

Doc Ref:

8/8/2019 0x00000e6f6

21/21

Open and Closed Issues

Open Issues

ID Issue Resolution Responsibility TargetDate

Impact Date

Closed Issues

ID Issue Resolution Responsibility TargetDate

Impact Date

Doc Ref: