Carry Analytic Account to child Manufacturing Orders
When confirming a Manufacturing Order, the components with MTO routes will generate child manufacturing orders.
This feature will set on those MOs the same Analytic Account as in parent MO.
auto_awesome What this module does
AI-generated from the code · Odoo 14.0When a Manufacturing Order is confirmed or its analytic account is changed, the same analytic account is automatically copied to the child manufacturing orders generated from it.
This module extends the Manufacturing Order (mrp.production) so that the analytic account used for cost tracking is not lost when a manufacturing order creates child orders.
- When you confirm a manufacturing order that already has an analytic account, Odoo looks at the child manufacturing orders generated through the procurement chain and writes the same analytic account on them.
- If you later change the analytic account on the parent manufacturing order, the child manufacturing orders are updated again with the new value.
- Only orders that actually have an analytic account are processed on confirmation, so orders without one are left untouched.
It works together with the mrp_analytic module, which is required for the analytic account field to exist on manufacturing orders. The module does not add new menus, screens, buttons or reports; it only changes what happens behind the scenes when confirming or saving a manufacturing order. The affected records are manufacturing orders (mrp.production) and the stock moves and procurement groups used to find the related child orders.
Depends on
Models and fields (1)
- mrp.production · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 14.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/account-analytic.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.