Create budgets for MIS reports.
This module lets you create budgets for any MIS report. Several budgets can be created for a given report template (ie one budget per year). Budget figures are provided by KPI or by GL account, with different time periods. A budget can then be selected as a data source for a MIS report column, and the report will show the budgeted values for each KPI, adjusted for the period of the column.
Table of contents
Usage
There are two ways to use this module: create budgets by KPI or budgets by GL accounts. Currently, the two methods cannot be combined in the same budget.
Budget by KPIs
To use this this mode, you first need to flag at least some KPI in a MIS report to be budgetable. You also need to configure the accumulation method on the KPI according to their type.
The accumulation method determines how budgeted values spanning over a time period are transformed to match the reporting period.
Sum: values of shorter period are added, values of longest or partially overlapping periods are adjusted pro-rata temporis (eg monetary amount such as revenue).
Average: values of included period are averaged with a pro-rata temporis weight. Typically used for values that do not accumulate over time (eg a number of employees).
When KPI are configured, you need to create a budget, using the MIS Budget (by KPIs) menu, then click on the budget items button to create or import the budgeted amounts for all your KPI and time periods.
Budget by GL accounts
You can also create budgets by GL accounts. In this case, the budget is populated with one line per GL account (and optionally analytic account and/or tags) and time period.
Add budget columns to report instances
Finally, a column (aka period) must be added to a MIS report instance, selecting your newly created budget as a data source. The data will be adjusted to the reporting period when displayed. Columns can be compared by adding a column of type “comparison” or “sum”.
Known issues / Roadmap
The mis_builder roadmap and known issues can be found on GitHub.
Changelog
11.0.3.5.0 (2020-03-28)
Features
Budget by GL account: allow budgeting by GL account in addition to the existing mechanism to budget by KPI. Budget items have a begin and end date, and when reporting a pro-rata temporis adjustment is made to match the reporting period. (#259)
11.0.3.4.0 (2019-10-26)
Bugfixes
Consider analytic tags too when detecting overlapping budget items. Previously only analytic account was considered, and this overlap detection mechanism was overlooked when analytic tags were added to budget items. (#241)
11.0.3.3.0 (2019-01-13)
Features
Support analytic filters. (#15)
11.0.3.2.1 (2018-06-30)
[IMP] Support analytic tags in budget items (#100)
11.0.3.2.0 (2018-05-02)
[FIX] #NAME error in out-of-order computation of non budgetable items in budget columns (#68)
11.0.3.1.1 (2018-02-04)
Migration to Odoo 11. No new feature. (#67)
10.0.3.1.0 (2017-11-14)
New features:
[ADD] multi-company record rule for MIS Budgets (#27)
10.0.1.1.1 (2017-10-01)
First version.
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 smashing it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Stéphane Bidoul <stephane.bidoul@acsone.eu>
Adrien Peiffer <adrien.peiffer@acsone.eu>
Benjamin Willig <benjamin.willig@acsone.eu>
Artem Kostyuk <a.kostyuk@mobilunity.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.
Current maintainer:
This module is part of the OCA/mis-builder 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 odoo11-addon-mis-builder-budget 11.0.3.5.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 | Actions Reset |
|---|---|---|---|---|
| odoo11_addon_mis_builder_budget-11.0.3.5.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for odoo11_addon_mis_builder_budget-11.0.3.5.0-py2.py3-none-any.whl |
Release files / odoo11_addon_mis_builder_budget-11.0.3.5.0-py2.py3-none-any.whl
| Download URL | odoo11_addon_mis_builder_budget-11.0.3.5.0-py2.py3-none-any.whl |
|---|---|
| Size | 56.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
f9fe8ccbf4b13b2b8dfa9c1e21cb2a37fb590d864e86c365461a8f83dff3800c
|
|
BLAKE2b-256 checksum How to use checksums |
fd902ffe70147508b93f533da61adab79d02c205dcd022b45450193aa04f7120
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/30.4.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.3
|
Security for odoo11-addon-mis-builder-budget 11.0.3.5.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
