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 Name Location

No.

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: 41164415.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.......................................................................................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 - <Scenario Number>...........................................................16

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

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

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

<Subject> Data Profile - <Scenario Number>

File Ref: 41164415.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: 41164415.doc (v. )
Company Confidential - For internal use only
 Doc Ref:

Accounts Receivable Test Sequences

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

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: 41164415.doc (v. )
Company Confidential - For internal use only
 Doc Ref:

Test Specification - Enter and Maintain Customer Records

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

10.1 Add a customer Customer profile saved without

profile. error.
Customers ->
Profile Class
10.2 Add several new System will automatically
customers with number the address and Bill_to
different profile site.
classes. Verify customer profile
Customers -> information defaults are
Standard correct.
10.3 View a customer Verify data entered in 10.1 is
Customers -> correct.
Summary
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
- Query up the for individual customer.
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: 41164415.doc (v. )
Company Confidential - For internal use only
 Doc Ref:

Test Specification - Enter and Process Receivables Transactions

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

20.1 Enter a Debit Memo. This debit memo should be

- Use "Manual - able to complete without any
Other" as Batch missing data (click on
Source "Complete" checkbox to
- Use "Debit Memo" complete a transaction).
for 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
that does not able to complete without any
associate to any missing data (click on
invoice "Complete" checkbox to
- Use "Manual - complete a transaction).
Other" 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
balances and detail. be the same as original
Transactions -> transaction amount since no
Transactions -> receipt has been applied.
(B)Balances
20.4 Enter transactions All invoices saved without
with transaction type error.

Data Profile - <Scenario Number>

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

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

"Invoice"
Transactions ->
Transactions ->

Data Profile - <Scenario Number>

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

Test Specification - Enter and Process Credit Memos

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

30.1 Enter Credit Memos This credit memo should

- Query up any one of complete 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 Items should be matched
Memos without error
- Query up one of the
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 balance.
credit 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: 41164415.doc (v. )
Company Confidential - For internal use only
 Doc Ref:

Test Specification - Enter and Process Adjustments

Scenari Test Role Action or Path Expected Results Actual Results Expected Actual Status
o Step Step Cycle Cycle
Time 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 The adjustment number is:
button ______
- 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 The adjustment status should
user as approver be changed to "Approved" if
- Enter the the approver’s approval limit is
adjustment number more than the adjustment
noted down above amount; otherwise the
and click Find button approver is not allowed to
- QuickPick on Status approve the adjustment and
field, select the adjustment status will stay
"Approved" and save the same.
Control ->
Adjustments ->
Approve

Data Profile - <Scenario Number>

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

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

Adjustments
40.4
40.5
40.6

Data Profile - <Scenario Number>

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

Test Specification - Enter and Process Receipts

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

50.1 - Enter a check Record saved without error.

receipt for one of the
invoices entered
above.
- Apply the full
receipt amount to
this invoice
Receipts ->
Batches
50.2 View invoice The invoice balance should be
balances 0.
Transactions ->
Transactions -> (B)
Balances
50.3 Reverse the receipt Reversal saved without error.
entered above
Receipts ->
Receipts -> (B)
Reverse
50.4 View invoice The invoice should show a
balances balance after reversal.
Transactions ->
Transactions -> (B)
Balances
50.5 - Enter a check The first run of Unapplied
receipt for the Receipt Register Report should
invoice entered show the receipt
above and leave this
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 ->

Data Profile - <Scenario Number>

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

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

Receipts Summary
-> (B)Application
50.7 - Enter a Misc receipt. Verify accounting entries
- Click on Distribution created as a result of this
button to enter miscellaneous receipt
distribution account transaction.
- Transmit to GL
Receipts ->
Batches -> (B)
Receipts

Data Profile - <Scenario Number>

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

Test Specification - Perform Receivables Inquiry

Scenari Test Role Action or Path Expected Results Actual Results Expected Actual Status
o Step Step Cycle Cycle
Time 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: 41164415.doc (v. )
Company Confidential - For internal use only
 Doc Ref:

Test Specification - Customer Call Processing

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

70.1 - Record a customer Customer call information

call regarding one of saved without error.
the 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
history up in View Customer Call
Collections -> History window.
Correspondence
70.3
70.4

Data Profile - <Scenario Number>

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

Test Specification - Receivables Print Statements and Dunning Letters

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

80.1 - Submit a statement The statement should contain

for the customer of all the invoices, debit memos,
the invoices entered credit memos, receipts and
above adjustment activity to your
- View Statement customer. This statement
Generation Program should also include unapplied
in Concurrent receipts which are associated
Request window 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 The overdue invoices for this
invoices, use the first customer should show up in
day of last month’s the dunning letter.
date as invoice 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: 41164415.doc (v. )
Company Confidential - For internal use only
 Doc Ref:

Test Specification - Receivables Month End Process - Run AR Reports

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

90.1 Run the following Verify data in reports is

reports before accurate.
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
following parameters: Batch 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
accounting period date for the closed period.
- Attempt Entry of an
Invoice to the Closed Next month will be available
Period for invoice entry in AR
- Open the next
accounting period
Control ->
Accounting ->
Open/Close Periods
90.4 Run Month-end Verify data in month end
reports reports is accurate
Control -> Request
-> Run

Data Profile - <Scenario Number>

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

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

Data Profile - <Scenario Number>

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

Data Profile - <Scenario Number>

Scenari Business Object Data Condition Business Rule Type Status
o Step

Data Profile - <Scenario Number>

File Ref: 41164415.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 Referenc closed, in
e process)

Oracle Receivables

Data Profile - <Scenario Number>

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

Open and Closed Issues

Open Issues

ID Issue Resolution Responsibility Target Impact Date

Date

Closed Issues

ID Issue Resolution Responsibility Target Impact Date

Date

Data Profile - <Scenario Number>

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