======================

Purchase Product Usage

.. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! This file is generated by oca-gen-addon-readme !! !! changes will be overwritten. !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

.. |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-AGPL--3-blue.png :target: http://www.gnu.org/licenses/agpl-3.0-standalone.html :alt: License: AGPL-3 .. |badge3| image:: https://img.shields.io/badge/github-OCA%2Fpurchase--workflow-lightgray.png?logo=github :target: https://github.com/OCA/purchase-workflow/tree/11.0/purchase_product_usage :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-11-0/purchase-workflow-11-0-purchase_product_usage :alt: Translate me on Weblate .. |badge5| image:: https://img.shields.io/badge/runbot-Try%20me-875A7B.png :target: https://runbot.odoo-community.org/runbot/142/11.0 :alt: Try me on Runbot

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

When purchasing, users can indicate a usage from a list, for every item in the purchase order.

Usages can be associated with specific accounts. When the supplier invoice is created from that purchase order line, the account defined for that usage will be proposed, instead of the product's default expense account. This proposal will only be effective if the product is a consumable or a service.

Usages can be very diverse, like internal use, marketing use, testing use. So a product "Paper" could potentially translate to marketing expense, or an office expense, irrespective of what is the expense account defined in the product "Paper".

Table of contents

.. contents:: :local:

Configuration

In order to be able to define usages, assign users to the group "Define Purchase Product Usages". The group is proposed by default to users in the group "Purchase Manager"

Go to Purchases / Configuration / Purchase Product Usages and define the usages, indicating the description and optionally the code, default product and account to use.

Usage

In the PO line set the usage of the purchased product. If the usage has a default product it will be set in the PO line. If the product is a consumable or a service then the invoice will take the account from the usage. In any other case the normal behavior is expected.

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 smashing it by providing a detailed and welcomed feedback <https://github.com/OCA/purchase-workflow/issues/new?body=module:%20purchase_product_usage%0Aversion:%2011.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

* Eficent

Contributors

• Jordi Ballester Alomar jordi.ballester@eficent.com
• Aaron Henriquez ahenriquez@eficent.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/11.0/purchase_product_usage>`_ project on GitHub.

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