3 Batch Execution Details

This section explains the various batch processes that are executed in Oracle Banking Collections Cloud Service once the delinquent account is onboarded.

Inbound data processing:

Oracle Banking Collections Cloud Service 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 File Interface Specification document for the details. (file-interface-specification-guide.doc)

    These files can then be uploaded in Oracle Banking Collections Cloud Service to on-board the delinquent accounts.

  • Option 2:

    Oracle Banking Collections Cloud Service can receive delinquent accounts from the host system 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 Cloud Service after all relevant validations.

Mandatory headers which are applicable to all batches are listed below:

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.
env cloud Yes Specifies the environment.
tenantId nonprod Yes Identifies the tenant environment.
tenantPdb dvcXXXatpXXX Yes Specifies the Pluggable Database (PDB) for the tenant.
tenantSvc devtestbankXX Yes Defines the database service name for the tenant.

Details of batches: