Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0036070Openbravo ERP09. Financial managementpublic2017-05-23 11:252017-08-25 13:42
Reporteregoitz 
Assigned ToTriage Omni OMS 
PriorityurgentSeveritymajorReproducibilityalways
StatusacknowledgedResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerOBPS
Web browser
ModulesCore
Support ticket46627
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0036070: Performance problems on the journal entries report.
DescriptionExecuting the report for a year where there is a huge amount of data takes long.
Steps To Reproduce1. Access to Journal Entries Report and set any filtering criteria for one year and organization *.
2. Getting the report on any of the available outputs (pdf,html or excel) takes long.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to design defect 0035947 new Triage Omni OMS Prevent user to launch accounting reports more than one time 
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 0035563 acknowledged vmromanos Trial Balance report takes long to be printed on xls. 
related to design defect 0031740 new dmiguelez Report trial balance report is slow with high number of transactions 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2017-05-23 11:25egoitzNew Issue
2017-05-23 11:25egoitzAssigned To => Triage Finance
2017-05-23 11:25egoitzOBNetwork customer => Yes
2017-05-23 11:25egoitzModules => Core
2017-05-23 11:25egoitzSupport ticket => 46627
2017-05-23 11:25egoitzResolution time => 1496181600
2017-05-23 11:25egoitzTriggers an Emergency Pack => No
2017-05-23 11:25egoitzIssue generated from0035947
2017-05-23 11:25egoitzRelationship addedrelated to 0035947
2017-05-24 10:59aferrazAssigned ToTriage Finance => markmm82
2017-05-25 18:46markmm82Statusnew => scheduled
2017-05-29 16:39aferrazRelationship addedrelated to 0035157
2017-06-02 12:36aferrazNote Added: 0097104
2017-06-02 12:36aferrazAssigned Tomarkmm82 => Triage Finance
2017-06-02 12:36aferrazStatusscheduled => acknowledged
2017-06-02 12:37aferrazTypedefect => design defect
2017-06-02 12:38aferrazNote Edited: 0097104bug_revision_view_page.php?bugnote_id=0097104#r15284
2017-06-02 12:39aferrazRelationship addedrelated to 0035563
2017-06-02 12:39aferrazRelationship addedrelated to 0031740
2017-08-25 13:42ngarciaNote Added: 0098656
2017-08-25 13:45ngarciaNote Deleted: 0098656

Notes
(0097104)
aferraz   
2017-06-02 12:36   
(edited on: 2017-06-02 12:38)
Moved to design defect.

Launching the report for a year is not a normal use case as it will return huge information which will be useless.

It could make sense to print the report once at the end of the year for the whole year, in order to have this info recorded. In this case, the report will take long time in case huge accounting data due to two reasons:
- Accounting data needs to be aggregated to show debit and credit values grouped by date and account.
- Huge data will need to be rendered to be printed in pdf or xls.

One approach to avoid the first problem could be to have this aggregated data previously calculated in a different table.