My Oracle Support Banner

Debit Credit Mismatch Due To Wrong Consolidation Amount Passed. (Doc ID 2803884.1)

Last updated on SEPTEMBER 03, 2021

Applies to:

Oracle FLEXCUBE Universal Banking - Version 12.3 and later
Information in this document applies to any platform.


Debit Credit Mismatch due to wrong consolidation amount passed.

A File had 103 transactions among which 2 contracts were rejected in this file one after the CONS was passed  and another one before the CONS was passed.

It is observed that system did not considered transaction before CONS was passed during the consolidation but system considered transaction after CONS was passed during the consolidation.

Due to this expected amount for consolidation is not equal to the actual amount passed for consolidation.

System should pass the correct consolidation amount.

The issue can be reproduced at will with the following steps:
1) Incoming Pain001 file is received with four transactions totaling to 'X' and the batch booking is ‘True’
2) Pain file is uploaded, and the CPG Job is run. The Respective contracts are created and processed.
3) The CONS Event is triggered, and the consolidation is also logged in the system for 'X'.
4) One of the transactions for 'Y' is rejected by the user and RJBS is triggered.
5) PR_PROCESS_CONS job is run and DRLQ is triggered by the system for the consolidated FILE_AMT of 'X'. And the Credit of DRLQ is fired for total of (X-Y) excluding the Y amount.
6) This results in a real debit / Credit mismatch.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.