3 Batch Execution Details
This section describes the various batch processes used to onboard delinquent accounts, as well as the subsequent OBC batches executed after the account is onboarded.
Inbound data processing:
Oracle Banking Collections can receive delinquent accounts from the host system in two different ways.
- Option 1:
Host system can send the delinquent accounts data in various files as per the agreed format. Please refer to the Interface Specification document for the details. (interface-specification-guide.doc)
These files can then be uploaded in Oracle Banking Collections to on-board the delinquent accounts.
- Option 2:
Oracle Banking Collections can receive delinquent accounts from the product processors in the staging area.
Various batches will be run as mentioned below to process the delinquent account details received in the staging area to Oracle Banking Collections after all relevant validations.
Table 3-1 Mandatory Headers
| Parameter Name | Value | Mandatory | Description |
|---|---|---|---|
| userld | ADMINUSER1 | Yes | User ID of the requesting user. |
| branchCode | DMO | Yes | Branch Code of the requesting user. |
| entityId | DEFAULTENTITY | Yes | Entity ID of the request. |
| Accept | application/json | Yes | Defines the expected response format. |
| Content-Type | application/json | Yes | Defines the request body format. |
| multiEntityAdmin | N | Yes | Indicates if multi-entity admin mode is enabled (Y/N). |
| Connection | keep-alive | Yes | Keeps the connection open for better. |
| Accept-Language | en-US | Yes | Requests responses Language. |
Details of batches:
- Entity Creation
This topic provides information on the creation of mandatory and non-mandatory entities during the onboarding of a delinquent account, as well as the processing of subsequent updates received. - Batch Execution
This section explains the various batch processes of Oracle Banking Collections.