| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Employees (hr)
• Purchase (purchase) • Discuss (mail) • Invoicing (account) |
| Lines of code | 413 |
| Technical Name |
eg_rfq_employee |
| License | OPL-1 |
| Website | http://www.inkerp.com |
| Versions | 11.0 12.0 13.0 14.0 15.0 16.0 17.0 |
Purchase order Request By Employees
This module allows users or employees to request the purchase of products. The organisation has its own stages for this process, and we have made the stage flow dynamic, allowing you to create stages as needed. Along with defining the stages, you also need to specify the related access group that will approve each stage.
Highlight Purchase order Request By Employees
Manage purchase stages and approval groups
Create multiple RFQs or POs from a request
Customizable stage flow for flexible control
Features
Screenshots
Support
Service
Features
Dynamic Stage Management:
Manage purchase request stages with customizable options and assign access groups for each stage to control approvals.
Multiple RFQ/PO Creation:
Easily generate multiple RFQs or POs from a single purchase request using the available buttons.
Screenshot
1) User form view:
Go to Settings ➡ Users. In the Purchase Request section, choose the user or manager.
Navigation : Settings ➡ Users & Companies ➡ User
2) Stage tree view:
The list view of the stages is shown below. You can configure stages according to the organization's rules and select the access groups that can approve each stage.
Navigation : Purchase Request ➡ Purchase Request ➡ Stages
3) Stage form view:
In the stage form view, enter the stage name, the next stage name, and select the access group that can approve it.
4) Purchase request form view:
Now, when a user requests a product purchase, the requesting user can only see the product request part.
Navigation : Purchase Request ➡ Purchase Request ➡ Purchase Request
5) Purchase request form view:
When the request is in the new stage, if the requesting user tries to confirm it, an alert is generated because the user does not have access to confirm the request. Users can see information about cancelling or purchasing requests in the 'Other Information' tab.
6) Purchase request form view:
After pressing the 'Approve' button, the request moves to the confirm stage.
7) Purchase request form view:
After that, if users try to confirm the request, an alert is generated.
8) Purchase request kanban view:
Now, when the request manager logs in, they can see all requests.
9) Purchase request form view:
The request manager can confirm that request.
10) Purchase request form view:
If the request manager tries to mark the request as 'Done', an alert is shown because the manager does not have access to complete the request.
11) Purchase request form view:
The next stages can be approved by the designated access group, so an alert is generated if the request manager tries to mark the request as 'Done'.
12) Purchase request form view:
Now, when the purchase user logs in, they have access to complete this request. Therefore, the purchase request moves to the 'Done' stage after pressing the 'Approve' button.
13) Purchase request form view:
TThe purchase user can either cancel this request or create the purchase order.
14) Purchase request form view:
After selecting the vendor, the purchase user (who has access) can create the purchase order.
15) Purchase order form view:
The created purchase order form view looks like below.
16) Purchase request form view:
Using the smart button, you can see the created RFQ/PO. You can find information about purchase requests in the 'Other Information' tab.
17) Purchase request form view:
Press the "cancel" button to cancel the purchase request.
18) Purchase request form view:
Write the cancel reason and press the "Cancel Request" button.
19)Purchase request form view:
After cancelling the request, it moves to the 'New' stage using the 'Set To Draft' button. You can see the cancelled request details in the 'Other Information' tab.
20) Purchase request form view:
The request goes to the 'New' stage. From here, all processes need to be completed to create the purchase order.
21) Purchase request kanban view:
You can group purchase requests by vendor, employee, request user, stage, request date (day, week, month, quarter, year), and request type.
User Guide
Suggested Products
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