Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | ||||||||
0031874 | ||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
design defect | [Modules] Valued Stock Enhanced | major | always | 2016-01-13 16:59 | 2016-12-28 10:54 | |||
Reporter | dmiguelez | View Status | public | |||||
Assigned To | Triage Omni OMS | |||||||
Priority | normal | Resolution | duplicate | Fixed in Version | ||||
Status | closed | Fix in branch | Fixed in SCM revision | |||||
Projection | none | ETA | none | Target Version | ||||
OS | Linux 32 bit | Database | PostgreSQL | Java version | 1.6.0_18 | |||
OS Version | Community Appliance | Database version | 8.3.9 | Ant version | 1.7.1 | |||
Product Version | SCM revision | |||||||
Regression date | ||||||||
Regression introduced by commit | ||||||||
Regression level | ||||||||
Review Assigned To | aferraz | |||||||
Regression introduced in release | ||||||||
Summary | 0031874: Performance problems in Valued Stock Report Enhanced | |||||||
Description | Performance problems in Valued Stock Report Enhanced with large volumes of data. | |||||||
Steps To Reproduce | Performance problems in Valued Stock Report Enhanced with large volumes of data. | |||||||
Proposed Solution | Create an aggregated table to store the information per accounting Period to the time it takes to run calculations needed in order to show the report. | |||||||
Tags | No tags attached. | |||||||
Attached Files | ||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |||||||||||||||||||||||||||||||||
|
Notes | |
(0083256) dmiguelez (developer) 2016-01-13 17:04 |
The proposal is: 1. Create an aggregated Table to store aggregated information for Stock and Valuation of the Stock. - This information should be grouped for each Product and Locator - This information needs to be created for each closed Accounting Period. The reason to do it is because the Valued Stock Report can be run as of Date, so it is needed to have aggregated information for different dates. - The information will be only stored for Closed and Permanently Closed Periods. 2. Create a Process to insert the information into the Table for each Closed Period. This Process will be scheduled as a background Process. 3. When a Period is Closed or Permanently Closed, the background Process will take it into account and will create the needed data when the process is run. 4. When a Period is Opened, if there is data for that Period (or for the next ones), it will be automatically deleted at that moment. |
Issue History | |||
Date Modified | Username | Field | Change |
2016-01-13 16:59 | dmiguelez | New Issue | |
2016-01-13 16:59 | dmiguelez | Assigned To | => Triage Finance |
2016-01-13 16:59 | dmiguelez | Relationship added | related to 0030197 |
2016-01-13 17:04 | dmiguelez | Note Added: 0083256 | |
2016-04-19 14:45 | aferraz | Relationship added | related to 0032493 |
2016-04-22 14:41 | ngarcia | Issue Monitored: ngarcia | |
2016-12-28 10:54 | aferraz | Review Assigned To | => aferraz |
2016-12-28 10:54 | aferraz | Relationship added | duplicate of 0034482 |
2016-12-28 10:54 | aferraz | Status | new => closed |
2016-12-28 10:54 | aferraz | Resolution | open => duplicate |
2017-03-02 17:40 | vmromanos | Relationship added | causes 0035415 |
Copyright © 2000 - 2009 MantisBT Group |