| REPOSITORY | |
|---|---|
| REPOSITORY | OCA/stock-logistics-warehouse |
| GIT | |
| GIT | https://github.com/OCA/stock-logistics-warehouse.git |
| GIT FOLDER | |
| GIT FOLDER | https://github.com/OCA/stock-logistics-warehouse/tree/7.0/stock_inventory_location |
| VERSION | |
| VERSION | 1.1 |
| CATEGORY | |
| CATEGORY | Warehouse Management |
| LICENSE | |
| LICENSE | LGPL-3 |
| APPLICATION | |
| APPLICATION | No |
| AUTO-INSTALLABLE | |
| AUTO-INSTALLABLE | No |
| AUTHORS | |
| AUTHORS | Odoo Community Association (OCA), Numérigraphe |
| MAINTAINERS | |
| MAINTAINERS | Odoo Community Association (OCA), Numérigraphe |
| COMMITTERS | |
| COMMITTERS | Alexandre Fayolle, Lionel Sausin (Numérigraphe) |
| WEBSITE | |
| WEBSITE | |
| LAST TRACKING UPDATE | |
| LAST TRACKING UPDATE | 2026-07-06 00:07:13 |
| ODOO DEPENDENCIES | |
| ODOO DEPENDENCIES |
odoo/odoo: - stock - product - base - process - web - decimal_precision - base_setup - web_kanban - account - analytic - board - edi - email_template |
| PYTHON DEPENDENCIES | |
| PYTHON DEPENDENCIES | Not have |
| SYSTEM DEPENDENCIES | |
| SYSTEM DEPENDENCIES | Not have |
| DESCRIPTION | |
| DESCRIPTION | Let users make exhaustive Inventories ===================================== Standard Physical Inventories in OpenERP only contain a generic list of products by locations, which is well suited to partial Inventories and simple warehouses. When the a standard Inventory is confirmed, only the products in the inventory are checked. If a Product is present in the computed stock and not in the recorded Inventory, OpenERP will consider that it remains unchanged. But for exhaustive inventories in complex warehouses, it is not practical: - you want to avoid Stock Moves to/from these Locations while counting goods - you must make sure all the locations you want have been counted - you must make sure no other location has been counted by mistake - you want the computed stock to perfectly match the inventory when you confirm it. This module lets choose whether an Physical Inventory is exhaustive or standard. For an exhaustive Inventory: - in the state "Draft" you define the Location where goods must be counted. - the new Inventory status "Open" lets you indicate that the list of Locations is final and you are now counting the goods. In that status, no Stock Moves can be recorded in/out of the Inventory's Locations. - if the Location or some of it's children have not been entered in the Inventory Lines, OpenERP warns you when you confirm the Inventory. - only the Inventory's Location or its children can be entered in the Inventory Lines. - every good that is not in the Inventory Lines is considered lost, and gets moved out of the stock when you confirm the Inventory. |
| XML ID | Name | Model | Type | Status |
|---|---|---|---|---|
stock_inventory_location_form_view |
stock.inventory.location.form | stock.inventory | xpath | Inherits stock.view_inventory_form |
view_confirm_uninventoried_location |
stock.inventory.uninventoried.locations.form | stock.inventory.uninventoried.locations | form | New |
view_inventory_complete_filter |
complete.inventory.filter | stock.inventory | xpath | Inherits stock.view_inventory_filter |
view_stock_fill_inventory_location |
Import Inventory | stock.fill.inventory | xpath | Inherits stock.view_stock_fill_inventory |
No new fields.
Public methods (1)default_get(self, cr, uid, fields, context=None)
No new fields.
Public methods (4)action_done(self, cr, uid, ids, context=None)
action_open(self, cr, uid, ids, context=None)
confirm_missing_locations(self, cr, uid, ids, context=None)
get_missing_locations(self, cr, uid, ids, context=None)
No new fields.
Public methods (1)onchange_location_id(self, cr, uid, ids, inventory_location_id, exhaustive, location_id, context=None)
No new fields.
Public methods (3)create(self, cr, uid, vals, context=None)
unlink(self, cr, uid, ids, context=None)
write(self, cr, uid, ids, vals, context=None)
No new fields.
Public methods (0)No public methods.