openerp-wms-expert team mailing list archive

[Numérigraphe <informatique@xxxxxxxxxxxxxxxx>]

Blueprint changed by Numérigraphe:

Whiteboard changed:
- The following is a based on reflections by Philippe Rossi and Lionel Sausin at Numérigraphe SARL.
- Additions and corrections are most welcome.
+ Additions and corrections are most welcome here.
+ ...
  
- We propose to move the features of the "process" wizard to the main views, to make them available at all times. The "process" button should only be in charge of changing the states and advancing the workflows.
- The features of the wizard that we want to keep are :
- [1] automatically creating backorders, keeping the initial stock moves unfinished so that the other objects don't advance
- [2] entering prices
- [3] updating the average prices when the picking advances to "done"
- 
- In this perspective, it would be a big plus if we also refactor all the
- wizards that split lines to make them more consistent and make them
- share more code and views.
- 
+ Side notes and additional thoughts:
  ----
  Note : are partial moves a stock concern in the first place?
  It would be tempting to declare that the partial shipping management should not be handeled by the stock module at all. After all, isn't it more intuitive to let users change the quantity on the stock move? Then the ERP could compare that shipped quantity with that of the origin order (sale, purchase, production, procurement) and create the needed backorder.
  Unfortunately that would require very deep changes to several workflows that expect events to come from the stock to progress.
  There is also a problem with procurements, which only have a link to a single stock move. Finishing that move means the procurement is complete, which may mean the sale order line is honoured: no backorder can be made then.
  
  ---
  Other possible approach : make the main views read-only and move all the features to the "process" wizard
  Moving everything to the wizard has several problems. First it's not consistent with the rest of OpenERP. Moreover, it makes data volatile, which can be a real problem for complex cases and data that take long to key in.

-- 
New partial picking procedure
https://blueprints.launchpad.net/openobject-addons/+spec/new-partial-picking-wizard