My Oracle Support Banner

FCUBS - System Not Replicating Dormancy Changes Into OBBRN (Doc ID 3022351.1)

Last updated on MAY 20, 2024

Applies to:

Oracle Banking Branch - Version 14.6.0.0.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
System not replicating dormancy changes into OBBRN.

When user tries to mark an account from dormant to no dormant from status change screen system is replicating in CORE table, but PLATO CORE replication is failing.
First, it was thought it's a roles issue, so gave ALLROLES still issue persists, in the replication its showing error which is misleading like WS is null.

Same when tried to change no debit status from STATUS change screen both in FCCORE and PLATOCORE replication is success.



EXPECTED BEHAVIOR
-----------------------
System behavior should be ideal during replication of account status.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Change the Account status in STDSTCHN
2. Dormant to Non Dormant
3. First try of replication is failed - ExtStatus X
4. Second try of replication is failed - ExtStatus E


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot replicate the account status to PLATO CORE

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
References


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