My Oracle Support Banner

PC Module: When CASA Account Is Amended In Incoming Payment, System Fires Incorrect Entries Charges. (Doc ID 2639975.1)

Last updated on FEBRUARY 18, 2020

Applies to:

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

Symptoms



ACTUAL BEHAVIOR
---------------
In PC module, during creation of an incoming payment contract, if the main CASA account number is amended, system is firing entries using correct account number for the main transaction amount. However, the charge entries are taken from a different account.


EXPECTED BEHAVIOR
-----------------------
Charge accounting entries must be triggered with the same account number in which system is firing entries for the main transaction amount.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
a) Create an incoming payment contract using an account as 024XXXXXXXXXXX91.
b) Visit Charges call form, Click on OK and press Hold
c) Click on unlock and amend the account number as 024XXXXXXXXXXX92
d) Visit Charges call form, Click on OK and save.
e) Unlock the contract and amend the account number as : 024XXXXXXXXXXX93
f) Visit Charges call form, Click on OK and save.
g) Authorize this via checker & Observe 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
References


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