AIM FF

TE.040AR SYSTEM TEST SCRIPT

RECEIVABLES
<Company Long Name>
<Subject>

Author: <Author>
Creation Date: July 20, 1999
Last Updated: July 20, 1999
Document Ref: <Document Reference Number>
Version: DRAFT 1A

Approvals:

<Approver 1>

<Approver 2>
TE.040ar System Test Script Receivables Doc Ref: <Document Reference Number>
July 20, 1999

Document Control

Change Record
4

Date Author Version Change Reference

20-Jul-99 <Author> Draft 1a No Previous Document

Reviewers

Name Position

Distribution

Copy No. Name Location

1
Library Master Project Library
2 Project Manager
3
4

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.

<Subject> Data Profile - <Scenario Number>

File Ref: 431616059.doc (v. DRAFT 1A )
Company Confidential - For internal use only
TE.040ar System Test Script Receivables Doc Ref: <Document Reference Number>
July 20, 1999

Contents

Document Control.....................................................................................................................

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

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

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

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

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

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

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

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

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

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

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

Data Profile - <Scenario Number>..........................................................................................

Defect Log...................................................................................................................................

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

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

<Subject> Data Profile - <Scenario Number>

File Ref: 431616059.doc (v. DRAFT 1A )
Company Confidential - For internal use only
 Doc Ref:

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.

Data Profile - <Scenario Number>

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

Accounts Receivable Test Sequences

Sequence # Date Time Accounts Receivable Test Name Description Tester Test Status Notes

10 Enter and Maintain Customer

Records
20 Enter and Process Receivables
Transactions
30 Enter and Process Credit Memos
40 Enter and Process Adjustments
50 Enter and Process Receipts
60 Perform Receivables Inquiry
70 Customer Call Processing
80 Receivables Print Statements and
Dunning Letters
90 Receivables Month End Process -
Run AR Reports
100
110
120
130
140
150
160

Data Profile - <Scenario Number>

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

Test Specification - Enter and Maintain Customer Records

Scenario Test Step Role Action or Path Expected Results Actual Results Expected Actual Status
Step Cycle Time Cycle Time

10.1 Add a customer profile. Customer profile saved without

Customers -> Profile error.
Class
10.2 Add several new System will automatically number
customers with different the address and Bill_to site.
profile classes. Verify customer profile
Customers -> Standard information defaults are correct.
10.3 View a customer Verify data entered in 10.1 is
Customers -> Summary correct.
10.4 Update a Customer Update saved without error.
record
Customers -> Standard
10.5 Maintain Individual You are allowed to override the
Customer’s Profile customer profile information for
- Query up the customer individual customer.
entered in 10.2
Go to any one of the
Profile Alternative
region and change any
information
Customers -> Standard

Data Profile - <Scenario Number>

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

Test Specification - Enter and Process Receivables Transactions

Scenario Test Step Role Action or Path Expected Results Actual Results Expected Actual Status
Step Cycle Time Cycle Time

20.1 Enter a Debit Memo. This debit memo should be able to

- Use "Manual - Other" complete without any missing data
as Batch Source (click on "Complete" checkbox to
- Use "Debit Memo" for complete a transaction).
transaction class and
type.
- In the Lines window,
QuickPick line name,
and enter other line
related information.
- Make sure all the
account code
combinations are there.
Transactions ->
Transactions
20.2 Enter a Credit Memo This credit memo should be able to
that does not associate complete without any missing data
to any invoice (click on "Complete" checkbox to
- Use "Manual - Other" complete a transaction).
as Batch Source
- Use "Credit Memo" for
transaction class and
type.
- In the Lines window,
QuickPick line name,
and enter other line
related information (Use
negative amount).
Enter a couple more
credit memos
Transactions ->
Transactions
20.3 View transactions The transaction balance should be
balances and detail. the same as original transaction
Transactions -> amount since no receipt has been
Transactions -> applied.
(B)Balances
20.4 Enter transactions with All invoices saved without error.
transaction type
"Invoice"
Transactions ->
Transactions ->

Data Profile - <Scenario Number>

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

Test Specification - Enter and Process Credit Memos

Scenario Test Step Role Action or Path Expected Results Actual Results Expected Actual Status
Step Cycle Time Cycle Time

30.1 Enter Credit Memos This credit memo should complete

- Query up any one of successfully.
the debit transactions
entered above as
Credited Transaction
- Enter a credit memo to
fully credit this debit
transaction.
Transactions -> Credit
Transactions
30.2 Reapply Credit Memos Items should be matched without
- Query up one of the error
credit memos entered
above.
- Match this credit item
to a debit item.
Transactions ->
Transactions Summary
-> (B) Applications
30.3 View transaction All transactions should show a
balances for both credit balance.
memo and credited
transaction. Repeat
steps.
Transactions ->
Transactions Summary
-> (B) Open ->
(B)Balance
30.4
30.5
30.6

Data Profile - <Scenario Number>

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

Test Specification - Enter and Process Adjustments

Scenario Test Step Role Action or Path Expected Results Actual Results Expected Actual Status
Step Cycle Time Cycle Time

40.1 - select invoice/debit The adjustment should have

memo to be adjusted "Approved" status
- Click on Adjust button
- QuickPick any activity
name. Enter adjustment
amount less than the
adjustment limit of the
person who is doing this
adjustment.
Transactions ->
Transaction Summary
(B) Adjust
40.2 - Select invoice/debit The adjustment should have
memo to be adjusted "Pending Approval" status
- Click on Adjust button The adjustment number is: ______
- QuickPick any activity
name. Enter adjustment
amount more than the
adjustment limit of the
person who is doing this
adjustment.
Transactions ->
Transaction Summary
(B) Adjust
40.3 - Login as another user The adjustment status should be
as approver changed to "Approved" if the
- Enter the adjustment approver’s approval limit is more
number noted down than the adjustment amount;
above and click Find otherwise the approver is not
button allowed to approve the adjustment
- QuickPick on Status and the adjustment status will stay
field, select "Approved" the same.
and save
Control -> Adjustments
-> Approve
Adjustments
40.4
40.5
40.6

Data Profile - <Scenario Number>

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

Test Specification - Enter and Process Receipts

Scenario Test Step Role Action or Path Expected Results Actual Results Expected Actual Status
Step Cycle Time Cycle Time

50.1 - Enter a check receipt Record saved without error.

for one of the invoices
entered above.
- Apply the full receipt
amount to this invoice
Receipts -> Batches
50.2 View invoice balances The invoice balance should be 0.
Transactions ->
Transactions -> (B)
Balances
50.3 Reverse the receipt Reversal saved without error.
entered above
Receipts -> Receipts ->
(B) Reverse
50.4 View invoice balances The invoice should show a balance
Transactions -> after reversal.
Transactions -> (B)
Balances
50.5 - Enter a check receipt The first run of Unapplied Receipt
for the invoice entered Register Report should show the
above and leave this receipt
receipt unapplied. Enter
the receipt amount same
as invoice amount
Run Unapplied Receipt
Register Report
Receipts -> Batches ->
(B) Receipts
50.6 Apply the receipt The second run of the report
against this invoice should not show the receipt
Run Unapplied Receipt
Register Report
Receipts -> Receipts
Summary ->
(B)Application
50.7 - Enter a Misc receipt. Verify accounting entries created
- Click on Distribution as a result of this miscellaneous
button to enter receipt transaction.
distribution account
- Transmit to GL
Receipts -> Batches ->
(B) Receipts

Data Profile - <Scenario Number>

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

Test Specification - Perform Receivables Inquiry

Scenario Test Step Role Action or Path Expected Results Actual Results Expected Actual Status
Step Cycle Time Cycle Time

60.1 View Customers

Customers -> Summary
60.2 View Invoice Image
Transactions ->
Transactions Summary
->(B)Open->(B)Balance
60.3 View Receipts Batches
Receipts -> Batches
Summary
60.4 View Receipts by
Customer/Batch
Receipts -> Receipts
Summary
60.5 View Transaction
History
Collections -> Account
Details -> (B) Activity
60.6 View Customer Account
Detail
Collections -> Account
Details
60.7 View Customer Account
Summary
Collections -> Account
Overview
60.8 View Customer Account
Summary: Aging
Collections -> Aging

Data Profile - <Scenario Number>

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

Test Specification - Customer Call Processing

Scenario Test Step Role Action or Path Expected Results Actual Results Expected Actual Status
Step Cycle Time Cycle Time

70.1 - Record a customer call Customer call information saved

regarding one of the without error.
open invoices entered
above
- Click Topic button to
record the topic
- Click on Action button
to record the call actions
Collections ->
Customer Calls
70.2 View customer call The Customer Call should show up
history in View Customer Call History
Collections -> window.
Correspondence
70.3
70.4

Data Profile - <Scenario Number>

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

Test Specification - Receivables Print Statements and Dunning Letters

Scenario Test Step Role Action or Path Expected Results Actual Results Expected Actual Status
Step Cycle Time Cycle Time

80.1 - Submit a statement for The statement should contain all

the customer of the the invoices, debit memos, credit
invoices entered above memos, receipts and adjustment
- View Statement activity to your customer. This
Generation Program in statement should also include
Concurrent Request unapplied receipts which are
window associated to a bill_to site.
- View Statement on-
line once the concurrent
program is complete
- Print the statement
Print Documents ->
Statements
80.2 - Enter a few invoices, The overdue invoices for this
use the first day of last customer should show up in the
month’s date as invoice dunning letter.
date and "30 Net" as
payment terms.
- Print a dunning letter
for this customer, use
"Days Overdue" as
dunning method
Print Documents ->
Dunning Letters
80.3
80.4
80.5
80.6

Data Profile - <Scenario Number>

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

Test Specification - Receivables Month End Process - Run AR Reports

Scenario Test Step Role Action or Path Expected Results Actual Results Expected Actual Status
Step Cycle Time Cycle Time

90.1 Run the following Verify data in reports is accurate.

reports before posting:
- Deposited Cash Report
- Other Receipts Report
- Unposted Journal
Entries Report
Control -> Requests ->
Run
90.2 Posting to GL, use the Verify the Unposted Journal Batch
following parameters: created in GL.
- Post in Summary
- Use Period End date as
GL Posted Date
- Use first day of the
current period for GL
Start Date, use the last
day of the current
period as GL End Date
- Set "Yes" for Journal
Import
Interfaces -> General
Ledger
90.3 - Close current Oracle AR will reject the GL date
accounting period for the closed period.
- Attempt Entry of an
Invoice to the Closed Next month will be available for
Period invoice entry in AR
- Open the next
accounting period
Control -> Accounting
-> Open/Close Periods
90.4 Run Month-end reports Verify data in month end reports is
Control -> Request -> accurate
Run

Data Profile - <Scenario Number>

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

Data Profile - <Scenario Number>

Scenario Business Object Data Condition Business Rule Type Status
Step

Data Profile - <Scenario Number>

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

Defect Log

Defect ID Test Step Module Name Defect Description Resolution Re-Test By Re-Test Date Status (open,
Number Reference closed, in
process)

Oracle Receivables

Data Profile - <Scenario Number>

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

Open and Closed Issues

Open Issues

ID Issue Resolution Responsibility Target Date Impact Date

Closed Issues

ID Issue Resolution Responsibility Target Date Impact Date

Data Profile - <Scenario Number>

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