• No results found

Oracle Receivables User Guide

N/A
N/A
Protected

Academic year: 2021

Share "Oracle Receivables User Guide"

Copied!
10
0
0

Loading.... (view fulltext now)

Full text

(1)

Oracle

r

Receivables

User Guide

RELEASE 11i VOLUME 1

(2)

Oracler Receivables User Guide Release 11i

The part number for this book is A81019–03. To reorder this book, use set part number A80838–03

Copyright E 1988, 2003, Oracle Corporation. All rights reserved.

Primary Authors: Charles Ahern, Stephen R. Damiani, Melanie Heisler, Robert MacIsaac, Essan Ni, Kristin Penaskovic

The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse

engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. Program Documentation is licensed for use solely to support the deployment of the Programs and not for any other purpose.

The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error–free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose.

If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS

Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are ”commercial computer software” or ”commercial technical data” pursuant to the applicable Federal Acquisition Regulation and agency–specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documenta-tion and technical data, shall be subject to the licensing restricdocumenta-tions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227–19, Commercial Computer Software – Restricted Rights (June, 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.

The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be licensee’s responsibility to take all appropriate fail–safe, back up, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or the content provided on, third party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third–party products; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

(3)

iii Contents

Contents

VOLUME 1Volume 1 . . . i

Preface . . . xxiii

Chapter 1 Overview of Oracle Receivables . . . 1 – 1

Receivables Workbenches . . . 1 – 2 Receipts Workbench . . . 1 – 6 Transactions Workbench . . . 1 – 11 Collections Workbench. . . 1 – 17 Bills Receivable Workbench. . . 1 – 21

Chapter 2 Setting Up . . . 2 – 1

(4)

The Default Account Generator Process for

(5)
(6)

Chapter 3 Customers . . . 3 – 1

Customer Overview. . . 3 – 2 Data Quality Management Overview . . . 3 – 6 Setting Up DQM . . . 3 – 6 Setting Up Word Replacement Lists for Fuzzy Searches . . . 3 – 9 Searching Before Entering Parties or Customer Accounts . . . 3 – 10

Searching for Parties and Customer Accounts with

the Search Criteria Window . . . 3 – 10 Searching for Parties and Customer Accounts with

the Find/Enter Customers Window . . . 3 – 16 Find a Customer Account Using Alternate Names . . . 3 – 26 Entering Parties and Customer Accounts. . . 3 – 27 Customer Accounts Field Reference. . . 3 – 33 Checking for and Resolving Duplicates. . . 3 – 37 Assigning Banks to Customer Accounts . . . 3 – 41 Assigning Payment Methods to Customer Accounts . . . 3 – 43 Entering Marketing Information. . . 3 – 45 1099 Eligibility for Customers . . . 3 – 46 Entering Addresses for Customer Accounts. . . 3 – 48 Addresses Field Reference . . . 3 – 53 Characteristics Field Reference . . . 3 – 55 Assigning a Business Purpose to a Customer Address . . . 3 – 56 Defining Customer Account Drawee Sites . . . 3 – 61 Business Purposes Field Reference. . . 3 – 64 Entering Contacts . . . 3 – 68 Entering Customer Account Contact Roles. . . 3 – 70 Contacts and Roles Field Reference . . . 3 – 71 Entering Contact Points . . . 3 – 73 Defining Party Relationships. . . 3 – 76 Using Party Paying Relationships . . . 3 – 78 Creating Customer Account Relationships . . . 3 – 84 Defining Customer Profile Classes . . . 3 – 87

Assigning Profile Classes to Customers, Accounts, or

Addresses . . . 3 – 93 Updating a Customer Profile Class . . . 3 – 95 Customer Profile Classes Field Reference . . . 3 – 96 Flexible Addresses . . . 3 – 100

(7)

vii Contents Address Validation. . . 3 – 123

Sales Tax Location Flexfield Structure . . . 3 – 124 Address Validation Level. . . 3 – 125 Defining Flexible Address Validation . . . 3 – 127 Merging Customers . . . 3 – 133 Merging Sites for the Same Customer . . . 3 – 137 Merging Different Customers . . . 3 – 140 Submitting the Merge Process . . . 3 – 145 Customer Merge Execution Report . . . 3 – 147 Reviewing Merged Customers . . . 3 – 149 Customer Interface. . . 3 – 150 Preparing Receivables. . . 3 – 153 Interface Data Required to Run Customer Interface . . . 3 – 155 System Tables Updated by Customer Interface . . . 3 – 160 A Sample Customer Import. . . 3 – 161 Creating Unique Customer References . . . 3 – 165 Importing Customers Using Customer Interface. . . 3 – 167 Customer Interface Transfer Report . . . 3 – 170 Oracle Exchange Customer Import Request Set . . . 3 – 173

Chapter 4 Credit Management . . . 4 – 1

(8)

Retrieving a Case Folder . . . 4 – 39 Entering Data into a Case Folder . . . 4 – 40 Manually Creating a New Case Folder . . . 4 – 40 Analyzing Credit Data. . . 4 – 42 Using the Case Folder. . . 4 – 43 Calculating a Credit Score . . . 4 – 43 Adding Analysis Notes to the Case Folder . . . 4 – 44 Viewing Case Folder Attachments . . . 4 – 44 Refreshing Case Folder Data . . . 4 – 45 Viewing the Credit Summary . . . 4 – 45 Making a Recommendation . . . 4 – 47 Implementing the Recommendation . . . 4 – 48 Reviewing Credit Management Performance . . . 4 – 49 Periodic Credit Review Program . . . 4 – 51 Credit Management Application Workflow. . . 4 – 53 Setting Up the Credit Management Application Workflow . 4 – 54 Credit Management Application Workflow

Main Process Activities . . . 4 – 55

Index

VOLUME 2Volume 2 . . . i

Chapter 5 Transactions . . . 5 – 1

(9)

ix Contents Revenue Accounting . . . 5 – 43 Event–Based Revenue Management . . . 5 – 50

Evaluating Invoices for Event–Based

Revenue Management. . . 5 – 52 Applying Receipts and Event–Based Revenue Management 5 – 56 Monitoring Contract Contingencies with

(10)

Creating On–Account Credits . . . 5 – 135 Applying On–Account Credits . . . 5 – 137 Updating Credit Memos and On–Account Credits . . . 5 – 140 Accounting for Credit Memos . . . 5 – 142 Credit Memo Request Workflow . . . 5 – 175 Customizing the Credit Memo Request Process . . . 5 – 176 The Credit Memo Request Workflow Item Type . . . 5 – 178 Summary of the Credit Memo Request Process. . . 5 – 182 Credit Memo Request Process Activities. . . 5 – 184 Summary of the Collector Approval Subprocess . . . 5 – 190 Collector Approval Subprocess Activities. . . 5 – 192 Summary of the Primary Approval Subprocess . . . 5 – 200 Primary Approval Subprocess Activities . . . 5 – 202 Summary of the HR Management Approval Subprocess . . . 5 – 209 HR Management Approval Subprocess Activities. . . 5 – 211 Summary of the Receivables Approval Subprocess . . . 5 – 219 Receivables Approval Subprocess Activities . . . 5 – 221 Summary of the Credit Memo Creation Subprocess. . . 5 – 227 Credit Memo Creation Subprocess Activities . . . 5 – 229 Notifications . . . 5 – 232 Setting Up Credit Memo Request Workflow . . . 5 – 233 Initiating the Credit Memo Request Process . . . 5 – 237 Credit Cards . . . 5 – 238 Credit Card Validation and Integration . . . 5 – 241 Setting Up Receivables for Credit Card Transactions and

Payments . . . 5 – 245 Processing Credit Card Transactions . . . 5 – 248 Credit Card Refunds. . . 5 – 255 Viewing Credit Card Refund Activity on

the Customer Account . . . 5 – 260 Correcting Credit Card Refund Errors. . . 5 – 261 Reversing Receipts with Credit Card Refunds . . . 5 – 262 Accounting for Exchange Rate Gains and Losses When

References

Related documents

An analysis of the economic contribution of the software industry examined the effect of software activity on the Lebanese economy by measuring it in terms of output and value

As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on

As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions

As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions

We tested a hypothesis that both individual-level risk factors (partner number, anal sex, condom use) and local-network features (concurrency and assortative mixing by race) combine

As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the

Actual application in a curl to install the container applications using docker client will download the good time getting a server that we deploy our changes are running.. Isolate

For more information on all aspects of student finance relating to Newcastle University: www.ncl.ac.uk/undergraduate/finance For more information on general student