Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0032299Openbravo ERP09. Financial managementpublic2016-02-17 19:512016-02-23 14:01
maite 
AtulOpenbravo 
immediateminoralways
closedfixed 
5
 
3.0PR15Q4.4 
vmromanos
Core
Production - Confirmed Stable
2014-09-23
3.0PR14Q4
https://code.openbravo.com/erp/devel/pi/rev/179d97ee602d [^]
No
0032299: Wrong payment status when unmatching bankstatement line manually matched against an invoice
Wrong payment status when unmatching bankstatement line manually matched against an invoice
0. Configure "Bank" financial account to use "Advanced Matching algorithm"
1. Access Financial Account, create Bank Statement record and add line with amount in =100. Process bank statement
2. Register Sales invoice with any line and total invoice amount = 100
3. Come back to Financial Account and run "Match Statement" process
4. Select "Cancel" option to not execute automatic matching
5. Run "add transaction" process by pressing + button
6. Create payment by pressing "+" button in payment's selector and select your invoice. Process Done and Done to finish with matching process
7. Filter in the grid by "matched=yes" records and unmatch record. Press OK to save reconciliation
8. Realize that transaction has correct status "deposited not cleared"
9. Navigate to related payment in and realize that status is "payment cleared" instead of "deposited not cleared"

NOTE: I followed same steps in an standard MP30.3 version and both payment and transaction has status "deposited not cleared"
No tags attached.
blocks defect 0032268 closed AtulOpenbravo Wrong payment status when unmatching bankstatement line manually matched against an invoice 
Issue History
2016-02-22 10:46AtulOpenbravoTypedefect => backport
2016-02-22 10:46AtulOpenbravoTarget Version => 3.0PR15Q4.4
2016-02-22 10:55AtulOpenbravoRegression date => 2014-09-23
2016-02-22 10:55AtulOpenbravoRegression introduced in release => 3.0PR14Q4
2016-02-22 11:14AtulOpenbravoNote Added: 0084401
2016-02-23 14:01hgbotCheckin
2016-02-23 14:01hgbotNote Added: 0084424
2016-02-23 14:01hgbotStatusscheduled => resolved
2016-02-23 14:01hgbotResolutionopen => fixed
2016-02-23 14:01hgbotFixed in SCM revision => http://code.openbravo.com/erp/backports/3.0PR15Q4.4/rev/b207c78d4bbc3cc992798e07dba3451d57da2ad1 [^]
2016-02-23 14:01vmromanosReview Assigned To => vmromanos
2016-02-23 14:01vmromanosNote Added: 0084427
2016-02-23 14:01vmromanosStatusresolved => closed

Notes
(0084401)
AtulOpenbravo   
2016-02-22 11:14   
Test Plan
- Configure "Bank" financial account to use "Advanced Matching algorithm".
- Access Financial Account, create Bank Statement record and add line with amount in =100. Process bank statement.
- Register Sales invoice with any line and total invoice amount = 100.
- Come back to Financial Account and run "Match Statement" process.
- Select "Cancel" option to not execute automatic matching.
- Run "add transaction" process by pressing + button.
- Create payment by pressing "+" button in payment's selector and select your invoice. Process Done and Done to finish with matching process.
- Filter in the grid by "matched=yes" records and unmatch record. Press OK to save reconciliation.
- Check that financial account transaction has correct status "deposited not cleared".
- Go to related payment in and check that status is "deposited not cleared" which is correct.
(0084424)
hgbot   
2016-02-23 14:01   
Repository: erp/backports/3.0PR15Q4.4
Changeset: b207c78d4bbc3cc992798e07dba3451d57da2ad1
Author: Atul Gaware <atul.gaware <at> openbravo.com>
Date: Mon Feb 22 15:33:27 2016 +0530
URL: http://code.openbravo.com/erp/backports/3.0PR15Q4.4/rev/b207c78d4bbc3cc992798e07dba3451d57da2ad1 [^]

Fixes Issue 32299: Wrong payment status when unmatching bankstatement line
manually matched against an invoice

Incase a finTransaction is unmatched which has finPayment,status of finPayment
is also updated accordingly as per isReceipt flag

---
M modules/org.openbravo.advpaymentmngt/src/org/openbravo/advpaymentmngt/utility/APRM_MatchingUtility.java
---
(0084427)
vmromanos   
2016-02-23 14:01   
Code review + testing OK