c2c-oerpscenario team mailing list archive

["vra \(openerp\)" <423124@xxxxxxxxxxxxxxxxxx>]

** Also affects: openobject-addons/5.0
   Importance: Undecided
       Status: New

** Also affects: openobject-addons/trunk
   Importance: Undecided
       Status: Confirmed

** Changed in: openobject-addons/trunk
   Importance: Undecided => Low

** Changed in: openobject-addons/trunk
     Assignee: (unassigned) => OpenERP R&D Addons Team 2 (openerp-dev-addons2)

** Changed in: openobject-addons/5.0
       Status: New => Triaged

-- 
PO does wrongly take into account supplier information in product when using purchase UOM
https://bugs.launchpad.net/bugs/423124
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Addons Modules: Confirmed
Status in OpenObject Addons 5.0 series: Triaged
Status in OpenObject Addons trunk series: Confirmed

Bug description:
SITUATION IDENTIFIED IN:
Purchase order, price calculation of order line.

REPRODUCTION ENVIRONMENT:
Stable version 5.0.3 via bazaar updated today via bazaar.
revision-id: jvo@xxxxxxxxxxx-20090901132612-lzwqtjho1dsbu2z5
date: 2009-09-01 18:56:12 +0530
build-date: 2009-09-02 13:37:30 +0200
revno: 2372
branch-nick: addons

PROBLEM DESCRIPTION:
When using different product UOM's for storage and purchase, the price calculation for purchase order line is wrongly computed when making use of supplier information

SPECIFIC PARAMETER SETUP:
Go pricelist on PO --> Select the pricelist version --> Select Pricelist item.
Set based on selection field to be ''Partner section of the product form'.
See https://answers.launchpad.net/openobject-addons/+question/74021 where this process is answered.

STEPS TO BE FOLLOWED:
Create a product with storage unit is pair ( defined as 2 pcs) and purchase unit is Box (defined as 30 pcs = 15 pairs)
A Box of 15 pairs costs to purchase 47,93 euro excl. tax, resulting that a pair costs 3.1953333 euro.
The cost price of this product is stored as pair and rounded to 3.20 euro. No problem as we can set in purchase supplier information on the third tab that we purchase 1 box for 47,93 euro.

OBSERVED RESULT:
The PO is not taken into account the purchase unit. It will calculate always on storage unit, not on the purchase unit. This will result in using always rounded purchase prices of 3.20 euro, and not the 47,93 euro for 1 box. This way we never get the right purchase price on the purchase order.

EXPECTED RESULT:
That purchase price calculation will be based on the purchase unit defined in the product and that the supplier information does take the purchase unit into account (instead of the storage unit).

ADDITIONAL COMMENTS:
Tested on standard Manufacturing environment and Manufacturing environment with account_anglo_saxon module installed. 
Please check when providing a standard solution if account_anglo_saxon needs a modification too (you may contact hda internally for this if needed).