Failure To Transfer "CHANGE LOG" - STDCUSAC
(Doc ID 2786615.1)
Last updated on SEPTEMBER 06, 2021
Applies to:
Oracle FLEXCUBE Universal Banking - Version 12.3 to 12.3 [Release 12]Information in this document applies to any platform.
Symptoms
On : 12.3 version, Production Support-SET
ACTUAL BEHAVIOR
---------------
Failure to transfer "CHANGE LOG" - STDCUSAC
EXPECTED BEHAVIOR
-----------------------
System should transfer record for change log of STDCUSAC
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) Create new Customer Account with STDCUSAC
2) Make some modification with unlock and save for that customer account on STDCUSAC ("Mod. No." greater than 1- assure that CHANGE LOG is populated)
3a) Transfer Customer Account using CSDACCTR
or
3b) Transfer Customer No. using STDCUSTR
BUSINESS IMPACT
-----------------------
Due to this issue, system doesn't transfer the record on CHANGE LOG of STDCUSAC.
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 |
| Cause |
| Solution |