Define these Oracle Credit Management system options.
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.
Note: To ensure that credit review comparisons display consistent aging data, you cannot change this system option once you have saved it.
See: Aging Buckets and Interest Tiers.
Why does my Credit Management aging data not match my Oracle Receivables aging data?
Credit Management calculates its own aging data after pulling certain pieces of information from Oracle Receivables tables.
In Credit Management, the primary concern is around credit and collections. For example, what are the due dates and collection dates? In Receivables, the primary concern is around collection. For example, what are the effective dates, when was the receivable booked?
Due to this difference in focus, Credit Management and Oracle Receivables aging data can be different.
Credit classification assignments can either be assigned by a previously completed credit review, or assigned on the customer profile.
For those customers or prospects who do not yet have credit classification assignments, use this system option to select the credit classification that you want to use as the default on credit applications.
The default is High Risk.
See: Defining Customer Profile Classes.
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.
A narrower time period shows short-term trends, while a longer time period shows long-term viability.
The default is 12 months.
See: Populating Transaction Data.
Indicate if you want Credit Management to automatically assign a number to each credit application.
The default is Yes.
Caution: Carefully consider your business requirements before setting this system option to No. For example, credit review requestors from outside Credit Management can include a credit application ID in the credit review request itself. However, if the incoming credit request does not contain the credit application ID and the Application Numbering Option system option is set to No , then the workflow will fail, requiring manual intervention. A credit analyst will need to add a credit application ID to the application.
Select the 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.
The default is Corporate.
Credit Management uses this value to convert data when data point values are calculated, and also for reporting.
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.
The default is 90 days.
Other applications integrating with Credit Management can appeal a credit recommendation. You control the appeal period by entering a default number of days, after which an appeal is no longer allowed. Credit Management calculates the appeal expiration date as the recommendation date plus the Appeal Days value that you select here.