← Back to team overview

c2c-oerpscenario team mailing list archive

[Bug 765901] Re: [PS] stock : pull rule : wrong procurement method

 

Hello Francois Pietquin (OpenERP),

the indian team leader pointed out something really confusing in your
example and i checked with fp: actually, the system is behaving directly
here.

Indeed, 
1) the procurement method used on the 1st procurement has _always_ to be the one defined on the sale order line (coming with onchange from the product)
2) the pull/push flows are intended to be triggered only when the procurement method of the sale order line _is_ make to order. (We could make readonly those rules when the procurement method of the product isn't MTO, but we want to keep the possibility to define rules to use when people manually change the procurement method on the sale order line).
3) the procurement method you set on the pull rule is related to the _second_ procurement that will be created, not the first. (If you create a rule saying you want to pull product from stock 1 to stock 2, then this field is usefull to say if this job has to be treated as MTO or MTS)

So, i'm sorry to say that this bug has been INVALIDATED BY FP! :-)

See you,
Quentin


** Changed in: openobject-addons
       Status: In Progress => Invalid

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/765901

Title:
  [PS] stock : pull rule : wrong procurement method

Status in OpenERP Modules (addons):
  Invalid

Bug description:
  6.0.2

  I've the following stock locations structure :
  - Company 1
  --- Stock 1
  --- Ouput 1

  - Company 2
  --- Stock 2
  --- Ouput 2

  I have a product with the following settings :
  - procurement type : stockable product
  - procurement method : make to stock
  - supply method : buy

  On the same product, I add this pull rule :
  - destination : stock 2
  - origin : stock 1
  - procurement method : make to order

  If I sale a product from company 2, then I should have 2 stock moves
  - from stock 2 to customer
  - from stock 1 to stock 2

  The problem is I don't get the second one!
  Because the system checks first the procurement method defined on the product (and not the one set into the pull rule), it is expecting a minimum stock rule. So the algorythm isn't correct!

  Normally, the system should check all the pull rules defined on the
  product first : if a destination location (of a pull rule) matches
  with the procurement then OpenERP should only uses the procurement
  method defined on this rule. Then, if no pull rule is matching, the
  system has to use the default values set under the first tab.

  This bug has been VALIDATED BY QDP !

  Thanks

  François Pietquin
  OpenERP Professional Services


References