Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0003449 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| feature request | [Openbravo ERP] 04. Warehouse management | minor | always | 2008-01-22 22:46 | 2008-06-19 09:28 | |||
| Reporter | cromero | View Status | public | |||||
| Assigned To | cromero | |||||||
| Priority | normal | Resolution | fixed | Fixed in Version | 2.40 | |||
| Status | closed | Fix in branch | Fixed in SCM revision | na | ||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | SCM revision | |||||||
| Merge Request Status | ||||||||
| Review Assigned To | ||||||||
| OBNetwork customer | No | |||||||
| Web browser | ||||||||
| Modules | Core | |||||||
| Support ticket | ||||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0003449: Pareto Report | |||||||
| Description | It would be desirable to have a simple ABC report, which makes a list of all the products of the warehouse, giving the letters from A to C depending the amount of exits, value or whatever condition that these products have had in a period of time. This report is also called Pareto´s report, who said that the 20% of the products have the 80% of the total exits of the warehouse. The rationale for a Pareto report is usually that 20% of your products have 80% of the value and therefore these reports are usually structured as: · Product Code · Product Description · Quantity On Hand · Cost (either std or avg) · Value (Qty*Cost) · Class (A, B or C) Then, based on the classification you assign different frequency of cycle counting (A products are counted weekly, B products are counted monthly and C products yearly or never). So, it would be interesting not only to have a report but to be able to fully tie this functionality in the physical inventory process. For example, the calculated class A, B or C could be stored as org-specific product attribute and then used as a filter in the Create Inventory Count List process. | |||||||
| Tags | No tags attached. | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0007038) user71 2005-06-01 00:00 edited on: 2008-06-12 09:44 |
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis. You can see the original bug report in: https://sourceforge.net/support/tracker.php?aid=1877668 [^] |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2008-06-19 09:27 | pjuvara | Status | new => scheduled |
| 2008-06-19 09:28 | pjuvara | Status | scheduled => resolved |
| 2008-06-19 09:28 | pjuvara | Fixed in Version | => 2.40alpha |
| 2008-06-19 09:28 | pjuvara | svn_revision | => na |
| 2008-06-19 09:28 | pjuvara | Resolution | open => fixed |
| 2008-06-19 09:28 | pjuvara | Status | resolved => closed |
| 2008-06-19 09:28 | pjuvara | Fixed in Version | 2.40alpha => 2.40 |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |