Account Analytic Second Axis (analytic_secondaxis)

Security findings

Migration considerations

account_analytic_line — Class 'account_analytic_line' still inherits from the old-style `osv.osv` API: rewrite it against `models.Model`/`models.TransientModel`/`models.AbstractModel` - the old `osv`/`orm` API was removed entirely in modern Odoo. migration-old-api-base · source
account_analytic_line — Class 'account_analytic_line' declares `_columns` as a plain dict: old-style field/default declarations, replace with `fields.X(...)` class attributes and `default=`. migration-old-style-fields · source
activities_analytic_chart — Class 'activities_analytic_chart' still inherits from the old-style `osv.osv_memory` API: rewrite it against `models.Model`/`models.TransientModel`/`models.AbstractModel` - the old `osv`/`orm` API was removed entirely in modern Odoo. migration-old-api-base · source
activities_analytic_chart — Class 'activities_analytic_chart' declares `_columns` as a plain dict: old-style field/default declarations, replace with `fields.X(...)` class attributes and `default=`. migration-old-style-fields · source
analytic_account — Class 'analytic_account' still inherits from the old-style `osv.osv` API: rewrite it against `models.Model`/`models.TransientModel`/`models.AbstractModel` - the old `osv`/`orm` API was removed entirely in modern Odoo. migration-old-api-base · source
analytic_account — Class 'analytic_account' declares `_columns` as a plain dict: old-style field/default declarations, replace with `fields.X(...)` class attributes and `default=`. migration-old-style-fields · source
project_activity_al — Class 'project_activity_al' still inherits from the old-style `osv.osv` API: rewrite it against `models.Model`/`models.TransientModel`/`models.AbstractModel` - the old `osv`/`orm` API was removed entirely in modern Odoo. migration-old-api-base · source
project_activity_al — Class 'project_activity_al' declares `_columns` as a plain dict: old-style field/default declarations, replace with `fields.X(...)` class attributes and `default=`. migration-old-style-fields · source
project_activity_al — Class 'project_activity_al' declares `_defaults` as a plain dict: old-style field/default declarations, replace with `fields.X(...)` class attributes and `default=`. migration-old-style-fields · source
view_activity_al_list — View 'view_activity_al_list' is defined with a `<tree>` root tag: renamed to `<list>` in Odoo 18.0. migration-view-tree-tag · source
view_activity_al_tree — View 'view_activity_al_tree' is defined with a `<tree>` root tag: renamed to `<list>` in Odoo 18.0. migration-view-tree-tag · source

Migration review checklist, not a compatibility verdict. No target version is selected: apply version-specific advice only when migrating to that version or later.

Repository: OCA/account-analytic · module folder · Try on Runboat
Module version: 1.1
Category: Generic Modules/Accounting
Folder size: 0.04 MB
License: AGPL-3
Application: No
Auto-installable: No
Website: http://camptocamp.com
Last tracking update: 2026-08-07 07:17:45
Authors: Camptocamp, Odoo Community Association (OCA)
Maintainers: Camptocamp, Odoo Community Association (OCA)
Committers: Pedro M. Baeza, Stéphane Bidoul (ACSONE)

Odoo dependencies

odoo/odoo:

- account

- base_setup

- base

- web_kanban

- web

- product

- decimal_precision

- mail

- bus

- web_tour

- report

- analytic

- web_planner

Python dependencies

None

System dependencies

None

Required by

analytic_secondaxis_multicurrency, analytic_secondaxis_timesheet

Description

    Add a second analytical axis on analytic lines allowing you to make
    reporting on.

    Unless the account_analytic_plans from OpenERP SA, this module allow you to
    make cross-reporting between those two axes, like all analytic lines that
    concern for example:
    The activity "Communication" and the project "Product 1 Integration".

    This second axis is called "activities" and you will be able to define for
    each analytical account, what are the allowed activities for it.

    There's also a kind of heritage between analytical account. Adding
    activities on parent account will allow child to benefit from. So you can
    define a set of activities for each parent analytic account like:

    Administratif
        - Intern
        - Project 1
    Customers project
        - Project X
        - Project Y

    What will be true for Administratif, will be true for Intern too.

Code Analysis info_outline

Views touched (9)

XML ID	Name	Model	Type	Status
`account_analytic_line_extended_form`	account.analytic.line.extended_form	account.analytic.line	form	Inherits account.account_analytic_line_extended_form
`activities_analytic_chart_view`	Chart of Analytic Activities	activities.analytic.chart	form	New
`view_account_analytic_account_form`	account.analytic.account.form	account.analytic.account	form	Inherits account.view_account_analytic_account_form
`view_account_analytic_line_filter`	account.analytic.line.select	account.analytic.line	search	Inherits account.view_account_analytic_line_filter
`view_account_analytic_line_form`	account.analytic.line.form	account.analytic.line	form	Inherits account.view_account_analytic_line_form
`view_account_analytic_line_tree`	account.analytic.line.tree	account.analytic.line	tree	Inherits account.view_account_analytic_line_tree
`view_activity_al_form`	project.activity_al.form	project.activity_al	form	New
`view_activity_al_list`	project.activity_al.list	project.activity_al	tree	New
`view_activity_al_tree`	project.activity_al.tree	project.activity_al	tree	New

HTTP endpoints (0)

No HTTP endpoints found for this module.

Models touched (0)

No models found for this module.