$ 56.34
Availability |
Odoo Online
Odoo.sh
On Premise
|
Odoo Apps Dependencies |
•
Invoicing (account)
• Purchase (purchase) • Discuss (mail) • Inventory (stock) |
Lines of code | 375 |
Technical Name |
po_three_level_approval_cr |
License | OPL-1 |
Website | https://www.candidroot.com/ |
Versions | 17.0 16.0 12.0 13.0 15.0 14.0 |
Community
Enterprise
PO Three Level Approval
This module helps to approve purchase orders, according to manager approval limit.
Youtube Video
01
Settings -> Users & Companies -> Companies -> Select your company -> Three Level Approve Settings Tab
Configure Three Level Approve Settings
02
Settings -> Users & Companies -> Users -> Select your user -> Custom groups under purchase section
Assign managers according to groups.
03
Click on Confirm Order button.
04
After Order is confirm, purchase order state will move into To Approve state.
Here A RFQ/Purchase order is created from user side, with amount of $ 3,500.00, which is higher than purchase manager limit.
05
In order to notify purchase manager, an email will get sent from user to purchase manager.
06
Click on Approve Order button.
07
After Order is approve, purchase order state will move into To Finance Approval State and Purchase Manager info will get added under Approve Information section.
Here A RFQ/Purchase order is created from user side, with amount of $ 3,500.00, which is higher than finance manager limit.
08
In order to notify finance manager, an email will get sent from purchase manager to finance manager.
09
Click on Finance Approval button.
10
After Order is approve, purchase order state will move into To Director Approval State and Finance Manager info will get added under Approve Information section.
Here A RFQ/Purchase order is created from user side, with amount of $ 3,500.00, which is higher than director manager limit.
11
In order to notify director, an email will get sent from finance manager to director.
12
Click on Director Approval button.
13
After Order is approve, state will move into To Purchase Order state and Director Manager info will get added under Approve Information section.
Then shipping record will get created, when puchase order is fully confirmed.
14
Refuse button for each manger.
15
Add refuse reason and click on Refuse button.
16
When manager click on refuse button, realted information will get added under Refuse Information section and purchase order state will move into Refuse state.
17
In order to notify user, an email will get sent from director to user about purchase order refusal.
Get Help From Us!
Our Services
Odoo Implementation
Odoo Customization
Odoo Development
Odoo Migration
Odoo Integration
Odoo Consulting
Odoo Support
Odoo Theme Development
Odoo CMS Development
Odoo Ecommerce Development
Mobile Application Development
Odoo Training
Please Follow Us On
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