AIM FF

TE.040AR SYSTEM TEST SCRIPT

RECEIVABLES

Author: Surya Maddiboina

Creation Date: January 26, 20182017
Last Updated: February 21, 2018
Document Ref: TE.040_AR
Version: DRAFT 1A

Approvals:

<Approver 1> Karthik

<Approver 2>
TE.040ar System Test Script Receivables Doc Ref: TE.040_AR
February 21, 2018

Document Control

Change Record
4

Date Author Version Change Reference

26-Jan-18 <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.

Error: Reference source not found Open and Closed Issues 18 of 52

File Ref: 440204287.doc (v. DRAFT 1A )
Company Confidential - For internal use only
TE.040ar System Test Script Receivables Doc Ref: TE.040_AR
February 21, 2018

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

Error: Reference source not found Open and Closed Issues 18 of 52

File Ref: 440204287.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.

Open and Closed Issues 18 of 52

File Ref: 440204287.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

Open and Closed Issues 18 of 52

File Ref: 440204287.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

Open and Closed Issues 18 of 52

File Ref: 440204287.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 ->

Open and Closed Issues 18 of 52

File Ref: 440204287.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

Open and Closed Issues 18 of 52

File Ref: 440204287.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

Open and Closed Issues 18 of 52

File Ref: 440204287.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

Open and Closed Issues 18 of 52

File Ref: 440204287.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

Open and Closed Issues 18 of 52

File Ref: 440204287.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

Open and Closed Issues 18 of 52

File Ref: 440204287.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

Open and Closed Issues 18 of 52

File Ref: 440204287.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

Open and Closed Issues 18 of 52

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

Data Profile - <Scenario Number>

Scenario Business Object Data Condition Business Rule Type Status
Step

Open and Closed Issues 18 of 52

File Ref: 440204287.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

Open and Closed Issues 18 of 52

File Ref: 440204287.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

Open and Closed Issues 18 of 52

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

Autoinvoice Setup For R12

1. Define Common Accounts Receivable Configuration

Common Accounts configuration pertains to the Accounting Flexfield setup. This is done in the General Ledger (GL) application. The assumption of this
case study is that you have already defined your accounting flexfield segments, and can create and complete manual transactions using the Transaction
Workbench.

Open and Closed Issues 18 of 52

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

2. Manage Receivables Descriptive Flexfields

Oracle Receivables uses the transaction flexfields to uniquely identify each transaction line that is imported though AutoInvoice.

AutoInvoice is capable of using information from four types of transaction flexfields:

 Line Transaction Flexfield

 Link-to Transaction Flexfield
 Reference Transaction Flexfield
 Invoice Transaction Flexfield

For this case study, you need to setup a Line Transaction Flexfield as shown below.

Click on the segments button to create the following rows. The values in the field Column are not shown
completely, they are INTERFACE_LINE_ATTRIBUTE1 and INTERFACE_LINE_ATTRIBUTE2 respectively.

Open and Closed Issues 18 of 52

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

3. Manage Receivables Profile Options

Open and Closed Issues 18 of 52

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

A. Security Profile
There Are Three Profile Options Which Govern Access To Data Partitioned By Organizations.

MO: Operating Unit

R11i Profile Option That Will Be Maintained For Those Products And Customers Not
Leveraging Multiple Organizations.

MO: Security Profile

The MO Security Profile Controls The List Of Operating Units That A Responsibility Can
Access. So You Would Assign The Security Profile That You Just Created To This Profile
Option. The Lowest Level You Can Set The Profile Option For Is The Responsibility Level.

MO: Default Operating Unit

This Allows You To Specify An Operating Unit That Will Be The Default When You Open
Different Subledger Application Pages. Because Users Can Access Multiple Operating Units,
You May Want To Set Up A Default Operating Unit Rather Than Forcing Users To Constantly
Have To Choose One During Data Entry. When We Talk About The User Preferences Later,
You Can Also Specify A Different Default Operating Unit Than The One Assigned To This
Profile Option.

B. AR: AutoInvoice Gather Statistics

This Profile Option Determines If The AutoInvoice Master Program Analyzes And Gathers
Information About The Interface Tables Each Time AutoInvoice Is Run. Analyzing Tables Ties
Up System Resources, But In Some Cases May Address AutoInvoice Performance Issues.

If The Value For This Profile Option Is Set To Yes, Or Is Null, AutoInvoice Analyzes The
Interface Tables And Gathers Statistics. If The Value Is Set To No, AutoInvoice Does Not
Analyze The Interface Tables.

This Profile Option Can Be Set By The System Administrator At The Site, Application,
Responsibility, And User Levels. The User Can Also Update This Profile Option.
C. AR: Default Exchange Rate Type
This Option Determines The Default Exchange Rate To Use When Converting Foreign
Currency Transactions To Your Functional Currency.
Valid Values Are:
 Corporate Exchange Rate - An Exchange Rate You Define To Standardize Rates. This
Rate Is Usually A Standard Market Rate Determined By Senior Financial Management For
Use Throughout The Organization.
 Spot Exchange Rate - An Exchange Rate To Perform A Conversion Based On The Rate
On A Specific Date.
 User Specified Rate - An Exchange Rate To Specify When Entering A Foreign Currency
Transaction.

Open and Closed Issues 18 of 52

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

D. AR: Maximum Lines Per AutoInvoice Worker

This Profile Option Lets You Set A Maximum Number Of Lines Per AutoInvoice Worker. The
Value For This Option Can Be Set By The System Administrator At The Site, Application
Responsibility, And User Levels, But Cannot Be Updated By The User. This Profile Option
Has No Default Value.

E. AR: Use Invoice Accounting For Credit Memos

This Profile Option Determines Whether To Assign Your Credit Memo To The Same Accounts
That Are Assigned To The Invoice You Are Crediting.

The Value For This Option Can Be Set By The System Administrator At The Site,
Application,Responsibility, And User Levels, But Cannot Be Updated By The User.
Note:

If You Are Interfacing Data From Project Accounting, You Need To Set This Profile To No At
The Application Level For Oracle Projects. This Setting Will Then Allow Data To Be Passed
Into RA_INTERFACE_DISTRIBUTIONS_ALL Table For Projects Invoices.

F. Sequential Numbering
Sequential Numbering Assigns Numbers To Documents That You Create In Oracle Financial
Products. For Example, When You Are In A Window That Creates Invoices, Each Invoice
Document Can Be Numbered Sequentially.

Sequential Numbering Provides A Method Of Checking Whether Documents Have Been

Posted Or Lost.
Not All Windows Within An Application Can Be Selected To Support Sequential Numbering.

Sequential Numbering Has The Following Profile Option Settings:

 Always Used - You May Not Enter A Document If No Sequence Exists For It.
 Not Used - You May Always Enter A Document.
 Partially Used - You Will Be Warned, But Not Prevented From Entering A Document,
When No Sequence Exists.

Only System Administrators Can Change This Profile Option. Users Can See This Profile
Option, But They Cannot Update It.

This Profile Option Is Visible And Updatable At The Site, Application, And Responsibility
Levels.

Open and Closed Issues 18 of 52

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

4. Manage Transaction Types

The data you insert into the interface table will be associated to a particular transaction type.
Create an invoice transaction type which will be used when we insert data into the Interface table.

Responsibility: Receivables Manager

Navigation: Setup > Transactions > Transaction Types

Note: If you also want to run a test case to import a Credit memo, create a Credit Memo transaction type as
shown below, otherwise you don't need to create a Credit Memo transaction type.

Open and Closed Issues 18 of 52

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

5. Manage AutoAccounting Rules

AutoAccounting enables you to create default accounts for revenue, receivable, freight, tax, unearned revenue, unbilled receivable, late charges, bills
receivables accounts, and AutoInvoice clearing (suspense) accounts.

In the following screen, the source for the third segment is 'Transaction Types'. When the default accounting is generated for the Receivable account, the
accounting flexfield will pull the third segment from the Receivables account defined for the transaction type. If we cross-reference this to the screenshot
from the previous task, the value for the third segment is 1210, coming from 01-000-1210-0000-000 defined for Receivables account.

Responsibility: Receivables Manager

Navigation: Setup > Transactions > AutoAccounting

Open and Closed Issues 18 of 52

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

During AutoInvoice, you are interfacing data with the intention of creating complete transactions automatically.
Hence, you are advised to complete the setup for AutoAccounting so that AutoInvoice can determine the GL
accounts to use for your interfaced transactions, and process them completely without errors and without the
need for manual intervention.

6. Manage AutoInvoice Line Ordering Rules

If you want the data in your interface table to be created in a particular sort order, define Line Ordering Rules.

The following screenshot shows a Line Ordering Rule, that references the same fields we used in the Line transaction flexfield defined in Task 2 above.

Responsibility: Receivables Manager

Navigation: Setup > Transactions > AutoInvoice > Line Ordering Rules

Open and Closed Issues 18 of 52

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

7. Manage AutoInvoice Grouping Rules

Grouping rules specify attributes that must be identical for lines to be created as one transaction. Grouping rules always include the mandatory attributes,
and to this is added optional attributes that you define in your grouping rule.

The following screenshot shows a Grouping Rule that uses the Line Ordering Rule defined in Task 6 above.

Responsibility: Receivables Manager

Navigation: Setup > Transactions > AutoInvoice > Grouping Rules

Open and Closed Issues 18 of 52

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

8. Manage Receivables Payment Terms

Payment terms let you define the due date to be calculated for transactions. When you interface data, it is mandatory to provide either a TERM_ID or a
TERM_NAME in the RA_INTERFACE_LINES_ALL table (depending on how you have set up your transaction batch source). Although there is a defaulting
mechanism for payment term when entering transactions manually in the form, this is defaulting is not available during AutoInvoice, because it would
significantly slow down the performance of the process.

The following screenshot shows a Payment term we will use in our interface data.

Responsibility: Receivables Manager

Navigation: Setup > Transactions > Payment Terms

9. Manage Transaction Sources

Batch sources define default information such as transaction type and automatic numbering. There are two types available: Manual and Imported.
AutoInvoice requires a batch of type Imported.

The following screenshot shows a Transaction source we will use to interface data via AutoInvoice. Highlighted below is the transaction type we created
earlier, here we are associating it to this Imported Batch Source.

Responsibility: Receivables Manager

Navigation: Setup > Transactions > Sources

Open and Closed Issues 18 of 52

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

Following screenshots show the sub-tab for the Transaction Sources form:

The AutoInvoice Options tab highlights the Grouping rule created earlier. The setup indicates this batch will
group data as specified in this grouping rule

Open and Closed Issues 18 of 52

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

The following screenshots show the rest of the sub-tabs of this form, including Customer, Accounting,
Salescredit and other information. You need to define whether the data you will interface provides the Value or
the ID so that AutoInvoice can validate the data.

Customer Information tab: .

Open and Closed Issues 18 of 52

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

Accounting Information tab:

Open and Closed Issues 18 of 52

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

Other Information tab:

Sales Credit Validation tab:

Open and Closed Issues 18 of 52

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

10. Manage Receipt Classes And Methods

To default a payment method to the transactions you interface via AutoInvoice, you need to define a Receipt Class and Method for your transaction to
use.
Responsibility: Receivables Manager
Navigation: Setup > Receipts > Receipt Classes

11. Manage Receivables Customer Profile Classes

Oracle Receivables provides a profile class DEFAULT.

If necessary, you can define different customer profile classes to categorize your customers. You can associate Customer Profile classes to customer
records you create later. By using a profile class you default certain attributes/fields into the customer records to make customer maintenance more
efficient.

The following screenshot defines a new customer profile class, to which we associate the Payment Term from Task 8 and the grouping rule from Task 7.

Responsibility: Receivables Manager

Navigation: Customers > Profile Classes

Open and Closed Issues 18 of 52

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

12. Create Customer

Create customer record to use for interface data, at this point we reference various setup data we created earlier.

The following screenshot shows the various sub-tabs at the ACCOUNT profile level.

On the Account Profile tab, we associate to this customer record the customer profile created in Task 11, the payment term from Task 8 and the Grouping
Rule from Task 7 created earlier.

Responsibility: Receivables Manager

Navigation: Customers > Customers

Open and Closed Issues 18 of 52

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

Payment Details tab: here we associate to this customer record the Receipt method created in Task 10.
We have defined the Receipt method at the ACCOUNT level profile. If this customer has only one site, or all the
Sites of this customer will use the same Receipt method, there is no need to set up Payment Details at the Site
Level.

Open and Closed Issues 18 of 52

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

However, if there will be multiple sites for this account, and each site that uses a Receipt method different from
that set at the ACCOUNT level, then you will need to set up the Payment Details at the SITE level as shown
below.

Open and Closed Issues 18 of 52

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

13. Manage Receivables System Options

The settings in System Options that impact AutoInvoice are in the Trans and Customers tab. The following screenshot shows recommended settings for
fields in the 'AutoInvoice' Section. Also highlighted is the Grouping rule we defined earlier.

Log file message level = 10 provides the most detailed debug messages, and is useful when you are debugging or troubleshooting.

Responsibility: Receivables Manager

Navigation: Setup > System > System Options

Open and Closed Issues 18 of 52

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

14. Manage Receivables Accounting Periods

Open or close periods in your accounting calendar to control the recording of accounting information for these periods. Since the objective of AutoInvoice
is to create new transactions, the goal is to have these transactions impact open GL periods.

Ensure that the GL_DATE value you provide in the next task is within an open period.

Responsibility: Receivables Manager

Navigation: Control > Accounting > Open/Close periods

Open and Closed Issues 18 of 52

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

15. Manage Remit-To Address

Define a Remit-To Address so that customers know where to send payment for their invoices.

Responsibility: Receivables Manager

Navigation: Setup > Print > Remit To Address > Create Remit-To Address

16. Define Shipping Parameters:

Navigation: Order Management --> Setup --> Shipping --> Shipping Parameters.

In General Tab.

Open and Closed Issues 18 of 52

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

In Pick Release Tab:

Open and Closed Issues 18 of 52

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

In Shipping Transaction Tab:

17. Define Transaction Type Line:

Navigation: Order Management --> Setup --> Transaction Type -->Define.

Open and Closed Issues 18 of 52

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

In Shipping Tab:

Open and Closed Issues 18 of 52

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

In Finance Tab:

Open and Closed Issues 18 of 52

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

Save your work.

18. Define Transaction Type Order:

Navigation: Order Management --> Setup --> Transaction Type --> Define

In Main Tab:

Open and Closed Issues 18 of 52

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

Click On Assign Line Flows:

Save your work.

19. Define Grants and Roles:

Open and Closed Issues 18 of 52

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

Navigation: Order Management --> Setup --> Shipping --> Grants and Role Definitions --> Grants.

20. Testing AutoInvoice: AutoInvoice Import Process

Once the data is inserted into the Interface table, we are ready to submit the AutoInvoice Import Process
Responsibility: Receivables Manager
Navigation: Interfaces > AutoInvoice

Open and Closed Issues 18 of 52

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

To Monitor The Progress Of The Process,

Navigation: View > Requests
Click On Find Button

Open and Closed Issues 18 of 52

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

21. Review Invoice Created By AutoInvoice

To Verify Whether AutoInvoice Created The Invoice Successfully, View The Invoice In The
Transaction Workbench.

Responsibility: Receivables Manager

Navigation: Transactions > Transactions

Then Run A Query Using View > Query By Example

Enter The Following Filters:
 Batch Source Name = 'TIP BATCH SOURCE'
 Reference Field =
 For The Invoice: Enter The Value You Provided For Interface_line_attribute1 = 'TIP
SAMPLE INVOICE 1'
 For The Credit Memo (If You Also Ran This Test): Enter The Value You Provided For
Interface_line_attribute1 = 'TIP SAMPLE CM 1' Or 'TIP SAMPLE CM 2'
 For The Invoice With Rules: Enter The Valud You Provided For
Interface_line_attribute1 = 'TIP RULE INVOICE 1'

Then execute the query.

Open and Closed Issues 18 of 52

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

Click On Line Items Button To See Invoice Lines.

Open and Closed Issues 18 of 52

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

a. CREATE A CUSTOMER
b. CREATE A ITEM
c. CREATE A PRICE LIST
d. CREATE A INVOICE SOURCE
e. CREATE A RECEIVABLES TRANSACTION TYPE
f. CREATE A ORDER TRANSACTION TYPE (Order Line)
g. CREATE A ORDER TRANSACTION TYPE (Order)
h. DEFINE THE DOCUMENT
i. ASSIGN DOCUMENT CATEGORIES
j. DOCUMENT ASSIGNMENT TO BE REFLECTED IN ORDER TYPE
k. DEFINE PICKING RULE

List of Setup Steps for OM

1.Define multiple organizations in Oracle

Inventory

2. Setup Multi-Org (Multiple Organization)

Access Control

3. Define key and descriptive flexfields

4. Define inventory organizations

(warehouses), parameters, subinventories,
and picking rules in Oracle Inventory

5. Define Profiles

6. Setting OM System Parameters

7. Define invoicing information

8. Define your sales representatives

9. Define Tax Features

Open and Closed Issues 18 of 52

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

10. Define Quickcodes

11. Define header and line processing flows

12. Define Document Sequences for Order

Numbering

13. Define Order Import Sources

14. Define the units of measure

15. Define item information

16. Define the items that you sell

17. Define the configurations that you sell

18. Define price lists

19. Define customer profile classes

20.Define information on your customers

21. Define item cross references

22. Define your sourcing rules

23. Define Order Management Transaction

Types

24. Set up Cost of Goods Sold Accounting

Open and Closed Issues 18 of 52

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

flexfield combination

25. Define Processing Constraints

26. Define Defaulting Rules

27.Define Credit Checking Rules

28. Define Automatic Holds

29. Define Attachments

30. Define Freight and Special Charge

Types

31. Define shipping parameters

Open and Closed Issues 18 of 52

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

Open and Closed Issues 18 of 52

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

Open and Closed Issues 18 of 52

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