openerp-india team mailing list archive

[Alexandre Fayolle - camptocamp <alexandre.fayolle@xxxxxxxxxxxxxx>]

Public bug reported:

I'm at loss with picking waves.

>From what I understand, the goal is to group pickings to ease the
warehouse work. One typical use case is to group things together that
should be picked together.

Eg I have

SO01 with 3 x prod1 and 2 x prod2 for partner1
SO02 with 2 x prod1, 3 x prod3 for partner2

I group the Stock -> Output pickings related to the 2 SO in a single
wave. Since these are internal pickings, I expect to be able to easily
dispatch someone in the warehouse telling him to pick 5 x prod1, 2 x
prod2 and 3 x prod3.

Instead, the report is a "dumb" aggregation of the different picking
reports.

** Affects: openerp-trunk-wms
     Importance: Undecided
         Status: New

** Project changed: openobject-addons => openerp-trunk-wms

-- 
You received this bug notification because you are a member of OpenERP
Indian Team, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/1269754

Title:
  picking wave : grouping by product

Status in New OpenERP WMS:
  New

Bug description:
  I'm at loss with picking waves.

  From what I understand, the goal is to group pickings to ease the
  warehouse work. One typical use case is to group things together that
  should be picked together.

  Eg I have

  SO01 with 3 x prod1 and 2 x prod2 for partner1
  SO02 with 2 x prod1, 3 x prod3 for partner2

  I group the Stock -> Output pickings related to the 2 SO in a single
  wave. Since these are internal pickings, I expect to be able to easily
  dispatch someone in the warehouse telling him to pick 5 x prod1, 2 x
  prod2 and 3 x prod3.

  Instead, the report is a "dumb" aggregation of the different picking
  reports.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openerp-trunk-wms/+bug/1269754/+subscriptions