Monday, August 14, 2023
7 changes · master
Miscellaneous changes
Add tax computation for Brazil. Just like in the US, taxes in Brazil are highly variable and depend on all sorts of details of the seller, customer and the products being sold. This module provides these details to Avatax and Avatax tells us what taxes we should charge. Depending on `account_avatax` was considered and attempted but resulted in complex code and features that weren't needed, e.g. `avatax_tax_date`, `product.avatax.category` and the concept of committing records. On top
Original PR description
Add tax computation for Brazil. Just like in the US, taxes in Brazil are highly variable and depend on all sorts of details of the seller, customer and the products being sold. This module provides…
Add tax computation for Brazil. Just like in the US, taxes in Brazil are highly variable and depend on all sorts of details of the seller, customer and the products being sold. This module provides these details to Avatax and Avatax tells us what taxes we should charge. Depending on `account_avatax` was considered and attempted but resulted in complex code and features that weren't needed, e.g. `avatax_tax_date`, `product.avatax.category` and the concept of committing records. On top of that some changes needed to be made anyway to the core of `account_avatax`, most importantly having to support price-included taxes and subtracted taxes (negative "price-excluded" taxes). Another major difference is the need to have separate sandbox and production credentials and the fact that this module requires IAP: customer accounts have to be created under Odoo Inc's "master" Avatax account. A separate IAP service will create these "sub-accounts" and proxy the tax calculation requests and perform an IAP charge for each of them. A final difference is that negative lines are not allowed by the Brazilian government, because of this the module will spread these amounts over the positive lines (similar to `l10n_mx_edi`). There's also the concept of "transport" costs which are distributed over lines based on the subtotal. The downside of not inheriting `account_avatax` is duplicated code (~32% more, from 1054 LOC (excl mocked API responses) to 1388 LOC). The goal is to extract the duplicated code to a common module in master. Community PR: https://github.com/odoo/odoo/pull/128216 IAP PR: https://github.com/odoo/iap-apps/pull/610 task-2968770 Alternative approach to #39970 Forward-Port-Of: odoo/enterprise#45223 Forward-Port-Of: odoo/enterprise#43797
*: l10n_din5008_account_followup,l10n_din5008_industry_fsm The DIN5008 layout is mandatory in Germany, Austria and a part of Switzerland. The community module l10n_din5008 implements it but it is currently still not working correctly for (at least) the follow-up report (from account_followup) and the task report (from industry_fsm). This PR makes the DIN5008 layout work for both of the aforementioned reports. The new modules 'l10n_din5008_account_followup' and 'l10n_din5008_industry_fsm'
Original PR description
*: l10n_din5008_account_followup,l10n_din5008_industry_fsm The DIN5008 layout is mandatory in Germany, Austria and a part of Switzerland. The community module l10n_din5008 implements it but it is…
*: l10n_din5008_account_followup,l10n_din5008_industry_fsm The DIN5008 layout is mandatory in Germany, Austria and a part of Switzerland. The community module l10n_din5008 implements it but it is currently still not working correctly for (at least) the follow-up report (from account_followup) and the task report (from industry_fsm). This PR makes the DIN5008 layout work for both of the aforementioned reports. The new modules 'l10n_din5008_account_followup' and 'l10n_din5008_industry_fsm' are added as part of this fix. It also fixes some issues in case the DIN5008 format is not used. 1. The font-size of the salutation is too small. See comparison pictures in https://github.com/odoo/enterprise/pull/44908#issuecomment-1669461467 2. There is an unnecessary address below the document title https://github.com/odoo/enterprise/pull/44908#issuecomment-1669465457 Community PR: https://github.com/odoo/odoo/pull/130337 task-3394263 Forward-Port-Of: odoo/enterprise#45736 Forward-Port-Of: odoo/enterprise#44908
The tour testing css has been removed (see Community PR), so the override is useless now. Forward-Port-Of: odoo/enterprise#45740 Forward-Port-Of: odoo/enterprise#44977
Original PR description
The tour testing css has been removed (see Community PR), so the override is useless now. Forward-Port-Of: odoo/enterprise#45740 Forward-Port-Of: odoo/enterprise#44977
Before these commit when we create quotation and confirm it. we will not be able to see the cancel button on the form. Fix : When we install the bridge module sale_subscription the cancel button gets hide due to that we can't see the cancel button. After doing some changes in sale_subscription we will be able to see the cancel button on the form. task-3433526 Forward-Port-Of: odoo/enterprise#44623
Original PR description
Before these commit when we create quotation and confirm it. we will not be able to see the cancel button on the form. Fix : When we install the bridge module sale_subscription the cancel button gets hide due to that we can't see the cancel button. After doing some changes in sale_subscription we will be able to see the cancel button on the form. task-3433526 Forward-Port-Of: odoo/enterprise#44623
Issue: ------ The `note` field in the form view: Payroll > Configuration > Rule Categories > New does not use the full width of the form. opw-3451106 Forward-Port-Of: odoo/enterprise#45655 Forward-Port-Of: odoo/enterprise#45438
Original PR description
Issue: ------ The `note` field in the form view: Payroll > Configuration > Rule Categories > New does not use the full width of the form. opw-3451106 Forward-Port-Of: odoo/enterprise#45655 Forward-Port-Of: odoo/enterprise#45438
Since shop floor app. The mrp_workorder module is an auto install of mrp and not trigger by the setting of work orders anymore. Also the mrp_workorder contains now the shop floor application. The shop floor app doesn't require the workorder and could be use for simple use case with only production orders mrp_workorder should be rename mrp_enterprise in a future work. Currently since the workorders are not related to the module, we remove it from the demo data Forward-Port-Of: odoo/enterpr
Original PR description
Since shop floor app. The mrp_workorder module is an auto install of mrp and not trigger by the setting of work orders anymore. Also the mrp_workorder contains now the shop floor application. The shop floor app doesn't require the workorder and could be use for simple use case with only production orders mrp_workorder should be rename mrp_enterprise in a future work. Currently since the workorders are not related to the module, we remove it from the demo data Forward-Port-Of: odoo/enterprise#44492
Steps to reproduce: 1. Install l10n_co_edi 2. configure co localization: https://drive.google.com/file/d/10Y6rTEg14kOMXS_yqZfLrBhOFXM2d3y0/view 3. Create a Vendor Bill with any product, with an amount of "0.00" 4. traceback Issue: according to https://www.odoo.com/web#id=2985449&cids=1&menu_id=5879&action=333&active_id=5645&model=project.task&view_type=form it's not possible to have lines with "0" in invoices. It is also the same for `Doc soporte` Fix: create a validation error for
Original PR description
Steps to reproduce: 1. Install l10n_co_edi 2. configure co localization: https://drive.google.com/file/d/10Y6rTEg14kOMXS_yqZfLrBhOFXM2d3y0/view 3. Create a Vendor Bill with any product, with an amount of "0.00" 4. traceback Issue: according to https://www.odoo.com/web#id=2985449&cids=1&menu_id=5879&action=333&active_id=5645&model=project.task&view_type=form it's not possible to have lines with "0" in invoices. It is also the same for `Doc soporte` Fix: create a validation error for this case opw-3442071 Forward-Port-Of: odoo/enterprise#45168