Purchase Order Approval Block
This module allows you to block the approval of an RFQ when an Approval Block Reason has been provided. Upon confirmation of an RFQ the orders will be waiting for approval by a Manager.
Table of contents
Configuration
Go to ‘Purchases / Configuration / Purchase Approval Block Reasons’ and create the blocking reasons as needed, providing a name and a description. A field ‘Active’ allows you to deactivate the reason if you do not plan to use it any more.
Assign the security group ‘Release RFQ with approval block’ to users that should be able to release the block. Users in group ‘Purchase / Managers’ are by default assigned to this group.
Usage
Set the Purchase Approval Block
Go to ‘Purchases / Purchase / Requests for Quotation’
Create a new RFQ and indicate the approval block reason (found in the right hand side of the screen, below the order date).
Search existing RFQ
There is a filter ‘Blocked’ to search for orders that are blocked for approval. It is also possible to search RFQ’s with a specific block reason.
Confirm the RFQ
Press the button ‘Confirm’. If there’s an approval block, the order will be set to status ‘To Approve’. You will then need to request a Purchase Manager to approve it.
Release the purchase approval block
While the RFQ is in draft, members of security group ‘Release RFQ with approval block’, can see a button ‘Release Approval Block’. From this point and on, anyone seeing that RFQ will be able to validate it.
Notifications to followers
Followers of the RFQ receive notifications when an approval block has been set or released.
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 to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Jordi Ballester Alomar <jordi.ballester@forgeflow.com>
Roser Garcia <roser.garcia@forgeflow.com>
Darshan Patel <darshan.patel.serpentcs@gmail.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.
This module is part of the OCA/purchase-workflow 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 odoo-addon-purchase-order-approval-block 18.0.1.1.0
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 |
|---|---|---|---|---|
| odoo_addon_purchase_order_approval_block-18.0.1.1.0-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_purchase_order_approval_block-18.0.1.1.0-py3-none-any.whl |
Release files / odoo_addon_purchase_order_approval_block-18.0.1.1.0-py3-none-any.whl
| Download URL | odoo_addon_purchase_order_approval_block-18.0.1.1.0-py3-none-any.whl |
|---|---|
| Size | 37.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6d7f3a926373d1bf1d5cb20a631f369e93bdc6b1309d86d13765feef8ba051a6
|
|
BLAKE2b-256 checksum How to use checksums |
3757b7405995352f82676a6926d8b94357b1005557a0552c6a8ace6257191bdd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo-addon-purchase-order-approval-block 18.0.1.1.0
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.
