MMDVAMIN: MM VAMI Accounting Entries Are Incorrect
(Doc ID 2887072.1)
Last updated on AUGUST 01, 2022
Applies to:
Oracle FLEXCUBE Universal Banking - Version 14.3.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
Actual Behavior
User is testing the VAMI for MM and find that when we do Amendment to the Principal amount of the contract, the accounting entries for the VAMI event are not correct.
For the same contract, during the contract INIT, the accounting entries are correct.
Expected Behavior
System is expected to credit the settlement bridge account in the entry for the VAMI and INIT event. However, system directly credited the NOSTRO account.
Steps
1. Pick up an MM contract which is active.
2. Access the MMDVAMIN screen and do a principal increase for the contract.
3. Save the VAMI and authorize the contract.
4. Validate the accounting entries.
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 |