You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Peter Santa (Jira)" <ji...@apache.org> on 2023/05/17 06:32:00 UTC
[jira] [Created] (FINERACT-1931) Savings Account with overdraft - cannot deposit after holdAmount drove to negative balance
Peter Santa created FINERACT-1931:
-------------------------------------
Summary: Savings Account with overdraft - cannot deposit after holdAmount drove to negative balance
Key: FINERACT-1931
URL: https://issues.apache.org/jira/browse/FINERACT-1931
Project: Apache Fineract
Issue Type: Bug
Components: Savings
Affects Versions: 1.9.0
Reporter: Peter Santa
Fix For: 1.9.0
h1. Steps to reproduce
Have a Saving Account, with overdraft allowed. Start the test vith balance = available balance = 0.
# Deposit 100 - no issues so far
# Withdraw 100 - no issues so far
# holdAmount 50 -> available balance is negative - no issues so far
# releaseAmount 50 - no issues so far
# Deposit 100
h1. Actual result
[
\{
"requestId": 3,
"statusCode": 403,
"body": "{\n \"developerMessage\": \"The request caused a data integrity issue to be fired by the database.\",\n \"httpStatusCode\": \"403\",\n \"defaultUserMessage\": \"Recent Portfolio changes w.r.t Charges for Savings have Broken the accounting code\",\n \"userMessageGlobalisationCode\": \"Recent Portfolio changes w.r.t Charges for Savings have Broken the accounting code\",\n \"errors\": [\n {\n \"developerMessage\": \"Recent Portfolio changes w.r.t Charges for Savings have Broken the accounting code\",\n \"defaultUserMessage\": \"Recent Portfolio changes w.r.t Charges for Savings have Broken the accounting code\",\n \"userMessageGlobalisationCode\": \"Recent Portfolio changes w.r.t Charges for Savings have Broken the accounting code\",\n \"args\": []\n }\n ]\n}"
}
]
h1. Expected result
Handle the deposit correctly. Handle all the next transactions correctly.
h1. Investigation
Hint: most probably the exception has been thrown by AccountingProcessorHelper.java, around L751
--
This message was sent by Atlassian Jira
(v8.20.10#820010)