3.4 Increment DPD Batch

Oracle Banking Collections receives delinquent accounts data from multiple product processors via file or online services.

Last DPD Update Date is an optional field in the ‘Account Details’ entity. If the product processor sends the value in this field, the same should be updated in Oracle Banking Collections.

If the product processor sends blank value in this field, then in Oracle Banking Collections, the value should be set as current business date.

This batch will increment the DPDs for all accounts in collections by the difference between Previous Business Date and Current Business Date.It is recommended to run as part of BOD.

This batch can be switched off for specific product processor, if required.

Job Name: obcr-incrementdpd-batch

Dependent Batch/Job: Not Applicable

Multi-threaded: Yes

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

Table 3-9 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-10 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.
excludePPC	TPH	No	If multiple product processor needs to be skipped, then we need to pass their codes as comma separated values.
overrideDate	2023-10-01	No	It must be in yyyy-mm-dd format. It is required to run the batch for a specific day.

Success/Failure Details:

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