With Activity Based Costing (ABC), costs are generated by activities.
Activities generating costs are represented as Analytic Items. For example, a timesheet entry could be an activity. Other activities could be captured to be stored in Odoo as Analytic Items.
These activity Analytic Items will automatically generate additional Analytic Items for the costs driven this activity. For example, a machine operating time could drive consumptions of Labor and Overhead.
The cost drivers are regular non-storable Products, with an additional definition of the costs they drive.
Table of contents
Usage
When creating Analytic Items for a cost driver Product, the corresponding Analytic Items for driven cost are generated.
When an Analytic Item is created, an automatic process checks the Activity Based Cost Rules to identify the ones that apply.
Each rule creates a new Analytic Item for the driven costs, as a copy of the original one, with:
Product: set to rule’s Cost Type Product. A validation error prevents this from being the same as the source Analytic Item Product, to avoid infinite loops.
Cost Quantity: is the original quantity multiplied by the rule’s Factor
Cost Amount: is -1 * Quantity * Product Unit Cost
Parent Analytic Item (new field): set with a link to the original Analytic Item
Quantity: zero, to avoid duplication
Amount: zero, to avoid duplication
Project and Task: if present, are reset, to avoid representing the driven costs as timesheet lines.
An update on the original Quantity triggers a recalculation of the quantity and amount of the child Analytic Items.
A delete cascades to the child Analytic Items, causing them to also be deleted.
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
Open Source Integrators <https://opensourceintegrators.com>:
Daniel Reis <dreis@opensourceintegrators.com>
Chandresh Thakkar <cthakkar@opensourceintegrators.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/account-analytic 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-analytic-activity-based-cost 14.0.4.1.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 |
|---|---|---|---|---|
| odoo14_addon_analytic_activity_based_cost-14.0.4.1.0-py3-none-any.whl | Python 3 | none | any | Details for odoo14_addon_analytic_activity_based_cost-14.0.4.1.0-py3-none-any.whl |
Release files / odoo14_addon_analytic_activity_based_cost-14.0.4.1.0-py3-none-any.whl
| Download URL | odoo14_addon_analytic_activity_based_cost-14.0.4.1.0-py3-none-any.whl |
|---|---|
| Size | 41.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
499a0d4e17e732bfaf1bb12ed0390b410c174adc44cb8f8a05636974b07a0c5e
|
|
BLAKE2b-256 checksum How to use checksums |
4fe47761005d43338e97083b5c4ff85797594b8a5ba6c04bb41a5adb6354c559
|
| 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-analytic-activity-based-cost 14.0.4.1.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.
