[IMP] inventory: update locations doc
closes odoo/documentation#9128
X-original-commit: 5d735775b6
Signed-off-by: Brandon Seltenrich (brse) <brse@odoo.com>
This commit is contained in:
parent
7373c3ed36
commit
c8ff187873
@ -2,45 +2,94 @@
|
||||
Locations
|
||||
=========
|
||||
|
||||
A *location* is a specific space within a warehouse. This can be a shelf, room, aisle, etc. There
|
||||
are three types of locations in Odoo:
|
||||
In Odoo *Inventory*, a *location* is a specific space within a warehouse. This can be a shelf, room,
|
||||
aisle, rack, bin, etc.
|
||||
|
||||
- *Physical locations* are spaces within a warehouse owned by the user's company. These can be a an
|
||||
area where items are stored like an aisle or shelf, or an area where operations take place, like
|
||||
loading and unloading bays.
|
||||
- *Partner locations* are the same as physical locations except that they exist within the warehouse
|
||||
of a customer or vendor.
|
||||
- *Virtual locations* are locations that do not exist physically, but where items that are not in
|
||||
inventory can be placed. These can be items that have not yet entered inventory, like products
|
||||
that are on the way to a warehouse, or items that are no longer in inventory due to loss or other
|
||||
factors.
|
||||
There are also external and virtual locations. For example, customer locations, and locations
|
||||
specifically designated as "virtual", instead of real, physical locations.
|
||||
|
||||
.. important::
|
||||
In order to use locations, the :guilabel:`Storage Locations` setting must be enabled. To do so,
|
||||
navigate to :menuselection:`Inventory --> Configuration --> Settings`, scroll down to the
|
||||
:guilabel:`Warehouse` heading, and enable the :guilabel:`Storage Locations` checkbox.
|
||||
Locations allow for the storage of products in designated areas of the warehouse, to help track
|
||||
inventory accurately.
|
||||
|
||||
Configuration
|
||||
=============
|
||||
|
||||
To specify storage locations, the *Storage Locations* setting must be enabled. To do so, navigate to
|
||||
:menuselection:`Inventory app --> Configuration --> Settings`, and scroll down to the
|
||||
:guilabel:`Warehouse` section. Tick the checkbox next to :guilabel:`Storage Locations` to enable the
|
||||
feature, and click :guilabel:`Save`.
|
||||
|
||||
.. image:: use_locations/use-locations-enabled-setting.png
|
||||
:align: center
|
||||
:alt: Enabled Storage Location setting in Inventory app settings.
|
||||
|
||||
Once the :guilabel:`Storage Locations` feature is enabled, two additional internal link options
|
||||
appear below it: :guilabel:`Locations` and :guilabel:`Putaway Rules`. Click :guilabel:`Locations` to
|
||||
open a list of all existing locations in the warehouse.
|
||||
|
||||
Create a new location inside a warehouse
|
||||
========================================
|
||||
|
||||
Starting from the :menuselection:`Inventory` app, select :menuselection:`Configuration --> Locations
|
||||
--> Create`. The new location form can then be configured as follows:
|
||||
To create a new location inside a warehouse, navigate to :menuselection:`Inventory app -->
|
||||
Configuration --> Locations`. Doing so opens a list of all existing locations. Click :guilabel:`New`
|
||||
to open a new location creation form.
|
||||
|
||||
- :guilabel:`Location Name`: the name that will be used to reference the location
|
||||
- :guilabel:`Parent Location`: the location or warehouse that the new location exists within
|
||||
- :guilabel:`Location Type`: choose the category that the location belongs to
|
||||
- :guilabel:`Company`: the company that owns the warehouse that the location is inside of
|
||||
- :guilabel:`Is a Scrap Location?`: check this box to allow for scrapped/damaged goods to be stored
|
||||
in this location
|
||||
- :guilabel:`Is a Return Location?`: check this box to allow products to be returned to this
|
||||
location
|
||||
- :guilabel:`Barcode`: the barcode number assigned to the location
|
||||
- :guilabel:`Removal Strategy`: the :doc:`strategy <../removal_strategies>` for how items
|
||||
should be taken from inventory
|
||||
In the :guilabel:`Location Name` field, assign a name for the new location. In the :guilabel:`Parent
|
||||
Location` field, assign the location that this new location exists in.
|
||||
|
||||
.. image:: use_locations/new-location-form.png
|
||||
.. example::
|
||||
A new location `Gate 1` is created. Its parent location is `Dispatch Zone`. In the
|
||||
:guilabel:`Parent Location` for `Gate 1`, select `Dispatch Zone`.
|
||||
|
||||
In the :guilabel:`Additional Information` section, fill out the necessary details for the new
|
||||
location.
|
||||
|
||||
In the :guilabel:`Location Type` field, select which type of location this is. There are seven
|
||||
different types of locations to choose from:
|
||||
|
||||
- :guilabel:`Vendor Location`: virtual location representing the source location for products coming
|
||||
from vendors.
|
||||
- :guilabel:`View`: virtual location used to create a hierarchical structure for a warehouse;
|
||||
aggregates its child locations. **Should not directly contain products**.
|
||||
- :guilabel:`Internal Location`: physical location inside a warehouse.
|
||||
- :guilabel:`Customer Location`: virtual location representing the destination location for products
|
||||
sent to customers.
|
||||
- :guilabel:`Inventory Loss`: virtual location serving as a counterpart for inventory operations.
|
||||
Used to correct stock levels of physical inventory.
|
||||
- :guilabel:`Production`: virtual counterpart location for production operations. This location
|
||||
consumes components and produces finished products.
|
||||
- :guilabel:`Transit Location`: counterpart location that should be used in inter-company or
|
||||
inter-warehouse operations.
|
||||
|
||||
.. image:: use_locations/use-locations-new-location-form.png
|
||||
:align: center
|
||||
:alt: The form for creating a new location.
|
||||
:alt: Additional Information section of new location creation form.
|
||||
|
||||
Configure the remaining fields in the :guilabel:`Additional Information` section as follows:
|
||||
|
||||
- :guilabel:`Company`: the company whose warehouse the location is inside of. Leave this field blank
|
||||
if this location is shared between companies.
|
||||
- :guilabel:`Is a Scrap Location?`: tick this checkbox to allow for scrapped/damaged goods to be
|
||||
stored in this location.
|
||||
- :guilabel:`Is a Return Location?`: tick this checkbox to allow products to be returned to this
|
||||
location.
|
||||
- :guilabel:`Barcode`: the barcode assigned to the location.
|
||||
- :guilabel:`Replenish Location`: tick this checkbox to get all quantities to replenish at this
|
||||
location.
|
||||
|
||||
In the :guilabel:`Cyclic Counting` section, change the value in the :guilabel:`Inventory Frequency
|
||||
(Days)` field from the default `0`, if necessary.
|
||||
|
||||
.. image:: use_locations/use-locations-cyclic-counting.png
|
||||
:align: center
|
||||
:alt: Cyclic Counting section of new location creation form.
|
||||
|
||||
When different than `0`, the inventory count dates for products stored at this location are
|
||||
automatically set at the defined frequency.
|
||||
|
||||
In the :guilabel:`Logistics` section, in the :guilabel:`Removal Strategy` field, click the drop-down
|
||||
menu and select the :doc:`removal strategy <../removal_strategies>` for how items should be removed
|
||||
from this location.
|
||||
|
||||
.. _inventory/location-hierarchy:
|
||||
|
||||
@ -48,14 +97,22 @@ Create location hierarchies
|
||||
===========================
|
||||
|
||||
The *Parent Location* setting on the new location form allows for a location to exist within a
|
||||
warehouse or another location. Every location can serve as a parent location, and every parent
|
||||
location can have multiple locations within it, allowing for the creation of a virtually infinite
|
||||
hierarchical structure.
|
||||
warehouse, or below another location.
|
||||
|
||||
Every location can serve as a parent location, and every parent location can have multiple locations
|
||||
within it, allowing for the creation of a hierarchical structure.
|
||||
|
||||
.. example::
|
||||
Location hierarchy could be organized so that a shelf is located within an aisle, which is
|
||||
located within a room, which is located within the overall warehouse.
|
||||
Location hierarchy could be organized so that a small refrigerator is located on a specific
|
||||
shelf, which is located in the warehouse.
|
||||
|
||||
To create the location hierarchy in the example above, set the warehouse as the parent of the room,
|
||||
the room as the parent of the aisle, and the aisle as the parent of the shelf. This can be adapted
|
||||
to a hierarchy of any magnitude.
|
||||
.. image:: use_locations/use-locations-hierarchy.png
|
||||
:align: center
|
||||
:alt: Location hierarchy of small refrigerator, on a shelf in a warehouse.
|
||||
|
||||
To create the location hierarchy in the example above (`WH/Stock/Shelf 2/Small Refrigerator`),
|
||||
set the warehouse stock as the parent of the shelf, and the shelf as the parent of the small
|
||||
refrigerator. This can be adapted to a hierarchy of any magnitude.
|
||||
|
||||
.. seealso::
|
||||
:doc:`warehouses_locations`
|
||||
|
Binary file not shown.
Before Width: | Height: | Size: 9.0 KiB |
Binary file not shown.
After Width: | Height: | Size: 46 KiB |
Binary file not shown.
After Width: | Height: | Size: 48 KiB |
Binary file not shown.
After Width: | Height: | Size: 76 KiB |
Binary file not shown.
After Width: | Height: | Size: 98 KiB |
Loading…
Reference in New Issue
Block a user