Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0036738Openbravo ERP09. Financial managementpublic2017-08-29 12:502017-09-08 13:07
Reporterngarcia 
Assigned ToAtulOpenbravo 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Toaferraz
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0036738: Performance problems in General Ledger Report when grouping it by Business Partner
DescriptionPerformance problems in General Ledger Report when grouping it by Business Partner

In an environment with the following data, the report takes one hour:

- 11127 records in FACT_ACCT table for the date range selected
- 3507 different business partners on that records
Steps To ReproduceAs group admin role:
   Launch the General Ledger Report from 01-01-2017 to 31-07-2017
   Filter it by only one account: Clientes (euros) a corto plazo
   Group By Business Partner
   Check the report remains waiting and do not show any value
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 0035157 closed AtulOpenbravo The report general ledger journal colapse the system when the query gets thousands of rows 
related to design defect 0035947 new Triage Omni OMS Prevent user to launch accounting reports more than one time 
related to defect 0037188 closed AtulOpenbravo Performance problems in General Ledger Report 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2017-08-29 12:50ngarciaNew Issue
2017-08-29 12:50ngarciaAssigned To => Triage Finance
2017-08-29 12:50ngarciaModules => Core
2017-08-29 12:50ngarciaResolution time => 1505772000
2017-08-29 12:50ngarciaTriggers an Emergency Pack => No
2017-08-29 12:51ngarciaRelationship addedrelated to 0035157
2017-08-29 12:51ngarciaIssue Monitored: networkb
2017-08-29 12:52ngarciaRelationship addedrelated to 0035947
2017-08-29 19:05jfrancesIssue Monitored: jfrances
2017-08-30 09:39ngarciaDescription Updatedbug_revision_view_page.php?rev_id=15761#r15761
2017-08-30 10:24aferrazAssigned ToTriage Finance => markmm82
2017-08-30 14:54aferrazAssigned Tomarkmm82 => aferraz
2017-08-30 14:54aferrazAssigned Toaferraz => AtulOpenbravo
2017-09-01 12:25AtulOpenbravoStatusnew => scheduled
2017-09-08 13:07aferrazReview Assigned To => aferraz
2017-09-08 13:07aferrazNote Added: 0098909
2017-09-08 13:07aferrazStatusscheduled => closed
2017-09-08 13:07aferrazResolutionopen => no change required
2017-10-30 17:07JONHMRelationship addedrelated to 0037188

Notes
(0098909)
aferraz   
2017-09-08 13:07   
Problem is due to a big value in Session Preferences records range parameter.
General Ledger report uses this value as report pagination when running it in HTML.
If we set a lower value (e.g. 100), report is correctly paginated and it takes only some seconds.