Odoo Changelog — 2019-08-01

Thursday, August 1, 2019

3 changes

Bug Fixes(3)

Resolved issues and error corrections

[REF] stock_account: _compute_average_price unit price rounding

Coremasterstock_account

This update adjusts how average product costs are calculated so small currency rounding differences are reduced. It helps keep inventory valuation and invoice-related accounting amounts more consistent, especially in Anglo-Saxon accounting flows.

Original PR description

Since the introduction of the stock valuation layer, unit_cost is
rounded in the company currency (actually it is NOT because of an ORM
bug that will be fixed later). With the test introduced at [0], fixing
that ORM bug shows we have a rounding issue (27.02 instead of 27) due to
the company currency rounding on the unit_cost. Since the logic of the
anglo saxon will probably always give some rounding issue (we always
return a price unit that will be multiply by the invoiced quantity)
recomputing a not rounded price unit by using the not rounded value with
the not rounded quantity seems a good enough compromise.

[0] 13a535a0918f6f75d8c631a465fbc9238ea954bf

#inventory#accounting#rounding

[MERGE] base: remove field source of ir.translation

PR #34598

Coremasterbasetransifexwebsite_gengotest_new_apiMEDIUM

Odoo now keeps translation source text in sync automatically instead of storing a separate outdated source field. This improves consistency when records are edited in single-language or multi-language databases, reducing cases where users could still see old translated values after an update.

Original PR description

Instead, make sure the field src is always up to date

Change a bit the behaviour of `_write` to always try to update potential
translations when in monolanguage (was only done in multi-language if different
than en_US) and always create translations when writing on a translatable field
when in multi-language (was skipped in en_US)

Add tests

Task-id: 2031752
Pad: https://pad.odoo.com/p/r.dbf835d0aae979d858f73446dcbfb1df

#translations#localization#data consistency

[REF] mrp_mps: date_planned

PR #4992

Enterprisemastermrp_mps

Restores a planning date used by the manufacturing master production schedule to decide whether a purchase order already covers a need. This helps avoid unnecessary duplicate purchase orders after a related purchasing logic change.

Original PR description

Community changed the logic of date_planned on the PO but mrp_mps still
needs the original to know if it should create a new po or not.
Reintroduce the needed field.

task-2032417

#manufacturing#purchase orders#planning

Since the introduction of the stock valuation layer, unit_cost is rounded in the company currency (actually it is NOT because of an ORM bug that will be fixed later). With the test introduced at [0], fixing that ORM bug shows we have a rounding issue (27.02 instead of 27) due to the company currency rounding on the unit_cost. Since the logic of the anglo saxon will probably always give some rounding issue (we always return a price unit that will be multiply by the invoiced quantity) recomputing a not rounded price unit by using the not rounded value with the not rounded quantity seems a good enough compromise. [0] 13a535a0918f6f75d8c631a465fbc9238ea954bf

Instead, make sure the field src is always up to date Change a bit the behaviour of `_write` to always try to update potential translations when in monolanguage (was only done in multi-language if different than en_US) and always create translations when writing on a translatable field when in multi-language (was skipped in en_US) Add tests Task-id: 2031752 Pad: https://pad.odoo.com/p/r.dbf835d0aae979d858f73446dcbfb1df