Operating Unit in Sales
This module extends the Sales capabilities of Odoo and introduces the operating unit to the Sales Order. Security rules are defined to ensure that users can only display the Sales Orders in which they are allowed access to.
Table of contents
Usage
Follow these steps:
Create a Sale Order.
The Operating Unit of the Sale Team is assigned to the Sale Order.
Known issues / Roadmap
The onchange_team_id method is not working. If you try to change the team in a sales quotation and the operating unit is not taken from the sales team, and moreover, I cannot select the operating unit from the team, only Main OU shows, must have to have your salesperson in the sales team of the operating unit.
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@forgeflow.com>
Aaron Henriquez <ahforgeflow@forgeflow.com>
Lois Rilo <lois.rilo@forgeflow.com>
Miquel Raich <miquel.raich@forgeflow.com>
Sudhir Arya <sudhir.arya@serpentcs.com>
Darshan Patel <darshan.patel.serpencs@gmail.com>
Alan Ramos <alan.ramos@jarsa.com.mx>
Jorge Alberto Olvera Cuenca <jorge.olvera@jarsa.com>
Alejandro Padrón <alejandro.padron@bt-group.com>
-
Bhavesh Heliconia
-
Maksym Yankin <maksym.yankin@camptocamp.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.
1 maintainer
Metadata
1 maintainer
Release files for odoo-addon-sale-operating-unit 19.0.1.0.0.2
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 |
|---|---|---|---|---|
| odoo_addon_sale_operating_unit-19.0.1.0.0.2-py3-none-any.whl | Python 3 | none | any | Details for odoo_addon_sale_operating_unit-19.0.1.0.0.2-py3-none-any.whl |
Release files / odoo_addon_sale_operating_unit-19.0.1.0.0.2-py3-none-any.whl
| Download URL | odoo_addon_sale_operating_unit-19.0.1.0.0.2-py3-none-any.whl |
|---|---|
| Size | 31.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f76476c0d2499d0297f0b136e6dc3f109786b867966864a021e10e72bec661f1
|
|
BLAKE2b-256 checksum How to use checksums |
00830740e4df2bc1987000de961a6a49aad52332d321b3bf2482041cbceb746c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for odoo-addon-sale-operating-unit 19.0.1.0.0.2
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.
