Re: MTO question

by

Luke Branch

- 04/10/2016 02:26:18

Hi Fabien,

Thanks for your informative email. Would you mind posting a link to the PR once work on this is started?

I'm very interested in this feature for 9.0 as I have the need to have a 1:1 relationship between SO and RFQ (ie. one sale order from one customer triggers one RFQ). This is a pretty common requirement for trading companies in Hong Kong so it would be great to have this as a configuration option built into the core.

For the record, I think there is a bug on the way Odoo groups PO or not. It should use the procurement group so that you can configure your MTO rule if you want a grouping or not (propagate procurement group field). That way, it's exactly the same grouping mechanism than pickings. (for now on, it always group)

We reported the bug this morning and it should be fixed in a few days. That way, you can do what you expect in standard, simply by changing the propagate procurement group method on the MTO pull rule.

Copy of reported bug:

In inventory, I setup a product with MTO and buy. Then, I create and confirm two sales order for this product.

Depending on the MTO pull rule configuration, I expect to have the purchases grouped in one PO or not . (some companies want one PO because they want to be able to manage every PO manually, others want PO to be grouped)

It should depends on the "Propagate Procurement Group" setting on the "Make to Order" PULL rule. For now on, the procurement group does not seem to be used when generating PO. (note: you need to be in technical feature to see the propagate procurement group field on the rule)

To do:

group on PO or not, based on procurement group

On the rule "Make to Order", change the default value of the field "Propagation of Procurement Group" from Propagate to "Leave Empty" so that the default behavior does not change.

Note: the rule and propagation of the procurement group is done correctly. It's just the grouping on the PO that forget to use the procurement group concept, like in pickings.

1.- I know it was not an Odoo bug. It is just that Odoo way is not our way of conducting business which means we have to find alternatives. Odoo prioritizes economy of processing while we favour granularity.

2.- Your suggestion:

Impressive to say the least.

But somehow, I am not surprised coming from you. You have set a very high bar.

Thank you for the pointer. We will see if we can integrate it in our current flow.

This is not a bug of Odoo. It is the way that procurements are connected with purchasing.

In order to fulfill your need, you need extra tools. What you may need is to decouple a bit more the procurement and purchasing, so that purchasing has some more flexibility in the decisions releated to how to purchase what is being asked.