3.9 Promise Tracking Batch
Oracle Banking Collections has the capability to monitor all the promises taken from the customer and appropriate the payment received against these promises to mark them as kept or broken.
- Batch 1: Payment Appropriation Batch
This batch will allocate the payments received from product processor against an account which have active promises based on FIFO (First in First Out) method. If amount is reversed from the product processor then payment appropriated will also be reversed, only if promise is still active.
Job Name: obcr-ptp-appropriation-batch-services
Dependent Batch/Job: Not Applicable
Multi-threaded: Yes
Multi-stream: Yes
Table 3-29 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-30 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. - Batch 2: PTP Decisioning Batch
Based on the promise appropriation batch output, system will mark whether the promise is kept or broken. Follow-up date of the linked task is also updated based on the decision.
Job Name: obcr-ptp-decisioning-batch-services
Setup Prerequisites
Following is the prerequisite for the setup:
The PTP Appropriation batch must have completed its run.
Dependent Batch/Job: Payment appropriation batch.
Multi-threaded: Yes
Multi-stream: Yes
Table 3-31 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-32 Parameters
Parameter Name Value Mandatory Description runDate 01102023 Yes It must be in ddmmyyyy format. branchCode DMO Yes Branch code. userId ADMINUSER1 Yes The user running the batch. 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 the following tables in CR_PTP schema.
- DM_PTP_DECISIONING_DRIVER
- DM_PTP_APPR_DRIVER
- For a successful processing of a record, the below condition should be satisfied.
ERROR_CODE = ‘Success’ and PROCESS_RESULT = ‘1’
Parent topic: Batch Execution Details