Merge lp:~npg-team/openobject-addons/stock_multilocation_picking_npg into lp:openobject-addons/extra-trunk

Proposed by Novapoint Group
Status: Needs review
Proposed branch: lp:~npg-team/openobject-addons/stock_multilocation_picking_npg
Merge into: lp:openobject-addons/extra-trunk
To merge this branch: bzr merge lp:~npg-team/openobject-addons/stock_multilocation_picking_npg
Reviewer Review Type Date Requested Status
Numérigraphe Needs Information
OpenERP Committers Pending
Review via email: mp+78436@code.launchpad.net

Description of the change

NovaPoint Group has developed this module to provide inventory tracking capabilities in a warehouse.It is used primarily in a dynamic/high-turnover warehouse.
Provides the ability for a product to be placed in multiple locations throughout a warehouse.

To post a comment you must log in.
Revision history for this message
Numérigraphe (numerigraphe) wrote :

Please, would you care to add more detail to the module description, to explain the purpose of the module and how it works ?
Reading the whole code to guess what it does won't help with the adoption of the module.
Lionel Sausin.

review: Needs Information
Revision history for this message
David Mitchell (www.novapointgroup.com) (david-novapointgroup.com) wrote :

> Please, would you care to add more detail to the module description, to
> explain the purpose of the module and how it works ?
> Reading the whole code to guess what it does won't help with the adoption of
> the module.
> Lionel Sausin.

OpenERP by default for a product includes one "location" for the product. Row, Aisle, Etc.
This is not sufficient in a dynamic warehouse environment.

Often in large warehouses a portion of the products onhand are located in a "primary picking" area which is in close proximity to where goods are "boxed/packed". The objective is for Final Pickers to have a short distance to travel to pick stock for orders - versus navigating through a 300-400K ft warehouse (which is inefficient). The module enables a product to be assigned to multiple picking locations - and displays those so warehouse staff can easily view them.

In addition, in our use case, a company under a specific warehouse may have product located in multiple locations (a primary picking location (which can dynamically change, and multiple secondary overstock locations) - up to 20 in our example. Often, a specific picker is assigned the tasks of replenishing the primary picking locations from secondary overstock locations so warehouse operations are efficient. There are values which designate targets for replenishment (you should only replenish the amount that the location in the warehouse can hold). A report is available to provide to the replenishment picker to pull from the overstock locations where a product is held - and replenish the primary picking locations.

Of course inventory shows stock values underroof in the warehouse, but also in individual locations + virtual stock etc.

Shipments in our use case are well above 1,000 shipments a day - with over 5,000 items picked and packaged.

In summary
A product can have multiple locations assigned which have their own replenishment points.
A product can have a primary picking location designated.
A product can have numerous stock locations underroof (e.g. 22 was our max in real life)
A replenishment picker can easily restock the primary picking locations and has a report to guide their actions.
And OpenERP can now efficiently support large distribution facilities who focus on quick turns.
In addition, the picking locations of products frequently changes - due to the rapid nature of product sales. So often warehouse staff just look to drop product wherever there is an open bay and record it in the system - versus always putting product stock in the same locations. This is the dynamic nature of a quick-ship distribution facility. versus a more "static" nature that OpenERP has today.

Does that help?

Revision history for this message
Numérigraphe (numerigraphe) wrote :

Thanks, your explanation sure helps. I suggets you copy part of it to __openerp__.py.

Revision history for this message
Numérigraphe (numerigraphe) wrote :

Doc strings on methods would help too.

Unmerged revisions

5306. By Novapoint Group

[Add]: stock_multilocation_picking to provide inventory tracking capabilities in a dynamic warehouse

5305. By Xavier (Open ERP)

[ADD] modifiers setup on account.move.line override of fields_view_get

this way, the web clients correctly gets @required fields, and hides the columns which should be hidden

5304. By Stephane Wirtel (OpenERP)

[FIX] base_setup: Set the right xml_id for the hidden/link category

5303. By Stephane Wirtel (OpenERP)

[FIX] base_setup: Set the right modules of the category

5302. By Stephane Wirtel (OpenERP)

[FIX] base_setup: Fix a problem with categories to show

5301. By Olivier Dony (Odoo)

[IMP] account_invoice_layout: missing state field in list view (used for `states` modifiers)

5300. By Launchpad Translations on behalf of openerp

Launchpad automatic translations update.

5299. By Antony Lesuisse (OpenERP)

[FIX] packaging rename doc python rpm build does not tolerate spaces in files

5298. By Antony Lesuisse (OpenERP)

[FIX] packaging rename doc python rpm build does not tolerate spaces in files

5297. By Antony Lesuisse (OpenERP)

[FIX] crm tests, openid import

Subscribers

People subscribed via source and target branches