$ 25.32
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Purchase (purchase) • Discuss (mail) • Invoicing (account) |
| Lines of code | 699 |
| Technical Name |
purchase_requisition_creation |
| License | OPL-1 |
| Website | https://www.aktivsoftware.com/ |
| Versions | 12.0 13.0 14.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Purchase (purchase) • Discuss (mail) • Invoicing (account) |
| Lines of code | 699 |
| Technical Name |
purchase_requisition_creation |
| License | OPL-1 |
| Website | https://www.aktivsoftware.com/ |
| Versions | 12.0 13.0 14.0 |
Purchase Requisition Creation & Allocation
Overview
In Odoo's Purchase application, viewing purchase requisition and taking actions on it is very
accessible and easy from the requesting user's perspective. One can easily know when the
requested products purchase has started and when the products are received.
But on the contrary, for the Purchase Department, it becomes a bit more complex. So, here's the
advanced version of Purchase Requisition module.
We have defined the module features from three different users' perspective:
1. Purchase Requisition Creation User (Employee)
2. Purchase Requisition Approval User (Purchase Manager)
3. Buyer
Features
Purchase creation user can create and view the requisition.
Approval user can view requisition and could choose from these three options- approve, approved, rejected.
Buyers can view requisition assigned to them and requisitions which are approved by the approval user.
Buyer can directly create RFQ of approved requisition.
Setup & Configuration
Prerequisites
-
No prerequisites required before installation.
Configuration
User will need to define different access roles from user setting.
Define Buyer groups to manage purchase of different products throughout the organization.
Go to Inventory -> Configuration -> Product Categories -> Set product group.
Screenshots
Creation user will add product, product quantity and expected delivery date to create a purchase requisition.
Creation users can view requisitions created by them.
Approval user now will approve or reject the orders/whole requisition.
Approval user can select multiple requisition to approve/reject them.
Reject Purchase Requisition
If the Approval User rejects the Purchase Requisition, system will ask the reason behind rejection to analyze it further.
A wizard is generated once the requisition is rejected and it will allow user to enter rejection reason which will be stored in the log note.
When the Purchase Requisition has at least one item "Approved" and remaining items are waiting for the approval, then Purchase Requisition will be in "Partially Approved" state.
Buyers can view approved requisition assigned to them.
Buyers can select approved requisition and create RFQ from the "Action" itself.
Buyers can select multiple approved requisition and create one RFQ.
When the Purchase Requisition has at least one item "Closed" from the list, then the Purchase Requisition will be in "Partially Closed" state.
Our Services
Odoo Consulting
Odoo Customization
Odoo Implementation
Odoo Integration
Odoo Migration
Odoo Support
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