[IMP] Inventory: make Storage Categories current with 18.0 #15090
Conversation
|
|
There was a problem hiding this comment.
Good job testing doing this deep dive, @erjer-odoo !
Appreciate the strenuous testing you did and challenging my misunderstandings of the putaway behavior to result in a more accurate document! To make sure your new findings are properly highlighted, I'd like to suggest we move some things around and map out the workflows in even more detail
Let me know if I can clarify any of my comments!
...cations/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst
Show resolved
Hide resolved
...cations/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst
Show resolved
Hide resolved
...cations/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst
Show resolved
Hide resolved
...cations/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst
Show resolved
Hide resolved
...cations/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst
Show resolved
Hide resolved
...cations/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst
Show resolved
Hide resolved
...cations/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst
Show resolved
Hide resolved
...cations/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst
Show resolved
Hide resolved
...cations/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst
Show resolved
Hide resolved
...cations/inventory_and_mrp/inventory/shipping_receiving/daily_operations/storage_category.rst
Show resolved
Hide resolved
| Click the :guilabel:`New` button to create the putaway rule. In the :guilabel:`Sublocation` field, | ||
| choose :guilabel:`Closest Location` or :guilabel:`Last Used`, then select a category in the | ||
| :guilabel:`Having Category` field. | ||
|
|
||
| Use the :guilabel:`Sublocation` field to specify whether a sublocation should be used and how to | ||
| find that sublocation: | ||
|
|
||
| - :guilabel:`No`: No sublocation is used. The destination is whatever is listed in the | ||
| :guilabel:`Store to` field. | ||
| - :guilabel:`Last Used`: The last location that had a move associated with it for that product or | ||
| product category is used. If there is no last location used, the destination is whatever is | ||
| specified in the :guilabel:`Store to` field. | ||
| - :guilabel:`Closest Location`: The locations specified as part of the storage category are used. A | ||
| storage category is mandatory in the :guilabel:`Having Category` field. |
There was a problem hiding this comment.
Is there a Sublocation we MUST set the putaway rule for the storage category to work? This Sublocation definition here seems more like an aspect of a putaway rule rule.
For the purposes of this PR, let's tell the reader if there's a Sublocation they must set to, and in a future PR, we'll move this sublocation definition part out to a future PR. (we wouldn't want to do that right now because your storage categories PR would be merged first, and this crucial info about sublocation doesn't exist anywhere, and we'd like it to exist even if there might be a better place for it.)
| If using multiple storage locations for a single category, create putaway rules for each location to | ||
| ensure that if one storage location is in use, the secondary locations must be used. |
There was a problem hiding this comment.
A nitpick but I was thinking that this paragraph is a little easy to miss since it's being sandwiched by an image and a heading. Do you think you can move this up to above the image?
Making storage categories documentation current with 18.0, requested here:: https://www.odoo.com/odoo/my-tasks/4681301