Purpose ======= Make it possible to compare analytic values between plans by inputting up to one account per plan on each line. For instance, if we have 2 plans: "Country" and "Product Type", with the following accounts | Country | Product Type | | ------- | ------------ | | BE | Drinks | | LU | Food | And the following invoices: * 1000€ of drinks in Belgium * 2000€ of food in Belgium * 3000€ of food in Luxemburg We want to be able to display the following pivot tables: | | Drinks | Food | Total | | --- | ------ | ---- | ----- | | BE | 1000 | 2000 | 3000 | | LU | 0 | 3000 | 3000 | | Tot | 1000 | 5000 | 6000 | | | Total | | ------ | ----- | | Food | 5000 | | * BE | 2000 | | * LU | 3000 | | Drinks | 1000 | | * BE | 1000 | | Total | 6000 | Implementation ============== * `ir.fields` are added/removed dynamically on `account.analytic.line` * Each analytic plan corresponds to one field on `account.analytic.line` * The fields are added dynamically in the views. * `account.analytic.plan` doesn't have a `company_id` field anymore, meaning that all the companies have access to all the plans. This means that the applicability fields and lines are now company dependent, and those can be used to know which fields/plans to display for which company. * There can no longer be one "Project" plan per company, even if the accounts of that project can still be owned by only one company. * There is now only one method to get the default (or "Project" plan), which is `_get_plan_columns` task-3497653 closes odoo/odoo#139225 Related: odoo/upgrade#5306 Related: odoo/enterprise#49226 Signed-off-by: William André (wan) <wan@odoo.com> Co-authored-by: william <wan@odoo.com> Co-authored-by: h4818 <ayh@odoo.com>
20 lines
879 B
XML
20 lines
879 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<odoo>
|
|
<data noupdate="1">
|
|
<record id="decimal_percentage_analytic" model="decimal.precision">
|
|
<field name="name">Percentage Analytic</field>
|
|
<field name="digits" eval="2"/>
|
|
</record>
|
|
|
|
<!--
|
|
Save which plan is used for Projects. Once it is set, even if not used, it cannot be changed safely without a SQL script.
|
|
The other plans will generate dynamic columns, so changing this param would require renaming the columns also.
|
|
-->
|
|
<function model="ir.config_parameter" name="set_param" eval="('analytic.project_plan', '1')"/>
|
|
<record id="analytic_plan_projects" model="account.analytic.plan">
|
|
<field name="name">Projects</field>
|
|
<field name="default_applicability">optional</field>
|
|
</record>
|
|
</data>
|
|
</odoo>
|