Here are Top 12 Issue , you may observe while you support Oracle Credit Management.

Two Major Enhancement in Credit Management in R12.2

1. Credit Tolerance Limits
   Tolerance limits Field In credit check rule setup. This provided functionality to define credit tolerance limits to prevent credit check holds from getting reapplied on orders that were previously released from credit check hold. Changes in order amounts are compared to tolerance limits, as defined in the credit check rule. Reapplication of credit check hold is prevented if the change in order amount is within the specified tolerance limit
2. Credit Hold Based on Bill To Customer
   A new system parameter “Apply Credit Hold Based On“¨ has been added. Options are:
   • Sold To Customer
   • Header Level Bill To Customer
   • Line Level Bill To Customer

This allows the customers to place orders on credit hold if the Bill To Customer is on credit hold. Additionally, customers can decide to place the Order on credit hold based on the header level Bill To Customer, or Order line on credit hold based on the line level Bill To Customer.

This new feature is extension of existing capability of placing orders on credit hold if the Sold To Customer is on credit hold ‘Sold To Customer is the default value and maintains existing behavior.

You can refer to RCD for more insights.

Oracle Credit Management have mainly three integration touce-point for credit needs with these EBS appliucation:

1. Oracle Order Management
2. Oracle Lease Management
3. Oracle Loans

• Oracle Order Management : This have integration for Order Management Credit Review.As we know Credit Management is used by Credit/Receivables analysts to allow more in depth management of customer credit worthiness and credit availability.Credit Management allows the C/R analysts to assign a level of credit worthiness/risk to customer accounts.In OM when a sales order is placed on credit check failure hold, a case folder is created in Credit Management
  • Setups to be verified for Review from Order Management
    • Credit check checkbox should be checked in payment terms
    • Setup order credit limit in customer standard page for the currency for which credit application needs to be created.
    • Checklist for review type order hold needs to be created along with credit classification of the customer.
    • Make sure credit check rule is selected on Order Transaction type.
• Oracle Lease Management :Lease applications are created and managed in Lease and Finance Management for the purpose of obtaining credit approval from Oracle Credit Management. A lease application contains both a lease sales quote and a credit application. Once a prospect has accepted a lease sales quote, you can convert the lease quote into a lease application, add customer credit data and pricing information and submit it for approval. You can also create a lease application without converting a lease sales quote.
  • Setups to be verified for Review from Lease Management
    • Lease application template has been setup in Lease for credit classification for the customer with review purpose as New Deal Lease Application
    • End of term option should be set up in lease
    • Checklist for review type new deal lease application needs to be created along with credit classification of the customer.
• Oracle Loans – Oracle Loans integrates with Oracle Credit Management to perform credit reviews for loan application requests and decide to approve or reject it. The Credit Review option is set at the Loan Type level. You can either create a loan with a loan product that requires credit review or request review while creating or updating a loan. You must complete as much of the application including recording assets, financial data, co-borrowers, guarantors and other loan details to request credit review. Loans displays information from Oracle Credit Management in the Borrower Summary.
  • Setups to be verified for Review from Loans
    • Loan type should have credit review enabled
    • Checklist for review type Loan needs to be created along with credit classification of the customer.

A reader question:

Can You help me for one of senarios for my client :

“I have single customer ABC .For Same customer we have set credit limit of 50000 USD, but with same customer we are doing two business first of finish goods sold and second is service.So we don’t want to give that much credit limit to service business. that’s why we want to set two credit limit for same customer. Is there any way to Handle this ?How can two credit limits be set for one (the same) customer?

Answer : Here is summary of Requirement , for same customer , need two credit limit

• The First is Goods Sold
• The Second is Service

If you have such requirement , then you may be get disappointed. Currently OCM application is not designed to handle such requirement. Though Oracle have enhancement request for Future releases . Thats means, Future release might have TWO CREDIT LIMIT ON SINGLE CUSTOMER .Sound Intresting .

Therefore , for this case what you can do as workaround is to setup multiple customer accounts under that same party and then define separate credit limits. This way you can use different customer accounts for different types of businesses. Hope this helps.

Oracle Credit Management gives you the information and tools you need to monitor and evaluate the creditworthiness of your customers and make informed credit decisions faster.

CREATING A NEW CREDIT APPLICATION

To create a new credit application, you must first enter your search criteria and then select the credit applicant . This procedure capitalizes on the data that you already maintain by automatically populating the credit application with basic information about the applicant.

When you open a new application , Credit Management automatically prefills the application with certain basic information from the account record that you selected, such as account name, account number, address, requestor name, and so on.

Only those parties (both customers and prospects) who are defined with the customer type of Organization are included in the search results.

If you select a customer at the top organization level, then data for all accounts that are related to the organization will be consolidated for the credit analysis. Or, if you select a specific customer account from the search results, then the data for all sites that are associated with the account will be consolidated.

NO CASE FOLDER UPON CREDIT APPLICATION CREATION – WAY TO CHECK

When you create a credit application but do not get a case folder, what should you do?

Look for script wfstatus.sql (You can find the wfstatus.sql under $FND_TOP/sql/wfstatus.sql) , to get information about what may have occurred with the creation of your case folder during the workflow process.

In this script , the first parameter is the itemtype.

• The itemtype for Oracle Credit Management (OCM) is ARCMGTAP.
• The second parameter is the itemkey. There are two ways to get the itemkey:

If you check the workflow status and see that there is an error existing for your process, you can see the itemkey as part of the error.

For example, if your error looks something like this:

AR_CMGT_WF_ENGINE.IMPLEMENT_RECOMMENDATION(ARCMGTAP, 100424, Error while applying Removing Hold for Party : 76902 Cust Account id 107716 Site Use Id ONTOE_HOLDS_AUTHORIZATION_FAILEDACTIONRelease, ORA-0000: normal successful completion) Wf_Engine_Util.Function_Call(ar_cmgt_wf_engine.implement_recommendation, ARCMGTAP, 100424, 158878, RUN)

• You will see both the itemtype = ARCMGTAP and right next to it the itemkey = 100424 < /FONT > .

If you do not see any errors, next step for you is to get the itemkey by using the CREDIT_REQUEST_ID using this query.

select APPLICATION_NUMBER,
CASE_FOLDER_NUMBER,
CREDIT_REQUEST_ID
from AR_CMGT_CREDIT_REQUESTS
where APPLICATION_NUMBER = ‘&number’;< /FONT >

FYI… WHEN CASE FOLDER IS MISSING FOR THE APPLICATION SUBMITTED

1. Make sure the checklist actually exists for the credit classification and review type provided in the application.
2. In some cases checklist exists but it may not be submitted. It may only be saved. It is also possible it may be end dated.
3. Make sure credit assignment rules are assigned to the profile class/customer/bill to location.
4. It is possible that your customer has multiple currency transaction rates for which currency exchange rates must be missing.
5. Your checklist/scoring model to the checklist may have and additional customized data point for which setup may be incorrect.
6. Workflow activities may have been stopped. Please run Workflow background process for item type “AR: Credit Management Application Process”
7. In case of credit review from order management review type will be common ‘Order Hold’ for all applications hence there should be a checklist for these review type with customer applicable credit classification.
8. Some things may be mandatory to be provided in application like bank references, trade references, financial data etc. which may not be provided while submitting application. This mandatory data is required for the checklist created.

What needs to be done if you are implementing Credit Managment but we have Order Management on a legacy system? If a Sales order is on credit hold at legacy, how will that information come to the Credit analyst to do a credit Analysis before deciding to release the credit hold.

You will need to use the Credit Management API to create a credit application from your OM system.
You will need to call this API from your legacy custom code when ever the order goes on hold due to credit limits to create the Credit Application.

The Credit Management public APIs includes five APIs:

• Create Credit Request API :The ar_cmgt_credit_request_api.create_credit_request routine is used to create a credit request for initiating a credit review for a party, account, or account site.
• Update Credit Request API :The ocm_credit_request_update_pub routine is used to update an existing credit request for a party, account, or account site.
• Withdraw Credit Request API :The ocm_credit_req_withdraw_pub routine is used to withdraw an existing credit request for a party, account, or account site.
• Guarantor API :The ocm_guarantor_pub routine is used to automatically submit a credit application for a guarantor that is included on a credit application or in a case folder.
• Get External Decision API :The ocm_get_extrl_decsn_pub routine is used to bypass Credit Management’s scoring functionality and extract case folder contents for scoring by an external scoring engine.

Setting up Credit Management for OM

If you are using Oracle OM , these are mandatory setup

• Credit check checkbox should be checked in payment terms
• Setup order credit limit in customer standard page for the currency for which credit application needs to be created.
• Checklist for review type order hold needs to be created along with credit classification of the customer.
• Make sure credit check rule is selected on Order Transaction type.

Here is a summary of steps to set up Oracle Credit Management

1. Maintaining Customer Data :Oracle Credit Management employs the Data Quality Management (DQM) match rules to identify how search results should be displayed in the application’s search screens
   • DQM Match Rule
   • Run DQM Staging
2. Defining Credit Analysts :Credit analysts assist in the resolution of credit-related issues and evaluate the creditworthiness of your customers and prospects. Credit analysts can view credit applications and case folders in Oracle Credit Management, and can submit recommendations after concluding a credit analysis.
   • Import/assign Credit Analysts – First define your credit analysts as employees in Oracle Human Resources Management System (HRMS).Next, import employees from HRMS into Resource Manager and assign roles.Two seeded roles exist for Credit Management:
     • Credit Analyst :You can assign the credit manager role to a credit analyst
     • Credit Manager : This is setup functionality
3. Credit Mgmt System Options : You can define these Oracle Credit Management system options.
   • Aging Bucket :Specify which aging buckets to use when presenting aging data in Credit Management. Credit Management presents aging data as data points in several pages, such as from the Aging Details and Credit Summary pages.
     • Take a note, Credit Management calculates its own aging data after pulling certain pieces of information from Oracle Receivables tables.
     • Take a note , Credit Management and Oracle Receivables aging data can be different beacuse of due dates and collection dates.In Receivables, the primary concern is around collection
   • Default Customer Credit Classification :Credit classification assignments can either be assigned by a previously completed credit review, or assigned on the customer profile. Default Value is High Risk
   • Period for Time Sensitive Data :Select the period for which credit data will be collected into the summary tables and used in scoring during a credit analysis. Reviewing summarized order, invoice, and payment data over a period of time can provide you with an overall picture of a customer’s past credit relationship with you, and can help to predict future performance. Default Value is 12
   • Application Numbering Option :Indicate if you want Credit Management to automatically assign a number to each credit application.Default Value is YES
   • Exchange Rate Type :Pick either default exchange rate type that Credit Management will use to convert foreign currency data points to your credit currency during a credit analysis. You can select Corporate, Spot, or User.Default Value is Corporate
   • DSO Days : You have to indicate the time period that Credit Management uses to calculate Days Sales Outstanding (DSO) and Delinquent Days Sales Outstanding (DDSO).The default is 90 days.
4. Define Hierarchical Relationship :To provide global credit limits that are shared by some or all entities within a complex, multinational organization, you can define credit relationships between parties using Oracle Trading Community Architecture Relationship Manager.
5. Credit Mgmt Profile Options
6. Populate Summary Tables
7. Setup Credit Usage Rules
   • Credit usage rule sets are used as follows:
     • In Oracle Order Management, credit usage rule sets define the set of currencies that will share a predefined credit limit during the credit checking process, and enable the grouping currencies for global credit checking.
     • 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.
   • 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.
8. Remove existing credit limits from Profile Classes and propagate changes to all customers (Optional) : This setup is used to pull and tag dafault setting of customer master.
9. Assign Credit Info to Profile Classes (Default Credit Analyst, Default Classification)
   • Updating Customer Profile Classes : in AR Customer Profile Classes window, use the Collectors region on the Profile Class tab to assign credit information to your customer profile classes:
   • Classification :use the Assign Customer Credit Classification program.
   • Periodic review cycle :Update Periodic Credit Review Program.
   • Analyst : you can 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.
     • Take a note, Oracle Credit Management looks for an assigned credit analyst at the customer profile, only after other locations fail to provide an assignment.
10. Assign Credit Usage Rule
11. Credit Management Application Workflow :The Credit Management Application workflow manages the process flow of gathering and analyzing account or prospect credit data, and making and implementing credit decisions.
    • Enable Workflow Agent Listener (If not enabled)
    • Schedule WF Agent Listener (WF_DEFERRED)
    • Schedule WF Background for Credit Management
12. Create hierarchical Party Relationship (Optional) : This is required if you have requirement to keep the customer setup as-is, a hierarchical relationship was created between parent party and its customers.
13. Define Scoring Model
    • A scoring model is one of the primary credit review tools that Oracle Credit Management uses to assess the creditworthiness of your customers
    • 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.
    • During a credit analysis, Credit Management uses the scores that you assigned to each data point range of values to calculate a score. The lower the credit score, the greater the credit risk.
14. Define Checklist
    • 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 criteria in the form of data points from a multitude of sources. Credit Management uses these checklists in two places:
      • Credit application – The checklist determines which fields are required on the application.
      • Credit analysis – The checklist identifies what data should be automatically collected and displayed in the case folder.
    • 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).
    • Additionally, your enterprise defines these credit classifications:
      • High Risk
      • Moderate Risk
      • Low Risk
15. Assign Credit Analyst
16. Define Automation Rule :For any scoring model, you can define a set of automation rules to guide the implementation of credit recommendations without user intervention. Automation rules let a credit review proceed uninterrupted through the workflow, during which a credit recommendation is automatically implemented based on the score that the scoring model calculates.
17. Define AME Rule :For credit recommendations that require approval, Credit Management works with Oracle Approvals Management (AME) to manage the list of required approvers.

If you are global company and have regional customer , and using third party Credit Bureau data like :

• Transunion
• KI
• Experien
• Equifax

If you are planning to integrate with Oracle Credit Managment , then there is waiting time for you as out of box feature is not offered.

Currently Credit Management is only designed to work with Dun & Bradstreet .Though if have third part data product you can easily integrate with the help of some customization.

CREDIT REPORTING AGENCY

This term refers to businesses that maintain historical information pertaining to credit experience on individuals or businesses.

The data is collected from various sources, most commonly firms extending credit such as credit card companies, banks and credit unions. They also collect information from public records, such as bankruptcies.

You can use Third Party Data Integration to obtain any of these data products:

• Business Verification
• Quick Check
• Delinquency Score
• Global Failure Risk Score
• Financial Standing
• Decision Support
• Enterprise Management
• Commercial Credit Score
• Vendor Management