odoo-addon-purchase-request

================ Purchase Request

.. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! This file is generated by oca-gen-addon-readme !! !! changes will be overwritten. !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! source digest: sha256:a773f51d0c8b186ca91b9dbf7169f0b3e5a044209ff795e57711b9e5e090ca1e !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

.. |badge1| image:: https://img.shields.io/badge/maturity-Beta-yellow.png :target: https://odoo-community.org/page/development-status :alt: Beta .. |badge2| image:: https://img.shields.io/badge/licence-LGPL--3-blue.png :target: http://www.gnu.org/licenses/lgpl-3.0-standalone.html :alt: License: LGPL-3 .. |badge3| image:: https://img.shields.io/badge/github-OCA%2Fpurchase--workflow-lightgray.png?logo=github :target: https://github.com/OCA/purchase-workflow/tree/18.0/purchase_request :alt: OCA/purchase-workflow .. |badge4| image:: https://img.shields.io/badge/weblate-Translate%20me-F47D42.png :target: https://translation.odoo-community.org/projects/purchase-workflow-18-0/purchase-workflow-18-0-purchase_request :alt: Translate me on Weblate .. |badge5| image:: https://img.shields.io/badge/runboat-Try%20me-875A7B.png :target: https://runboat.odoo-community.org/builds?repo=OCA/purchase-workflow&target_branch=18.0 :alt: Try me on Runboat

|badge1| |badge2| |badge3| |badge4| |badge5|

You use this module if you wish to give notification of requirements of materials and/or external services and keep track of such requirements.

Requests can be created either directly or indirectly. "Directly" means that someone from the requesting department enters a purchase request manually.

The person creating the request determines what and how much to order, and the requested date.

"Indirectly" means that the purchase request initiated by the application automatically, for example, from procurement orders (MO, SO).

A purchase request is an instruction to Purchasing to procure a certain quantity of materials services, so that they are available at a certain point in time.

A line of a request contains the quantity and requested date of the material to be supplied or the quantity of the service to be performed. You can indicate the service specifications if needed.

Once request is approved go to the Purchase Request Lines from the menu entry 'Purchase Requests', and also from the 'Purchase' menu.

Select the lines that you wish to initiate the RFQ for, then go to 'More' and press 'Create RFQ'.

You can choose to select an existing RFQ or create a new one. In the later, you have to choose a supplier.

In case that you chose to select an existing RFQ, the application will search for existing lines matching the request line, and will add the extra quantity to them, recalculating the minimum order quantity, if it exists for the supplier of that RFQ.

In case that you create a new RFQ, the request lines will also be consolidated into as few as possible lines in the RFQ.

Table of contents

.. contents:: :local:

Configuration

To configure the product follow this steps:

1. Go to a product form.
2. Go to Inventory tab.
3. Check the box Purchase Request along with the route Buy and Replenish on Order (MTO)

Note that MTO route is archived by default, you should unarchive it first:

• Go to Inventory > Configuration > Routes, in the Search dropdown menu, click Archived to show Replenish on Order (MTO) route and Unarchive it.

With this configuration, whenever a procurement order is created and the supply rule selected is 'Buy' the application will create a Purchase Request instead of a Purchase Order.

Usage

Purchase requests are accessible through a new menu entry 'Purchase Requests', and also from the 'Purchase' menu.

Users can access the list of Purchase Requests or Purchase Request Lines.

It is possible to filter requests by its approval status.

Bug Tracker

Bugs are tracked on GitHub Issues <https://github.com/OCA/purchase-workflow/issues>. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback <https://github.com/OCA/purchase-workflow/issues/new?body=module:%20purchase_request%0Aversion:%2018.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**>.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

• ForgeFlow

Contributors

• Jordi Ballester Alomar [e-mail]

• Jonathan Nemry [e-mail]

• Aaron Henriquez [e-mail]

• Adrien Peiffer [e-mail]

• Lois Rilo [e-mail]

• Héctor Villarreal [e-mail]

• Ben Cai [e-mail]

• Rattapong Chokmasermkul [e-mail]

• Stefan Rijnhart [e-mail]

• Trobz <https://trobz.com>\ _:

  • Son Ho [e-mail]

• Komit Company Limited <https://komit-consulting.com/>__:

  • Quoc Pham Ngoc [e-mail]

Other credits

The development of this module has been financially supported by:

|Aleph Objects, Inc|

Images

-  Enric Tobella (logo)

.. |Aleph Objects, Inc| image:: https://upload.wikimedia.org/wikipedia/en/3/3b/Aleph_Objects_Logo.png
   :target: https://www.alephobjects.com

Maintainers
-----------

This module is maintained by the OCA.

.. image:: https://odoo-community.org/logo.png
   :alt: Odoo Community Association
   :target: https://odoo-community.org

OCA, or the Odoo Community Association, is a nonprofit organization whose
mission is to support the collaborative development of Odoo features and
promote its widespread use.

This module is part of the `OCA/purchase-workflow <https://github.com/OCA/purchase-workflow/tree/18.0/purchase_request>`_ project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.