This release is a pre-release and may not be stable for production use.
This module introduces the following features:
It introduces the operating unit to the purchase order.
The operating unit is copied to the invoice.
The operating unit is copied to the stock picking.
It implements user’s security rules.
Table of contents
Usage
Follow these steps:
Use or create a new Operating Unit in Settings -> Users & Companies -> Operating Unit (OU)
Assign the OU to the User in Settings -> Users & Companies -> Users
Create a new Warehouse for the OU in Inventory -> Warehouse Management -> Warehouses.
Create a new Purchase Order with the OU and confirm it.
The OU is propagated to the Stock Picking.
After the confirmation, create a new Invoice. The OU is propagated, but you have to verify that the Journal has the same OU.
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 <aheficent@eficent.com>
Sudhir Arya <sudhir.arya@serpentcs.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/operating-unit project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Metadata
Release files for odoo11-addon-purchase-operating-unit 11.0.1.1.1.99.dev2
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 |
|---|---|---|---|---|
| odoo11_addon_purchase_operating_unit-11.0.1.1.1.99.dev2-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for odoo11_addon_purchase_operating_unit-11.0.1.1.1.99.dev2-py2.py3-none-any.whl |
Release files / odoo11_addon_purchase_operating_unit-11.0.1.1.1.99.dev2-py2.py3-none-any.whl
| Download URL | odoo11_addon_purchase_operating_unit-11.0.1.1.1.99.dev2-py2.py3-none-any.whl |
|---|---|
| Size | 29.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
b9f142a671c312b9459688352e5a8d09cb76b2752ed8393a1b6a025f44c65281
|
|
BLAKE2b-256 checksum How to use checksums |
6da06638689d591c9271aafd5b3b31e069957f365159d10f70a76c47b1eb34ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.5
|
Security for odoo11-addon-purchase-operating-unit 11.0.1.1.1.99.dev2
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.