Approvals: option to not merge POs
by CLuedoo https://www.cluedoo.com/shop/licclusetpur0032-approvals-option-to-not-merge-pos-6730$ 249.99
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Approvals (approvals)
• Purchase (purchase) • Discuss (mail) • Employees (hr) • Invoicing (account) • Inventory (stock) |
| Community Apps Dependencies | Show |
| Lines of code | 395 |
| Technical Name |
fal_approval_purchase_no_grouping |
| License | OPL-1 |
| Website | https://www.cluedoo.com/shop/licclusetpur0032-approvals-option-to-not-merge-pos-6730 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Approvals (approvals)
• Purchase (purchase) • Discuss (mail) • Employees (hr) • Invoicing (account) • Inventory (stock) |
| Community Apps Dependencies | Show |
| Lines of code | 395 |
| Technical Name |
fal_approval_purchase_no_grouping |
| License | OPL-1 |
| Website | https://www.cluedoo.com/shop/licclusetpur0032-approvals-option-to-not-merge-pos-6730 |
ODOO'S FUNCTION
In Odoo Approvals, if two RFQs are created with the same vendor and approved, the system automatically merges them into one draft Purchase Order , which may simplify processing but can overwrite distinct line details like descriptions.
CLUEDOO'S FUNCTION
CLuedoo adds an option in the Product Category to disable PO merging for Approvals. When the same product is used in different Approval lines with unique descriptions, it generates a single RFQ with separate lines , preserving each description. It also introduces a "Vendor" field in the Approval, which is transferred to the RFQ.
NO ORDER GROUPING
1. Create a product and choose a Product Category |
|
|
Make sure you choose No order grouping in Procured Purchase Grouping |
|
|
2. Create another product and make sure it has the same Product Category and Vendor as the first one |
|
|
3. Go to
Approvals
>
New Request
> Create 2 requests with each product, fill in other necessary information like
Description
>
Submit
Note: You can add a Vendor here if you do not set it up in the product form |
|
|
4. After the Approver approves the requests and
Create RFQ's
> you will have 2 different RFQs with the same
Vendor
|
|
DESCRIPTION AND VENDOR PROPAGATION
1. Go to the Product Category and choose No line grouping in Procured Purchase Grouping |
|
|
2. Go to Approvals > New Request > Add the same product in different lines with different Descriptions , also select a Vendor here (can be different than the one you set in product form) > Submit |
|
|
3. After the Approver approves the requests and Create RFQ's > The Descriptions and the Vendor will be propagated to the RFQ, keeping the original ones from the approvals |
|
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module