卓忆翻译（英中对照）：Odoo9工作流的改变：销售和采购工作流的改变

Sale and purchase workflow

原文链接： https://www.odoo.com/groups/community-59/community-13922152?mode=thread

by

Fabien Pinckaers (fp)

- 09/16/2015 13:46:44

Hello,

A lot of people are asking more information about the changes in sale and purchase apps in Odoo 9, mostly the removal of the workflow.

In short, we did a huge cleanup of the sale.* and purchase.* modules while porting them to the new API. The result in 5000 lines of code removed, for more features supported, and no feature removed.

Why? 原因？

The v8 sale module had a lot of issues:

Odoo8的销售模块有些问题（潜台词是原有的工作流解决这些问题会比较麻烦）：

- not possible to modify a sale order (open orders) 不太可能修改销售订单

- no way to handle inter-company invoicing based on delivery/receptions (only one of the two invoices was generated)

- not possible to invoice kits based on deliveries

- too many different ways to incoice customers: based on sale order, based on sale order lines, based on support contracts, based on regular contracts, based on expenses, based on delivery orders, final invoice on timesheets, ...

- those different invoice methods could not be mixed in a single sale order (sell physical products with a support contract on timesheets)

- some of these invoicing methods were very complex to configure: to invoice on timesheet, you had to: 1/ create a SO, 2/ create a contract, 3/ set a product on the employee form, 4/ set the analytic_user_function to know to role of the user, 5/ invoice from the contract...

- contracts (based on analytic accounts) are a pain. They are complex to understand (support contracts vs regular contracts) and to manage on a regular basis. (e.g. How do you make a quotation for a new support contract?)

*How?* 方法

Complete rewrite the sale and purchase modules. We cleaned all the legacy code while porting everything to the new API. The net result is 5000 lines of python code removed. Less lines of code for more features is a good sign of something that is technically clean.

完全重写采购和销售模块。在移植到新API时清除了所有遗留的老API代码。移除了5000行Python代码。更少的代码更多的功能标志着在技术上更为干净。

*What are the main changes?* 主要的改变

In addition to the quantity ordered field on sale order lines, you have three new fields: Qty Delivered, Qty Invoiced, Qty to Invoice. Qty delivered can be set manually (milestones of a project you invoice manually) or computed based on timesheets or delivery orders. The two others fields are always computed.

The product has a new field "Invoice Method": based on quantities ordered, based on quantities delivered (could be timesheets), based on time and material (reinvoice costs or expenses).

So, whatever the products/services, you always generate invoices based on sales order. All other methods disappeared, you can do everything from the sale order.

因此，无论是产品/服务，您都可以基于销售订单生成发票。其他方式在v9中已被取消，您都可以从销售订单上来生成发票（原来的英文有夸张的成分。。呵呵也许老外习惯这样说，心态上蛮好，改变总是好的）。

The meaning of "Done" in sales order in different. In v8, done means "delivered and invoiced". In v9, done means "you can not change the order anymore". Delivered and Invoiced are written on SO lines, not in the status.

We removed the workflow because it was a mess. For example, in version 8, the "state" field was used for the SO state (quotation --> sale order) as well as the invoice state and delivery state (done=delivered and invoiced). We splitted this in several computed fields:

  - State: Quotation --> Sent  --> Sale Order

  - Invoice State: Nothing to Invoice, To Invoice, Fully Invoiced, Upselling Opportunity

  - Delivered: quantities are set on SO lines

More over, as the user can edit the SO at any step, workflows were not useful anymore. It's also much faster now.

*What are the improvements?*

Compared to v8, all complex use cases work perfectly in v9:

- single point of invoicing: sale order --> super easy

- you can mix any kind of services and invoice everything at once from the sale order: pre-paid support contract, project invoiced on milestones, physical products, extra travel and expenses, etc.

- the system manages upselling opportunities (when delivered quantities > ordered quantities). Example: you sell a support contract of 25h, when you arrive at 30h on timesheets, the sale order switch to "Upselling Opportunity"

管理 用于 超单销售 （ 已送货数量 大于 订单数量）。例如：您可以 销售 支持合同 25小时，当 在计工单 中数量 达到30小时 时 ， "超单销售" ( 测试下来 销售订单  交付 数量如果 在开票 之后 又增加了， 销售订单上的 发票状态 会被判断为超售 )

- inter-company rules with invoice for both the supplier and the customer, based on delivered quantities

- invoice kits, based on delivered quantities

- handle correctly unit of measures: sell a support contract by "Pack 40h", work by hours in your timesheets

- modify a confirmed SO: it will handle delivery and invoicing correctly

change prices on a confirmed SO: some lines are readonly or not based on what have already been invoiced

- more efficient management of deposits 对于存款/保证金 更有效率的管理

- 3 ways to track services: manually (set milestones as done), timesheet on contract (the v8 method), timesheets on tasks

- correctly handle the right product when a user do timesheet (defined by the SO line): you can work as a senior developer or on a support contract --> no need for analytic_user_function anymore

What about purchases?采购

We also reviewed purchase orders with a similar concept (Qty delivered, Qty invoiced) In v8, you had three methods to generate draft invoices: based on PO, based on PO lines, based on receptions. It's much easier in version 9, there are 0 methods :)

We don't pre-generate draft invoices anymore, but you can select POs when you create a vendor bill: it will fill all invoice lines automatically based on what can be invoiced (received products or services).

No more problem of merge, partial invoices, control of quantities if received in several steps, ...

It's very difficult to explain such a huge change in just a small email.

So I hope this small email helps,

You can get more information in the documentation, some docs have been updated to the new process (check the sale tab):

Thanks, 谢谢

--

Fabien

评论：

Odoo官方自己也用Odoo,近水楼台先得月，

他们发现了 一些 V8使用上的麻烦， 因此在V9 中进行了 修改。

不过 仔细阅读 后 发现 也不是所有 公司都用v9好，对项目型 的 更有意义些。

那些 不需要为 服务 ，计工单 开票的公司 就要综合衡量了。

而且V9中的合同实际上是 企业版才有的功能，社区版目前并没有。

翻译过程中 难免出现 错误，希望大家提出更好的建议。 谢谢 大家

卓忆 2016/08/22