Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0015546 | Openbravo ERP | 02. Master data management | public | 2010-12-29 18:05 | 2012-01-31 18:46 |
|
Reporter | RenateNieuwkoop | |
Assigned To | mirurita | |
Priority | normal | Severity | major | Reproducibility | always |
Status | scheduled | Resolution | open | |
Platform | | OS | 5 | OS Version | |
Product Version | 3.0RC3 | |
Target Version | | Fixed in Version | | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0015546: 3.0RC3: ABC Code, used for Warehouse Management, is missing from the Product screen |
Description | The pareto report is part of warehouse management and assigns an ABC code to products. The ABC code is used for Physical Inventory also.
The ABC code was on the org specific tab, but that does not make any sense, since all fields on that tab are related to MRP setups.
So the proposal is, as discussed with Dmitry, to add the ABC code to the general tab of the product. |
Steps To Reproduce | |
Proposed Solution | As per Dmitry's mail:
I checked our description of business process and wall-to-wall count starts from ABC report so I would prefer not to change the basis (business process) on which we agreed on but to change the field placement. |
Additional Information | |
Tags | No tags attached. |
Relationships | related to | defect | 0019481 | | closed | Sandrahuguet | "Pareto Product Report" must be set as "Professional" feature same applies to "ABC Activity" |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2010-12-29 18:05 | RenateNieuwkoop | New Issue | |
2010-12-29 18:05 | RenateNieuwkoop | Assigned To | => adrianromero |
2010-12-29 18:05 | RenateNieuwkoop | Modules | => Core |
2011-02-09 19:34 | psarobe | Target Version | 3.0RC4 => 3.0 |
2011-05-20 17:58 | psarobe | Note Added: 0037292 | |
2011-05-20 17:58 | psarobe | Status | new => scheduled |
2011-05-20 17:58 | psarobe | Target Version | 3.0MP0 => 3.0MP3 |
2011-06-03 10:57 | dalsasua | Assigned To | adrianromero => dalsasua |
2011-07-20 18:16 | dalsasua | Assigned To | dalsasua => jonalegriaesarte |
2011-08-23 10:47 | jonalegriaesarte | Assigned To | jonalegriaesarte => psarobe |
2011-08-31 11:36 | jonalegriaesarte | Note Added: 0040605 | |
2011-08-31 11:36 | jonalegriaesarte | Target Version | 3.0MP3 => 3.0MP4 |
2011-09-15 12:52 | dalsasua | Assigned To | psarobe => mirurita |
2011-09-30 10:12 | jonalegriaesarte | Note Added: 0041392 | |
2011-09-30 10:12 | jonalegriaesarte | Target Version | 3.0MP4 => 3.0MP5 |
2011-10-29 16:30 | psarobe | Type | defect => design defect |
2011-10-31 11:56 | jonalegriaesarte | Note Added: 0042397 | |
2011-10-31 11:56 | jonalegriaesarte | Target Version | 3.0MP5 => |
2012-01-20 08:57 | RenateNieuwkoop | Note Added: 0044455 | |
2012-01-31 18:34 | dmitry_mezentsev | Relationship added | related to 0019481 |
2012-01-31 18:46 | dmitry_mezentsev | Note Added: 0044744 | |
2015-05-14 15:07 | plujan | Relationship added | has duplicate 0014885 |
Notes |
|
|
Needs to be refactored or find a better solution |
|
|
(0040605)
|
jonalegriaesarte
|
2011-08-31 11:36
|
|
Due to the load with other issues we were not able to research this one for MP3, are planning MP4 for it now. |
|
|
(0041392)
|
jonalegriaesarte
|
2011-09-30 10:12
|
|
Due to the load with other issues we were not able to research this one for MP4, are planning MP5 for it now. |
|
|
(0042397)
|
jonalegriaesarte
|
2011-10-31 11:56
|
|
Removing target version because it is a design defect |
|
|
(0044455)
|
RenateNieuwkoop
|
2012-01-20 08:57
|
|
This issue is related to issue 19481, please add relationship. If the Pareto is considered a professional feature, this field should also be displayed only upon activation of the instance.
thanks
Renate |
|
|
|
Writing the documentation I clarified that ABC classification is indeed Org.Specific and one product for different organizations can have different classification. So moving this field to the Header is not a good idea as I thought before.
So the best solution would be to separate current Org.Specific Tab to 2 placing in one things that are related to Production and to another that are not. |
|