Previous Next JavaScript must be enabled to correctly display this content

## 3 Oracle Banking Liquidity Management Job

The topic describes the Oracle Banking Liquidity Management Job names and its descriptions.

Table 3-1 Oracle Banking Liquidity Management Job

S.No | EOD stage | Job Name | Description | Input Parameters
--- | --- | --- | --- | ---
1 | MCUT | markcutoff | Job will check for pending tasks and any existing running process before starting EOD. | BranchCode
2 | EOD | CHKPENDINGMAINT | Job will check pending maintenances that required approval. | BranchCode
3 | EOD | SWEEP | Job will execute sweep process scheduled to run during EOD. The following optional change can be done to the existing EOD.SWEEP to enable parallel processing feature: Modify - inputParameters.http_request.body.jobName = "eodSweepJobV2" Add - inputParameters.http_request.body.jobParameters.key = "gridSize" Add - inputParameters.http_request.body.jobParameters.value = 5 (Can be changed as per need) | BranchCode
4 | EOD | CLEAR_BALANCE_CACHE | Job will clear the Value Dated balance cache that’s populated during EOD Sweep executions. | BranchCode
5 | EOD | POOL | Job will execute non-main pool (i.e. subPool is 'S' or null) structures. The workflow JSON is revised for Plato Batch framework adoption. The job name was changed from "eodPoolJob" to "OBLM_POOL_EOD_001". The "branchCode" parameter was removed. New parameters were introduced: "invokeBatchFrm": "Y" triggers the Plato Batch framework logic instead of the core logic. "isDynamicParamReq": "Y" signals that dynamic parameters, such as branchCode and runDate, will be fetched from the domain service. "isCallback": "Y" indicates that a callback is required. "callbackType": "PLATOORCH" specifies that the callback should be sent to the PLATO Orchestration service for task status updates. "subPool": "S" indicates that Pool Batch will be processing the NonMain Pool Structures. Batch-related parameters and configurations—such as stream size, commit frequency, driver table page size, and skip policy—are now controlled through entries in the PLATO_BATCH_TM_JOB_DETAILS table in the batch schema. The relevant record uses JOB_NAME = 'OBLM_POOL_EOD_001'. These changes align the workflow configuration with the Plato Batch framework’s standards, supporting enhanced integration, dynamic parameter management, centralized batch configuration, and streamlined callback handling. | BranchCode subPool
6 | EOD | MAINPOOL | Job will execute main pool(i.e. subPool is 'M') structures. Other job details would be same as above POOL Job except subPool parameter value | BranchCode subPool
7 | EOD | EOD.BALANCEUPDATE | Job Fetches the balance for all the accounts of the branch. If there are any BVT transactions on the current branch date, the job will update the account balance from the BVT value date and also marks Recalc in IC. Performs End-Of-Day balance updates for all eligible accounts in the branch. It fetches latest balances, updates batch driver tables, and triggers further downstream calculations or processes as needed. Job Parameters: workflowId`: Unique workflow execution identifier. `referenceTaskName`: Should be set to `EOD.BALANCEUPDATE` for traceability. `microServiceName`: Service name for routing; typically `oblm-integration-services`. `contextRoot`: REST API root; typically `oblm-integration-services`. `appId`: Application code; for OBLM, always `LMX`. `invokeBatchFrm`: Always `Y` (true); indicates batch mode invocation. `isDynamicParamReq`, `isCallback`: Always `Y` (true); indicates batch mode invocation. `callbackType`: Always 'PLATOORCH' | BranchCode
8 | EOD | EOD.INTEREST-OPTIMIZATION | Executes Interest Optimization SDE (System Defined Elements) batch processing for the branch, updating batch data and writing interest optimization results as required by day-end routines. Runs advanced interest allocation/optimization for all structures and linked accounts for financial close. Job Parameters: `workflowId`: Workflow execution ID. `referenceTaskName`: Should be `EOD.INTEREST-OPTIMIZATION`. `microServiceName`, `contextRoot`, `appId`: As above; always `oblm-integration-services`, `LMX`. `appId`: Application code; for OBLM, always `LMX`. `invokeBatchFrm`: Always `Y` (true); indicates batch mode invocation. `isDynamicParamReq`, `isCallback`: Always `Y` (true); indicates batch mode invocation. `callbackType`: Always 'PLATOORCH' | BranchCode
9 | EOD | EOD.RATIO | Processes ratio method SDE calculations at End-Of-Day, aggregating and storing critical ratio metrics for branch accounts. Feeds results for pool/structure analytics and compliance reporting. Job Parameters: `workflowId`: ID for this workflow instance. `referenceTaskName`: Should be `EOD.RATIO`. `microServiceName`, `contextRoot`, `appId`: Service/application routing; generally `oblm-integration-services`, `LMX`. `appId`: Application code; for OBLM, always `LMX`. `invokeBatchFrm`: Always `Y` (true); indicates batch mode invocation. `isDynamicParamReq`, `isCallback`: Always `Y` (true); indicates batch mode invocation. `callbackType`: Always 'PLATOORCH' | BranchCode
9 | EOD | IC.MARKCUTOFF | Job will check for pending tasks and any existing running process before starting Interest batch. | BranchCode
8 | EOD | OBLM-IC | Job will execute Interest batch. | BranchCode
9 | MS-EOFI | MS-EOFI | Milestone for the end of financial input. | BranchCode
10 | EOFI | MARKEOFI | Job will mark the end of financial input | BranchCode
11 | MS-CHKB4FLIPDATE | MS-CHKB4FLIPDATE | Milestone for date flip. | BranchCode
12 | EOD | CMC.DATEFLIP | Job will change system date to next working date in common core. | BranchCode
13 | EOD | OBLM.DATEFLIP | Job will change system date to next working date in Oracle Banking Liquidity Management. | BranchCode
14 | EOD | RCUT.RELEASECUTOFF | Job will mark release cutoff after EOD. | BranchCode
15 | EOD | IC.RELEASECUTOFF | Job will mark release cutoff for IC Batch. | BranchCode
16 | BOD | BOD.REALLOC | Job will execute reallocation. The following optional change can be done to the existing BOD.REALLOC to enable parallel processing feature: Modify - inputParameters.http_request.body.jobName = "bodReallocationJobV2" Add - inputParameters.http_request.body.jobParameters.key = "gridSize" Add - inputParameters.http_request.body.jobParameters.value = 5 (Can be changed as per need) Job Name: Old: "bodReallocationJob" New: "OBLM_REALLOCATION_009" (standardized, versioned) - Parameters: Old: Fewer, only basics (`branchCode`, `appId`, etc.) New: Adds workflow/context (`workflowId`, `referenceTaskName`), orchestration flags (`invokeBatchFrm`), dynamic params (`isDynamicParamReq`), and callback setup (`isCallback`, `callbackType`). - Purpose: The new DSL is designed for use with orchestration platforms, allowing traceability, callbacks, dynamic params, and cleaner job versioning. Old DSL is for legacy direct batch launch. | BranchCode
17 | BOD | BOD.SWEEP | Job will execute the Reverse sweep and BOD sweeps in sequence The following optional change can be done to the existing BOD.SWEEP to enable parallel processing feature: Modify - inputParameters.http_request.body.jobName = "bodSweepJobV2" Add - inputParameters.http_request.body.jobParameters.key = "gridSize" Add - inputParameters.http_request.body.jobParameters.value = 5 (Can be changed as per need) | BranchCode
18 | BOD | TI.MARKTI | Job will mark the transaction inputs. | BranchCode
19 | BOD | BOD.ICL | Job will execute the ICL. - Job Name: Old: `"bodICLJob"` New: `"OBLM_ICL_010"` (versioned, standardized) - Parameters Added: New version adds: - `workflowId` - `referenceTaskName` - `invokeBatchFrm` - `isDynamicParamReq` - `isCallback` - `callbackType` *(All above enable orchestration, dynamic params, and callback support.)* - Purpose: New DSL is orchestration-ready and supports callback & dynamic execution, while the old one is static and direct. | BranchCode
20 | BOD | chargeCalculationJob | Job will calculate the LM charges for given branch code. | BranchCode
21 | BOD | chargePostingJob | Job will post the LM charges for given branch code. | BranchCode
22 | OBLM | OBLM.UPDATEDEFERREDENTRY | Job will update the Deferred entries for pool contribution for given BranchCode. Integration Type Changed: - Old: Called OBLM-POOL-SERVICES directly with a GET method to a REST endpoint. - New: Now handled by submitting a batch job to PLATO-BATCH-SERVER using a POST. URL Changed: - Old: `/oblm-pool-services/web/v14.8.2.0.0/pools/deferred-entries/by-branch?branchCode={branchCode}` (REST GET) - New: `/plato-batch-server/jobLauncher/launch/` (Job orchestration POST) Request Method Changed: - Old: GET - New: POST (with job parameters in the body) Headers Changed: - Old: `appId: LMP`, plus branchCode and userId - New: `appId: PLATOBATCH`, plus branchCode, userId, and eocType in headers Request Body: - Old: No request body (REST GET call) - New: Body specifies a batch job with: - `jobName: OBLM_UPDATE_DEF_ENTRIES_005` - `jobParameters`: workflowId, referenceTaskName ("OBLM-UPDATEDEFERREDENTRY"), microServiceName, contextRoot, appId, invokeBatchFrm, isDynamicParamReq, isCallback, callbackType Async Execution: - Old: Synchronous (`asyncComplete: false`) - New: Asynchronous (`asyncComplete: true`) Purpose of Change: - Deferred entry update was a synchronous direct fetch from the pool service. Now, it's performed as an orchestrated, asynchronous batch job as part of the EOD process, with callback and orchestration support. | BranchCode
23 | OBLM | OBLM.MBCVBALANCEFETCH | Job will fetch balance from respective external system for all CM accounts under the EOD branch . Service Endpoint Changed: - Old: Called `PLATO-BATCH-SERVER` with jobName `mbcvBalanceUpdateJob`. - New: Still calls `PLATO-BATCH-SERVER` but now uses jobName `OBLM_CM_ACCBAL_REQ_007`. Job Name Changed: - Old: `"jobName": "mbcvBalanceUpdateJob"` - New: `"jobName": "OBLM_CM_ACCBAL_REQ_007"` jobParameters Updated: - Old: - branchCode - balanceRequestType: "Internal" - microServiceName: oblm-integration-services - contextRoot: oblm-integration-services - appId: LMX - New: - workflowId - referenceTaskName ("OBLM.MBCVBALANCEFETCH") - microServiceName: oblm-integration-services - contextRoot: oblm-integration-services - appId: LMX - invokeBatchFrm: "Y" - isDynamicParamReq: "Y" - isCallback: "Y" - callbackType: "PLATOORCH" > *Notably, jobParameters have been extended and standardized to match other PLATO batch jobs, adding orchestration/callback info and dropping `balanceRequestType`.* Operation Type Changed: - Old: Synchronous batch job (`asyncComplete: false`) - New: Asynchronous batch job (`asyncComplete: true`) Purpose of Change: - The fetch of MBCV balance is now submitted as a standardized asynchronous plato batch framework job, with additional orchestration and callback parameters, for better integration within EOD processing. | BranchCode
25 | OBLM | OBLM.UPLOADINTERESTACCRUALREPORT | Job will update the Accrual Interest details for given BranchCode. Integration Type Changed: - Old: Called OBLM-POOL-SERVICES directly with a GET method to a REST endpoint. - New: Now handled by submitting a batch job to PLATO-BATCH-SERVER using a POST. URL Changed: - Old: `/oblm-pool-services/web/v14.8.2.0.0/pools/deferred-entries/by-branch?branchCode={branchCode}` (REST GET) - New: `/plato-batch-server/jobLauncher/launch/` (Job orchestration POST) Request Method Changed: - Old: GET - New: POST (with job parameters in the body) Headers Changed: - Old: `appId: LMP`, plus branchCode and userId - New: `appId: PLATOBATCH`, plus branchCode, userId, and eocType in headers Request Body: - Old: No request body (REST GET call) - New: Body specifies a batch job with: - `jobName: OBLM_UPDATE_DEF_ENTRIES_005` - `jobParameters`: workflowId, referenceTaskName ("OBLM-UPDATEDEFERREDENTRY"), microServiceName, contextRoot, appId, invokeBatchFrm, isDynamicParamReq, isCallback, callbackType Async Execution: - Old: Synchronous (`asyncComplete: false`) - New: Asynchronous (`asyncComplete: true`) Purpose of Change: - Deferred entry update was a synchronous direct fetch from the pool service. Now, it's performed as an orchestrated, asynchronous batch job as part of the EOD process, with callback and orchestration support. | BranchCode
26 | IC | IC.INTRADAYBATCH | Job will update the Intra day batch to notify UBS. | BranchCode
27 | OBLM | OBLM.UPDATESTRUCTURESTATUS | Job will update the status of all structures under the EOD branch. Service Endpoint Changed: - Old: Called directly on `OBLM-STRUCTURE-SERVICES` using PUT method. - New: Now calls `PLATO-BATCH-SERVER` as a batch job using POST. URL Changed: - Old: `/oblm-structure-services/web/v14.8.2.0.0/structures/structureStatus/{branchCode}` (direct REST update) - New: `/plato-batch-server/jobLauncher/launch/` (batch job submission) Operation Type Changed: - Old: Synchronous update (the call waits for a direct response from service). - New: Asynchronous batch job (system will process and callback; not immediate). Request Payload Changed: - Old: No request body, just parameterized URI and headers. - New: Has a batch job request body, specifying a job name (`OBLM_STR_STATUS_UPDATE_008`) and multiple parameters (like workflowId, task name, microServiceName, contextRoot, appId, callback type, etc). AppId and Header Changes: - Old: `appId` was "LMA" - New: `appId` is now "PLATOBATCH" (header), but the job body includes `appId: LMX`. Purpose of Change: - The update is now handled via plato-batch-framework orchestrator, integrating structure status updates into broader EOD batch workflows, improving manageability and allowing more control/features (like retries, orchestration, async callbacks). | BranchCode
28 | OBLM | OBLM.DATEFLIP | Job will update the branch date of the EOD branch in LM table. | BranchCode
29 | OBLMIC | OBLMIC.DATEFLIP | Job will update the branch dates of the EOD branch in OBLM IC tables. | BranchCode
30 | EOD | CHECKINSTANCE | Job will check the current EOD instance is updated in CMC table CMC_TB_BRANCHEOD_INSTANCES. | BranchCode and WorkflowId

Note:

The Charge Calculation (ChargeCalculation) and Charge Posting (ChargePosting) jobs are allowed to be configured either before date flip (EOD) or after date flip (BOD). Based on the bank's requirement, this can be configured. By default, these jobs are configured after date flip (BOD) and is shipped with EOD configuration.