-
-
Notifications
You must be signed in to change notification settings - Fork 752
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[13.0][ADD] purchase_isolated_rfq #851
[13.0][ADD] purchase_isolated_rfq #851
Conversation
2441058
to
9c9db37
Compare
9c9db37
to
20a2dfb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM (excel some very small comments about wording)
20a2dfb
to
cd8cdb0
Compare
Thank you for your review. Fixed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code and Functional review
LGTM 👍
This PR has the |
@kittiu, is it ready for merge? |
@HviorForgeFlow yes, it is ready :) |
/ocabot merge |
What a great day to merge this nice PR. Let's do it! |
Congratulations, your PR was merged at eeafc38. Thanks a lot for contributing to OCA. ❤️ |
This module base on Module : sale_isolated_quotation
Description:
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.
cc. @kittiu @Oakyman