Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0021212Openbravo ERP09. Financial managementpublic2012-07-25 18:582012-08-30 10:06
VictorVillar 
jecharri 
urgentmajoralways
closedfixed 
5
3.0MP13 
3.0MP15 
Core
No
0021212: Problems in match statement process if the user does not allow charge the data
we have tested that if the users uncheck "hide transactions after statement date" flag before the data has been shown, then, the matched lines proposed and others are going to be included in a reconciliation with and without bank statement lines associated and then the user could not open again the match statement window because the mixing reconciliation error.
The same problem happens if the users check "Cleared" flag before the data has been loaded.
As system admin role,
Install the Advanced Matching algorithm module.

As group admin role,
Financial account,
Import a large number of bank statement lines (it would be fine to have a bank statement file for the client F&B) It is tested with 170 bank statement lines.
Process it

click in Match Statement button.
BEFORE the lines appear, uncheck "hide transactions after statement date" flag, then try to handle the information. The same problem happens if the users check "Cleared" flag before the data has been loaded.
Check or uncheck the lines proposed, and we realise that suddenly some lines are included in the reconciliation and if you click Cancel Button a Null Pointer Exception error appear.
It would no be possible to open again the match statement window because the mixing reconciliation error.

If you see the lines of the reconciliation we realise that there are mixed lines reconciled, with and without bank statement line associated.
Disabled the "hide transactions after statement date" flag till all the data has been charged.
No tags attached.
Issue History
2012-07-25 18:58VictorVillarNew Issue
2012-07-25 18:58VictorVillarAssigned To => mirurita
2012-07-25 18:58VictorVillarModules => Core
2012-07-25 18:58VictorVillarResolution time => 1347660000
2012-07-25 18:59VictorVillarIssue Monitored: networkb
2012-07-25 19:01VictorVillarSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=3666#r3666
2012-07-26 13:41miruritaAssigned Tomirurita => jonalegriaesarte
2012-07-30 09:43VictorVillarDescription Updatedbug_revision_view_page.php?rev_id=3673#r3673
2012-07-30 09:43VictorVillarSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=3674#r3674
2012-08-02 10:45jonalegriaesarteAssigned Tojonalegriaesarte => jecharri
2012-08-08 08:33hgbotCheckin
2012-08-08 08:33hgbotNote Added: 0051152
2012-08-08 08:33hgbotStatusnew => resolved
2012-08-08 08:33hgbotResolutionopen => fixed
2012-08-08 08:33hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/5940c0deb9b516395f32ec4ef87c7506a20a5535 [^]
2012-08-30 10:06VictorVillarNote Added: 0051664
2012-08-30 10:06VictorVillarStatusresolved => closed

Notes
(0051152)
hgbot   
2012-08-08 08:33   
Repository: erp/devel/pi
Changeset: 5940c0deb9b516395f32ec4ef87c7506a20a5535
Author: Javier Etxarri <javier.echarri <at> openbravo.com>
Date: Wed Aug 08 08:31:32 2012 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/5940c0deb9b516395f32ec4ef87c7506a20a5535 [^]

Fixes issue 21212: Problems in match statement
process if the user does not allow charge the data

---
M modules/org.openbravo.advpaymentmngt/src/org/openbravo/advpaymentmngt/ad_actionbutton/MatchTransaction.html
---
(0051664)
VictorVillar   
2012-08-30 10:06   
Verified