Community mailing list archives
Re: MTO questionby
Looks like it works perfectly on v9, nothing to fix. I should have missed something in my tests.
You can change the MTO rule (or create another one if you want to group some products and others not in the PO). No need for a community module, un grouping/grouping PO is standard.
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.On Fri, Apr 8, 2016 at 10:47 AM, Luis Panozzo <email@example.com> wrote:Two comments here: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.On 8 April 2016 at 13:11, Jordi Ballester Alomar <firstname.lastname@example.org> wrote:Luis,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.See:Code here:On Fri, Apr 8, 2016 at 12:11 PM, Luis Panozzo <email@example.com> wrote:Environment:We have many products defined with the MTO / Buy Route options.And we use drop shipping.Scenario:An agent confirms a quotation for product 123 which is manufactured by supplier S1.Let's say we MAY want this delivered by April 30th in UK (or it may end up being May 30th, according to the customer)The corresponding draft PO (RFQ) is generated but given the uncertainty of the delivery date we can not confirm the PO.One hour later another quotation (this time for product 321) -which is also manufactured by S1- is confirmed. But this product needs to be delivered by May 15th in GermanyThe system detects an open RFQ for S1 and adds the second product to it.Which is not what we want since we need a separate RFQ to be created.Are we missing something in the proper configuration of the purchase methodology? Any module anyone may be aware of to bypass this situation?Thank you in advance--