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:
Exporting case folder contents outside Credit Management, and scoring the contents using your own scoring engine
Importing the resulting credit score, and storing it in the case folder
To determine whether a case folder's data should be externally scored, Credit Management reviews the scoring model that is associated with the checklist in the case folder. External scoring is initiated if the scoring model includes the seeded External Score data point.
See: Defining Scoring Models.
If the scoring model includes the External Score data point, then the Credit Management workflow bypasses the assigned scoring model and instead automatically submits the Extract XML Case Folder concurrent program. This program extracts the case folder data points in an XML file, which you can retrieve for processing in your external system by subscribing to the business event, oracle.apps.ar.cmgt.CaseFolder.extract.
Upon extraction of the case folder data points, the Credit Management workflow locks the case folder to prevent manual updates and sets the case folder status to In Process.
Additionally, the workflow sends a notification to the credit analyst assigned to the case folder, or to the Credit Scheduler if a credit analyst has not yet been assigned. The notification indicates that the case folder was submitted for external scoring.
After your external system completes the scoring process, you must then import the final score back into Credit Management for storage in the case folder. To import the score, use the Get Score API.
Additional Information: For API usage information, see the Credit Management API User Notes appendix in the Oracle Credit Management User Guide.
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.
Once approvals are processed, the case folder is closed.
Note: In addition to importing an externally derived credit score, you can also import credit recommendations, as well as additional data points. See: Importing Credit Recommendations and Other Data.
When using an external scoring engine, you are not limited to importing only the final credit score. You can also optionally import additional data points that you want to capture in the case folder, as well as credit recommendations.
Attention: Before you can import credit recommendations, the recommendations must already be defined in Credit Management. See: Defining Lookups.
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.
Note: Credit recommendations that are imported take precedence over any automation rules that might already exist on the scoring model.
Additional data points and credit recommendations are stored in the same XML file (attached to the case folder) where the credit score resides.
Other Sources
Appendix F: Credit Management API User Notes