My Oracle Support Banner

PAYMENT AND STATUS CHANGE FAILED SINCE NO RECORDS FOUND IN CLTB_ACCOUNT_COMP_BAL_BREAKUP TABLE (Doc ID 2802695.1)

Last updated on AUGUST 28, 2021

Applies to:

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

Symptoms

On : 12.0.2 version, Production Support-SET

ACTUAL BEHAVIOR
--------------------

1)Payment and sattus change failing with breakup not found error.
2)system deletes the record from cltb_Account_comp_bal_breakup table on version reversal.Hence failure is happening

EXPECTED BEHAVIOR
-----------------------
system should have correct record in breakup table

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.do rollover for the account which is in other than NORM status.

2)system will fire rollover and STCH.

3) 2 new version will be created one for rollover and another one for STCH.

4) in breakup history table system inserted the breakup details correctly for the rollover version and the subsequent STCH version does not insert the record in the history table

3) reverse the STCH version. since there is no back up record in history table for the version system is not inserting any record in breakup table.

4) Do the STCH again or payment for this account.

5)it is failing with balance breakup not found error.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot do payment .

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution


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