Purchase Goods From Supplier based on a Foreign Currency Pricelist
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Addons (MOVED TO GITHUB) |
Confirmed
|
Medium
|
OpenERP R&D Addons Team 1 |
Bug Description
Hi,
Please find appended below the details of the above mentioned issue:
1) OpenERP Version 7.0 (Test done on www.openerp.com demo account)
2) Inventory accounting method: Anglo Saxon Accounting (Setup for input/valuation
3) Inventory valuation method: Real-Time Automated (Average Cost)
4) Test 1: Company currency in $SGD. Set up currency table and updated SGD as 1.0000.
Test 2: Company Default Currency in Euro set at 1.000.
5) Test 1: Supplier pricelist in GBP based on default purchase pricelist version $SGD (Cost Price).
Test 2: Supplier pricelist in SGD based on default purchase pricelist version Euro (Cost Price).
6) Proceed to create purchase order for goods bought from overseas supplier in GBP.
7) Tried to process receipt of goods by clicking receive goods on P.O. form this error message appears on both tests:
-------
ValidateError
Error occurred while validating the field(s) amount_currency: The amount expressed in the secondary currency must be positif when journal item are debit and negatif when journal item are credit.
-------
Kindly advise further. Thank you for your kind attention.
Warmest Regards,
Ashley Marc
Changed in openobject-addons: | |
assignee: | nobody → OpenERP R&D Addons Team 3 (openerp-dev-addons3) |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in openobject-addons: | |
assignee: | OpenERP R&D Addons Team 3 (openerp-dev-addons3) → OpenERP R&D Addons Team 1 (openerp-dev-addons1) |
Dear all,
I'm really busy currently and will not have the time to reproduce this bug. As it is a confirmed one, I can think that this exception is raised...
What I'm sure about is that the constraint we've put here is good. We need positive amount currency at debit and negative at credit and this should NEVER be made otherwise...
So I think the trouble comes from the generated entries that should respect the constraints. So please, do not change the constraints to solve the bug :) !
Looking the code, may be we forget in the constraint the case where debit AND credit = 0.0, but this sounds a use case that should not happened. As long as we are not in that case, the correction need to be made where the entries have been generated. Again, do not touch the constraints as it was there to prevent such case.
Hope this helps.
Regards,
Joël