Anonymous | Login

Project:

News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ]

[ Issue History ] [ Print ]

ID

0036070

Type

Category

Severity

Reproducibility

Date Submitted

Last Update

design defect

[Openbravo ERP] 09. Financial management

major

always

2017-05-23 11:25

2017-08-25 13:42

Reporter

egoitz

View Status

public

Assigned To

Triage Omni OMS

Priority

urgent

Resolution

open

Fixed in Version

Status

acknowledged

Fix in branch

Fixed in SCM revision

Projection

none

ETA

none

Target Version

OS

Any

Database

Any

Java version

OS Version

Database version

Ant version

Product Version

SCM revision

Review Assigned To

Web browser

Modules

Core

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

No

Summary

0036070: Performance problems on the journal entries report.

Description

Executing the report for a year where there is a huge amount of data takes long.

Steps To Reproduce

1. 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.

Tags

No tags attached.

Relationships [ Relation Graph ] [ Dependency Graph ]

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

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

Issue History
Date Modified	Username	Field	Change
2017-05-23 11:25	egoitz	New Issue
2017-05-23 11:25	egoitz	Assigned To	=> Triage Finance
2017-05-23 11:25	egoitz	Modules	=> Core
2017-05-23 11:25	egoitz	Resolution time	=> 1496181600
2017-05-23 11:25	egoitz	Triggers an Emergency Pack	=> No
2017-05-23 11:25	egoitz	Issue generated from	0035947
2017-05-23 11:25	egoitz	Relationship added	related to 0035947
2017-05-24 10:59	aferraz	Assigned To	Triage Finance => markmm82
2017-05-25 18:46	markmm82	Status	new => scheduled
2017-05-29 16:39	aferraz	Relationship added	related to 0035157
2017-06-02 12:36	aferraz	Note Added: 0097104
2017-06-02 12:36	aferraz	Assigned To	markmm82 => Triage Finance
2017-06-02 12:36	aferraz	Status	scheduled => acknowledged
2017-06-02 12:37	aferraz	Type	defect => design defect
2017-06-02 12:38	aferraz	Note Edited: 0097104	View Revisions
2017-06-02 12:39	aferraz	Relationship added	related to 0035563
2017-06-02 12:39	aferraz	Relationship added	related to 0031740
2017-08-25 13:42	ngarcia	Note Added: 0098656
2017-08-25 13:45	ngarcia	Note Deleted: 0098656

Copyright © 2000 - 2009 MantisBT Group