All credit reviews begin with either a manual or automatic request:
Credit or other personnel can manually initiate a credit review for a customer or prospect by submitting an online credit application, or by creating a case folder without a credit application. A case folder is an electronic representation of a hardcopy credit file.
See: Collecting Credit Data.
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.
You can configure Credit Management to complete the review process without assistance from credit personnel. In such cases, a credit analyst is not assigned unless a failed validation step prevents the automated process from successfully completing.
For credit reviews whose workflow processing fails, Credit Management uses the Rules Engine to determine the appropriate credit analyst for assignment. See: Credit Analyst Assignment Rules.
If an analyst cannot be determined, then a notification is sent to the Credit Scheduler to assign a credit analyst to complete the credit review. See: Credit Management Application Workflow.