Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0036738
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 09. Financial managementmajoralways2017-08-29 12:502017-09-08 13:07
ReporterngarciaView Statuspublic 
Assigned ToAtulOpenbravo 
PriorityurgentResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned Toaferraz
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0036738: 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
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
related to defect 0035157 closedAtulOpenbravo The report general ledger journal colapse the system when the query gets thousands of rows 
related to design defect 0035947 newTriage Omni OMS Prevent user to launch accounting reports more than one time 
related to defect 0037188 closedAtulOpenbravo Performance problems in General Ledger Report 

-  Notes
(0098909)
aferraz (manager)
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.

- Issue History
Date Modified Username Field Change
2017-08-29 12:50 ngarcia New Issue
2017-08-29 12:50 ngarcia Assigned To => Triage Finance
2017-08-29 12:50 ngarcia Modules => Core
2017-08-29 12:50 ngarcia Resolution time => 1505772000
2017-08-29 12:50 ngarcia Triggers an Emergency Pack => No
2017-08-29 12:51 ngarcia Relationship added related to 0035157
2017-08-29 12:51 ngarcia Issue Monitored: networkb
2017-08-29 12:52 ngarcia Relationship added related to 0035947
2017-08-29 19:05 jfrances Issue Monitored: jfrances
2017-08-30 09:39 ngarcia Description Updated View Revisions
2017-08-30 10:24 aferraz Assigned To Triage Finance => markmm82
2017-08-30 14:54 aferraz Assigned To markmm82 => aferraz
2017-08-30 14:54 aferraz Assigned To aferraz => AtulOpenbravo
2017-09-01 12:25 AtulOpenbravo Status new => scheduled
2017-09-08 13:07 aferraz Review Assigned To => aferraz
2017-09-08 13:07 aferraz Note Added: 0098909
2017-09-08 13:07 aferraz Status scheduled => closed
2017-09-08 13:07 aferraz Resolution open => no change required
2017-10-30 17:07 JONHM Relationship added related to 0037188

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker