EOM: Period Code Mismatch due to DE Entries posted during EOM
(Doc ID 2966123.1)
Last updated on AUGUST 15, 2023
Applies to:
Oracle FLEXCUBE Universal Banking - Version 14.3.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
On : 14.3.0.0.0 version, Production Support-SET
Period code mismatch for transaction posted in same branch during EOM
Cross branch Transaction done from External system during EOM when one branch
moved to next period while the other branch is still in old period
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.Restore the month end dump.
2.Starting EOD of 125, 101 and 999 branches.
3.Complete the EOD of 125 branch till Date Chnage. But hold the 101 and 999
branches in earlier dates.
4.Initiate the similar channel transaction using branch 125.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, Transaction posted in 125 BRanch one leg in MArch and one
Leg in April. This results in AC-FINBAL error in next EOD
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 |