Monday, November 2, 2020
3 changes · master
Enhancements to existing features
Duplicating accounting journals now creates safer, company-unique journal codes instead of risking duplicate codes. This helps prevent duplicate accounting entry names and makes journal copying more reliable for finance teams.
Original PR description
Before that, even though the code contained something about it, the duplication of account.journal objects handled their code field pretty poorly (as it was trimmed to 5 characters), leading to situations where journals could have the same code, leading to possibility for account moves to have the same name. This commit improves the SQL constraint testing journal codes so that they must now be unique per company. We also recompute the code in a more advanced way so that journal duplications works as smoothly as possible. Task 2346404
The partner commission test setup now uses a unique journal code to align with updated accounting validation rules. This keeps automated checks reliable and helps prevent false failures during ongoing development.
Original PR description
Following the changes introduced by https://github.com/odoo/odoo/pull/59791 for task 2346404. This journal code was already used elsewhere in the tests, so we simply replace it by a unique one.
The module description now clarifies when landed costs can be applied in Mexican electronic invoicing workflows. This helps users understand that landed costs require FIFO or AVCO costing and automated inventory valuation before setup or use.
Original PR description
Landed costs can only be applied to products with a FIFO or AVCO costing methods and an automated inventory valuation.