c2c-oerpscenario team mailing list archive

["Francois Pietquin \(OpenERP\)" <765901@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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

** Affects: openobject-addons
     Importance: High
         Status: New


** Tags: profserv

** Description changed:

  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! 
+ 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 : if a destination location (of a pull rule) matches with the
- procurement then OpenERP should only uses the procurement method defined
- on this rule.
+ 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, then 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

** Description changed:

  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, then the system
- has to use the default values set under the first tab.
+ 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

-- 
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):
  New

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