Skip to main content

Beta License: AGPL-3 OCA/purchase-workflow Translate me on Weblate Try me on Runbot

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

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 Purchase / 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. 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.

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

Credits

Authors

  • ForgeFlow

Contributors

Maintainers

This module is maintained by the OCA.

Odoo Community Association

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 project on GitHub.

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

Metadata

Release files for odoo13-addon-purchase-product-usage 13.0.1.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for odoo13-addon-purchase-product-usage 13.0.1.1.1
File Interpreter ABI Platform
odoo13_addon_purchase_product_usage-13.0.1.1.1-py3-none-any.whl Python 3 none any Details

Release files / odoo13_addon_purchase_product_usage-13.0.1.1.1-py3-none-any.whl

Download URL odoo13_addon_purchase_product_usage-13.0.1.1.1-py3-none-any.whl
Size 30.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
f832221f8ba8a245a7cfc8ff25e4830566d0188a1627e5283e9bb00d3bfeb47d
BLAKE2b-256 checksum
How to use checksums
cd261c3adcfcc698714a8712efadf4b7ccbe0d3115527abf1b8b9f3a969e17c5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.2.0 pkginfo/1.6.1 requests/2.25.1 setuptools/51.0.0 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.7.3
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page