- APPS
- Multi-Warehouse Access Control - Stock Picking Batch 19.0
Multi-Warehouse Access Control - Stock Picking Batch
by T.V.T Marine Automation (aka TVTMA) Viindoo
4.9
| Lines of Code | 442 |
| Technical name | viin_multi_warehouse_access_control_stock_picking_batch |
| License | OPL-1 |
| Website | https://viindoo.com/apps/modules/19.0/viin_multi_warehouse_access_control_stock_picking_batch |
| Required Apps | Invoicing (account) Discuss (mail) Inventory (stock) |
| Included Dependencies | Multi Warehouse Access Control Viindoo Base Viin Warehouse Viin Warehouse Accounting |
Each warehouse validates its own batched transfers, and planning stays with coordinators
For companies that run several warehouses in one database and group transfers into batches or waves
Let warehouse staff validate the transfers of their warehouses that sit in a batch.
Odoo Community and Odoo Enterprise · Odoo Proprietary License v1.0 (OPL-1) · No text of its own to translate: screens follow your Inventory languages
Builds on Multi Warehouse Access Control: the access levels and the people listed on each warehouse come from there.
What changes for your team
Batched transfers get validated where the goods are
Today, an operator limited to their own warehouse has no access to the batches Inventory builds, so the transfers grouped there are out of reach.
→ Batch Transfers and Wave Transfers are in their Operations menu; they validate a whole batch, or one transfer while the rest stays batched.
Each team sees the batches of its own warehouses
Today, the way to reach batches is a wider level that opens the batches of every warehouse.
→ A batch follows the warehouse of its operation type: operators and warehouse managers see the batches of the warehouses they are listed on, and of open warehouses.
Building batches and waves stays with coordinators
Today, whoever can open batches also gets the controls that create, regroup and merge them.
→ Prepare Wave, Add to batch, Add to wave, the batch and wave entries of the Overview cards and Merge are offered to All Warehouses Users only.
Features
Finding the batched work
- ✓ Batch Transfers and Wave Transfers in the operator's menu
- ✓ Batches and waves of assigned and open warehouses only
- ✓ A batch belongs to the warehouse of its operation type
Shipping and receiving
- ✓ Validate a whole batch from its form
- ✓ Validate one transfer of a batch; the others stay batched
- ✓ Update a batch of one's warehouse, such as its responsible person
Planning stays with coordinators
- ✓ Prepare Wave, Add to batch, Add to wave: All Warehouses Users only
- ✓ Merge and the Overview card batch entries: All Warehouses Users only
- ✓ All Warehouses Users keep standard batch access
Built for daily use
- ✓ The server applies the limits to every list, form and export
- ✓ Operators and warehouse managers cannot create or delete a batch
- ✓ Batches with no warehouse stay with All Warehouses Users
- ✓ Installs by itself when Batch Transfers and the base module are present
Ready on day one
Rules in place at install
Batch access by warehouse and the coordinator-only controls work as soon as the module is installed.
Nothing to set on batches
Each batch follows the warehouse of its operation type, including the batches Inventory builds by itself.
What the administrator sets first
An Inventory level for each person and the accessing users of each warehouse, as for the base module.
Before you decide
Can an operator create, delete or merge batches?
No. Operators and warehouse managers read, update and validate the batches of their warehouses. Standard entries such as Duplicate or Delete can still appear in an Actions menu; the server's rules decide whether they are accepted.
Which batches does an operator see?
Batches whose operation type belongs to a warehouse that lists them as an accessing user, or lists nobody. A batch with no operation type, or whose operation type has no warehouse, is seen by All Warehouses Users only.
Does validating one transfer validate the whole batch?
No. The transfer is done and leaves its batch; the other transfers stay. Validate on the batch form validates all of them.
Does anything change for coordinators?
No. A person with All Warehouses User sees every batch and wave and keeps every control of standard Inventory. The module calls no outside service; data stays in your database.
What does it take to run, or to remove?
No Python package or system program beyond Odoo. It installs by itself once Batch Transfers and the base module are installed; uninstalling removes the access it adds and gives Merge back as standard.
Try it, then ask us
Open the live demo of this listing to see the batch transfers, and read the Documentation tab for each role.
Pre-sales & partnership
viindoo.com/contactusTechnical support
viindoo.com/ticketMulti-Warehouse Access Control - Stock Picking Batch
Who this guide is for: Inventory administrators who give warehouse staff their access, and the warehouse operators and managers who validate transfers that Inventory has grouped into batches.
Note
Extends Multi Warehouse Access Control - see its documentation for the access levels and for listing the people who work in a warehouse.
Overview
Inventory can group confirmed transfers into batch transfers by itself: when an operation type has automatic batching switched on, every new transfer of that type joins a batch. A warehouse operator who is limited to their own warehouses must still be able to validate a transfer that sits in such a batch, and to open the batch it belongs to.
This module lets people who hold Users: Own Documents or Warehouse Manager in Inventory read and update the batches of their own warehouses. A batch belongs to the warehouse of its operation type. People who hold All Warehouses User keep the access of standard Inventory.
| Role | What they do | Access right to assign |
|---|---|---|
| Inventory administrator | Installs the module, lists the accessing users of each warehouse and gives each person an Inventory level. | Inventory: Administrator |
| Warehouse operator | Reads the batches of the assigned warehouses and validates their transfers, one by one or as a whole batch. | Inventory: Users: Own Documents |
| Warehouse manager | Does the same as the operator on the assigned warehouses. | Inventory: Warehouse Manager |
| Logistics coordinator | Creates, changes and deletes batches and waves of every warehouse; groups transfers with Add to batch, Add to wave and Prepare Wave; merges batches. | Inventory: All Warehouses User |
Setup (for the Inventory administrator)
Install the module
- Open Apps.
- Search for Multi-Warehouse Access Control - Stock Picking Batch.
- Press Install if it is not installed yet. It installs itself when both Multi Warehouse Access Control and Batch Transfers are installed.
Choose who reads which batches
- Give each warehouse operator Users: Own Documents (or Warehouse Manager) in the Inventory field of the user, and list them in Accessing Users of their warehouses. Both steps are described in the guide of Multi Warehouse Access Control.
- Nothing else is configured here: a batch belongs to the warehouse of its Operation Type.
A warehouse whose Accessing Users list is empty is open to everyone holding an Inventory level, so its batches are readable by all of them. Once the list names people, only those people (and All Warehouses Users) see the batches of that warehouse. A batch without an operation type, or whose operation type has no warehouse, is visible only to All Warehouses Users.
Warehouse operator and manager: work with batches
The warehouse manager has the same access to batches as the operator, on the warehouses they are assigned to; this chapter applies to both.
Find the batches of my warehouse
- Open Inventory > Operations. The Jobs group lists Batch Transfers and Wave Transfers.
- Select Batch Transfers. The list shows the batches of your warehouses only.
The list has no New button: an operator does not create batches. Batches are created when Inventory groups transfers automatically.
Open a batch
- Select a batch in the list.
- The Operations tab lists the products of every transfer of the batch, and the Transfers tab lists the transfers themselves.
- You may update the batch, for example its Responsible person.
Validate the whole batch
- Open the batch.
- Press Validate. The transfers of the batch are validated together.
Validate one transfer of a batch
- Open Inventory > Operations > Transfers and choose Deliveries (or Receipts). The Batch Transfer column shows the batch of each transfer.
- Open the transfer and press Validate.
- The transfer is done and leaves its batch. The other transfers stay in the batch.
Limits of this access
- A batch of another warehouse is hidden from you: it is not in the list and opening it is refused.
- You read and update batches; you cannot create or delete one.
- The controls that start a new batch or wave, or that merge batches, are not offered to you: Prepare Wave on Wave Transfers, Add to batch and Add to wave in the Actions menu of the transfers lists, the batch and wave entries on the operation cards of Inventory > Overview, and Merge on the batch list. They belong to All Warehouses Users.
- Wave Transfers is in your menu so that you can read the waves of your warehouses. The card links that only open a list, such as the number of batches of a delivery card, stay.
- The Actions menu of a list may still show standard entries such as Duplicate or Delete; the batch and transfer rules decide whether they are accepted.
Logistics coordinator: standard batch access
A person who holds All Warehouses User sees every batch and works as in standard Inventory: creating and deleting batches, Add to batch, Add to wave, Prepare Wave, the batch and wave entries of the operation cards and Merge are all available.
Troubleshooting
- An operator does not see a batch
- The warehouse of the batch lists accessing users and the operator is not one of them. Add the operator to Accessing Users of that warehouse, or give them All Warehouses User.
- An operator does not find Prepare Wave, Add to batch, Add to wave or Merge
- Creating a batch or a wave, and merging batches, is for All Warehouses User only, so these controls are not offered to the other levels. A coordinator holding that level prepares the batch or the wave.
- A transfer cannot be validated because of its batch
- The batch must belong to a warehouse the person is assigned to. Check the operation type of the batch and the Accessing Users of its warehouse.
FAQ
- Can a warehouse operator create or delete a batch?
- No. They read and update the batches of their warehouses and validate their transfers.
- Do operators see the batches of other warehouses?
- Not when the other warehouse lists accessing users that do not include them. Warehouses with an empty list are open.
- Does validating one transfer validate the whole batch?
- No. The transfer leaves the batch and the rest stays. Use Validate on the batch form to validate all of them.
This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file).
You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one).
It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software.
The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.