Purchase Isolated RFQ
by Ecosoft https://github.com/OCA/purchase-workflow , Odoo Community Association (OCA) https://github.com/OCA/purchase-workflow| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Purchase (purchase)
• Invoicing (account) • Discuss (mail) |
| Lines of code | 176 |
| Technical Name |
purchase_isolated_rfq |
| License | AGPL-3 |
| Website | https://github.com/OCA/purchase-workflow |
| Versions | 14.0 13.0 |
Purchase Isolated RFQ
Note: This module is similar to sale_isolated_quotation, but for purchase/rfq
In some countries/companies, It’s already common to separate these two documents. For filing purposes, the document sequence of Requests For Quotation (RFQ) and Purchases order has to be separated. In practice, there could be multiple RFQ open to a vendor, yet only one RFQ get converted to the Purchases order.
This module separate RFQ and Purchases order by adding order_sequence flag in purchase.order model.
Each type of document will have separated sequence numbering. RFQ will have only 2 state, Draft and Done. Purchases Order work as normal.
Table of contents
Usage
- Create RFQ as normal
- As user click “Convert to Order”, the isolated purchases order will be created
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
Authors
- Ecosoft
Contributors
- Rattapong Chokmasermkul <rattapongc@ecosoft.co.th>
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/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