TE040 Test Script AR

TE.040ar System Test Script Receivables

Doc Ref: TE.040ar System Test Script ReceivablesXXX 0, 0000

AIM FF

TE.040ar System Test Script Receivables

Author:

Creation Date:July 20, 1999Last Updated:July 20, 1999Document Ref:

Version: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

4DateAuthorVersionChange Reference

20-Jul-99Draft 1aNo Previous Document

Reviewers

NamePosition

Distribution

Copy No.NameLocation

1 Library MasterProject Library

2 Project Manager

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

iii

Document Control

Century Date Compliance1

Accounts Receivable Test Sequences2

Test Specification - Enter and Maintain Customer Records3

Test Specification - Enter and Process Receivables Transactions5

Test Specification - Enter and Process Credit Memos7

Test Specification - Enter and Process Adjustments8

Test Specification - Enter and Process Receipts10

Test Specification - Perform Receivables Inquiry12

Test Specification - Customer Call Processing13

Test Specification - Receivables Print Statements and Dunning Letters14

Test Specification - Receivables Month End Process - Run AR Reports15

Data Profile - 16

Defect Log17

Open and Closed Issues18

Open Issues18

Closed Issues18

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.

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.

Accounts Receivable Test Sequences

Note: Verify that the testing sequences are within the scope of the implementation as defined by the Project Management Plan [PJM.CR.010, initial complete], as produced in task PJM.CR.030.

Sequence #DateTimeAccounts Receivable Test NameDescriptionTesterTest StatusNotes

10Enter and Maintain Customer Records

20Enter and Process Receivables Transactions

30Enter and Process Credit Memos

40Enter and Process Adjustments

50Enter and Process Receipts

60Perform Receivables Inquiry

70Customer Call Processing

80Receivables Print Statements and Dunning Letters

90Receivables Month End Process - Run AR Reports

100

110

120

130

140

150

160

Test Specification - Enter and Maintain Customer Records

Note: A Test Specification defines test script execution. You can have several specification line items for each process task.

Follow these guidelines:1) Scenario Step: Give a unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario.2) Test Step: Enter the series of procedural steps that must be taken for the scenario step in order to properly perform the test.3) Role: Specify the Step/Sequence owner.4) Action or Path: Provide a description of action to be taken by the primary resource or role during the test; either navigation, location or directive information.5) Expected Results: List anticipated outcomes or outputs described in measurable terms.6) Actual Results: List actual outcomes or outputs described in measurable terms.7) Expected Cycle Time: Enter anticipated elapsed time for processing the Step/Sequence.8) Actual Cycle Time: Enter actual elapsed time consumed during processing the Step/Sequence.9) Status: Describe as Active, Pending Active, Pending Obsolete, or Obsolete.

Scenario StepTest StepRoleAction or PathExpected ResultsActual ResultsExpected Cycle TimeActual Cycle TimeStatus

10.1Add a customer profile.

Customers -> Profile ClassCustomer profile saved without error.

10.2Add several new customers with different profile classes.

Customers -> StandardSystem will automatically number the address and Bill_to site.

Verify customer profile information defaults are correct.

10.3View a customer

Customers -> SummaryVerify data entered in 10.1 is correct.

10.4Update a Customer record

Customers -> StandardUpdate saved without error.

10.5Maintain Individual Customers Profile

- Query up the customer entered in 10.2

Go to any one of the Profile Alternative region and change any information

Customers -> StandardYou are allowed to override the customer profile information for individual customer.

Test Specification - Enter and Process Receivables Transactions


20.1Enter a Debit Memo.

- Use "Manual - Other" as Batch Source

- Use "Debit Memo" 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 -> TransactionsThis debit memo should be able to complete without any missing data (click on "Complete" checkbox to complete a transaction).

20.2Enter a Credit Memo that does not associate to any invoice

- Use "Manual - 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 -> TransactionsThis credit memo should be able to complete without any missing data (click on "Complete" checkbox to complete a transaction).

20.3View transactions balances and detail.

Transactions -> Transactions -> (B)BalancesThe transaction balance should be the same as original transaction amount since no receipt has been applied.

20.4Enter transactions with transaction type "Invoice"

Transactions -> Transactions ->All invoices saved without error.

Test Specification - Enter and Process Credit Memos


30.1Enter Credit Memos

- Query up any one of the debit transactions entered above as Credited Transaction

- Enter a credit memo to fully credit this debit transaction.

Transactions -> Credit TransactionsThis credit memo should complete successfully.

30.2Reapply Credit Memos

- Query up one of the credit memos entered above.

- Match this credit item to a debit item.

Transactions -> Transactions Summary -> (B) ApplicationsItems should be matched without error

30.3View transaction balances for both credit memo and credited transaction. Repeat steps.

Transactions -> Transactions Summary -> (B) Open -> (B)BalanceAll transactions should show a balance.

30.4

30.5

30.6

Test Specification - Enter and Process Adjustments


40.1- select invoice/debit memo to be adjusted

- 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) AdjustThe adjustment should have "Approved" status

40.2- Select invoice/debit memo to be adjusted

- Click on Adjust 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) AdjustThe adjustment should have "Pending Approval" status

The adjustment number is: ______

40.3- Login as another user as approver

- Enter the adjustment number noted down above and click Find button

- QuickPick on Status field, select "Approved" and save

Control -> Adjustments -> Approve AdjustmentsThe adjustment status should be changed to "Approved" if the approvers approval limit is more than the adjustment amount; otherwise the approver is not allowed to approve the adjustment and the adjustment status will stay the same.

40.4

40.5

40.6

Test Specification - Enter and Process Receipts


50.1- Enter a check receipt for one of the invoices entered above.

- Apply the full receipt amount to this invoice

Receipts -> BatchesRecord saved without error.

50.2View invoice balances

Transactions -> Transactions -> (B) BalancesThe invoice balance should be 0.

50.3Reverse the receipt entered above

Receipts -> Receipts -> (B) ReverseReversal saved without error.

50.4View invoice balances

Transactions -> Transactions -> (B) BalancesThe invoice should show a balance after reversal.

50.5- Enter a check receipt for the invoice entered above and leave this receipt unapplied. Enter the receipt amount same as invoice amount

Run Unapplied Receipt Register Report

Receipts -> Batches -> (B) Receipts The first run of Unapplied Receipt Register Report should show the receipt

50.6Apply the receipt against this invoice

Run Unapplied Receipt Register Report

Receipts -> Receipts Summary -> (B)ApplicationThe second run of the report should not show the receipt

50.7- Enter a Misc receipt.

- Click on Distribution button to enter distribution account

- Transmit to GL

Receipts -> Batches -> (B) ReceiptsVerify accounting entries created as a result of this miscellaneous receipt transaction.

Test Specification - Perform Receivables Inquiry


60.1View Customers

Customers -> Summary

60.2View Invoice Image

Transactions -> Transactions Summary ->(B)Open->(B)Balance

60.3View Receipts Batches

Receipts -> Batches Summary

60.4View Receipts by Customer/Batch

Receipts -> Receipts Summary

60.5View Transaction History

Collections -> Account Details -> (B) Activity

60.6View Customer Account Detail

Collections -> Account Details

60.7View Customer Account Summary

Collections -> Account Overview

60.8View Customer Account Summary: Aging

Collections -> Aging

Test Specification - Customer Call Processing


70.1- Record a customer call regarding one of the open invoices entered above

- Click Topic button to record the topic

- Click on Action button to record the call actions

Collections -> Customer CallsCustomer call information saved without error.

70.2View customer call history

Collections -> CorrespondenceThe Customer Call should show up in View Customer Call History window.

70.3

70.4

Test Specification - Receivables Print Statements and Dunning Letters


80.1- Submit a statement for the customer of the invoices entered above

- View Statement Generation Program in Concurrent Request window

- View Statement on-line once the concurrent program is complete

- Print the statement

Print Documents -> StatementsThe statement should contain all the invoices, debit memos, credit memos, receipts and adjustment activity to your customer. This statement should also include unapplied receipts which are associated to a bill_to site.

80.2- Enter a few invoices, use the first day of last months 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 LettersThe overdue invoices for this customer should show up in the dunning letter.

80.3

80.4

80.5

80.6

Test Specification - Receivables Month End Process - Run AR Reports


90.1Run the following reports before posting:

- Deposited Cash Report

- Other Receipts Report

- Unposted Journal Entries Report

Control -> Requests -> RunVerify data in reports is accurate.

90.2Posting to GL, use the following parameters:

- 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 LedgerVerify the Unposted Journal Batch created in GL.

90.3- Close current accounting period

- Attempt Entry of an Invoice to the Closed Period

- Open the next accounting period

Control -> Accounting -> Open/Close PeriodsOracle AR will reject the GL date for the closed period.

Next month will be available for invoice entry in AR

90.4Run Month-end reports

Control -> Request -> RunVerify data in month end reports is accurate

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 for each process task.

Follow these guidelines:1) Scenario Step: Give a unique sequence number for each task as listed on the Business Requirements Scenario (RD.050) for this scenario.2) Business Object: Specify the name of a particular data element that must be present (like Customer or Master Demand Schedule).3) Data Condition: List actual values or reference to some other document containing valuesor even a screen shot.4) Business Rule: Identify the policy or decision drivers that influence the process step.5) Type: Specify the entity type.6) Status: Specify the entity state.

Scenario StepBusiness ObjectData ConditionBusiness RuleTypeStatus

Defect Log

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

Oracle Receivables

Open and Closed Issues

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.040) and managed using a project level Risk and Issue Form (PJM.CR.040). 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

Document Control 1 If > 1 16 of 19 = - Sec1 15 ii ii

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

Company Confidential - For internal use only

_993968923.doc