Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0013361Openbravo ERP09. Financial managementpublic2010-05-18 12:102010-12-16 22:15
Reporternetworkb 
Assigned Tosivaraman 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version2.50MP14 
Target Version2.50MP18Fixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerOBPS
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0013361: The General Ledger Report does not work well using the group by option with a big amount of data
DescriptionThe General Ledger Report does not work well using the group by option with a big amount of data
Steps To ReproduceExecute the General Ledger Report using the group by option having in the databas a big amount of data as following:

 FACT_ACCT : 773754 rows
 C_BPARTNER : 101450 rows
 M_PRODUCT : 200 rows

After execute the report the applications didn't show anything.
The browser is waiting for the response but doesn't get anyting.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 00136522.50MP20 closed eduardo_Argal The General Ledger Report does not work with 3.400.000 entries on the fact_act 
related to defect 00136572.50MP20 closed adrianromero The sales invoice Dimensional Report does not work with a big amount of data using partner dimension 
Attached Filesdiff MaxRowsExceeded.diff (90,016) 2010-09-09 13:35
https://issues.openbravo.com/file_download.php?file_id=3066&type=bug
diff Fixes_Issue_13361.diff (101,453) 2010-09-20 14:59
https://issues.openbravo.com/file_download.php?file_id=3103&type=bug
diff Fixes_Issue_13361 (updated).diff (101,466) 2010-09-28 10:48
https://issues.openbravo.com/file_download.php?file_id=3129&type=bug
Issue History
Date ModifiedUsernameFieldChange
2010-05-18 12:10networkbNew Issue
2010-05-18 12:10networkbAssigned To => dalsasua
2010-05-18 12:10networkbOBNetwork customer => Yes
2010-05-18 13:54adrianromeroNote Added: 0027424
2010-05-18 16:49networkbSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=384#r384
2010-05-18 16:52adrianromeroStatusnew => scheduled
2010-05-18 16:52adrianromerofix_in_branch => pi
2010-06-02 17:23jonalegriaesarteAssigned Todalsasua => eduardo_Argal
2010-06-21 16:37eduardo_ArgalNote Added: 0028633
2010-06-21 16:37eduardo_ArgalStatusscheduled => resolved
2010-06-21 16:37eduardo_ArgalFixed in SCM revision =>
2010-06-21 16:37eduardo_ArgalResolutionopen => fixed
2010-07-02 12:18dmitry_mezentsevRelationship addedrelated to 0013652
2010-09-07 13:27jonalegriaesarteNote Added: 0030760
2010-09-07 13:27jonalegriaesarteStatusresolved => new
2010-09-07 13:27jonalegriaesarteResolutionfixed => open
2010-09-09 13:12adrianromeroRelationship addedblocks 0013657
2010-09-09 13:12adrianromeroRelationship deletedblocks 0013657
2010-09-09 13:13adrianromeroRelationship addedrelated to 0013657
2010-09-09 13:35adrianromeroFile Added: MaxRowsExceeded.diff
2010-09-09 13:36adrianromeroNote Added: 0030896
2010-09-09 13:36adrianromeroAssigned Toeduardo_Argal => adrianromero
2010-09-09 13:37adrianromeroStatusnew => scheduled
2010-09-10 10:07emartinezIssue Monitored: emartinez
2010-09-10 10:30emartinezNote Added: 0030928
2010-09-20 14:59sivaramanFile Added: Fixes_Issue_13361.diff
2010-09-20 14:59sivaramanAssigned Toadrianromero => sivaraman
2010-09-20 15:15sivaramanNote Added: 0031232
2010-09-23 13:06adrianromeroStatusscheduled => resolved
2010-09-23 13:06adrianromeroResolutionopen => fixed
2010-09-28 10:48adrianromeroFile Added: Fixes_Issue_13361 (updated).diff
2010-12-14 18:31psarobeStatusresolved => closed
2010-12-16 22:15anonymoussf_bug_id0 => 3138771

Notes
(0027424)
adrianromero   
2010-05-18 13:54   
What does "Do not work well" mean. Could you please be more detailed.

http://wiki.openbravo.com/wiki/Bug_Reporting_Guidelines#Quick_guide_to_writing_good_bug_reports [^]
(0028633)
eduardo_Argal   
2010-06-21 16:37   
Diff sent to customer. Once it is validated on their side changes will be applied to pi
(0030760)
jonalegriaesarte   
2010-09-07 13:27   
The problem persists. If you filter by Sep.2009 and you generate the html report -> OK, if you generate the xls report ->KO and if you generate the pdf report -> KO. Thanks.
(0030896)
adrianromero   
2010-09-09 13:36   
The attached file MaxRowsExceeded.diff contains the solution proposed. It is only missing to apply the limit for the PDF report.
(0030928)
emartinez   
2010-09-10 10:30   
The export to excel does not work neither.
(0031232)
sivaraman   
2010-09-20 15:15   
The uploaded patch (Fixes_Issue_13361.diff) has included a check that will not allow PDF report if row count exceeds PDF_REPORT_LIMIT. Actually, this report limit is supposed to be taken from preference. As we don't have the option in MP14, it has been hard coded in ReportGeneralLedger.java. Kindly change the value before to test the limitation.