mirror of
https://github.com/odoo/documentation.git
synced 2026-01-04 02:36:32 +07:00
[IMP] Inventory: Bringing Closest location removal strategy current
closes odoo/documentation#15744 Signed-off-by: Felicia Kuan (feku) <feku@odoo.com> Co-authored-by: Jess Rogers <104637850+jero-odoo@users.noreply.github.com>
This commit is contained in:
@@ -8,9 +8,6 @@ storage location titles.
|
||||
The goal of this strategy is to save the warehouse worker from taking a long journey to a farther
|
||||
shelf when the product is also available at a closer location.
|
||||
|
||||
.. seealso::
|
||||
:doc:`About removal strategies <../removal_strategies>`
|
||||
|
||||
.. _inventory/warehouses_storage/sequence:
|
||||
|
||||
To understand *location sequence* in the closest removal strategy, consider the following example:
|
||||
@@ -20,29 +17,38 @@ To understand *location sequence* in the closest removal strategy, consider the
|
||||
A/Rack 2`.
|
||||
|
||||
.. image:: closest_location/locations.png
|
||||
:align: center
|
||||
:alt: Show a mockup of real storage location in a warehouse.
|
||||
|
||||
The sublocation, `Pallet`, is on the ground level. Products stored here are easier to retrieve,
|
||||
compared to requiring a forklift to reach `Rack 1` and `Rack 2`. The storage locations were
|
||||
strategically named in alphabetic order, based on ease of access.
|
||||
|
||||
.. important::
|
||||
To use this removal strategy, the :guilabel:`Storage Locations` and :guilabel:`Multi-Step Routes`
|
||||
settings **must** be enabled in :menuselection:`Inventory app --> Configuration --> Settings`.
|
||||
Enabling the Closest Location removal strategy
|
||||
==============================================
|
||||
|
||||
.. seealso::
|
||||
:ref:`Set up removal strategy <inventory/warehouses_storage/removal-config>`
|
||||
**Storage locations** and **multi-step routes** are necessary features for setting all types of
|
||||
removal strategies on a location. However, these features are specifically required for the closest
|
||||
location removal strategy since it is only applied at the location level.
|
||||
|
||||
To activate these features, navigate to :menuselection:`Inventory app --> Configuration -->
|
||||
Settings`. Under the :guilabel:`Warehouse` heading, enable the :guilabel:`Storage Locations` and
|
||||
:guilabel:`Multi-Step Routes` features. Be sure to :guilabel:`Save` your changes.
|
||||
|
||||
.. image:: closest_location/enable-configuration-settings.png
|
||||
:alt: Enable Storage Locations and Multi-Step Routes in the inventory settings.
|
||||
|
||||
.. _inventory/warehouses_storage/location-name:
|
||||
|
||||
Location names
|
||||
==============
|
||||
Configure location names
|
||||
------------------------
|
||||
|
||||
To configure location names, begin by navigating to :menuselection:`Inventory app --> Configuration
|
||||
--> Locations`. Then, select an existing location, or click :guilabel:`New` to create a new one, and
|
||||
then enter the desired name in the :guilabel:`Location Name` field.
|
||||
|
||||
Set the removal strategy
|
||||
------------------------
|
||||
|
||||
Once the locations are named in alphabetical order, based on their proximity to the output or
|
||||
packing location, set the removal strategy on the :ref:`parent location
|
||||
<inventory/location-hierarchy>`.
|
||||
@@ -53,46 +59,52 @@ named storage locations.
|
||||
Doing so opens the form for the parent location. In the :guilabel:`Removal Strategy` field, select
|
||||
:guilabel:`Closest Location`.
|
||||
|
||||
.. image:: closest_location/set-closest-location.png
|
||||
:alt: Set Closest Location as the location's removal strategy.
|
||||
|
||||
.. example::
|
||||
In a warehouse, the storage location `WH/Stock/Shelf 1` is located closest to the packing area,
|
||||
where products retrieved from shelves are packed for shipment. The popular product, `iPhone
|
||||
charger` is stored in three locations, `WH/Stock/Shelf 1`, `WH/Stock/Shelf 2`, and
|
||||
`WH/Stock/Shelf 3`.
|
||||
|
||||
To use closest location, set the removal strategy on the parent location, 'WH/Stock'.
|
||||
To use the closest location, set the removal strategy on the parent location, `WH/Stock`.
|
||||
|
||||
Workflow
|
||||
========
|
||||
|
||||
To see how the closest location removal strategy works, consider the following example, featuring
|
||||
the popular product, `iPhone charger`, which is stored in `WH/Stock/Shelf 1`, `WH/Stock/Shelf 2`,
|
||||
and `WH/Stock/Shelf 3`.
|
||||
the popular product, `iPhone Charger`, which is stored in `WH/Stock/Shelf A/Pallets`,
|
||||
`WH/Stock/Shelf A/Rack 1`, and `WH/Stock/Shelf A/Rack2`.
|
||||
|
||||
Fifteen, five, and thirty units are in stock at each respective location.
|
||||
|
||||
.. tip::
|
||||
To check the on-hand stock at each storage location, navigate to the product form, and click the
|
||||
:guilabel:`On Hand` smart button.
|
||||
To check the on-hand stock at each storage location, open the :guilabel:`Locations` report by
|
||||
clicking :menuselection:`Inventory app --> Reporting --> Locations`. Filter by :guilabel:`On
|
||||
Hand`, as well as product (if necessary).
|
||||
|
||||
.. image:: closest_location/on-hand-stock.png
|
||||
:align: center
|
||||
:alt: Show on-hand stock at all locations.
|
||||
|
||||
Create a :ref:`delivery order <inventory/delivery/one-step>` for eighteen units of the `iPhone
|
||||
charger` by navigating to the :menuselection:`Sales app` and creating a new quotation.
|
||||
Charger` by navigating to the :menuselection:`Sales app` and creating a new quotation.
|
||||
|
||||
After adding the products, clicking :guilabel:`Confirm` creates a delivery order that reserves items
|
||||
stored at the closest location, using the removal strategy.
|
||||
|
||||
For more details about *where* the units were picked, select the :guilabel:`⦙≣ (bulleted list)`
|
||||
icon, located on the far-right. Doing so opens the :guilabel:`Open: Stock move` pop-up window that
|
||||
displays how the reserved items were picked, according to the removal strategy.
|
||||
For more details about *where* the units were picked, click the :guilabel:`Details` link, located on
|
||||
the far right. Doing so opens the :guilabel:`Detailed Operations` pop-up window that displays how
|
||||
the reserved items were picked, according to the removal strategy.
|
||||
|
||||
In the :guilabel:`Open: Stock move` pop-up window, the :guilabel:`Pick from` field displays where
|
||||
In the :guilabel:`Detailed Operations` pop-up window, the :guilabel:`Pick From` field displays where
|
||||
the quantities to fulfill the :guilabel:`Demand` are picked. All fifteen of the units stored at the
|
||||
closest location, `WH/Stock/Shelf 1`, are picked first. The remaining three units are then selected
|
||||
from the second closest location, `WH/Stock/Shelf 2`.
|
||||
closest location, `WH/Stock/Shelf A/Pallets`, are picked first. The remaining three units are then
|
||||
selected from the second closest location, `WH/Stock/Shelf A/Rack 1`.
|
||||
|
||||
.. image:: closest_location/stock-move-window.png
|
||||
:align: center
|
||||
:alt: Display *Pick From* quantities for the order for iPhone chargers.
|
||||
.. image:: closest_location/detailed-operations-window.png
|
||||
:alt: Display Pick From quantities for the order for iPhone chargers.
|
||||
|
||||
.. seealso::
|
||||
- :doc:`About removal strategies <../removal_strategies>`
|
||||
- :ref:`Set up removal strategy <inventory/warehouses_storage/removal-config>`
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 8.6 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 11 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 17 KiB After Width: | Height: | Size: 16 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 7.2 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 13 KiB |
Reference in New Issue
Block a user