This release is a pre-release and may not be stable for production use.
Operating Unit in Purchase Requests
This module introduces the following features:
Adds the Operating Unit (OU) to the Purchase Request.
The user’s default Operating Unit (OU) is proposed at the time of creating the Purchase Request.
Security rules are defined to ensure that users can only see the Purchase Request of that Operating Units in which they are allowed access to.
Table of contents
Usage
Follow these steps:
Create or use an existing Operating Unit (OU) in Settings -> Users & Configuration -> Operating Unit.
Change the configuration of the Users. In Application Accesses, put an User as Request manager and another one as Request User.
Create a Purchase Request Order. By default, if there is no Approver, any Manager with the same OU can accept the PO. If you specify an Approver, he must be in the same Operating Unit as the Purchase Request.
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>
Serpent Consulting Services Pvt. Ltd. <support@serpentcs.com>
Saran Lim. <saranl@ecosoft.co.th>
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.
1 maintainer
Metadata
1 maintainer
Release files for odoo14-addon-purchase-request-operating-unit 14.0.1.0.1.dev8
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 |
|---|---|---|---|---|
| odoo14_addon_purchase_request_operating_unit-14.0.1.0.1.dev8-py3-none-any.whl | Python 3 | none | any | Details for odoo14_addon_purchase_request_operating_unit-14.0.1.0.1.dev8-py3-none-any.whl |
Release files / odoo14_addon_purchase_request_operating_unit-14.0.1.0.1.dev8-py3-none-any.whl
| Download URL | odoo14_addon_purchase_request_operating_unit-14.0.1.0.1.dev8-py3-none-any.whl |
|---|---|
| Size | 34.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
983ad82908d491d7db5e4f2bd01d8b332d20e0b98d5fde0610a5e6bb36a871ff
|
|
BLAKE2b-256 checksum How to use checksums |
f184d645bc81c96e011e3cdc00c6f580865d3b6471b9484be69376768d13af01
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Security for odoo14-addon-purchase-request-operating-unit 14.0.1.0.1.dev8
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.
