Budget Control - Operating Unit
This module adds Operating Units in budget control sheet, budget transfer and budget move adjustment by selecting an OU in an Analytic Account, which can only be selected once per Analytic per OU.
Table of contents
Usage
The budget control sheet will compute the Operating Units from the Analytic accounts. Analytic accounts with no Operating Units assigned to them will be accessible to all users with access to analytic accounts. To configure the Operating Units for an Analytic account, follow these steps:
Go to Budgeting > Configurations > Analytic Accounts and add the accepted Operating Units to each analytic account.
Normally, budget transfer can only be made within the budget control’s Operating Unit. If you want to transfer across Operating Units, you can talk with budget manager.
Note: The budget control must have only one Operating Unit from the Analytic account.
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
Saran Lim. <saranl@ecosoft.co.th>
Maintainers
Current maintainer:
This module is part of the ecosoft-odoo/budgeting project on GitHub.
You are welcome to contribute.
Metadata
Release files for odoo-addon-budget-control-operating-unit 18.0.2.0.0
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 | Reset |
|---|---|---|---|---|
| odoo_addon_budget_control_operating_unit-18.0.2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_budget_control_operating_unit-18.0.2.0.0-py3-none-any.whl
| Download URL | odoo_addon_budget_control_operating_unit-18.0.2.0.0-py3-none-any.whl |
|---|---|
| Size | 33.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
813656c43349c82cd03900cda31089542ad9dfc9fc6e3e7e3876bf77298b4dfd
|
|
BLAKE2b-256 checksum How to use checksums |
0b3a86f8c05fb1b4b1d0b5619294c62aca1a1558936172b7336dc2ff7c2e60a3
|
| 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-budget-control-operating-unit 18.0.2.0.0
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.