summaryrefslogtreecommitdiff
path: root/addons/mail/static/src/xml/thread.xml
diff options
context:
space:
mode:
authorjem-odoo <jem@openerp.com>2017-12-12 09:29:35 +0100
committerjem-odoo <jem@openerp.com>2018-01-29 17:16:27 +0100
commit75995f5965b36b07dcce67375fd0031b32b766ef (patch)
tree18af041fdf457a9a310d493eb74baab94dc74789 /addons/mail/static/src/xml/thread.xml
parentaaced1542c21fb14d79162d781cc64d6ce1331c1 (diff)
[IMP] sale,sale_*: correct use of expense_policy
A product can be sell or expense, but for some cases the product configuration make both flow incompatible. Indeed, when expensing the delivered qty was computed based on the AAL total amount, and manually editable. Before the delivered qty refactoring, reexpensing erased the manual value. This came from the fact product expense policy is wrongly used: the delivered qty of expensable product is not manually editable, which is a problem for milestones (and other consumable product when stock is no installed). The new refactoring of deli qty API force the expense line to be completely readonly, but the problem is not completely solved; we still can't sell properly a expensable product. To do so, the SO line must be flag as coming from an expense or vendor bill, and the reinvoice product policy should only be used to calculate the price of new SO line. This commit: 1) reinforces the readonly caracter of expense SO line, by making the expense policy independent of the computation method for delivered qty on SOL. 2) prevents generate picking when updating ordered quantity on a expense SOL with a stockable product. 3) allows service to sell a task with zero hours as ordered quantity. (it still prevents task/project creation for expense SOL). 4) does not increment anymore an existing line when expensing product at sales price and invoicing at 'delivered qty'. The only line to be incremented will be the expense line (and not the native SOL).
Diffstat (limited to 'addons/mail/static/src/xml/thread.xml')
0 files changed, 0 insertions, 0 deletions