19.24

v 16.0 Third Party 2
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Employees (hr)
Purchase (purchase)
Discuss (mail)
Invoicing (account)
Lines of code 525
Technical Name ethics_purchase_request
LicenseOPL-1
Websitehttp://www.ethicsinfotech.in
Versions 13.0 14.0 15.0 16.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Employees (hr)
Purchase (purchase)
Discuss (mail)
Invoicing (account)
Lines of code 525
Technical Name ethics_purchase_request
LicenseOPL-1
Websitehttp://www.ethicsinfotech.in
Versions 13.0 14.0 15.0 16.0

Purchase Request

This will Add Menu Purchase Request to Purchase Module.


This module allows the user or employee to request to purchase products/services with two steps Approval and it will easily create Quotation from Purchase Request.




How To Use?


Go to Settings -> Users & Companies -> Users. It will add Purchase Request Group to Access Rights.Give Rights to particular User like User,Verifier or Approver.
Go to Purchase -> Orders -> Purchase Request.
Create Purchase Request select Employee, Department and Responsible person for Request.Then add Products to purchase with its Quantity and Save it.Then click on button 'Submit For Verifier'.
Purchase Request's state is changed to 'Waiting For Verifier'.Verifier can send it for Approval from Approver or can Reject it as shown in the snapshot:
After Verification state is changed to 'Waiting For Approver' and if verifier will reject it then to 'Draft'.Approver have to choose Vendors/Suppliers for particular product and Confirm it.
Once Request is approved by the Approver RFQs/Orders will be created automatically for each Vendor and State is changed to 'Confirm'.

RFQs/Orders:

Click on RFQs/Orders to Check RFQs and confirm it to Purchase Order.

RFQs/Orders with Back Purchase Request:

If Approver have added vendor in some required products and some products will be used in future so he/she will create Back Purchase Request for that products.
By clicking on 'Back PR' ,new PR will be created for product which vendor name is not added.
For product which vendor name is added RFQ will be created for each vendor.
New Purchase Request created by Back PR is shown below in snapshot:

PR Rejection Process:

Approver have to click on 'Reject' to reject the Purchase Request and select the Rejection Reason.
To add Rejection reason: Go to Purchase -> Configuration -> PR Reject Reason and click on 'Create'.
After clicking on 'Reject', PR status will be changed to 'Cancelled'.

Our Businesses


Ethics Infinity Pvt. Ltd.

Infrastructure Development

Ethics Infotech LLP

IT Services & Hardware Automation

Ethics Prosperity Pvt. Ltd.

Warehousing & Distribution

Ethics Travel Management Pvt. Ltd.

Tourism & Travel

Ethics Express Pvt. Ltd.

Logistics & Services

Need Support?


+91 90163 23084
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

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.