3.1 Case Creation Batch
When a new account comes into collections, case creation batch will create a case on the primary party linked to this account based on certain conditions.
Case is always created on the Customer. For all new accounts received in collections, system will first check whether any existing active case is running on the primary Customer of the account. If yes, then the account will be linked to the same Case number, else, a new case number will be generated and account will be linked to it. At any given point of time, only a single active case will be running on a Customer across all product processors.
Setup Prerequisites
Following is the prerequisite for the setup:
New Accounts are available in Oracle Banking Collections though inbound file processing.
Job Name: obcrCaseCreateBatch
Dependent Batch/Job: Not Applicable
Multi-threaded: No
URI: <protocol>://obcr-strategy-services/jobLauncher/run/
Table 3-1 Mandatory Headers
Parameter Name | Value | Mandatory | Description |
---|---|---|---|
userld | COLLADMIN1 | Yes | User Id of the requesting user. |
appld | CRSTRTGY | Yes | The application ID of the host service. |
branchCode | BCR | 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-2 Parameters
Parameter Name | Value | Mandatory | Description |
---|---|---|---|
microServiceName | obcr-strategy-services | Yes | Service that consists the case creation batch. |
appld | CRSTRTGY | Yes | The application ID of the host service. |
contextRoot | obcr-strategy-services | Yes | Context path of the service. |
timestamp | YYYYMMDDHHMMSS.SSSSS | Yes | Each batch run should have unique parameters so the current timestamp is to be added. |
collStartDt | YYYY-MM-DD | No | Optional parameter Collection Start Date of the accounts to be mapped. If no date is passed Application Date is considered. |
- Fetch the latest Job Instance Id from the table PLATO_BATCH_JOB_INSTANCE in PLATOBATCH schema with the job name obcrCaseCreateBatch.
- Check the Job_instance_id in PLATO_BATCH_JOB_EXECUTION the status and exit_code will be marked COMPLETED.
- Additionally, verify the entries in DM_CASE and DM_CASE_ACCOUNT_ASSO tables in CR_STRTGY schema for delinquent accounts.
Parent topic: Batch Execution Details