Description of the issue/feature this PR addresses: When the current user is the system user, which happens during install and upgrades, the env company is possibly not included with the companies given to `_get_query_currency_table`, this can lead to a KeyError when [fetching the rate ](https://github.com/odoo/odoo/blob/2130b3bbe627d97b41bbb9a93ff407c2990560a3/addons/account/models/res_currency.py#L65)for said company. Current behavior before PR: Steps to reproduce: - Create company 2 w

Description of the issue/feature this PR addresses:

When the current user is the system user, which happens during install and upgrades, the env company is possibly not included with the companies given to `_get_query_currency_table`, this can lead to a KeyError when [fetching the rate ](https://github.com/odoo/odoo/blob/2130b3bbe627d97b41bbb9a93ff407c2990560a3/addons/account/models/res_currency.py#L65)for said company.

Current behavior before PR:
Steps to reproduce:
- Create company 2 with a currency different than the original company
- Deactivate the original company
- Install module Purchase (or another module that uses `_get_query_currency_table`)
- failure

Same behavior on upgrade if purchase is already installed and the company linked to the system user is deactivated and has a different currency than the active companies.

Desired behavior after PR is merged:



---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#171605

[FIX] l10n_bd: Fix tax report name There is an issue with the name of the tax report, '(BD)' in the name is duplicate. So, Fixed it in this task task-id#3974212 enterprise-pr#https://github.com/odoo/enterprise/pull/66236 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#172254

[FIX] l10n_bd: Fix tax report name

There is an issue with the name of the tax report, '(BD)' in the name is duplicate. So, Fixed it in this task

task-id#3974212

enterprise-pr#https://github.com/odoo/enterprise/pull/66236

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#172254

When a menu link is defined towards an anchor, the scroll effect of the browser does not trigger from within the translated pages where the URL contains the additional path element about the used locale. This scrolling is achieved by the browser itself, it is not related to `scroller_service.js`. The URL is not transformed by `website.menu`'s `clean_url` method. The language is added in `ir.http`'s `url_lang` method, but we cannot always know the current URL at that point, nor during the tem

When a menu link is defined towards an anchor, the scroll effect of the browser does not trigger from within the translated pages where the URL contains the additional path element about the used locale.

This scrolling is achieved by the browser itself, it is not related to `scroller_service.js`.
The URL is not transformed by `website.menu`'s `clean_url` method. The language is added in `ir.http`'s `url_lang` method, but we cannot always know the current URL at that point, nor during the template rendering - making it impossible to determine if the rendered anchor is local.

This commit solves this client-side by replacing link's `href` values with their anchor only whenever they are targeting the current page.

Steps to reproduce:
- Install a second language on the website.
- Put some content in the Home page so that the bottom section requires scrolling to be seen.
- Add a menu element that targets `#bottom`.
- Either be a visitor or a connected user.
- Go to the default language Home page.
- Click on the new link. => Page scrolls to the bottom.
- Switch to the second language Home page.
- Click on the new link.

=> Page reloads targeting the bottom instead of scrolling.

opw-3956066

Forward-Port-Of: odoo/odoo#176077
Forward-Port-Of: odoo/odoo#169944

Since [1] cover images are implicitly converted to webp. An issue was fixed in [2] because the converted image attachments were not public. This commit fixes another issue: if the cover's record name contains a slash inside its name, the name of the attachment also contains that slash. `_compute_image_src` then puts that slash inside `image_src` which is used to reference the converted image from the website page. But the route does not support delivering such paths. Steps to reproduce: -

Since [1] cover images are implicitly converted to webp. An issue was fixed in [2] because the converted image attachments were not public.

This commit fixes another issue: if the cover's record name contains a slash inside its name, the name of the attachment also contains that slash. `_compute_image_src` then puts that slash inside `image_src` which is used to reference the converted image from the website page. But the route does not support delivering such paths.

Steps to reproduce:
- Create a new blog post.
- Name it "A/B Testing".
- Upload a JPG image as cover.
- Save.

=> The image was not displayed anymore.

[1]: https://github.com/odoo/odoo/commit/068dcc27e417d52b51d274c44497f4388fed780a
[2]: https://github.com/odoo/odoo/commit/715eb84a35d27fdbb378fd9937d7439f8619f99c

opw-4042913
opw-4047244
opw-4086947

Forward-Port-Of: odoo/odoo#175678
Forward-Port-Of: odoo/odoo#175630

On the general ledger and trial balance, the branch company needs to get access to the parent unaffected earning account. Also if a company and a branch is selected, we need to sum the moves on the unaffected earnings account. opw-3937063 Forward-Port-Of: odoo/enterprise#67534

On the general ledger and trial balance, the branch company needs to get access to the parent unaffected earning account.

Also if a company and a branch is selected, we need to sum the moves on the unaffected earnings account.

opw-3937063

Forward-Port-Of: odoo/enterprise#67534

[ADD] l10n_bd_reports: Create corporate tax report * Create new account tags * Create new corporate report * Create new fields in the settings to allow the user specifying accounts that should be used in the accounting entry * Create custom accounting entry button to create a move with the accounts specified by the user with amounts specified in the 'corporate tax amount' line in the corporate tax report NOTE: there is an issue with the name of the tax report, '(BD)' in the name is dupl

[ADD] l10n_bd_reports: Create corporate tax report

* Create new account tags
* Create new corporate report
* Create new fields in the settings to allow the user specifying accounts that should be used in the accounting entry
* Create custom accounting entry button to create a move with the accounts specified by the user with amounts specified in the 'corporate tax amount' line in the corporate tax report

NOTE: there is an issue with the name of the tax report, '(BD)' in the name is duplicate. So, Fixed it in this pr

task-id#3974212

odoo-pr#https://github.com/odoo/odoo/pull/172254

Forward-Port-Of: odoo/enterprise#66236

We want to provide more flexibility to the user that instead of ODOO/pin/1 they did Odoo/pin/1 or odoo/Pin/1 as the serial number, we will still accept it. Because, while copying, you do not necessarily pay attention to capital letters or not. Forward-Port-Of: odoo/enterprise#68222

We want to provide more flexibility to the user that instead of ODOO/pin/1 they did Odoo/pin/1 or odoo/Pin/1 as the serial number, we will still accept it.  Because, while copying, you do not necessarily pay attention to capital letters or not.

Forward-Port-Of: odoo/enterprise#68222

Before this commit: Having a quality control point using "Print label" with an IoT printer will not print anything and download the file. This happened due to the JS function `iotReportActionHandler` ignoring the device sent as it expected it to be a list, see: https://github.com/odoo/enterprise/blob/1412cd3edc6005b05d43d42828e6647ee58594ae/iot/static/src/iot_report_action.js#L21 Therefore, defaulting to the behavior of downloading the file After this commit: Print the label automa

Before this commit:
 Having a quality control point using "Print label" with an IoT printer will not print anything and download the file.
 This happened due to the JS function `iotReportActionHandler` ignoring the device sent as it expected it to be a list, see:
 https://github.com/odoo/enterprise/blob/1412cd3edc6005b05d43d42828e6647ee58594ae/iot/static/src/iot_report_action.js#L21
  Therefore, defaulting to the behavior of downloading the file

After this commit:
 Print the label automatically to the IoT like expected

opw-4032741,4017327,3895056

Forward-Port-Of: odoo/enterprise#68194
Forward-Port-Of: odoo/enterprise#68100

Version: 17.0+ Current Behavior: Peppol fields are automatically populated based on the `vat` field of the res.partner record. With l10n_mx localization installed the `vat` field is based on the first two letters of the first name and the first letter of the last name. However, the peppol fields with be automatically computed if the first two letters are similar to country codes. Purpose of this PR: This PR overrides the peppol computation so that the peppol fields are emptied when l10n_

Version: 17.0+

Current Behavior:
Peppol fields are automatically populated based on the `vat` field of the res.partner record. With l10n_mx localization installed the `vat` field is based on the first two letters of the first name and the first letter of the last name. However, the peppol fields with be automatically computed if the first two letters are similar to country codes.

Purpose of this PR:
This PR overrides the peppol computation so that the peppol fields are emptied when l10n_mx_edi is installed. These fields are unused in l10n_mx localization so they can be omitted.

Steps to Reproduce on Runbot:
1) Install accounting and contacts
2) Create a contact with l10n_mx vat format (i.e. ESPN0101011E2) 
3) Navigate to the Accounting Tab of the partner record and find that the peppol fields are filled.

Notes:
In the current behavior, the user will have to manually empty the peppol fields to avoid receiving the error of incorrect peppol format.

opw-4074094

Forward-Port-Of: odoo/enterprise#67737