This release is a pre-release and may not be stable for production use.
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 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. 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.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Jordi Ballester Alomar <jordi.ballester@eficent.com>
Aaron Henriquez <ahenriquez@eficent.com>
Maintainers
This module is maintained by the OCA.
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.
1 maintainer
Metadata
1 maintainer
Release files for odoo12-addon-purchase-product-usage 12.0.1.0.0.99.dev6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo12_addon_purchase_product_usage-12.0.1.0.0.99.dev6-py3-none-any.whl | Python 3 | none | any | Details for odoo12_addon_purchase_product_usage-12.0.1.0.0.99.dev6-py3-none-any.whl |
Release files / odoo12_addon_purchase_product_usage-12.0.1.0.0.99.dev6-py3-none-any.whl
| Download URL | odoo12_addon_purchase_product_usage-12.0.1.0.0.99.dev6-py3-none-any.whl |
|---|---|
| Size | 30.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dde626451f751402b2016fd71a7d193825daf06242b4aac53a3f071c20742adb
|
|
BLAKE2b-256 checksum How to use checksums |
2bc0694feb7586d05614309b4296bd79e584d7b06897fd6cc04d3675c8f1a92e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Security for odoo12-addon-purchase-product-usage 12.0.1.0.0.99.dev6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
