Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0014406Openbravo ERP04. Warehouse managementpublic2010-09-02 13:482010-09-22 00:00
Reporternetworkb 
Assigned Toadrianromero 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version2.50MP20 
Target Version2.50MP22Fixed in Version2.50MP22 
Merge Request Status
Review Assigned To
OBNetwork customerOBPS
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0014406: The callout SL_Inventory_Locator.java does not work well in some conditions.
DescriptionThe callout SL_Inventory_Locator.java does not work well in some conditions.
This happens when you have add a secondary UOM to a product after being working
with the product without this secondary UOM.
Steps To Reproduce-Create a product using UNIT as UOM
-Create a good receipt for this product, quantity 100.
-complete it.

-Go to phisycal inventory window. Create a new header and go to the lines.
-Create a new line selecting the product used in the shipment. See that the fields are correctly filled with the quantity 100.

-Add a new secondary UOM to the product used. i.e. kg.
-Add conversions for that new UOM- unit:10<->kg:1
-Create a new good receipt for the product using the secondary UOM. i.e: 5 kg=50 unit. Use the same locator used in the previous shipment
-complete the shipment

--Go to phisycal inventory window. Create a new header and go to the lines.
-Create a new line and select the product we are using.
-See that you have two lines for that producto. one using only the primary UOM,
and the other with the secondary UOM.
-Select the one using the secondary UOM.
-After select, the fields are filled, but another callout is executed
SL_Inventory_Locator and the fields are reseted using the information of the product without secondary UOM.

Proposed SolutionModify the select on the SL_Inventory_Locator_data.xsql and the java file in order to be able to use the new select that should have a new parameter (optional).
The change on the select should be to add a new optional parameter to use in the conditions also the secondary UOM becasue if you don't use it. the select
will select the two lines on the m_storage_detail table, the one using secondary UOM and the other that does not use it.
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-09-02 13:48networkbNew Issue
2010-09-02 13:48networkbAssigned To => adrianromero
2010-09-02 13:48networkbOBNetwork customer => Yes
2010-09-09 11:54adrianromeroStatusnew => scheduled
2010-09-09 11:54adrianromerofix_in_branch => pi
2010-09-10 13:58hgbotCheckin
2010-09-10 13:58hgbotNote Added: 0030938
2010-09-10 13:58hgbotStatusscheduled => resolved
2010-09-10 13:58hgbotResolutionopen => fixed
2010-09-10 13:58hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/03ad86a81a20906459f660f55fbda5fa92274cb8 [^]
2010-09-10 14:03adrianromeroNote Added: 0030939
2010-09-11 04:15hudsonbotCheckin
2010-09-11 04:15hudsonbotNote Added: 0030954
2010-09-21 10:18psarobeNote Added: 0031257
2010-09-21 10:18psarobeStatusresolved => closed
2010-09-21 10:18psarobeFixed in Version => 2.50MP22
2010-09-22 00:00anonymoussf_bug_id0 => 3072971

Notes
(0030938)
hgbot   
2010-09-10 13:58   
Repository: erp/devel/pi
Changeset: 03ad86a81a20906459f660f55fbda5fa92274cb8
Author: Adrián Romero <adrianromero <at> openbravo.com>
Date: Fri Sep 10 13:57:25 2010 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/03ad86a81a20906459f660f55fbda5fa92274cb8 [^]

Fixes issue 0014406: The callout SL_Inventory_Locator.java does not work well in some conditions.
It has been modified the request of data to take into account the secondary UOM when available to get the correct data line

---
M src/org/openbravo/erpCommon/ad_callouts/SL_Inventory_Locator.java
M src/org/openbravo/erpCommon/ad_callouts/SL_Inventory_Locator_data.xsql
---
(0030939)
adrianromero   
2010-09-10 14:03   
* Testing of the issue

Just follow the steps to test and verify that the values are properly assigned when the product is selected with the primary UOM or the secondary UOM. Verify also that the behavior of products with just one UOM has not been modified.

* Other areas affected

It has only been modified the callout of the Physical inventory lines tab SL_Inventory_Locator and its SQL associated. No other areas affected.
(0030954)
hudsonbot   
2010-09-11 04:15   
A changeset related to this issue has been promoted to main after passing a series of tests and an OBX has been generated:

Changeset: http://code.openbravo.com/erp/devel/main/rev/03ad86a81a20 [^]
Merge Changeset: http://code.openbravo.com/erp/devel/main/rev/bc66d27c7c23 [^]
Tests: http://builds.openbravo.com/view/int/ [^]
OBX: http://builds.openbravo.com/erp/core/obx/OpenbravoERP-2.50CI.18368.obx [^]
(0031257)
psarobe   
2010-09-21 10:18   
Tested working fine