3.2 Score Calculation Batch
Borrowers' risk or behavior scores are used by banks and financial institutions to define the right treatment strategy in collections. The Behavior score or Risk score is a clear indication of borrowers capacity or ability to payback his overdue amount. The inbuilt scoring engine of Oracle Banking collections uses quantitative scorecard models to calculate borrowers' behavior scores. The model can be built of borrower's multiple financial attributes and provides the application updates a borrower's account with a score generated from the model, which is built using their multiple financial attributes. Accounts can be segmented based on their risk profile using this score.
Job Name: obcr-opds-integration-batch
Dependent Batch/Job: obcrCaseCreateBatch
Multi-threaded: Yes
URI: <protocol>://obcr-entity-services/jobLauncher/runBatch/
Table 3-3 Mandatory Headers
| Parameter Name | Value | Mandatory | Description |
|---|---|---|---|
| userld | ADMINUSER1 | Yes | User Id of the requesting user. |
| appld | CRENTITY | Yes | The application ID of the host service. |
| branchCode | DMO | Yes | Branch Code of the requesting user. |
| entityId | DEFAULTENTITY | Yes | Entity ID of the request. |
| Accept | Application/json | Yes | Content Type of the request. |
Specify following parameters while executing this batch:
Table 3-4 Parameters
| Parameter Name | Value | Mandatory | Description |
|---|---|---|---|
| runDate | 01102023 | Yes | It must be in ddmmyyyy format. |
| branchCode | DMO | Yes | Branch code of the project. |
| userId | ADMINUSER1 | Yes | User id of the user. |
Success/Failure Details:
Verify the record level status in DM_ACCOUNT_OPDS_DRIVER table in CR_ENTITY schema. For a successful processing of a record, the below condition should be satisfied.
ERROR_CODE = ‘Success’ and PROCESS_RESULT = ‘1’
Parent topic: Batch Execution Details