Purchase Request Tier Validationby ForgeFlow https://github.com/OCA/purchase-workflow , Odoo Community Association (OCA) https://github.com/OCA/purchase-workflow
• Invoicing (account)
• Inventory (stock)
|Lines of code||4251|
|Also available in version||v 13.0 v 11.0 v 12.0|
Purchase Request Tier Validation
This module extends the functionality of Purchase Requests to support a tier validation process.
Table of contents
This module depends on base_tier_validation. You can find it at OCA/server-ux
A default tier is created allowing Purchase Request Manager to approve Purchase Requests.
In addition, you may want to add more tiers, so:
- Go to Settings > Technical > Tier Validations > Tier Definition.
- Create as many tiers as you want for Purchase Order model.
To use this module, you need to:
- Create a Purchase Request triggering at least one “Tier Definition”.
- Click on Request Validation button.
- Under the tab Reviews have a look to pending reviews and their statuses.
- Once all reviews are validated button to Confirm will be shown.
- You can filter the Purchase Request requesting your review through the filter Needs my Review.
- User with rights to confirm the Purchase Request (validate all tiers that would be generated) can directly do the operation, this is, there is no need for her/him to request a validation.
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.
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.
Please log in to comment on this module
- The author can leave a single reply to each comment.
- This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
- If you want to start a discussion with the author, please use the developer contact information. They can usually be found in the description.