Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0005823 | Openbravo ERP | 04. Warehouse management | public | 2008-11-04 17:22 | 2011-02-04 09:15 |
|
Reporter | jtarbal | |
Assigned To | rmorley | |
Priority | normal | Severity | major | Reproducibility | always |
Status | acknowledged | Resolution | open | |
Platform | | OS | 5 | OS Version | |
Product Version | 2.40beta | |
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 | 0005823: Same product with the same lot number purchased multiple times should appear in the same stock |
Description | Same product purchased at different times with the same lot number appears twice in stock (or as many times as purchased).
In this case, it would be great if the stock of the different entries would be grouped, so that in the stock report the same product and attributes appreared only once.
In the same way, when doing a goods shipment, the different entries are treated as different products, although they have the same attributes and are stored in the same storage bin. This is a problem in the next example:
- Imagine we received in two times 10 units of product A of lot 1 in storage bin SB1 and 15 units of product A of lot 1 in storage bin SB1 (same product, attributes and storage bin).
- If we need to ship 18 units of product A, we will have to create a goods shipment with two different lines, for example 10 units of product A of lot 1 from storage bin SB1 and 8 units of product A of lot 1 from storage bin SB1. Otherwise, the stock report will show -8 units of product A of lot 1 in storage bin SB1 and 15 units of product A of lot 1 in storage bin SB1, instead of showing 7 units of product A of lot 1 in storage bin SB1.
|
Steps To Reproduce | |
Proposed Solution | |
Additional Information | |
Tags | Clean-up, ReleaseCandidate |
Relationships | |
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2008-11-04 17:22 | jtarbal | New Issue | |
2008-11-04 17:22 | jtarbal | Assigned To | => rafaroda |
2008-11-04 17:22 | jtarbal | sf_bug_id | 0 => 2221492 |
2008-11-10 14:25 | rafaroda | Assigned To | rafaroda => pjuvara |
2008-11-17 08:20 | pjuvara | Type | feature request => defect |
2008-11-24 10:22 | rafaroda | Regression testing | => No |
2008-11-24 10:22 | rafaroda | Status | new => closed |
2008-11-24 10:22 | rafaroda | Note Added: 0010541 | |
2008-11-24 10:22 | rafaroda | Resolution | open => no change required |
2008-11-24 12:32 | jtarbal | Note Added: 0010556 | |
2008-11-24 12:50 | rafaroda | Status | closed => new |
2008-11-24 12:50 | rafaroda | Resolution | no change required => open |
2008-11-24 12:51 | rafaroda | Type | defect => feature request |
2008-11-24 12:58 | pjuvara | Tag Attached: Clean-up | |
2008-11-24 12:58 | pjuvara | Tag Attached: ReleaseCandidate | |
2008-11-24 12:58 | pjuvara | Status | new => acknowledged |
2008-11-24 12:59 | pjuvara | Summary | Same product purchased at different times with the same lot number appears twice in stock (or as many times as purchased) => Same product with the same lot number purchased multiple times should appear in the same stock |
2009-02-18 09:58 | jtarbal | Note Added: 0013627 | |
2011-02-04 09:15 | jpabloae | Assigned To | pjuvara => rmorley |
Notes |
|
|
This is not a bug but yes the normal behaviour of the application. Lot attribute is a instanciable attribute so it creates you a new entry in the m_ttributeinstance table. Another thing is that your configuration is not the correct one as you are allowing to have negative stock. |
|
|
|
This was a feature request and not a bug. We know that this is not the current behavior of the system, but we think it should be improved. Please, classify it as feature request. |
|
|
|
The impact of not having this feature is that even if in the warehouse there is enough quantity to deliver a sales order for specific product and attributes, if the reception of the goods has been done in different "Goods Receipt" documents, it is not possible to put in one line in the "Goods Shipment" the quantity that is needed to be delivered. As the application is not capable to sum up the quantities of the different receptions, it has to be treated as different products with different attributes even if it is not true. Thus, this is a "must have" in all industries that use attributes for the purchased products. |
|