[IMP] accounting: full documentation of the new report engine

Engine report for accounting.

taskid: 4720

Author: oco-odoo

content/applications/finance/accounting/reporting/overview/customize.rst

@@ -1,90 +1,248 @@
-==================================================
-Create a customized reports with your own formulas
-==================================================
+========================================
+Customized report with your own formulas
+========================================
 
 Overview
 ========
 
-Odoo 13 comes with a powerful and easy-to-use reporting framework.
-Creating new reports (such as a tax report or a balance sheet or
-income statement with specific groupings and layout ) to suit your
-needs is now easier than ever.
+Odoo comes with a powerful and easy-to-use reporting framework. The engine allows you to create new
+reports, such as **tax reports**, or **balance sheets** and **income statements** with **specific
+groupings** and **layouts**.
 
-Activate the developer mode
-===========================
+Create your report
+==================
 
-In order to have access to the financial report creation interface, the
-:ref:`developer mode <developer-mode>` needs to be activated.
+In order to create a new report, go to :menuselection:`Accounting app --> Configuration -->
+Accounting Reports`. From here, you can either create a **root report** or a **variant**.
 
-Create your financial report
-============================
+.. image:: customize/engine-accounting-reports.png
+   :align: center
+   :alt: Accounting reports engine.
+
+.. important::
+   To access the accounting report creation interface, the :ref:`developer mode <developer-mode>`
+   has to be activated.
+
+Root reports
+------------
 
-First, you need to create your financial report. To do that, go to
-:menuselection:`Accounting --> Configuration --> Financial Reports`
+Root reports can be regarded as generic, neutral accounting reports. They serve as models on which
+local accounting versions are built. A tax report for Belgium and the US would both use the same
+generic version as a base and adapt it for their domestic regulations.
 
-.. image:: customize/customize02.png
+When creating a new root report, you need to create a **menu item** for it. To do so, **save** your
+report and then on that same report, click on :menuselection:`Action --> Create Menu Item`. Refresh
+the page and the report is now available under :menuselection:`Accounting --> Reporting`. If a
+report has no root report, it is considered to be a root report itself.
+
+.. note::
+   Cases that require the creation of a new root report are very rare. Only in specific situations
+   where a country's regulations would require the creation of new, specific report, would a new
+   root report be necessary.
+
+.. image:: customize/engine-create-menu-item.png
    :align: center
+   :alt: Create Menu Item button.
+
+.. seealso::
+    List of built-in main :doc:`root reports <../overview/main_reports>`.
+
+Variants
+--------
+
+Variants are country's specific versions of root reports and, therefore, always refer to a root
+report. To create a variant, simply select a generic (root) report in the :guilabel:`Root Report`
+field when creating a new root report.
 
-Once the name is entered, there are two other parameters that need to be
-configured:
+When an accounting (or root) report is opened from one of the accounting app's main menus, all
+variants available for that root are displayed in the variant selector in the top right corner of
+the view. In the following image, :guilabel:`VAT Report (BE)` is the variant of the root
+:guilabel:`Generic Tax report`.
 
--  **Show Credit and Debit Columns**
+.. image:: customize/engine-variant.png
+   :align: center
+   :alt: Report variant selection.
 
--  **Analysis Period** :
+Lines
+-----
 
-   -  Based on date ranges (e.g. Profit and Loss)
+After having created a report (either root or variant), you need to fill it with lines. You can
+either create a new one by clicking on :guilabel:`Add a line`, or modify an existing line by
+clicking on it. All lines *require* a **name**, and can have an optional additional **code** (of
+your choice) if you wish to use their value in formulas.
 
-   -  Based on a single date (e.g. Balance Sheet)
+Further options can be accessed by clicking on an existing line.
+ 
+.. image:: customize/engine-lines-options.png
+   :align: center
+   :alt: Engine lines options.
 
-   -  Based on date ranges with 'older' and 'total' columns and last 3
-      months (e.g. Aged Partner Balances)
+Expressions
+-----------
 
-   -  Bases on date ranges and cash basis method (e.g. Cash Flow
-      Statement)
+Each line can contain one or multiple **expressions**. Expressions can be seen as **sub-variables**
+needed by a report line. To access an expression, click on a line.
 
-Add lines in your custom reports
-=================================
+When creating an expression, you must attribute a **label** used to refer to that expression.
+Therefore, it has to be **unique** among the expressions of each line. Both a
+:guilabel:`Computation engine` and a :guilabel:`formula` must also be indicated. The **engine**
+defines how your **formula(s)** and **subformula(s)** are interpreted. It is possible to mix
+expressions using different computation engines under the same line if you need to.
 
-After you've created the report, you need to fill it with lines. They
-all need a **name**, a **code** (that is used to refer to the line), a 
-**sequence number** and a **level** (Used for the line rendering).
+.. note::
+   Depending on the engine, :guilabel:`subformulas` may also be required.
 
-.. image:: customize/customize04.png
+.. image:: customize/engine-expressions.png
    :align: center
+   :alt: Engine expressions.
 
-In the **formulas** field you can add one or more formulas to assign a
-value to the balance column (and debit and credit column if applicable –
-separated by ;)
+'Odoo Domain' engine
+~~~~~~~~~~~~~~~~~~~~
 
-You have several objects available in the formula :
+With this engine, a formula is interpreted as an :ref:`Odoo domain <reference/orm/domains>`
+targeting `account.move.line` objects.
 
--  ``Ndays`` : The number of days in the selected period (for reports with a
-   date range).
+The subformula allows you to define how the move lines matching the domain are used to compute the
+value of the expression:
 
--  Another report, referenced by its code. Use ``.balance`` to get its
-   balance value (also available are ``.credit``, ``.debit`` and
-   ``.amount_residual``)
+- **sum** : The result is the sum of all the balances of the matched move lines;
 
-A line can also be based on the sum of account move lines on a selected
-domain. In which case you need to fill the domain field with an Odoo
-domain on the account move line object. Then an extra object is
-available in the formulas field, namely ``sum``, the sum of the account
-move lines in the domain. You can also use the group by field to group
-the account move lines by one of their columns.
+- **sum_if_pos** : The result is the sum of all the balances of the matched move lines if this
+  amount is positive. Else, it's `0`;
 
-Other useful fields :
+- **sum_if_neg** : The result is the sum of all the balances of the matched move lines if this
+  amount is negative. Else, it's `0`;
 
--  **Type** : Type of the result of the formula.
+- **count_rows** : The result is the number of sub-lines of this expression. If the parent line has
+  a group-by value, this will correspond to the number of distinct grouping keys in the matched move
+  lines. Else, it will be the number of matched move lines.
 
--  **Is growth good when positive** : Used when computing the comparison
-   column. Check if growth is good (displayed in green) or not.
+You can also put a `-` sign at the beginning of the subformula to **invert** the sign of the
+result.
 
--  **Special date changer** : If a specific line in a report should not use
-   the same dates as the rest of the report.
+'Tax Tags' engine
+~~~~~~~~~~~~~~~~~
 
--  **Show domain** : How the domain of a line is displayed. Can be foldable
-   (``default``, hidden at the start but can be unfolded), ``always``
-   (always displayed) or ``never`` (never shown).
+A formula made for this engine consists of a name used to match tax tags. If such tags do not exist
+when creating the expression, they will be created.
 
-.. seealso::
-    * :doc:`main_reports`
+.. example::
+   If the formula is **tag_name**, the engine matches tax tags **+tag_name** and **-tag_name**,
+   creating them if necessary.
+
+When evaluating the expression, the expression computation can roughly be expressed as: **(amount of
+the move lines with** `+` **tag)** `-` **(amount of the move lines with** `-` **tag)**.
+
+'Aggregate Other Formulas' engine
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Use this engine when you need to perform arithmetic operations on the amounts obtained for other
+expressions. Formula can be any expression with `+`, `-`, `/` and `*` operator. To refer to an
+expression, use the code of its **parent line** and its **label** (ex. **CODE.label**).
+
+**Subformulas** can be one of the following:
+
+- **if_above(CUR(amount))**: The value of the arithmetic expression will be returned only if it's
+  greater than the provided bound. Else, the result will be `0`;
+
+- **if_below(CUR(amount))**: The value of the arithmetic expression will be returned only if it's
+  lower than the provided bound. Else, the result will be `0`;
+
+- **if_between(CUR1(amount1), CUR2(amount2))**: The value of the arithmetic expression will be
+  returned only if it's strictly between the provided bounds. Else, it will be brought back to the
+  closest bound.
+
+`CUR` is the currency code in capital letters, and `amount` is the amount of the bound expressed in
+that currency.
+
+You can also use the `cross_report` subformula to match, if your expression refers to an expression
+defined in another report.
+
+'Prefix of Account Codes' engine
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+This engine is used to match amounts made on accounts using the prefixes of these accounts' codes as
+variables in an arithmetic expression.
+
+.. example::
+   | **21 + 10 - 5**
+   | Adds the balances of the move lines made on accounts whose codes start with `21` and `10`, and
+     subtract the balance of the ones on the accounts with the prefix `5`.
+
+It is also possible to ignore a selection of sub-prefixes.
+
+.. example::
+   | **21 + 10\\(101, 102) - 5\\(57)**
+   | Does the same as the previous example, but ignoring the prefixes `101`, `102` and `57`.
+
+You can apply 'sub-filtering' on **credits and debits** using `C` and `D` suffixes. In this case, an
+account will only be considered if its prefix matches, *and* if the total balance of the move lines
+made on this account is **credit/debit**.
+
+.. example::
+   Account `210001` has a balance of -42 and account `210002` has a balance of 25. The formula
+   **21D** only matches the account `210002`, and hence return 25. `210001` is not matched, as its
+   balance is *credit*.
+   
+Prefix exclusions can be mixed with `C` and `D` suffixes.
+
+.. example::
+   **21D + 10\\(101, 102)C - 5\\(57)**
+
+To match the letter `C` or `D` in a prefix and not use it as suffix, use an *empty* exclusion.
+
+.. example::
+   | **21D\\()**
+   | Matches accounts whose code starts with `21D`, regardless of their balance sign.
+
+'External Value' engine
+~~~~~~~~~~~~~~~~~~~~~~~
+
+The 'external value' engine is used to refer to **manual** and **carryover values**. Those values
+are not stored using `account.move.line`, but with `account.report.external.value`. Each of these
+objects directly points to the expression it impacts, so very little needs to be done about their
+selection here.
+
+**Formulas** can be one of the following:
+
+- **sum** : If the result must be the sum of all the external values in the period;
+
+- **most_recent**: If the result must be the value of the latest external value in the period.
+
+In addition, **subformulas** can be used in two ways:
+
+- **rounding=X** : Replacing **'X'** by a number, instructs to round the amount to X decimals;
+
+- **editable** : indicates this expression can be edited manually, triggering the display of an icon
+  in the report, allowing the user to perform this action.
+
+Both subformulas can be mixed, by separating them with a `;`.
+
+.. example::
+   **editable;rounding=2**
+    | Is a correct subformula mixing both behaviors.
+
+'Custom Python Function' engine
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+This engine is a means for developers to introduce custom computation of expressions on a
+case-by-case basis. The formula is the name of a **python function** to call, and the subformula is
+a **key** to fetch in the **dictionary** returned by this function. Use it only if you are making a
+custom module of your own.
+
+Columns
+-------
+
+Reports can have an **indefinite number** of columns to display. Each column gets its values from
+the **expressions** declared on the **lines**. The field :guilabel:`expression_label` of the column
+gives the label of the expressions whose value is displayed. If a line has no **expression** in that
+field, then nothing is displayed for it in this column. If multiple columns are required, you must
+use different **expression** labels.
+
+.. image:: customize/engine-columns.png
+   :align: center
+   :alt: Columns of report.
+
+When using the **period comparison** feature found under :menuselection:`Configuration -->
+Accounting Reports --> (Report you wish to use) --> Options`, all columns are repeated in and for
+each period.

content/applications/finance/accounting/reporting/overview/customize/customize02.png

@@ -375,7 +375,15 @@ You can check the meaning of the fields here:
 * :doc:`/developer/reference/standard_modules/account/account_report`
 * :doc:`/developer/reference/standard_modules/account/account_report_line`
 
-If you gave a `root_report_id` to your report, it is now available in its variant selector. If not, you still need to add a menu item for it. A default menu item can be created from the form view of the report, by clicking on 'Actions', then 'Create Menu Item'. You'll then need to refresh the page to see it. Alternatively, to create a dedicated section for a totally new report in the :guilabel:`Reporting` menu, you need to create a new `ir.ui.menu` record (usually in the main `l10n_XX` module) and a new `ir.actions.client` (usually in the new report xml file) that calls the `account.report` with  the new report id. Then, set the new menu as `parent_id` field in the action model. Example for the Belgian localization:
-
-* `ir.ui.menu record in l10n_be <{GITHUB_PATH}/addons/l10n_be/data/menuitem_data.xml>`_
-* `parent_id field in l10n_be_reports (v16) <https://github.com/odoo/enterprise/blob/a1614d0b1460dc453cbe395efba41573d29e7b7e/l10n_be_reports/data/partner_vat_listing.xml#L55-L65>`_
+If you gave a `root_report_id` to your report, it is now available in its variant selector. If not,
+you still need to add a menu item for it. A default menu item can be created from the form view of
+the report, by clicking on :menuselection:`Actions --> Create Menu Item'. You will then need to
+refresh the page to see it. Alternatively, to create a dedicated section for a totally new report in
+the :guilabel:`Reporting` menu, you need to create a new `ir.ui.menu` record (usually in the main
+`l10n_XX` module) and a new `ir.actions.client` (usually in the new report .XML file) that calls the
+`account.report` with  the new **report id**. Then, set the new menu as `parent_id` field in the
+action model.
+
+.. example ::
+   * `ir.ui.menu creation <{GITHUB_PATH}/addons/l10n_be/data/menuitem_data.xml>`_
+   * `ir.actions.client and menu item creation <{GITHUB_ENT_PATH}/l10n_be_reports/data/partner_vat_listing.xml>`_