CASA: System Allows Debit For Account Which Is marked For No Debit (Doc ID 2901988.1)

Last updated on OCTOBER 26, 2022

Applies to:

Symptoms

ACTUAL BEHAVIOR
---------------
An account was marked as No debit in status change screen. But it was not propagated at account level (STDCUSAC), so system allowed debit.

EXPECTED BEHAVIOR
-----------------------
Account should be marked for no debit after modification in status change screen

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.Query the account in STDCUSAC screen.
2.Now change the status of the account (change only no debit flag , status
should be same as previous) from STDSTCHN screen.
3.Save the changes .
4.Another user authorizes the changes.
5.Now unlock the account in already opened STDCUSAC screen. The data is not
refreshed.
6.Save and authorize the account . The no debit flag is cleared.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, accounts are debited though no debit flag is checked.

Changes

The following justifies how the issue is related to this specific customer:
There was a fix which was replacing current value with manual status change
value due to which status modified from STDSTDOR is not shown in STDCUSAC.

This is explained in the following bug:
Bug34538412 - NO DEBIT FLAG IGNORED IN ACCOUNT
 

Cause

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