Initial Inventory Item Status is saved wrong in case of non-serialized 
inventory and when reason of return is "Defective Item", at the the time of 
receiving returns
----------------------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: OFBIZ-3552
                 URL: https://issues.apache.org/jira/browse/OFBIZ-3552
             Project: OFBiz
          Issue Type: Bug
          Components: product
    Affects Versions: SVN trunk
            Reporter: Divesh Dutta
             Fix For: SVN trunk


Problem Description:

1) When returns are received and  reason of return is "Defective Item" ,whether 
 inventoryItemType is serialized or non-serialized,   Initial Inventory Item 
Status is always saved as "INV_DEFECTIVE"

2) This should not be the case, value of Initial Inventory Item Status should 
be dependent on inventoryItemType.

3) i. e In Receive Return screen , when user selects inventoryItemType value of 
Initial Inventory Item Status should be changed dynamically .

4) So when inventoryItemType is non-serialized then value of Initial Inventory 
Item Status should be INV_NS_DEFECTIVE and if  inventoryItemType is serialized 
value of value of Initial Inventory Item Status should be INV_DEFECTIVE.

5) This is a real bug, which causes ATP inventory figures wrong when sales 
order is placed. This is so because when sales order is placed, defective 
inventory items are assigned to sales order. 

6) Reason of #5 is when inventory reservations are done in case of 
non-serialized inventory, In reserveForInventoryItemInline simple-method of 
InventoryReserveServices.xml , checks are made on value of 
inventoryItem.statusId = "INV_NS_DEFECTIVE".
And as described in #1, Initial Inventory Item Status is always saved as 
"INV_DEFECTIVE". So this checks never gets satisfied. 




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to