4
It looks more like a bug for me, but I don't know where else can I report such issue:
When Payment Reconciliation Journals are processed in "not ascending" order (for example we posted Journal with "Statement No." = 10 first, and journal with "Statement No." = 9 was posted after). The next error appears:
"The record in table Bank Account Statement Line already exists. Identification fields and values: Bank Account No.='*',Statement No.='10',Statement Line No.='10000'".
The reason is next: During the posting Bank Account "Last Statement No." is updated to the Payment Reconciliation Journal "Statement No.". In our case, it is updated from 10 to 9.
(codeunit 370 "Bank Acc. Reconciliation Post", procedure UpdateBank)
After that, in the procedure"TransferToBankStmt", BC check if Bank Account Statement with such "Statement No." already exists, and runs "GetNextStatementNoAndUpdateBankAccount" procedure if not.
GetNextStatementNoAndUpdateBankAccount procedure just adds +1 to the Bank Account "Last Statement No", without checking if the new value is available and that's caused an error.
When Payment Reconciliation Journals are processed in "not ascending" order (for example we posted Journal with "Statement No." = 10 first, and journal with "Statement No." = 9 was posted after). The next error appears:
"The record in table Bank Account Statement Line already exists. Identification fields and values: Bank Account No.='*',Statement No.='10',Statement Line No.='10000'".
The reason is next: During the posting Bank Account "Last Statement No." is updated to the Payment Reconciliation Journal "Statement No.". In our case, it is updated from 10 to 9.
(codeunit 370 "Bank Acc. Reconciliation Post", procedure UpdateBank)
After that, in the procedure"TransferToBankStmt", BC check if Bank Account Statement with such "Statement No." already exists, and runs "GetNextStatementNoAndUpdateBankAccount" procedure if not.
GetNextStatementNoAndUpdateBankAccount procedure just adds +1 to the Bank Account "Last Statement No", without checking if the new value is available and that's caused an error.
STATUS DETAILS
Needs Votes
Business Central Team (administrator)
Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future. Best regards, Business Central Team