Stock Inventory Verification Request
Adds the capability to request a Slot Verification when an inventory is ‘Pending to Approve’ or create one at will when a potential issue with a specific location is found. When asked from an inventory adjustment, which have discrepancies over the threshold for the location, a Slot Verification Request will be created for each line that exceed the maximum discrepancy allowed.
A SVR must be created when warehouse operation (e.g. an inventory adjustment, a cycle count…) uncovers a count discrepancy within a slot (a small stock location), and the discrepancy is greater than the pre-defined acceptable variance threshold. It is a stock manager’s task to confirm the SVR and assign it to someone to perform it.
The aim of SVR is to find and fix errors before they are transferred to another location, so they will not be found again in similar stock operations. In other words, a SVR helps to correct an already existing error in our stock records the earliest possible. Many times, a SVR will likely lead to manual actions (before being marked as solved) in order to fix the problems uncovered.
Table of contents
Usage
In order to use this module act as follow:
From a Inventory Adjustment in state ‘Pending to Approve’ click in the button ‘Request Verification’. This will create all the Slot Verification Request needed.
Go to ‘Inventory / Inventory Control / Slot Verification Request’
Go to a Slot Verification Request ‘Waiting Actions’ and confirm it.
You can now check the involved lines and moves to help you.
Once you have found the problem and you have fixed it ‘Mark as Solved’ the Verification.
You can also create the SVR manually.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Lois Rilo Antelo <lois.rilo@forgeflow.com>
Michael Allen <mallen@opensourceintegrators.com>
Bhavesh Odedra <bodedra@opensourceintegrators.com>
Adrià Gil Sorribes <adria.gil@forgeflow.com>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainer:
This module is part of the OCA/stock-logistics-warehouse project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo12-addon-stock-inventory-verification-request 12.0.3.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo12_addon_stock_inventory_verification_request-12.0.3.0.1-py3-none-any.whl | Python 3 | none | any | Details for odoo12_addon_stock_inventory_verification_request-12.0.3.0.1-py3-none-any.whl |
Release files / odoo12_addon_stock_inventory_verification_request-12.0.3.0.1-py3-none-any.whl
| Download URL | odoo12_addon_stock_inventory_verification_request-12.0.3.0.1-py3-none-any.whl |
|---|---|
| Size | 175.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f434251d162f79f57256183a5a4ae04403e9619626f244d45b46fe973f017e7f
|
|
BLAKE2b-256 checksum How to use checksums |
8b28016df2d530cdd43223544db24b1d257fd8ffdb13423595374048e68dcbc7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.8.5
|
Security for odoo12-addon-stock-inventory-verification-request 12.0.3.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
