Tuesday, February 7, 2017
2 changes · master
Enhancements to existing features
The Purchase app settings now use the clearer label “Purchase Agreements” instead of “Call for Tenders” where vendor agreements are configured. This helps users better understand that blanket orders and similar vendor agreements are managed under this option, not only competitive tender requests.
Original PR description
Task : https://www.odoo.com/web#id=30883&view_type=form&model=project.task&action=333&active_id=131&menu_id=4720 Pad : https://pad.odoo.com/p/r.b4ddac3e87299228dcdea4d04ce97031 Description of the issue/feature this PR addresses: Current behavior before PR: - A blanket order (it's an agreement with a vendor) is not a call for tenders (you aks several vendor to provide you an offer) but they are regrouped under the category "Calls for tenders" in the Settings of Purchase which shoulld be changed . Desired behavior after PR is merged: - Change the setting option for 'Call For Tenders' : https://drive.google.com/a/odoo.com/file/d/0B0ITmdw6h3ZrZGxoX3R3V1JHekE/view?usp=drivesdk - Change 'Purchase Requisitions -> 'Purchase Agreements' : https://drive.google.com/file/d/0B0ITmdw6h3ZrZF9iazdDS2hnWmM/view -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Manufacturing now stores the available quantity value instead of recalculating it each time. This avoids tiny rounding differences that could cause inconsistent quantity comparisons or decisions in production workflows.
Original PR description
We store quantity available to avoid numerical inconsistencies. For exemple, with a rounding of 1e-6: - `product_uom_qty` = 0.058824 (stored) - `quantity_available` = 0.058823999999994 (not stored) The dependencies of the field are fixed from v10.0. opw-704775