Multiple UOM not handled by Inventory Analysis

Bug #741457 reported by snook
34
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Fix Released
Low
OpenERP R&D Addons Team 2

Bug Description

version: 6.0.1 stable
rev: 4467 (addons)
platform: Ubuntu 10.04

1. Create a UOMs as follows:
    "PCE" of category "unit" with ratio = 1
    "CT (12)" of category "unit" with ratio = 12

2. Create a product:
    name="Orval Beer"
    cost=12.00
    default Unit of Measure="CT (12)"
    default Purchase Unit of Measure="CT (12)"
    Assign a Supplier for later Purchase Order test

3. Add starting stock:
    On product form, click "Update" button and add stock quantity of 10.00 to "Stock" location.

4. Perform Inventory Analysis.
    Run: Warehouse/Reporting/Inventory Analysis

    Search for "Orval" to locate the product

    Issue#1 "Quantity" is NOT expressed in the products "default UOM" (should be 10.00 not 120.00)
    Issue#2 "Total Value" is INCORRECT at 1440.00 (should be 120.00)

5. Perform a Procurement/Purchase/Reception
    Purchase and receive 10.00 with a UOM of "CT (12)"

   Examining the Product Form all looks okay, now 20.00 CT (12) in Real and Virtual Stock.

6. Perform Inventory Analysis
    Notice that now "Quantity" is 240.00 and "Total Value" is 2880.00 (at least consistent)

Looking behind the scene a little, the "report_stock_move" view in postgres is storing:
    a. "product_qty" column as 10.00 being a UOM of "CT (12)"
    b. "product_qty_in" as 120.00 being a UOM of "PCE"

This looks like trouble mixing representations of QUANTITY/UOM.

report_stock_move table/view records the "product_uom" as being "CT (12)" and yet "product_qty_in" is recorded as a UOM of "PCE"

----------------------------------------------
My summary of situation:

1. Invoice Analysis should express to user the "Quantity" as the product's default UOM
2. generation of report_stock_move records should be consistent when representing a quantity in the record.

ps: wish we had a preview function before posting, hope layout is okay

Tags: maintenance

Related branches

snook (snook)
summary: - Multiple UOM not handled by Inventory Analysis
+ [6.0.1] Multiple UOM not handled by Inventory Analysis
Revision history for this message
DBR (OpenERP) (dbr-openerp) wrote : Re: [6.0.1] Multiple UOM not handled by Inventory Analysis

Thanks for Reporting...

Changed in openobject-addons:
assignee: nobody → OpenERP R&D Addons Team 2 (openerp-dev-addons2)
importance: Undecided → Low
status: New → Confirmed
summary: - [6.0.1] Multiple UOM not handled by Inventory Analysis
+ Multiple UOM not handled by Inventory Analysis
Changed in openobject-addons:
status: Confirmed → In Progress
Revision history for this message
Rohan Nayani(Open ERP) (ron-tinyerp) wrote :

Hello,

Thanks for Reporting.
It has been fixed in lp:~openerp-dev/openobject-addons/trunk-bug-741457-ron
Revision ID: <email address hidden>
Revision num:4621.

It will be available in trunk soon,

Changed in openobject-addons:
status: In Progress → Fix Committed
Revision history for this message
snook (snook) wrote : Re: [Bug 741457] Re: Multiple UOM not handled by Inventory Analysis

Thanks

On Tue, Apr 5, 2011 at 1:29 PM, Rohan Nayani(openerp)
<email address hidden> wrote:
> Hello,
>
> Thanks for Reporting.
> It has been fixed in lp:~openerp-dev/openobject-addons/trunk-bug-741457-ron
> Revision ID: <email address hidden>
> Revision num:4621.
>
> It will be available in trunk soon,
>
> ** Changed in: openobject-addons
>       Status: In Progress => Fix Committed
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/741457
>
> Title:
>  Multiple UOM not handled by Inventory Analysis
>
> Status in OpenERP Modules (addons):
>  Fix Committed
>
> Bug description:
>  version: 6.0.1 stable
>  rev: 4467 (addons)
>  platform: Ubuntu 10.04
>
>
>  1. Create a UOMs as follows:
>      "PCE" of category "unit" with ratio = 1
>      "CT (12)" of category "unit" with ratio = 12
>
>  2. Create a product:
>      name="Orval Beer"
>      cost=12.00
>      default Unit of Measure="CT (12)"
>      default Purchase Unit of Measure="CT (12)"
>      Assign a Supplier for later Purchase Order test
>
>  3. Add starting stock:
>      On product form, click "Update" button and add stock quantity of 10.00 to "Stock" location.
>
>  4. Perform Inventory Analysis.
>      Run: Warehouse/Reporting/Inventory Analysis
>
>      Search for "Orval" to locate the product
>
>      Issue#1 "Quantity" is NOT expressed in the products "default UOM" (should be 10.00 not 120.00)
>      Issue#2 "Total Value" is INCORRECT at 1440.00 (should be 120.00)
>
>  5. Perform a Procurement/Purchase/Reception
>      Purchase and receive 10.00 with a UOM of "CT (12)"
>
>     Examining the Product Form all looks okay, now 20.00 CT (12) in
>  Real and Virtual Stock.
>
>  6. Perform Inventory Analysis
>      Notice that now "Quantity" is 240.00 and "Total Value" is 2880.00 (at least consistent)
>
>  Looking behind the scene a little, the "report_stock_move" view in postgres is storing:
>      a. "product_qty" column as 10.00 being a UOM of "CT (12)"
>      b. "product_qty_in" as 120.00 being a UOM of "PCE"
>
>  This looks like trouble mixing representations of QUANTITY/UOM.
>
>  report_stock_move table/view records the "product_uom" as being "CT
>  (12)" and yet "product_qty_in" is recorded as a UOM of "PCE"
>
>  ----------------------------------------------
>  My summary of situation:
>
>  1. Invoice Analysis should express to user the "Quantity" as the product's default UOM
>  2. generation of report_stock_move records should be consistent when representing a quantity in the record.
>
>  ps: wish we had a preview function before posting, hope layout is okay
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/openobject-addons/+bug/741457/+subscribe
>

--
<email address hidden>

C&G BUSINESS SYSTEMS

PO Box 439, Greenwood WA 6924

T: +61 (0) 8 6364 4893

F: +61 (0) 8 6364 4897

qdp (OpenERP) (qdp)
Changed in openobject-addons:
status: Fix Committed → Fix Released
tags: added: maintenance
Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Hello Snook,

Thanks for reporting, it has been fixed by revision 4566 <email address hidden>.

Changed in openobject-addons:
milestone: none → 6.0.3
Revision history for this message
Chandra L (vesper83) wrote :

ver: 6.0.2
rev: 4566
platform: ubuntu 10.10

it still not work properly

here is my case:
 1. create UOM

Revision history for this message
Chandra L (vesper83) wrote :

1.create product :
     Name : test
     purchase UOM : box 2000
     default UOM : PCE
     where box 2000 =2000 PCE

2.buy product :
     product : test
     qty : 20
     UOM : box 2000 (which is default purchase UOM)

3.result in warehouse
  A.product :
          product :test
          UOM : PCE
          qty available : 40.000
          virtual available : 40.000

  B.inventory analysis :
          product : test
          quantity : 20

4. sell and deliver product :
      product : test
      qty : 100
      UOM : PCE ( which is default UOM)

5. result in warehouse :
  A.product :
          product :test
          UOM : PCE
          qty available : 39.900 (correct)
          virtual available : 39.900 ( correct)

  B.inventory analysis :
          product : test
          quantity : -80 (not correct)

summary
1.inventory analysis add "quantity" in "purchase UOM" but subtract it with "default UOM"
2.i think it would be nice addition if we can filter stock level with several UOM or packing list :)

thank you

Revision history for this message
Kyle Waid (midwest) wrote :

I confirm also that the inventory valuation report is bogus. It gives us a number that is nearly 10 times lower than what it should be. You can calculate the actual value by exporting the real stock value in excel and times it by the cost price

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.