12.2 Ocm
12.2 Ocm
12.2 Ocm
User Guide
Release 12.2
Part No. E48901-07
September 2018
Oracle Credit Management User Guide, Release 12.2
Copyright © 2003, 2018, Oracle and/or its affiliates. All rights reserved.
Contributor: Kinjal Joshi, Jean-Raymond Naveau, Karthik Ramachandran, Bijoy Sarkar, Amit Vohra, Kathy
Weitzel
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are
"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-
specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the
programs, including any operating system, integrated software, any programs installed on the hardware,
and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No
other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron,
the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless
otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates
will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party
content, products, or services, except as set forth in an applicable agreement between you and Oracle.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers that have purchased support have access to electronic support through My Oracle Support.
For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.
com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Contents
Preface
iii
Assigning Automation Rules..................................................................................................3-17
Setting Up Credit Recommendations..................................................................................... 3-19
Setting Up Credit Decision Approval Policies....................................................................... 3-22
Reviewing Credit Management Performance........................................................................ 3-26
6 Workload Management
Credit Analyst Assignment Rules.............................................................................................6-1
Reassigning Credit Reviews..................................................................................................... 6-2
Reassign Credit Analyst Program............................................................................................. 6-3
iv
7 Additional Implementation Considerations
Defining Credit Usage Rule Sets.............................................................................................. 7-1
Defining Credit Hierarchies..................................................................................................... 7-3
v
Major Features...........................................................................................................................F-2
API Usage.................................................................................................................................. F-3
Index
vi
Send Us Your Comments
Oracle welcomes customers' comments and suggestions on the quality and usefulness of this document.
Your feedback is important, and helps us to best meet your needs as a user of our products. For example:
• Are the implementation steps correct and complete?
• Did you understand the context of the procedures?
• Did you find any errors in the information?
• Does the structure of the information help you with your tasks?
• Do you need different information or graphics? If so, where, and in what format?
• Are the examples correct? Do you need more examples?
If you find any errors or have any other suggestions for improvement, then please tell us your name, the
name of the company who has licensed our products, the title and part number of the documentation and
the chapter, section, and page number (if available).
Note: Before sending us your comments, you might like to check that you have the latest version of the
document and if any concerns are already addressed. To do this, access the new Oracle E-Business Suite
Release Online Documentation CD available on My Oracle Support and www.oracle.com. It contains the
most current Documentation Library plus all documents revised or released recently.
Send your comments to us using the electronic mail address: appsdoc_us@oracle.com
Please give your name, address, electronic mail address, and telephone number (optional).
If you need assistance with Oracle software, then please contact your support representative or Oracle
Support Services.
If you require training or instruction in using Oracle software, then please contact your Oracle local office
and inquire about our Oracle University offerings. A list of Oracle offices is available on our Web site at
www.oracle.com.
vii
Preface
Intended Audience
Welcome to Release 12.2 of the Oracle Credit Management User Guide.
This guide assumes you have a working knowledge of the following:
• The principles and customary practices of your business area.
If you have never used Oracle E-Business Suite, we suggest you attend one or more of
the Oracle E-Business Suite training classes available through Oracle University.
See Related Information Sources on page x for more Oracle E-Business Suite product
information.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=docacc.
Structure
1 Overview of Oracle Credit Management
ix
This chapter provides an overview of Oracle Credit Management.
2 Implementing Oracle Credit Management
Complete the tasks in this chapter after installation, but before setting up credit policies.
3 Setting Up Your Credit Policies
This chapter describes setting up and administering credit policies, as well as reviewing
the performance of the policies.
4 Using Credit Management
This chapter describes how to use Oracle Credit Management.
5 E-Business Suite Integration
This chapter describes how other Oracle E-Business Suite applications integrate with
Oracle Credit Management for their credit needs.
6 Workload Management
This chapter describes managing credit analyst assignments.
7 Additional Implementation Considerations
This chapter describes additional setup steps to consider when implementing Oracle
Credit Management.
A Oracle Credit Management Profile Options and Profile Option Categories
This appendix describes setting profile options for Oracle Credit Management.
B Credit Management Application Workflow
This appendix describes the workflow in Oracle Credit Management.
C Credit Request Business Events
This appendix describes business events that you can use with Oracle Credit
Management.
D Oracle Credit Management Data Points
This appendix describes the seeded data points in Oracle Credit Management.
E Additional Data Point PL/SQL Guidelines
This appendix describes guidelines for PL/SQL packages and functions that derive data
point values.
F Credit Management API User Notes
This appendix describes public Oracle Credit Management APIs.
x
documentation for your product with each release.
• Online Help - Online help patches (HTML) are available on My Oracle Support.
• Release Notes - For information about changes in this release, including new
features, known issues, and other details, see the release notes for the relevant
product, available on My Oracle Support.
Related Guides
You should have the following related books on hand. Depending on the requirements
of your particular installation, you may also need additional manuals or guides.
Oracle Alert User's Guide:
This guide explains how to define periodic and event alerts to monitor the status of
your Oracle E-Business Suite data.
Oracle Application Framework Developer's Guide:
This guide contains the coding standards followed by the Oracle E-Business Suite
development staff to produce applications built with Oracle Application Framework.
This guide is available in PDF format on My Oracle Support and as online
documentation in JDeveloper 10g with Oracle Application Extension.
Oracle Application Framework Personalization Guide:
This guide covers the design-time and run-time aspects of personalizing applications
built with Oracle Application Framework.
Oracle Fusion Middleware Adapter for Oracle Applications User's Guide (Oracle
Application Server Adapter for Oracle Applications User's Guide):
This guide covers the use of Adapter for Oracle Applications in developing integrations
between Oracle E-Business Suite and trading partners.
Please note that the user's guide can be found in the following documentation libraries:
• As part of the Oracle Fusion Middleware and SOA Suite in 11g, Oracle Fusion
Middleware Adapter for Oracle Applications User's Guide is available in the Oracle
Fusion Middleware 11g Documentation Library.
• As part of the Oracle Application Server in 10g, Oracle Application Server Adapter for
Oracle Applications User's Guide is available in the Oracle Application Server 10g
xi
Documentation Library.
xii
can browse and view the integration interface definitions and services residing in
Oracle Integration Repository.
Oracle E-Business Suite Integrated SOA Gateway Implementation Guide:
This guide explains how integration repository administrators can manage and
administer the Web service activities for integration interfaces including native
packaged integration interfaces, composite services (BPEL type), and custom
integration interfaces. It also describes how to invoke Web services from Oracle E-
Business Suite by employing the Oracle Workflow Business Event System, and how to
manage Web service security, configure logs, and monitor SOAP messages.
Oracle E-Business Suite Integrated SOA Gateway Developer's Guide:
This guide describes how system integration developers can perform end-to-end service
integration activities. These include orchestrating discrete Web services into meaningful
end-to-end business processes using business process execution language (BPEL), and
deploying BPEL processes at run time.
This guide also explains how to invoke Web services using the Service Invocation
Framework. This includes defining Web service invocation metadata, invoking Web
services, and testing the Web service invocation.
Oracle E-Business Suite Maintenance Guide:
This guide contains information about the strategies, tasks, and troubleshooting
activities that can be used to help ensure an Oracle E-Business Suite system keeps
running smoothly, together with a comprehensive description of the relevant tools and
utilities. It also describes how to patch a system, with recommendations for optimizing
typical patching operations and reducing downtime.
Oracle E-Business Suite Security Guide:
This guide contains information on a comprehensive range of security-related topics,
including access control, user management, function security, data security, and
auditing. It also describes how Oracle E-Business Suite can be integrated into a single
sign-on environment.
Oracle E-Business Suite Setup Guide:
This guide contains information on system configuration tasks that are carried out
either after installation or whenever there is a significant change to the system. The
activities described include defining concurrent programs and managers, enabling
Oracle Applications Manager features, and setting up printers and online help.
Oracle E-Business Suite User's Guide:
This guide explains how to navigate, enter and query data, and run concurrent requests
using the user interface (UI) of Oracle E-Business Suite. It includes information on
setting preferences and customizing the UI. In addition, this guide describes
accessibility features and keyboard shortcuts for Oracle E-Business Suite.
Oracle E-Business Suite User Interface Standards for Forms-Based Products:
This guide contains the user interface (UI) standards followed by the Oracle E-Business
xiii
Suite development staff. It describes the UI for the Oracle E-Business Suite products and
how to apply this UI to the design of an application built by using Oracle Forms.
Oracle e-Commerce Gateway User's Guide:
This guide describes the functionality of Oracle e-Commerce Gateway and the
necessary setup steps in order for Oracle E-Business Suite to conduct business with
trading partners through Electronic Data Interchange (EDI). It also describes how to run
extract programs for outbound transactions, import programs for inbound transactions,
and the relevant reports.
Oracle e-Commerce Gateway Implementation Guide:
This guide describes implementation details, highlighting additional setup steps needed
for trading partners, code conversion, and Oracle E-Business Suite. It also provides
architecture guidelines for transaction interface files, troubleshooting information, and a
description of how to customize EDI transactions.
Oracle iSetup Developer's Guide:
This manual describes how to build, test, and deploy Oracle iSetup Framework
interfaces.
Oracle iSetup User's Guide:
This guide describes how to use Oracle iSetup to migrate data between different
instances of the Oracle E-Business Suite and generate reports. It also includes
configuration information, instance mapping, and seeded templates used for data
migration.
Oracle Report Manager User's Guide:
Oracle Report Manager is an online report distribution system that provides a secure
and centralized location to produce and manage point-in-time reports. Oracle Report
Manager users can be either report producers or report consumers. Use this guide for
information on setting up and using Oracle Report Manager.
Oracle Web Applications Desktop Integrator Implementation and Administration
Guide:
Oracle Web Applications Desktop Integrator brings Oracle E-Business Suite
functionality to a spreadsheet, where familiar data entry and modeling techniques can
be used to complete Oracle E-Business Suite tasks. You can create formatted
spreadsheets on your desktop that allow you to download, view, edit, and create Oracle
E-Business Suite data, which you can then upload. This guide describes how to
implement Oracle Web Applications Desktop Integrator and how to define mappings,
layouts, style sheets, and other setup options.
Oracle Workflow Administrator's Guide:
This guide explains how to complete the setup steps necessary for any product that
includes workflow-enabled processes. It also describes how to manage workflow
processes and business events using Oracle Applications Manager, how to monitor the
progress of runtime workflow processes, and how to administer notifications sent to
xiv
workflow users.
Oracle Workflow API Reference:
This guide describes the APIs provided for developers and administrators to access
Oracle Workflow.
Oracle Workflow Client Installation Guide:
This guide describes how to install the Oracle Workflow Builder and Oracle XML
Gateway Message Designer client components for Oracle E-Business Suite.
Oracle Workflow Developer's Guide:
This guide explains how to define new workflow business processes and customize
existing Oracle E-Business Suite-embedded workflow processes. It also describes how
to define and customize business events and event subscriptions.
Oracle Workflow User's Guide:
This guide describes how users can view and respond to workflow notifications and
monitor the progress of their workflow processes.
Oracle XML Gateway User's Guide:`
This guide describes Oracle XML Gateway functionality and each component of the
Oracle XML Gateway architecture, including Message Designer, Oracle XML Gateway
Setup, Execution Engine, Message Queues, and Oracle Transport Agent. It also explains
how to use Collaboration History that records all business transactions and messages
exchanged with trading partners.
The integrations with Oracle Workflow Business Event System, and the Business-to-
Business transactions are also addressed in this guide.
Oracle XML Publisher Report Designer's Guide:
Oracle XML Publisher is a template-based reporting solution that merges XML data
with templates in RTF or PDF format to produce a variety of outputs to meet a variety
of business needs. Using Microsoft Word or Adobe Acrobat as the design tool, you can
create pixel-perfect reports from the Oracle E-Business Suite. Use this guide to design
your report layouts.
This guide is available through the Oracle E-Business Suite online help.
Oracle XML Publisher Administration and Developer's Guide:
Oracle XML Publisher is a template-based reporting solution that merges XML data
with templates in RTF or PDF format to produce a variety of outputs to meet a variety
of business needs. Outputs include: PDF, HTML, Excel, RTF, and eText (for EDI and
EFT transactions). Oracle XML Publisher can be used to generate reports based on
existing Oracle E-Business Suite report data, or you can use Oracle XML Publisher's
data extraction engine to build your own queries. Oracle XML Publisher also provides a
robust set of APIs to manage delivery of your reports via e-mail, fax, secure FTP,
printer, WebDav, and more. This guide describes how to set up and administer Oracle
XML Publisher as well as how to use the Application Programming Interface to build
xv
custom solutions.
This guide is available through the Oracle E-Business Suite online help.
Oracle E-Business Suite Upgrade Guide Release 12.0 and 12.1 to 12.2:
This guide provides information for DBAs and Applications Specialists who are
responsible for upgrading a Release 11i Oracle E-Business Suite system (techstack and
products) to Release 12.2. In addition to information about applying the upgrade driver,
it outlines pre-upgrade steps and post-upgrade steps, and provides descriptions of
product-specific functional changes and suggestions for verifying the upgrade and
reducing downtime.
Oracle E-Business Suite Multiple Organizations Implementation Guide:
This guide describes the multiple organizations concepts in Oracle E-Business Suite. It
describes in detail on setting up and working effectively with multiple organizations in
Oracle E-Business Suite.
Oracle Financials and Oracle Procurement Functional Upgrade Guide: Release 11i to
Release 12:
This guides provides detailed information about the functional impacts of upgrading
Oracle Financials and Oracle Procurement products from Release 11i to Release 12.2.
This guide supplements the Oracle E-Business Suite Upgrade Guide Release 12.0 and 12.1 to
12.2.
Oracle Financials Concepts Guide:
This guide describes the fundamental concepts of Oracle Financials. The guide is
intended to introduce readers to the concepts used in the applications, and help them
compare their real world business, organization, and processes to those used in the
applications.
Oracle Financials Glossary:
The glossary includes definitions of common terms that are shared by all Oracle
Financials products. In some cases, there may be different definitions of the same term
for different Financials products. If you are unsure of the meaning of a term you see in
an Oracle Financials guide, please refer to the glossary for clarification. You can find the
glossary in the online help or in the Oracle Financials Implementation Guide.
Oracle Financials Implementation Guide:
This guide provides information on how to implement the Oracle Financials E-Business
Suite. It guides you through setting up your organizations, including legal entities, and
their accounting, using the Accounting Setup Manager. It covers intercompany
accounting and sequencing of accounting entries, and it provides examples.
Oracle Approvals Management Implementation Guide:
Use this guide to learn how to implement Oracle Approvals Management (AME). AME
is a self-service Web application that enables users to define business rules governing
the process for approving transactions in Oracle Applications where AME has been
integrated.
xvi
Oracle Loans User Guide:
This guide describes how to set up and use Oracle Loans. It includes information on
how to create, approve, fund, amortize, bill, and service extended repayment plan and
direct loans.
Oracle Receivables User Guide:
This guide provides you with information on how to use Oracle Receivables. Use this
guide to learn how to create and maintain transactions and bills receivable, enter and
apply receipts, enter customer information, and manage revenue. This guide also
includes information about accounting in Receivables. Use the Standard Navigation
Paths appendix to find out how to access each Receivables window.
Oracle Receivables Implementation Guide:
This guide provides you with information on how to implement Oracle Receivables.
Use this guide to understand the implementation steps required for application use,
including how to set up customers, transactions, receipts, accounting, tax, and
collections. This guide also includes a comprehensive list of profile options that you can
set to customize application behavior.
Oracle Receivables Reference Guide:
This guide provides you with detailed information about all public application
programming interfaces (APIs) that you can use to extend Oracle Receivables
functionality. This guide also describes the Oracle Receivables open interfaces, such as
AutoLockbox which lets you create and apply receipts and AutoInvoice which you can
use to import and validate transactions from other systems. Archiving and purging
Receivables data is also discussed in this guide.
Oracle HRMS Documentation Set:
This documentation set includes these books:
• Oracle HRMS Compensation and Benefits Management Guide:
Learn how to use Oracle HRMS to manage your total compensation package. For
example, read how to administer salaries and benefits, set up automated grade/step
progression, and allocate salary budgets. You can also learn about setting up
earnings and deductions for payroll processing, managing leave and absences, and
reporting on compensation across your enterprise.
xvii
manage your budgets and costs.
xviii
included are setup instructions and sample code.
Integration Repository
The Oracle Integration Repository is a compilation of information about the service
endpoints exposed by the Oracle E-Business Suite of applications. It provides a
complete catalog of Oracle E-Business Suite's business service interfaces. The tool lets
users easily discover and deploy the appropriate business service interface for
integration with any system, application, or business partner.
The Oracle Integration Repository is shipped as part of the Oracle E-Business Suite. As
your instance is patched, the repository is automatically updated with content
appropriate for the precise revisions of interfaces in your environment.
xix
1
Overview of Oracle Credit Management
• Six months have passed since a customer's last credit review date, automatically
initiating a periodic credit review.
For each credit review type and credit classification combination, you assign a set of
credit review tools that will vary according to your requirements. Credit review tools
include:
• Credit checklists
Credit checklists specify which data points are required or optional during a credit
review. Examples of data points are Days Sales Outstanding and Percentages Of
Invoices Paid Late. When defining checklists, choose from a universe of almost 200
data points, or define your own.
See: Defining Checklists, page 3-5.
• Scoring models
Scoring models include the data points and scoring method that are appropriate for
a particular credit review. When defining scoring models, for each data point, (1)
indicate a score for each range of values and (2) optionally assign a relative
weighting factor.
For example, will you use this scoring model to determine a credit limit increase for
an existing customer who has years of credit history with your enterprise? In that
case, you might assign a higher weighting factor to the Percentages Of Invoices
Paid Late data point, and a lower weighting factor to the Credit Agency Score data
point.
See: Defining Scoring Models, page 3-9.
• Automation rules
Automation rules guide the implementation of credit recommendations without
user intervention. Optionally define automation rules and assign them to a scoring
model. If a score is above a certain threshold, for example, you might want Credit
Management to automatically approve and implement a higher credit limit, or
release an order hold.
See: Assigning Automation Rules, page 3-17.
During setup, you model your credit policies by assigning the appropriate credit review
tool to each combination of credit review type and credit classification.
For example, for the combination of Increase Credit Limit credit review type and High
Risk customer credit classification, your credit policies might dictate a conservative
approach. In this scenario, you would use a conservative policy (scoring model) to
determine whether to grant additional credit and what the credit limit should be.
If an automated credit review fails at any point during the process, the workflow will
stop and the credit review will be routed for assignment to a credit analyst for manual
processing. See: How Automation Works, page 1-5.
Complete the tasks in this chapter after installation, but before setting up credit policies.
This chapter covers the following topics:
• Defining Credit Analysts
• Maintaining Customer Data
• Populating Transaction Data
• Defining Credit Management System Options
• Defining Lookups
• Updating Customer Profile Classes
• Assign Customer Credit Classification Program
2. Next, import employees from HRMS into Resource Manager and assign roles.
Two seeded roles exist for Credit Management:
• Credit Analyst
• Credit Manager
3. Finally, when defining your analysts as E-Business Suite users in the Users window,
link each analyst to his or her HRMS record by selecting:
• The analyst's name in the Person field
See: Users Window, Oracle E-Business Suite System Administrator's Guide - Security.
After you define a credit analyst, you can modify any of the analyst's information,
except the employee and user names.
2. Set the HZ: Enable DQM Party Search Determine profile option to Yes. DQM search
is enabled only for searches that has an assigned match rule, based on the above
profile options.
• AR_TRX_SUMMARY_ALL
Stores data, such as the count of open invoices and total invoice value, that is
summarized for a specified period of time.
You specify the period of time using the Period for Time Sensitive Data system
option, which controls how data is stored in this table. Why specify a time period?
Depending on whether your business is cyclical or seasonal in nature, you may
want to look back at customer data for a short or long period of time. See: Defining
Credit Management System Options, page 2-7.
• oracle.apps.ar.applications.CashApp.apply
• oracle.apps.ar.applications.CashApp.unapply
• oracle.apps.ar.applications.CreditMemoApp.apply
• oracle.apps.ar.applications.CreditMemoApp.unapply
• oracle.apps.ar.batch.AutoAdjustments.run
• oracle.apps.ar.batch.AutoInvoice.run
• oracle.apps.ar.batch.AutoReceipts.run
• oracle.apps.ar.batch.CopyInvoices.run
• oracle.apps.ar.batch.QuickCash.PostBatch
• oracle.apps.ar.receipts.CashReceipt.DebitMemoReverse
• oracle.apps.ar.receipts.CashReceipt.Delete
• oracle.apps.ar.receipts.CashReceipt.approve
• oracle.apps.ar.receipts.CashReceipt.confirm
• oracle.apps.ar.receipts.CashReceipt.create
• oracle.apps.ar.receipts.CashReceipt.modify
• oracle.apps.ar.receipts.CashReceipt.reverse
• oracle.apps.ar.receipts.CashReceipt.unconfirm
• oracle.apps.ar.transaction.Aging.PastDue
• oracle.apps.ar.transaction.ChargeBack.create
• oracle.apps.ar.transaction.ChargeBack.modify
• oracle.apps.ar.transaction.CreditMemo.complete
• oracle.apps.ar.transaction.CreditMemo.incomplete
• oracle.apps.ar.transaction.CreditMemo.modify
• oracle.apps.ar.transaction.DebitMemo.incomplete
• oracle.apps.ar.transaction.DebitMemo.modify
• oracle.apps.ar.transaction.Deposit.complete
• oracle.apps.ar.transaction.Deposit.incomplete
• oracle.apps.ar.transaction.Deposit.modify
• oracle.apps.ar.transaction.Guarantee.complete
• oracle.apps.ar.transaction.Guarantee.incomplete
• oracle.apps.ar.transaction.Guarantee.modify
• oracle.apps.ar.transaction.Invoice.complete
• oracle.apps.ar.transaction.Invoice.incomplete
• oracle.apps.ar.transaction.Invoice.modify
See: Aging Buckets and Interest Tiers, Oracle Receivables Implementation Guide.
DSO Days
Indicate the time period that Credit Management uses to calculate Days Sales
Outstanding (DSO) and Delinquent Days Sales Outstanding (DDSO).
Note: Credit Management uses its own DSO calculation; this value is
not populated from Oracle Receivables.
Appeal Days
Other applications integrating with Credit Management can appeal a credit
Defining Lookups
Credit Management uses lookups to help speed data entry and increase accuracy. You
can use the predefined lookups that Credit Management provides, or you can create
additional lookups where required.
For example, to identify an applicant's potential credit risk, you must select a credit
classification, if not previously assigned, when entering a credit application. The credit
classification describes the type of credit relationship that you have with the applicant.
Credit Management provides you with High Risk, Low Risk, Moderate Risk, and New
Prospect, but you can optionally define new credit classifications to fit your business
needs.
Use the Oracle Receivables Lookups window to define any additional lookups that you
require.
Tip: After you add new credit classifications or reason types, bounce
the apache server to make sure that the new values are available for
users to select in the application.
The following table lists lookup types used for Credit Management.
• Analyst
Optionally assign credit analysts to indicate who is responsible for monitoring the
creditworthiness of the account and for assisting in the resolution of credit-related
issues.
If a credit applicant does not have an assigned credit analyst, or is a prospect, then
any credit review for that applicant is routed to the Credit Scheduler for analyst
assignment. See: Credit Management Application Workflow, page B-1.
Related Topics
Defining Customer Profile Classes, Oracle Receivables Implementation Guide
Defining Credit Analysts, page 2-1
Overview of Oracle Credit Management Setup, page 3-1
Selected Parameters
Update Existing Credit Classification: Select Yes to update the credit classification for
all customers who are assigned to the specified profile class.
Select No if you do not want to update the credit classification for customers who
already have existing credit classifications.
If you select No, then only customers who have no existing credit classifications are
assigned the new credit classification.
Related Topics
Overview of Oracle Credit Management Setup, page 3-1
Defining Customer Profile Classes, Oracle Receivables Implementation Guide
This chapter describes setting up and administering credit policies, as well as reviewing
the performance of the policies.
This chapter covers the following topics:
• Overview of Oracle Credit Management Setup
• What is a Credit Data Point?
• Defining Checklists
• Adding Dun & Bradstreet Data Points to a Checklist
• Defining Scoring Models
• External Scoring
• Assigning Automation Rules
• Setting Up Credit Recommendations
• Setting Up Credit Decision Approval Policies
• Reviewing Credit Management Performance
Then, define credit recommendations, page 3-19 and approval policies, page 3-22.
Finally, use the tools on the Performance tab to ensure that your credit policies are
adequately assessing the creditworthiness of your customers and prospects. See:
Reviewing Credit Management Performance, page 3-26.
Related Topics
Chapter 2, Implementing Oracle Credit Management
• External
You can include data points from other sources from outside the E-Business
Suite, such as credit bureaus that are not currently integrated with Credit
Management.
Note: On the Additional Data Points page, you can view and update
only the user-defined data points, not the seeded data points.
If a data point has an associated function, then the data point value is not updatable
in the case folder.
For PL/SQL guidelines, see: Guidelines for Deriving Data Point Values, page E-1.
2. If you define a PL/SQL function for an ADP, make sure that the
function will complete normally and successfully for all
customers or scenarios. Make sure that you handle all ORA-
1403 or ORA-1422 (no data found/too many rows) issues which
return null or zero values inside your package.
3. All ADPs are executed for all customers on all case folders.
While you may not use the ADP in all cases, it should calculate
or handle exceptions for cases where it cannot compute a value.
• Specify a data point category. A data point category acts as a filter to classify your
user-defined data points. For example, you might want to organize data points by
external source, such as by credit bureau name.
Related Topics
Overview of Oracle Credit Management Setup, page 3-1
Defining Checklists
In Oracle Credit Management, you document your enterprise's credit policies via user-
defined credit checklists. Using various checklists, you manage the credit analysis
process by defining the required and optional data points that are included in the credit
review.
Defining a checklist is a multi-step process, during which you can select checklist
When defining a checklist, you select a credit review type and credit classification
combination. During a credit review, Credit Management uses the intersection of the
credit review type and the applicant's credit classification to select the appropriate
checklist to use for the credit analysis. The higher the customer credit classification risk,
the more stringent the credit policy (scoring model).
For example, your enterprise defines these credit review types:
• Credit checking
• Credit review
• Credit application
• Lease application
• Moderate Risk
• Low Risk
For each combination of credit review type and credit classification, define a checklist
based on your credit policies. For example, during a lease application credit review for
a High Risk customer, the assigned checklist might require additional collateral and
bank reference data points on which to base a credit decision.
This table lists the pages from which you select data points that you want to include in
the checklist.
Select Credit Data Points Indicates which credit-related data Receivables and user-entered
from Receivables and user-entered
business information to include in
the credit analysis
Select Payments Data Points Indicates which historical order and Order Management and Receivables
receivables data to include in the
credit analysis
Select Dun & Bradstreet Data Points Indicates which data points from the Dun & Bradstreet
specific Dun & Bradstreet Global
Access Data Products report to
include in the credit analysis
Prerequisites
You must first define your enterprise's credit classifications as well as credit review
types. See: Defining Lookups, page 2-10.
To define a checklist:
1. On the Define Checklist page, enter a name and description for this checklist.
2. Select the credit classification that you want to associate with this checklist.
3. Select the credit review type that you want to associate with this credit classification
and checklist.
5. The Start Date field defaults to the current date, but you can change it to a future
Note: If you enter a future end date, then you can associate a
second checklist with this same combination of credit classification
and credit review type, provided that the second checklist's start
date is after this checklist's end date.
7. Use the Credit Policy Statement field to optionally enter a description of the credit
policy that this checklist enforces.
8. The following group of pages display various data points that you can select for
inclusion in this checklist.
Select the data points that you want this checklist to include.
If you do not select either check box, then the checklist will not include the data
point at all.
Data points that are user-entered or from an external source can be designated as
required or optional. See: Defining Additional Data Points, page 3-3.
For additional information about selecting data points from Dun & Bradstreet, see
Adding Dun & Bradstreet Credit Data to a Checklist, page 3-9.
On each page, you can view the checklist criteria that you have saved up to that
point.
Related Topics
Overview of Oracle Credit Management Setup, page 3-1
• If the data is not available and you selected the All Data Optional check box, then
you will receive a notification that the data does not exist. However, Credit
Management will still complete the credit analysis and make a recommendation.
Related Topics
Third Party Data Integration Overview, Oracle Trading Community Architecture User
Guide
Overview of Oracle Credit Management Setup, page 3-1
The power of the scoring model lies in its ability to facilitate the automated credit
review process, because you can attach recommendations to each score range. Once a
score has been calculated, Credit Management can automatically determine the
appropriate credit recommendations without user intervention. See: Assigning
Automation Rules, page 3-17.
Credit Management provides you with the ability to define multiple scoring models.
Define a different scoring model for each type of credit review that you need. This lets
you apply standard and consistent scoring guidelines across your customers and
prospects.
You can assign a default scoring model to a credit checklist. See: Defining Checklists,
page 3-5.
Later, during credit analysis, you can generate various "what-if" scenarios during a
credit review by selecting different scoring models from the case folder. See: Calculating
a Credit Score, page 4-18.
Tip: You can ignore Credit Management's scoring model altogether and
use an external scoring engine to derive a credit score. See: External
Scoring, page 3-15.
Assigning Scores
For each data point that the scoring model includes, you must assign a range of values
and a corresponding score for each range. The ranges of values for a data point typically
represent levels of credit risk.
Numeric ranges can be positive or negative, and you can use decimal points. Scores
must be numeric values, either positive or negative.
For example, this table illustrates sample ranges and scores for the Percentage of
Low 0 to 20 15
Moderate 21 to 50 10
High 51 to 100 0
This table illustrates sample ranges and scores for the DSO data point:
Low -999 to 9 8
Moderate 10 to 24 5
High 25 to 34 2
Highest 35 to 999 1
Tip: You can view the minimum and maximum potential raw scores on
the Review page during scoring model definition. This is helpful to
know when defining automation rules. See: Assigning Automation
Rules, page 3-17.
Continuing the previous example, this table illustrates the possible weighting factors for
the Percentage of Invoices Paid Late and DSO data points:
DSO 35
Note: If you assign weights, then the sum of all data point weighting
factors must equal 100.
DSO 15
1. For each data point, the score for the value's range is divided by the largest possible
score for the data point.
• Percentage of Invoices Paid Late: 0 / 15 = 0
• DSO: 5 / 8 = .625
3. The results of step 1 and 2 are added for each data point.
0 + .13671875 = .13671875
2. In the Currency field, from the list of values, select the currency for this scoring
model.
The selected currency indicates the currency in which the data point range is
expressed. Credit Management uses the Exchange Rate Type system option during
currency conversion.
3. Use the Notes field to optionally enter comments about this scoring model.
4. The Start Date defaults to the current date, but you can change it to a future date.
If your credit requirements change and you want to define a new scoring model
that is more in line with your revised credit policies, inactivate the outdated scoring
model by entering an end date. The only valid end date is the current date.
When you create a new case folder or attach a scoring model to a credit checklist,
you can select only a scoring model that has no end date, or an end date that is
greater than the case folder or checklist creation date.
Note: Once you enter an end date and save your work, you can no
longer change or remove the date. This ensures that your credit
policies are strictly enforced, and also that comparisons across
scoring models remain meaningful.
5. Use the Convert null values to zero values check box to indicate how Credit
Management should treat data points with null values.
6. On the Select Data Points page, select the data points that you want to include in
the scoring model.
Note: If you enter alphanumeric values for a data point, then both
range values must be the same. This table illustrates an example:
8. When you have completed assigning ranges and scores to the data points in this
scoring model, optionally assign a weight to each data point. The weight that you
assign indicates the relative importance of the data point in the scoring model.
See: Assigning Weights (Optional), page 3-11.
Tip: If you have not assigned weights, then the scoring model will
calculate a raw score. Note the minimum and maximum potential
raw scores on this page, because you will need to know this range
if you define automation rules. See: Assigning Automation Rules,
page 3-17.
You can still update a scoring model after you save it. After you submit a scoring
model, however, you can no longer update it.
External Scoring
You can bypass Oracle Credit Management's scoring functionality and score a case
folder's data points using a third party scoring engine. This process involves:
1. Exporting case folder contents outside Credit Management, and scoring the
contents using your own scoring engine
2. Importing the resulting credit score, and storing it in the case folder
Upon import, Credit Management records the score as the value for the External Score
data point, and also includes the score in an XML file attached to the case folder for
audit purposes.
To unlock the case folder and resume workflow processing, you must ensure that the
Submit Case Folder API runs after the Get Score API.
The Submit Case Folder API unlocks the case folder and removes the In Process status.
The case folder is now ready for credit recommendations:
• If automation rules are associated with the scoring model, then credit
recommendations are automatically assigned according to the automation rules and
the externally derived credit score. The case folder is then submitted for approval.
• If no automation rules exist, then a credit analyst must manually assign a credit
recommendation and submit the case folder for approval.
To import additional data points and credit recommendations, ensure that the Include
Data Points API and Get Recommendations API are run after the Get Score API. As
always, the Submit Case Folder API must run at the end of the process to unlock the
case folder for processing.
Upon import, Credit Management refreshes the case folder with the additional data
points and credit recommendations.
Additional data points and credit recommendations are stored in the same XML file
(attached to the case folder) where the credit score resides.
Related Topics
Appendix F: Credit Management API User Notes
Overview of Oracle Credit Management Setup, page 3-1
2. Select a scoring model and click the Add Rules icon to define a set of automation
rules.
4. Use the Low Score and High Score fields to define the score range for this
automation rule.
5. Select the Skip Approval check box if you want to automatically implement credit
recommendations without the defined approval hierarchy.
See: Setting Up Credit Decision Approval Policies, page 3-22.
6. Click the Add Recommendations icon to assign automation rules (automatic credit
decisions) to this score range.
• Use the Overall Credit Limit or Transaction Credit Limit fields to define the
credit limit for this score range. Or, use the Change Overall Credit Limit by
Percentage or Change Overall Transaction Credit Limit fields to indicate a
percentage increase limit.
You can assign additional values for a recommendation. For example, for a
recommendation of increase credit limit to CAD $800,000, value 1 is currency =
CAD and value 2 is 800,000.
Do not enter a value in any field if you do not want Credit Management to
• From the list of values, select a credit classification that you want to
automatically assign to the applicant if they receive a credit score in this range.
7. You can add another row to enter another score range and associated automation
rules.
If the scoring model uses weighting factors for each score range, then the credit
score is always a complete range from 0 to 100. If not, then the scoring model will
produce a raw score that can be outside the 0 to 100 range.
8. Click Submit to freeze this set of automation rules for the selected scoring model.
After you submit, you can no longer update these automation rules.
Related Topics
Defining Scoring Models, page 3-9
Overview of Oracle Credit Management Setup, page 3-1
Oracle Approvals Management Implementation Guide
• No Change
• Authorize Appeal
• Extend
• Increase
• Reject
• Terminate
If you are using Oracle Lease and Finance Management or Oracle Loans and want to
define application-specific recommendations, see: Defining Recommendations for
Integrated Applications, page 5-1.
• Manual:
A credit analyst can make a credit recommendation at the conclusion of a manual
credit analysis.
But how are those credit recommendations actually approved and implemented?
During setup, you decide which recommendations require approval. For example,
certain risky credit recommendations might require approval by a defined list of
approvers.
On the other hand, you might want less risky credit recommendations to be
immediately implemented without approval.
This decision about whether to approve credit recommendations is another dimension
of credit policy management:
• For credit recommendations that do not require approval, you implement this type
of policy using the Skip Approval check box during scoring model definition. See:
Bypassing the Approval Hierarchy, page 3-23.
• For credit recommendations that require approval, Credit Management works with
Oracle Approvals Management (AME) to manage the list of required approvers.
Tip: Typically, all scoring models will have automation rules. For a set
of automation rules, you might enable the Skip Approval option on:
• the lowest credit score range, to automatically implement the
rejection recommendation due to high risk
You might require approval, however, for the mid-range credit score.
Also consider the following credit policy that your enterprise defines for Company
ABC, should ABC surpass its existing credit limit:
• During a credit review, if the customer scores 71 or higher, then the credit limit is
automatically increased to $200,000.
Implementation: For this credit score range, the Skip Approval check box is
selected.
• If the customer scores 50 or higher, but below 71, then the credit limit is increased to
$150,000, but approval by the sales department is required.
Implementation: For this credit score range, the Skip Approval check box is not
selected.
• If the customer scores less than 50, then the workflow fails and the credit review is
automatically passed to a credit analyst for manual processing.
Implementation: This credit score range does not exist on the scoring model's
automation rules.
You also have the flexibility to define a list of either parallel or sequential approvers.
For example, for orders placed on hold, perhaps your enterprise defined the following
credit policy:
• For orders $500 or less, the approval list should be Jane, a credit analyst, and Bob,
her credit manager.
• For orders over $500, the approval list should be Bob, the credit manager, and
Mary, the vice-president of Finance.
Related Topics
Overview of Oracle Credit Management Setup, page 3-1
The Quick Check provides you with a view into the amount of work that is
outstanding. A high number of in-process reviews can indicate that a delay exists in
meeting credit review completion goals.
Customer Trends
Use this comparison to view pertinent trend data from one credit review to the next for
an account. Comparison data from each case folder includes the receivables balance,
weighted average days paid, and days sales outstanding.
This is particularly useful for accounts who have a long-term relationship with you and
are assigned a periodic review cycle.
To perform this comparison, the account must have more than one case folder for a
credit review type, and the case folders must have a status of Closed. The credit reviews
must also use the same credit currency.
The absence of a risk factor indicates that a risk factor could not be calculated due to
missing data.
Related Topics
Overview of Oracle Credit Management Setup, page 3-1
Processing Credit Reviews, page 4-1
• Certain business events can automatically initiate a credit review by calling the
Create Credit Request API. This type of request creates a credit application and case
folder without user intervention.
For example, if a sales order is put on credit hold, then the credit hold process in
Oracle Order Management passes this information to the Create Credit Request
API, which automatically initiates a credit review.
Other events, such as a quarterly review or a lease application submission, can also
trigger a credit review.
If a change to the sales order amount occurs during credit review processing and
the case folder is still open, then Oracle Credit Management updates the existing
case folder with the new order amount and initiates the case folder data refresh,
rather than creating a duplicate credit request. If the case folder is closed, then a
new credit request is created.
Note: You can also use the Create Credit Request API to initiate a
credit review from a non-Oracle system.
Related Topics
Processing Credit Reviews, page 4-1
• Case folder
If the checklist identifies required data points that already exist within Oracle
Applications or are calculable, such as available credit, aging, and so on, then Credit
Management automatically inserts that information directly into the credit application
and case folder.
If the checklist requires data points that must be manually supplied, such as bank and
trade references, then a credit analyst must enter the required data into the credit
application or case folder.
The checklist that Credit Management associates with the case folder ensures that, for
this combination of credit review type and credit classification, all pertinent information
is available for the credit analysis.
Related Topics
Processing Credit Reviews, page 4-1
Note: You can also use the case folder to collect information. See: Using
Case Folders to Collect Credit Data, page 4-12.
Use the Application tab to create or search for one of three types of credit applications:
• Saved application
• In-process application
For all three application types, you must first execute a search in order to proceed.
Credit Management provides you with robust search capabilities that minimize both
the possibility of creating duplicates in your system, as well as the amount of manual
data entry that is required for a new application.
Search criteria is based upon the Data Quality Management (DQM) setup. See: Setting
Up Data Quality Management Search, page 2-3.
Related Topics
Processing Credit Reviews, page 4-1
Collecting Credit Data, page 4-3
Creating a New Credit Application, page 4-5
Searching for Saved Applications, page 4-7
Searching for In-Process Applications, page 4-7
Entering Data into a Credit Application, page 4-8
Submitting a Credit Application, page 4-11
Window Reference
• Click the View Accounts icon to view a customer's accounts. You can view an
account only if the address is All Locations or if the address type includes a bill-to
business purpose.
• Click the Create Credit Application icon to create a new credit application for this
prospect, customer, account, or site, depending on which search results are in view.
Credit Management opens a new application and automatically updates the
application with the relevant applicant data.
• Click the View Existing Applications icon to view the open credit applications that
exist for this prospect, customer, account, or site.
• If your customer search returned no results or you wish to purchase Dun &
Bradstreet information for an existing customer, then you can click Search D&B to
purchase a Dun & Bradstreet Global Data Product report for this prospect or
customer. If a new party is created, then you will receive a message indicating the
new registry ID for the prospect.
When you return to the New Application Search page, type the new registry ID into
the Search field. Simply click Go and the newly created customer appears in the
search results. You can now create a credit application for this customer.
Note: With the Dun & Bradstreet for Oracle Applications feature,
you can import D&B information and maintain that information
directly in the application database, without installing additional
software or performing additional data imports. This functionality
enables easy access to already purchased D&B credit data during
credit reviews.
Related Topics
Using Credit Applications to Collect Credit Data, page 4-4
Processing Credit Reviews, page 4-1
Third Party Data Integration Overview, Oracle Trading Community Architecture User
Guide
Window Reference
• Click the Update icon in any row to make changes to the related credit application.
• Click the Delete icon in any row to delete the related credit application.
Related Topics
Using Credit Applications to Collect Credit Data, page 4-4
Processing Credit Reviews, page 4-1
• Processed indicates that the credit application was submitted and the credit analysis
has been performed. Recommendations were made in the case folder and have been
approved. Modifications are not permitted at this stage.
If you are a credit analyst, then all applications assigned to you are automatically
Window Reference
• After you execute a search, optionally click the column headings for Application
Number, Registry ID, Name, and Status to sort the search results by the selected
column's data.
• Click the Update icon in any row to make changes to the related credit application.
Only credit analysts assigned to the application are permitted to make changes.
Related Topics
Using Credit Applications to Collect Credit Data, page 4-4
Processing Credit Reviews, page 4-1
The credit application's contents vary according to the credit classification of the
applicant and the type of credit review that you are conducting. You specify these
values on the first page of the credit application. If the applicant has a predefined credit
classification assigned from the customer profile class or from a previous credit review,
then the credit classification is prefilled on the application. Use the left-hand menu to
add information, such as bank references and financial data, to the application.
Tip: You must enter required data in the Create Credit Application:
Applicant page, but you can submit the credit application without data
in the required fields of other pages such as Create Credit Application:
Financial Data.
• Contact Telephone
• Contact Fax
• Contact E-mail
• Select and compare financial statements that are saved with the current credit
review. This lets you view a side-by-side comparison of balance sheets and income
statements.
The capability to analyze the trends of your credit applicants' financial results provides a
powerful analysis tool, which your credit department can leverage to increase the
quality of their credit decisions, and diminish the risk of poor credit recommendations.
• Collateral Data
• Guarantors
Assessing the creditworthiness of customers can include structures by which the
debt obligation is reduced through participation of guarantors. However,
guarantors also carry credit risk. On this page, you can add a new guarantor, or
select an existing guarantor, by leveraging Credit Management's integration with
Oracle Trading Community Architecture.
Related Topics
Using Credit Applications to Collect Credit Data, page 4-4
Processing Credit Reviews, page 4-1
3. Credit Management routes the credit review to the Credit Scheduler for assignment
if the person who submitted the credit application is not defined as a credit analyst,
and:
• The customer's profile does not have an assigned credit analyst, or
• The party under credit review is a prospect (a party with no customer accounts)
Related Topics
Processing Credit Reviews, page 4-1
Collecting Credit Data, page 4-3
Using Credit Applications to Collect Credit Data, page 4-4
Credit Management also creates a case folder when a business event calls the Create
Credit Request API to initiate a credit review. However, the manual addition of data to
a case folder is typically not required because, in such cases, Credit Management
attempts all data collection, analysis, and decisioning on its own. See: Credit
Management Application Workflow, page B-1.
When a business event initiates a credit review, both the Update Case Folder: Summary
and Case Folder pages display the originating source application, as well as additional
details. For example, if a sales order hold initiated a credit review, then Credit
Management displays details such as the order number and order ID.
The Credit Request Information region on these pages also allows you to navigate to
other case folders in the same chain. A chain exists when:
• A case folder is automatically created for the guarantor that is added to a credit
application. The chain links the original applicant and the guarantor. See: Entering
Data into a Credit Application, page 4-8.
The case folder you navigate to depends on the credit request reason, and other
conditions, as described in this table.
Original All but Guarantor Assessment The first case folder in the chain.
Current All but Guarantor Assessment The last case folder in the chain that
is not withdrawn, unless there is
only one case folder and it is
withdrawn.
Previous All but Guarantor Assessment The previous case folder in the chain
that is not withdrawn.
Next All but Guarantor Assessment The next case folder in the chain that
is not withdrawn.
Related Topics
Processing Credit Reviews, page 4-1
Collecting Credit Data, page 4-3
Retrieving a Case Folder, page 4-14
Entering Data into a Case Folder, page 4-15
Manually Creating a New Case Folder, page 4-16
• Case Folder Number: From the search results, you can use the inline icons to view
or update details for a specific case folder, provided that the case folder status is
either Created or Saved. Use this query to view a case folder's application number,
assigned credit analyst, and folder status.
This query is available only to credit personnel. Only the credit analyst assigned to
the case folder can update it.
• My Case Folder: This query is identical to the Case Folder query, except that it
returns only case folders that are assigned to you. Use this query to quickly resume
work on an in-process credit review, or to consider previous research that you
performed. To update a case folder, the case folder status must be either Created or
Saved.
This query is available only to credit personnel.
Search criteria is based on the Data Quality Management (DQM) setup. See: Setting Up
Data Quality Management Search, page 2-3.
Related Topics
Using Case Folders to Collect Credit Data, page 4-12
Processing Credit Reviews, page 4-1
Related Topics
Using Case Folders to Collect Credit Data, page 4-12
Processing Credit Reviews, page 4-1
Tip: To copy a case folder from the account or site level, first click the
View Accounts icon, then the View Case Folders icon.
After clicking Add Case Folder, you must then select the credit classification, if not
supplied, as well as credit review type and credit currency. You can also optionally
select a scoring model. Finally, click Apply.
Credit Management prefills the case folder with any available data, such as party
information and data points from the credit checklist that matches the specified credit
classification and credit review type. If you selected a scoring model for the case folder,
then Credit Management displays the score elements, as well.
You can continue to add credit data to a case folder after you create it. Note that you
must enter any required data points before Credit Management will make and
implement credit recommendations.
Related Topics
Processing Credit Reviews, page 4-1
Collecting Credit Data, page 4-3
Using Case Folders to Collect Credit Data, page 4-12
2. Credit personnel who want to view all point-in-time data for an active analysis.
Typically, a credit analyst performs a credit analysis based upon the data in the
case folder, determined by the checklist associated with the customer credit
classification and review type. If the credit analyst views the universe of data in
addition to what is contained in the case folder, then he might notice something that
could impact the outcome of the analysis. In such a case, the analyst could manually
add one or more data items to the case folder.
To add data points from the database that are not specified in the checklist, click
Add Data Points from the Checklist section of the Update Case Folder: Summary
page. Access this page by searching for a customer, then selecting the View Case
Folder > Update Case Folder icons.
For each category, only the data points not already selected in the case folder are
displayed with their corresponding value.
See: Using Case Folders to Collect Credit Data, page 4-12.
Related Topics
Using the Case Folder, page 4-18
Calculating a Credit Score, page 4-18
Adding Analysis Notes to the Case Folder, page 4-19
Viewing Case Folder Attachments, page 4-20
Refreshing Case Folder Data, page 4-20
Viewing the Credit Summary, page 4-20
Processing Credit Reviews, page 4-1
• An Analysis Notes section where you can document conditions of influence and
justify credit recommendations to approvers
Related Topics
Analyzing Credit Data, page 4-16
Processing Credit Reviews, page 4-1
Note: If some required data point values are missing, then Credit
Management cannot generate a score.
Related Topics
Analyzing Credit Data, page 4-16
Processing Credit Reviews, page 4-1
Related Topics
Analyzing Credit Data, page 4-16
Processing Credit Reviews, page 4-1
Related Topics
Analyzing Credit Data, page 4-16
Processing Credit Reviews, page 4-1
Note: Only the case folder data, and not data in the Credit Summary
Data pages, is refreshed. However, you can click Refresh Data in the
Credit Summary Data pages to update the values displayed there.
Related Topics
Analyzing Credit Data, page 4-16
Processing Credit Reviews, page 4-1
• Credit Summary
• Aging Summary
From the Credit Summary page, you can also use the links in the left-hand menu to
view additional billing and payment details, as well as additional aging details. Both
the Billing and Payment Details page and Aging Details page are view only.
Note: No data values are shown on the Credit Summary page until an
initial case folder has been created for the applicant. After that, you can
view and refresh Credit Summary data at any time.
Related Topics
Analyzing Credit Data, page 4-16
Processing Credit Reviews, page 4-1
Making a Recommendation
At the conclusion of a credit review, either Oracle Credit Management or a credit
analyst makes a recommendation in response to the original credit request:
• If a credit review is using a scoring model with assigned automation rules, then
Credit Management looks at the calculated credit score to automatically select the
appropriate credit recommendations, all without the assistance of credit personnel.
• If a credit analyst is managing the credit review, then the analyst records
Generally, a recommendation is specific to the type of review that was just concluded.
For example, a credit review that an order hold originally initiated would most likely
result in a recommendation to:
1. Increase the credit limit to accommodate the amount of the order and remove the
order from hold.
or
2. Deny the request for an increase in the credit limit and leave the order on hold.
Other recommendations might also put the customer on credit hold so that no new
orders could be processed. In such a case, Credit Management works with Oracle
Receivables to place all pending orders on hold, as well.
Credit Management confirms that multiple recommendations are complementary. For
example, you would not recommend to place the account on credit hold and increase
the applicant's overall credit limit at the same time.
After the case folder is submitted, the Credit Management workflow determines
whether the recommendations must be routed through an approval hierarchy. For
example, if automation rules on the scoring model have the Skip Approval check box
selected, then no approval is required. However, if no automation rules exist on the
scoring model, or if the Skip Approval check box is not selected, then the Credit
Management workflow calls the Approvals engine to route the recommendation
through the approval hierarchy. See: Setting Up Credit Decision Approval Policies,
page 3-22.
Each person in the approval hierarchy receives a notification that they must approve or
reject the recommendations. Upon final approval, the credit analyst receives notification
that the credit recommendations have been approved. See: Credit Management
Application Workflow, page B-1.
Upon approval, the Credit Management workflow evaluates the recommendations and
performs one of two actions:
• Implements the recommendation
For example, increase create limit by 10% and change the customer credit
classification to Moderate Risk.
Related Topics
Implementing the Recommendation, page 4-23
Processing Credit Reviews, page 4-1
Related Topics
Making a Recommendation, page 4-21
Processing Credit Reviews, page 4-1
Tip: These attributes also help you to decide whether a review cycle
reassignment for a customer is necessary, because you can easily view
when a customer is next eligible for a periodic review.
• If no last review date exists, then the program keeps the next review date as is, if
one exists, or leaves it empty, if null.
When the Periodic Credit Review program is submitted, the program automatically
selects those customers whose next review date is less than or equal to the system date.
Selected Parameters
Enter your selection criteria using the following parameters:
• Review Cycle
• If the program cannot calculate a next review date, then the customer is eligible
for selection, provided that other entered parameters are not in conflict. This
occurs during an initial periodic review.
• Currency Code
Specify the currency that you want to run a periodic credit review for.
When you submit this program for a specific currency, the program first checks if a
previous case folder with a Periodic source exists for the entered currency.
• Customer Level
Indicate which level of customer is selected for periodic review:
• Accounts
• All
• Bill-to Sites
• Parties
• Checklist
• Party Name
• Account Number
• Credit Classification
• Profile Class
• Processing Options
• Generate Report Only
This option only prints the Periodic Review Eligibility report, so that you can
preview which customers will be selected for processing.
• Process Reviews
This option only creates credit requests for eligible customers, and does not
print the Periodic Review Eligibility report.
2. The program uses standard guidelines to calculate the next review date, which is
April 19.
On the same day, run the Periodic Credit Review program for CAD currency.
1. Vision Operations has no previous CAD periodic reviews as well, but now, the next
review date is April 19.
2. The program will select this customer for processing, but will maintain the next
review date of April 19.
On April 20, run the Periodic Credit Review program for USD currency.
1. Vision Operations has a next review date of April 19.
2. The program will select this customer for processing, and will update the next
review date to April 26.
On April 22, run the Periodic Credit Review program for CAD currency.
1. Vision Operations now has a next review date of April 26, which is greater than the
system date. This customer fails the first test of eligibility.
2. Next, the program checks if a previous CAD case folder with a Periodic source
exists. A case folder with a date of April 12 is found.
3. The program uses the review cycle (weekly) and previous date (April 12) to
calculate the next review date, specifically for CAD currency. The newly calculated
date is April 19, which is less than the submission date of April 22. The customer is
selected for processing.
Related Topics
Processing Credit Reviews, page 4-1
This chapter describes how other Oracle E-Business Suite applications integrate with
Oracle Credit Management for their credit needs.
This chapter covers the following topics:
• E-Business Suite Integration Overview
• Oracle Order Management Integration
• Oracle Lease and Finance Management Integration
• Oracle Loans Integration
2. Re-enter the recommendations defined in the previous step using a second lookup
code, AR_CMGT_RECOMMENDATIONS. Credit analysts access these
recommendations when defining automation rules.
Tip: (Lease and Finance Management only) Use the Tag field in the
Receivables Lookups window to assign a URL or OA function to a term
credit recommendation. Later, when a credit analyst picks a
recommendation that has an assigned URL or OA function, the analyst
is presented with a new page where data can be entered and stored in
Lease and Finance Management. This is used when an analyst is
making a conditional approval. See: Approving a Credit Review with
Conditions, page 5-6.
2. A credit review request is sent to Oracle Credit Management via the Create Credit
Request API.
4. Once a credit score has been calculated by the assigned scoring model, either Credit
Management or a credit analyst assigns one or more recommendations to the case
folder. The case folder is submitted.
• Once approved, Credit Management closes the case folder and assigns a status
of Approved to the recommendations.
7. Order Management subscribes to the business event and, depending on the final
credit decision, can take the order off hold or not, increase the customer's credit
limit, and so on.
2. A credit review request is sent to Oracle Credit Management through the Create
Credit Request API.
4. Once a credit score has been calculated by the assigned scoring model, either Credit
Management or a credit analyst assigns one or more recommendations to the case
folder.
5. Recommendations can carry conditions that can request changes in certain terms of
the lease application. For example, perhaps the credit analyst disagrees with the
offered payment plan.
In this conditional approval flow:
• The credit analyst tells the sales representative to fix the lease payment plan.
The analyst assigns the case folder to the sales representative via the Credit
Scheduler (provided that the sales representative has been assigned the credit
analyst role).
The sales representative views the case folder and add the recommendation,
Update Payment Plan, for example. This recommendation immediately opens a
new user interface where the payment plan details can be updated.
Updates are stored in Lease and Finance Management.
• If the sales representative does not have access to the case folder, then the credit
analyst and sales representative discuss internally, then the credit analyst
updates the payment plan details accordingly.
6. Once the conditions are fulfilled, the case folder is submitted for approval.
9. Lease and Finance Management subscribes to the business event and implements
the final recommendation for the lease application.
10. In Lease and Finance Management, the sales representative can also:
• Resubmit the lease application due to pricing parameter changes on the quote.
The sales representative accordingly selects the Appeal, Rejection Appeal, or Re-
Submission credit request reason.
The appeal or re-submission from Lease and Finance Management creates a new
credit request, which undergoes the same general process in Credit Management as
the original request.
• A new lease application records the data of the appeal or re-submission.
References to the application being appealed are passed into Credit
Management.
At any time in the entire credit review process, the sales representative can withdraw
the lease application in Lease and Finance Management. The selected withdrawal
reason is passed to Credit Management.
The credit review request is automatically frozen in Credit Management, regardless of
the stage of the process and whether the credit review has completed or not. The
withdrawn credit application or case folder is purged from the credit analyst's work
queue; the pending approvals are deleted from the approver's queue, or the approvers
are notified of the cancellation of the lease application.
Note: The case folder number is the same as the loan number. Co-
borrower details are totaled with the primary borrower's data
points in a single, combined case folder.
Data points from Loans are listed as Additional Data Points, and can use PL/SQL
functions to automatically derive data point values.
If, at any time, the workflow processing fails, Credit Management assigns a credit
analyst to the credit review for manual processing.
4. Once a credit score has been calculated by the assigned scoring model, either Credit
Management or a credit analyst assigns one or more recommendations to the case
folder, and submits and closes the case folder.
5. In Oracle Loans, the loans agent reviews the case folder, especially the
recommendations.
• If the credit request is approved, the agent reviews the loan application and
submits it to the loans manager for approval.
• If the recommendation is to reject the loan application, the loans agent can
continue to seek approval from the loans manager, or resubmit the loan
application for credit review after making modifications to the loan application
based on the recommendations.
6. If the loans agent decides to resubmit for credit review, the re-submission from
Loans creates a new credit request, which undergoes the same general process in
Credit Management as the original request.
A case folder associated with the re-submission is generated in Credit Management.
This case folder is a duplicate of the closed case folder from the original credit
request, plus additional data for the new request.
• Define the rules that indicate how credit analysts are automatically assigned to case
folders. Credit Management evaluates the rules that you create in sequential order.
Use the Create Rule page to create your credit analyst assignment rules.
On the Create Rule page, enter the matching criteria for the rule. Then, in the Result
region, enter the credit analyst who will be assigned when the rule criteria is met.
When a credit analyst is required, the appropriate assignment is determined using the
following sequence:
1. The assignment rules that you defined using the Rules Engine are executed.
3. If no default credit analyst exists, then Credit Management uses the default credit
analyst on the assigned customer profile class.
If, after the above steps, Credit Management fails to identify a credit analyst, then
Credit Management automatically routes the credit review to the Credit Scheduler. A
credit manager must log on using the Credit Scheduler responsibility to manually select
a credit analyst.
Reassignments made through the Reassign Credit Reviews page do not modify credit
analyst assignments in the customer profile classes. As a result, the assigned credit
analyst from the profile will default on subsequent case folders or credit applications
submitted for the customer.
To change the credit analyst default for future credit requests, manually update the
customer profile classes. Or, submit the Reassign Credit Analyst program.
Access the Reassign Credit Reviews page using the Credit Scheduler responsibility.
Enter search criteria, then select one or more reviews for reassignment. Reassigned
reviews appear in assignees' queues without additional notification.
Tip: This process is different from using the Reassign Credit Reviews
page, which selectively moves credit applications and case folders
between credit personnel, and does not affect the customer profile class.
See: Reassigning Credit Reviews, page 6-2.
Selected Parameters
Credit Analyst From: Select the credit analyst that you want to remove from
assignment.
Credit Analyst To: Select the new credit analyst that you want to use for this
reassignment.
This chapter describes additional setup steps to consider when implementing Oracle
Credit Management.
This chapter covers the following topics:
• Defining Credit Usage Rule Sets
• Defining Credit Hierarchies
• In Oracle Credit Management, credit usage rule sets ensure that all transactions for
the specified currencies are converted to the credit currency and included in data
point calculations in the case folder.
For example, if a customer is assigned the Default profile class with a credit usage rule
set that includes USD, EUR, and CAD, then any transactions of those currencies are
included in that customer's case folder for data points such as Count of Open Invoices
or Amount of Open Invoices.
In Oracle Credit Management, credit usage rules are required. Even if you perform credit
reviews in only one currency, or conduct your business in only one currency, you must
still set up one credit usage rule.
Usage Examples
Example 1
The most typical usage will be as follows:
• In this case, the credit application currency can be either USD or CAD.
• If you enter a CAD credit application, then all transactions in both CAD and USD
are included in data point calculations.
Example 2
Perhaps you would like to maintain two different credit policies for a single customer,
based on territory. In this case, credit usage rules let you set up two different credit
policies and have two different credit limits. To accomplish this:
• Set up one credit usage rule set with a main currency, such as USD, and attach USD
and CAD. Set up another credit usage rule set with a main currency, such as EUR,
and attach EUR, CHF, and SEK.
• Let's say an order hold occurs on an order in SEK. The resulting currency on the
credit application is SEK.
• Due to the credit usage rules, Credit Management selects transactions in EUR, CHF,
and SEK.
Note: The previous example also applies in the case where a particular
currency fluctuates to a great extent. In such a case, for the purposes of
a credit review, you should isolate that currency's transactions from the
rest of your customer's transactions. Otherwise, what might be a high
credit score on one day could be drastically lower on another day,
simply due to the one fluctuating currency.
After you set up credit usage rule sets, you then assign the rule set to a credit profile
class, which you can finally assign directly to a customer.
2. Then, use the Assign Credit Usage Rules window to assign a credit usage rule set or
sets to each combination of customer and currency, as necessary.
The currencies default from the profile amounts in the assigned customer profile
class.
Note: Credit usage rules are mutually exclusive for a customer. For
example, if you assign credit usage rule A (USD and CAD) to USD,
then you cannot also assign the same credit usage rule to CAD.
3. Assign the same credit usage rule sets to the customer's sites if you plan to create
credit applications for individual customer sites. Otherwise, a case folder might not
be generated when you submit a credit application for the site.
See: Defining Credit Usage Rule Sets, Oracle Order Management Implementation Manual
and Assigning Credit Usage Rule Sets, Oracle Order Management Implementation Manual.
Related Topics
Overview of Oracle Credit Management Setup, page 3-1
You can define a credit hierarchy of parties, party relationships, hierarchy levels,
accounts, and account sites. Typically, the party object and party subject in a credit
relationship represent a parent and child, or HQ and division hierarchy. For each entity
in the hierarchy, you can view credit information, such as credit hold status, credit
limits by currency, and credit review cycle.
Using Relationship Manager, you assign to your entities an existing relationship type,
such as Global Ultimate, or your own user-defined Credit Management relationship
type. You then link the relationships to Credit Management by assigning the
Related Topics
Profile Options and Profile Option Categories Overview, page A-1
Overview of Oracle Credit Management Setup, page 3-1
Relationship Manager Overview, Oracle Trading Community Architecture User Guide
This appendix describes setting profile options for Oracle Credit Management.
This appendix covers the following topics:
• Profile Options and Profile Option Categories Overview
• Profile Option Category and Profile Options Descriptions
Oracle Credit Management Profile Options and Profile Option Categories A-1
The tables in this section provide profile option information as follows:
• The Default column displays either the default profile option value in italics, or No
Default if none exists.
• The User Access column indicates whether you can view or update the profile
option.
• View Only: You can view the profile option but cannot change it.
AR: Allow No Update View Only View Only Update View Only
Summary Default
Table Refresh,
page A-2
Oracle Credit Management Profile Options and Profile Option Categories A-3
B
Credit Management Application Workflow
• If a credit analyst cannot be identified, then the workflow notifies the person
assigned to the Credit Scheduler role that a credit analyst assignment is required.
The Credit Scheduler is a workflow role used in Credit Management to assign
credit tasks to credit analysts.
Related Topics
Setting Up the Credit Management Application Workflow, page B-2
Credit Management Application Workflow Main Process Activities, page B-3
Processing Credit Reviews, page 4-1
2. Install the Oracle Workflow Builder client component program if you want to
modify the Credit Management Application Workflow. For more information on
workflow installations, see: Overview of Setting Up, Oracle Workflow Administrator's
Guide.
7. From the Submit Request window using the System Administrator's responsibility,
schedule the Workflow Background Process concurrent program to run on a
regular basis:
• Choose the AR Credit Management Application Process item type.
Related Topics
Credit Management Application Workflow, page B-1
Credit Management Application Workflow Main Process Activities, page B-3
Processing Credit Reviews, page 4-1
• If automation rules exist, then the rule validations are executed, leading to
recommendations. This function then calls the Automation Subprocess.
See: Automation Subprocess, page B-6.
Related Topics
Credit Management Application Workflow, page B-1
Manual Subprocess, page B-6
Automation Subprocess, page B-6
Manual Subprocess
Related Topics
Credit Management Application Workflow, page B-1
Processing Credit Reviews, page 4-1
Automation Subprocess
Related Topics
Credit Management Application Workflow, page B-1
Processing Credit Reviews, page 4-1
Approval Subprocess
Related Topics
Credit Management Application Workflow, page B-1
Processing Credit Reviews, page 4-1
This appendix describes business events that you can use with Oracle Credit
Management.
This appendix covers the following topics:
• Credit Request Business Events
• Credit Request Events
Note: Credit request events are raised by the Credit Request processing
workflow engine; users should not manually raise them.
Setup
For example, if you want to subscribe your business process (such as custom
recommendations) to the implementation of the default recommendations for a credit
request, then you should subscribe your routine or custom program (also known as the
Deferred Subscriptions
The Workflow Release 2.6 Business Event System allows subscriptions to be executed in
deferred mode so that no overhead is added to the process raising the event. For Credit
Request business events, it is recommended that user subscriptions be executed in the
deferred mode.
One of the mechanisms to defer a subscription would be by setting the phase number of
a user-defined subscription to greater than 99. For additional details on different
mechanisms for deferring a subscription, see: Event Subscriptions, Oracle Workflow
Developer's Guide.
When the credit request processing flow raises an event for a deferred subscription, the
event message is sent to the deferred queue.
Subscriptions will be executed when the "Workflow Agent Listener" with the parameter
"WF_DEFERRED" is executed. When this concurrent program is executed, every
subscription from every instance of events in the DEFERRED queue at that moment will
be executed.
This concurrent program is seeded in the request group of the System Administrator
responsibility.
Coding a Subscription
How to subscribe
Per Oracle Workflow coding standards, two kinds of subscriptions exist for use:
• Oracle Workflow Release 2.6 rule function (which is a PL/SQL function)
• Workflow processes
For information about the standards for the event subscription rule function, see:
Standard API for an Event Subscription Rule Function, Oracle Workflow Developer's
Guide.
USER_ID The user ID of the initial session that had initiated the
credit request
SOURCE_COLUMN1 The unique identifier of the entity for which the credit
request was created
SOURCE_COLUMN2 The unique identifier of the entity for which the credit
request was created
SOURCE_COLUMN3 The unique identifier of the entity for which the credit
request was created
The org_id, user_id, resp_id, resp_appl_id, and security_group_id parameters let users
re-create the application environment at the moment the credit request was raised. This
is useful if your business logic depends on some application context parameters, such as
for a multi-organization environment.
You can use FND_GLOBAL.APPS_INITIALIZE(<USER_ID>, <RESP_ID>,
<RESP_APPL_ID>, <SECURITY_GROUP_ID>) to re-create the original application
context in your process.
2. <Phase> indicates the current stage in the life cycle of a credit request in which an
action is going to be performed.
3. <Action> indicates the action performed in the current phase of the credit request.
This appendix describes the seeded data points in Oracle Credit Management.
This appendix covers the following topics:
• Oracle Credit Management Data Points
• Business Information and Credit Data Points
• Financial Data Data Points
• References Data Points
• Guarantors Data Points
• Venture Funding Data Points
• Collateral Data Points
• Billing and Payments Data Points
• Aging Data Points
Credit ? ? ? ?
Exposure
VAT No Yes
Registration
Number
Related Topics
Oracle Credit Management Data Points, page D-1
Short-Term No No
Investments
Intangible Assets No No
Goodwill No No
Retained Earnings No No
Common Stock No No
Preferred Stock No No
Depreciation No No
Expense
Amortization No No
Expense
Extraordinary Gains No No
Extraordinary Losses No No
Interest Income No No
Interest Expense No No
Dividends No No
Current Ratio No No
Quick Ratio No No
Gross Profit No No
Operating Profit No No
Profit Margin No No
Related Topics
Oracle Credit Management Data Points, page D-1
Guarantors No Yes
Collateral No Yes
Related Topics
Oracle Credit Management Data Points, page D-1
Country No No
Address No No
Province/State No No
Postal Code No No
Key Executive No No
Contact No No
Phone No No
Fax No No
Email No No
Currency No No
Notes No No
Capital Stage No No
Related Topics
Oracle Credit Management Data Points, page D-1
Related Topics
Oracle Credit Management Data Points, page D-1
This table includes the Billing and Payments data points that are time-sensitive. All data
points are automatically derived. The data point category is Invoice.
High Credit Yes Yes ar_trx_summa op_bal_high_wat This column value contains
Amount ry ermark the highest Open
Receivables Balance for the
specific Account, Site,
Currency and date
(identified by as_of_date).
Last Payment Yes Yes ar_trx_summa last_payment_a Amount of the most recent
Amount ry mount cash receipt (based on
receipt date)
Last Payment No Yes ar_trx_summa last_payment_da Date of the most recent cash
Date ry te receipt (based on receipt
date)
Cash Receipts Yes Yes ar_trx_summa total_cash_receip Sum of the amounts of all
Amount ry ts_value Cash Receipts
Invoices paid Yes Yes ar_trx_summa inv_paid_amoun Sum of the total amount
Amount ry t paid against closed invoices
Related Topics
Oracle Credit Management Data Points, page D-1
Note: Aging buckets and their values are available for the checklist, but
the bucket names and the number of buckets are based upon Credit
Management system option settings.
Open Invoices Yes Yes ar_trx_bal_su op_invoices_co count of the open payments
Count mmary unt schedules (installments) of all
the Invoices
Open Debit Yes Yes ar_trx_bal_su op_debit_mem count of the open payments
Memos Count mmary os_count schedules (installments) of all
the Debit Memos
Open Deposits Yes Yes ar_trx_bal_su op_deposits_co count of the open payments
Count mmary unt schedules (installments) of all
the Deposits
Open Bills Yes Yes ar_trx_bal_su op_bills_receiv count of the open payments
Receivables mmary ables_count schedules (installments) of all
Count the Bills Receivables
Open Credit Yes Yes ar_trx_bal_su op_credit_mem count of the open payments
Memos Count mmary os_count schedules (installments) of all
the Credit Memos
Past Due Invoice Yes Yes ar_trx_bal_su past_due_inv_i count of the open payments
Count mmary nst_count schedules (installments) of all
the Invoices
Disputed Invoice Yes Yes ar_trx_bal_su inv_amt_in_dis sum of the amount in dispute
Amount mmary pute on open payment schedules
(installments) of all the
invoices
Receipts at risk Yes Yes ar_trx_bal_su receipts_at_risk sum of cash receipt amounts
amount mmary _value
Related Topics
Oracle Credit Management Data Points, page D-1
This appendix describes guidelines for PL/SQL packages and functions that derive data
point values.
This appendix covers the following topics:
• Guidelines for Deriving Data Point Values
• The function should include exceptions handling. For errors, include the error
message in the OUT variable. Workflow will use the message to send an
appropriate notification to the credit analyst.
FUNCTION get_data_points(
x_resultout OUT NOCOPY VARCHAR2,
x_errormsg OUT NOCOPY VARCHAR2)
RETURN VARCHAR2 AS
l_credit_classification varchar2(30);
pg_ocm_add_dp_param_rec OCM_ADD_DATA_POINTS.OCM_ADD_DP_PARAM_REC_TYPE;
BEGIN
x_resultout := FND_API.G_RET_STS_SUCCESS;
SELECT credit_classification
INTO l_credit_classification
FROM hz_customer_profiles
WHERE party_id = pg_ocm_add_dp_param_rec.p_party_id;
pg_ocm_add_dp_param_rec.P_data_point_value := l_credit_classification;
RETURN l_credit_classification;
EXCEPTION
WHEN NO_DATA_FOUND THEN
l_credit_classification := NULL;
WHEN OTHERS THEN
x_resultout := FND_API.G_RET_STS_UNEXP_ERROR;
x_errormsg := sqlerrm;
END get_data_points;
END ocm_data_points;
All APIs are PL/SQL APIs that create or update objects in the Credit Management
system based on the specified parameters. The APIs do not cause performance
degradation to the main flow calling the API.
Major Features
The major features of these public APIs are:
• Easy to administer and maintain the consumer product's processes.
Related Topics
Credit Request Business Events, page C-1
Input
Standard API parameters: 4
Credit Request parameters: 35
Output
Standard API parameters: 3
Credit Request parameters: 1
p_init_msg_list IN VARCHAR2 FND_API. Allows API callers to request that the API
G_FALSE executes initialization of the message list
on their behalf.
p_credit_request_st IN VARCHAR2 Credit request status. Possible values are SAVE and
atus (30) SUBMIT.
p_source_org_id IN NUMBER
p_source_user_id IN NUMBER
p_source_resp_id IN NUMBER
p_source_resp_app IN NUMBER
ln_id
p_source_security_ IN NUMBER
group_id
p_source_column1 IN VARCHAR2 Unique identifier of the entity for which the credit
(150) request was created.
p_source_column2 IN VARCHAR2 Unique identifier of the entity for which the credit
(150) request was created.
p_source_column3 IN VARCHAR2 Unique identifier of the entity for which the credit
(150) request was created.
p_review_cycle IN VARCHAR2
(30)
p_score_model_id IN NUMBER
Parameter Data-type
check_list_id NUMBER
credit_analyst_id NUMBER
case_folder_id NUMBER
stock_exchange VARCHAR2(50)
current_stock_price NUMBER
stock_currency VARCHAR2(30)
market_capitalization NUMBER
market_cap_monetary_unit VARCHAR2(15)
pending_litigations NUMBER
bond_rating VARCHAR2(30)
legal_entity_name VARCHAR2(240)
entity_type VARCHAR2(30)
recommendation_name VARCHAR2(30)
attachment_flag VARCHAR2
status VARCHAR2
request_id NUMBER
3. Get Recommendations
p_init_msg_list IN VARCHAR2 FND_API. Allows API callers to request that the API
G_TRUE executes initialization of the message list
on their behalf.
The following table lists the parameters for the Get Score API:
The following table lists the parameters for the Include Data Points API:
The following table lists the parameters for the Get Recommendations API:
The following table lists the parameters for the Submit Case Folder API:
• Some output values that the API caller might want to use (this is different for
different API routines and is described in API Usage, page F-3)
Return Status
The return status (x_return_status) of the API informs the caller about the result of the
operation (or operations) performed by the API. The different possible values for an
API return status are:
• Success (FND_API.G_RET_STS_SUCCESS)
• Error (FND_API.G_RET_STS_ERROR)
The following section describes the different values of return status and their meanings.
Success
A success return status means that the API was able to perform all the operations
requested by its caller. A success return status may be accompanied by messages in the
API message list which will be informative.
Error
An error return status means that the API failed to perform some or all of the operations
requested by its caller. An error return status is usually accompanied by messages
describing the error (or errors) and how to fix it.
In most cases, you should be able to take corrective action to fix regular, expected errors
such as missing attributes or invalid date ranges.
Unexpected error
An unexpected error status means that the API has encountered an error condition it
did not expect or could not handle. In this case, the API is unable to continue with its
regular processing. Examples of such errors are unrecoverable data consistency errors,
memory errors, and programming errors (such as attempting a division by zero).
In most cases, only system administrators or application developers can fix these
unexpected errors.
Messages
The APIs put result messages into a message list. Programs calling the APIs can then get
the messages from the list and process them by issuing them, loading them into a
database table, or writing them to a log file.
Messages are stored in an encoded format to let the API callers find message names
using the standard functions provided by the message dictionary. It also allows the
using, 4-18
A viewing attachments, 4-20
credit analysts
APIs
assigning to accounts, 2-12
Create Credit Request, F-3
assigning to a credit review, 4-2
Credit Request Creation, 4-2
defining, 2-1
Get External Decision, F-11
reassigning, 6-3
Guarantor, F-9
credit applications
Update Credit Request, F-7
collecting data, 4-4
Withdraw Credit Request, F-8
creating, 4-5
AR: Allow summary table refresh profile option,
entering data, 4-8
A-2
in-process applications, 4-7
AR: Credit Hierarchy Type profile option, A-3
saved applications, 4-7
AR: Default Credit Management Currency
submitting, 4-11
profile option, A-3
window reference, 4-6
Assign Customer Credit Classification program,
workflow, B-1
2-12
credit checklists
attachments
adding D&B data points, 3-9
to case folders, 4-20
collecting data, 4-3
to credit applications, 4-8
defining, 3-5
automation rules
for case folders, 4-4
assigning, 3-17
for credit applications, 4-3
defining, 3-17
credit data
analyzing, 4-16
C
collecting, 4-3
case folders credit hierarchies
adding analysis notes, 4-19 defining, 7-3
collecting data, 4-12 Credit Request Creation API, 4-2
credit checklists, 4-4 credit reviews
entering data, 4-15 analyzing credit data, 4-16
manually creating, 4-16 assigning an analyst, 4-2
refreshing data, 4-20 calculating scores, 4-18
retrieving, 4-14 collecting data, 4-3
Index-1
credit applications, 4-3, 4-4 Oracle Approvals Management, B-1
credit summaries, 4-20 Oracle Lease and Finance Management
initiating, 4-2 integration, 5-3
overview of processing, 4-1 Oracle Loans
reassigning, 6-2 integration, 5-6
recommendations, 4-21 Oracle Order Management
scheduling periodic reviews, 4-24 credit usage rule sets, 7-1
Credit Scheduler, 2-12, 4-11 Oracle Trading Community Architecture
credit summaries D&B integration, 2-3, 3-9
viewing, 4-20 Relationship Manager, 7-3
credit usage rule sets, 7-1 overview, 1-1
Customer Profile Classes window, 2-12
customers P
updating profile classes, 2-12
pages
Automation Rules, 3-17
D Checklists, 3-5
D&B Credit Analysis, 4-16
See Dun & Bradstreet Credit Summary, 4-20
data points, 3-2 Reassign Credit Reviews, 6-2
assigning scoring attributes, 3-10 scoring models, 3-9
assigning weights, 3-11 performance
Data Quality Management reviewing, 3-26
search, 4-5 Periodic Credit Review program, 4-24
setting up search, 2-3 Periodic Review Eligibility report, 4-26
days sales outstanding profile option categories
system option, 2-9 Credit Policies Management, A-2
Dun & Bradstreet description, A-1
adding data points to checklists, 3-9 overview, A-1
profile options
E AR: Allow summary table refresh, A-2
AR: Credit Hierarchy Type, A-3
E-Business Suite integration, 5-1
AR: Default Credit Management Currency, A-
3
G
descriptions, A-1
Get External Decision API, F-11 overview, A-1
Guarantor API, F-9 programs
Assign Customer Credit Classification, 2-12
L DQM Staging, 2-3
lookups, 2-10 Periodic Credit Review, 4-24
Reassign Credit Analyst, 6-3
N
R
notes
analysis notes, 4-19 Reassign Credit Analyst Program, 6-3
Reassign Credit Reviews page, 6-2
recommendations
O
defining, 3-20
Index-2
defining for integrated applications, 5-1 window reference
implementing, 4-23 Applications, 4-6
making, 4-21 windows
setting up, 3-19 Customer Profile Classes, 2-12
relationships Withdraw Credit Request API, F-8
defining credit hierarchies, 7-3 workflows
reports Credit Management Application, B-1
Periodic Review Eligibility, 4-26 Credit Management Application activities, B-3
Resource Manager, 2-1 Credit Management Application setup, B-2
rules Credit Scheduler, 4-11
automation rules, 3-17
credit usage rule sets, 7-1
S
scores
credit, 4-18
scoring models
assigning scoring attributes, 3-10
assigning weights, 3-11
automation rules, 3-17
defining, 3-9
setting up
Assign Customer Credit Classification
program, 2-12
assigning credit analysts, 2-12
automated review example, 3-23
automation rules, 3-17
Credit Management Application Workflow, B-
2
credit usage rule sets, 7-1
defining checklists, 3-5
defining credit analysts, 2-1
defining credit hierarchies, 7-3
defining scoring models, 3-9
lookups, 2-10
overview, 3-1
Reassign Credit Analyst program, 6-3
system options, 2-7
updating profiles, 2-12
system options, 2-7
U
Update Credit Request API, F-7
Index-3