Purchase Order Approved
This module extends the functionality of purchases adding a new state Approved in purchase orders before the Purchase Order state. Additionally add the possibility to set back to draft a purchase order in all the states previous to Purchase Order. From a user point of view, this change introduces a two-step validation process of the purchase order.
In this new Approved state:
You cannot modify the purchase order.
However, you can go back to draft and pass through the workflow again.
The incoming shipments are not created. You can create them by clicking the Convert to Purchase Order button, also moving to state Purchase Order.
The new state diagram is depicted below:
Table of contents
Configuration
This new workflow can be activated by company and by supplier.
To activate the new workflow by company:
Go to ‘Purchase > Configuration > Settings’.
In the Orders section you can set the State ‘Approved’ in Purchase Orders.
To activate the new workflow by supplier:
Open the supplier form view.
In the Purchase section in the Sales & Purchases tab the field Purchase requires second approval allows you to select the policy to apply for the current supplier. ‘Never’ | ‘Always’ | ‘Based on company policy’
Usage
To use this module, you need to:
Go to a Request for Quotation.
Click Confirm Order. The state is now Approved (if no order approval is not set).
To move forward to the state Purchase Order and release the creation of the deliveries, click on Convert to Purchase Order.
Changelog
11.0.1.0.0 (2018-06-06)
[MIG] Migrated to v11.
12.0.1.0.0 (2019-06-13)
[MIG] Migrated to v12.
12.0.1.0.0 (2020-07-16)
[MIG] Migrated to v13.
15.0.1.0.0 (2021-12-05)
[MIG] Migrated to v15.
16.0.1.0.0 (2023-02-28)
[MIG] Migrated to v16.
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
Lois Rilo <lois.rilo@forgeflow.com>
Rattapong Chokmasermkul <rattapongc@ecosoft.co.th>
Laurent Mignon <laurent.mignon@acsone.eu>
Moaad Bourhim <moaad.bourhim@gmail.com>
Rolando Duarte <rolando@vauxoo.com>
Elliott Bristow <elliott@glo.systems>
-
Quoc Pham Ngoc <quoc-pn@komit-consulting.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
Release files for odoo-addon-purchase-order-approved 19.0.1.0.2.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 | Reset |
|---|---|---|---|---|
| odoo_addon_purchase_order_approved-19.0.1.0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_purchase_order_approved-19.0.1.0.2.1-py3-none-any.whl
| Download URL | odoo_addon_purchase_order_approved-19.0.1.0.2.1-py3-none-any.whl |
|---|---|
| Size | 133.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5352f32f04e6f9bf774e7d17908b7b3d829537148ae9b627c2478b97be698f6f
|
|
BLAKE2b-256 checksum How to use checksums |
b7d9ba949b04a5f9c667667b892b23c526153a5db22cc7a36a29b51ee3319471
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
