3.10 Case Closure Batch

Oracle Banking Collections has the capability to move the active account out of collections based on certain conditions (based on pre-defined rule) and also capability to close the existing cases.

Job Name: obcr-caseclosure-batch

Setup Prerequisites

Following is the prerequisite for the setup:

The facts and rules are created before batch run.

Dependent Batch/Job: Not Applicable

Multi-threaded: Yes

Multi-stream: Yes

URI : <protocol>:// obcr-entity-services/jobLauncher/runBatch/

Table 3-33 Mandatory Headers

Parameter Name	Value	Mandatory	Description
userld	ADMINUSER1	Yes	User Id of the requesting user.
Appld	CRSEG	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-34 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.
overrideDate	2023-10-01	No	It must be in yyyy-mm-dd format. It is required to run the batch for a specific day.
filterId	“ACCT_CURED”	Yes	It is the rule, based on which accounts will be classified as cured.
exclusionRuleId	“Segment_Code”	No	It is rule to define which accounts needs to be excluded from processing. For example, in the list 10 accounts are classified where overdue_amount is Zero, however out of which we need to exclude accounts where segment is ‘Bankruptcy’ , this rule can be defined and used.

Success/Failure Details:

User can verify the record level status in DM_ACCOUNT_CLOSURE_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’