The Manufacturing Maintenance module now uses the correct plural form, “equipment,” instead of “equipments” in labels and demo data. This improves consistency and professionalism in user-facing text without changing functionality.

Modules:
	- mpr_maintenance.

The plural of "equipment" is "equipment" and not "equipments"

Changes in the community version: https://github.com/odoo/odoo/pull/100558

opw-2981186

HR officers are no longer sent to the employee-facing thank-you page after completing salary contract actions. This makes the workflow clearer for HR users and avoids showing them a confirmation page intended for employees.

The HR officer were redirected to the same `Thank You` page as the employee, which didn't make lot of sense.

task-2941760

The VoIP systray item has been reworked to use Odoo's newer internal model structure. This should make the calling menu easier to maintain and more consistent, with no major change expected for end users.

Task-3036700.

This change adds automated checks to ensure barcode-created inventory records are not removed just because their counted quantity is set to zero. It helps preserve inventory audit accuracy and prevents unexpected data loss during barcode inventory operations.

Following odoo/odoo@c085a51d285f7cd143d1a4b574646e4be40b4bd9
Adds a test/tour to check when a quant is created in the barcode inventory, it will not be automatically unlinked even if it has a inventory quantity to 0.

This fixes a flaky automated test in the barcode inventory workflow that could fail randomly because of timing conflicts. It helps keep validation of inventory adjustment behavior stable and reduces noise for teams maintaining the product.

Makes a change in `test_inventory_adjustment_tracked_product` test tour to avoid concurrency error.

This fixes compatibility in the German POS restaurant certification module after a related change in the core POS system. It helps ensure draft table orders continue to work correctly for German certified POS setups.

Adapting parameters of the get_table_draft_order method to match the
changes in the community version.

Related PR: https://github.com/odoo/odoo/pull/100353

This update restores missing report actions in accounting ledgers, fixes report export behavior, and improves report totals so users can access the right records and get more accurate outputs. It also removes obsolete interface code and improves spreadsheet filter handling, reducing maintenance risk while keeping key business workflows working as expected.

The Barcode app and related manufacturing barcode screens were updated to use Odoo's newer interface technology, improving maintainability and consistency. The change also includes minor fixes for inventory adjustment saving and page navigation after editing quantities.

The Owl library bumped to a v2.0.1 now correctly throw an error for duplicate object t-keys. So this commit fixes bad t-key usage in templates. Commumity pull request: odoo/odoo#103735 Forward-Port-Of: odoo/enterprise#33091 Forward-Port-Of: odoo/enterprise#33067

The Owl library bumped to a v2.0.1
now correctly throw an error for duplicate object t-keys.

So this commit fixes bad t-key usage in templates.

Commumity pull request: odoo/odoo#103735

Forward-Port-Of: odoo/enterprise#33091
Forward-Port-Of: odoo/enterprise#33067

It seems some banks are refusing SEPA Credit Transfer files because the element EndToEndId is starting with a whitespace. This can happen depending of the full name of the company which is used and is trimmed to 30 characters. opw-3012901 Forward-Port-Of: odoo/enterprise#32907

It seems some banks are refusing SEPA Credit Transfer files because the element EndToEndId is starting with a whitespace. This can happen depending of the full name of the company which is used and is trimmed to 30 characters.

opw-3012901

Forward-Port-Of: odoo/enterprise#32907

Currently, we are using computed field partner.contact_address to fill in AddrLine element in SDD XML files. However, the company name is included by default, which is not necessary since the company name is already present in Nm Element just above. We should display the address without the company name instead. Before this commit: ``` <Dbtr> <Nm>Azure Interior</Nm> <PstlAdr> <Ctry>US</Ctry> <AdrLine>Azure Interior 4557 De Silva St Fr

Currently, we are using computed field partner.contact_address to fill in AddrLine element in SDD XML files. However, the company name is included by default, which is not necessary since the company name is already present in Nm Element just above. We should display the address without the company name instead.

Before this commit:
```
        <Dbtr>
          <Nm>Azure Interior</Nm>
          <PstlAdr>
            <Ctry>US</Ctry>
            <AdrLine>Azure Interior 4557 De Silva St  Fremont CA 94538 United States</AdrLine>
          </PstlAdr>
        </Dbtr>
```

After this commit:
```
        <Dbtr>
          <Nm>Azure Interior</Nm>
          <PstlAdr>
            <Ctry>US</Ctry>
            <AdrLine>4557 De Silva St  Fremont CA 94538 United States</AdrLine>
          </PstlAdr>
        </Dbtr>
```

opw-3008901

Forward-Port-Of: odoo/enterprise#32761

If we have time off that goes over two months, from 1/28/2022 to 2/3/2022, the only part that is the first month should be defered, thus from 1/28/2022 to 1/31/2022. task - 2997820 Forward-Port-Of: odoo/enterprise#32472

If we have time off that goes over two months, from 1/28/2022 to 2/3/2022, the only part that is the first month should be defered, thus from 1/28/2022 to 1/31/2022.

task - 2997820

Forward-Port-Of: odoo/enterprise#32472

The partner will now be created even when no Partner Autocomplete credits are available. Forward-Port-Of: odoo/enterprise#33032 Forward-Port-Of: odoo/enterprise#32993

The partner will now be created even when no Partner Autocomplete credits are available.

Forward-Port-Of: odoo/enterprise#33032
Forward-Port-Of: odoo/enterprise#32993

Refused leaves were still showing in the leaves to defer, even though they don't need to be deferred. task-3010061 Forward-Port-Of: odoo/enterprise#32894

Refused leaves were still showing in the leaves to defer, even though they don't need to be deferred.

task-3010061

Forward-Port-Of: odoo/enterprise#32894

Steps : Go to Timsheet. In grid view, press play button and add a project. Go to list view and check the newly created line. Issue : You can't pause the timer. Cause : On top of the conditions that display_timer is true and the record is not selected, another condition means to check that the field is not readonly, in which case it would make sens to not display the button. Yet, on one hand, this widget is never used for readonly fields and, on the other hand, record.isReadonly(fieldN

Steps :
Go to Timsheet.
In grid view, press play button and add a project. Go to list view and check the newly created line.

Issue :
You can't pause the timer.

Cause :
On top of the conditions that display_timer is true and the record is not selected,
another condition means to check that the field is not readonly, in which case it would make sens to not display the button. Yet, on one hand, this widget is never used for readonly fields and, on the other hand, record.isReadonly(fieldName) returns true when the timer is running.

Fix :
Rework these conditions:
display_timer still has to be true
the line isn't selected and/or the timer is running.

task-3037181

Forward-Port-Of: odoo/enterprise#33042

Fix the colspan for the account_online_account_ids field in the online synchronization form view, so that it takes the whole width as expected. Forward-Port-Of: odoo/enterprise#33039

Fix the colspan for the account_online_account_ids field in the online synchronization form view, so that it takes the whole width as expected.

Forward-Port-Of: odoo/enterprise#33039

Use the new routes for IAP extract. The new routes start with "/api/extract/". task-2886665 Forward-Port-Of: odoo/enterprise#32939

Use the new routes for IAP extract. The new routes start with "/api/extract/".

task-2886665

Forward-Port-Of: odoo/enterprise#32939

Like already done for the account_invoice_extract (task-2416741) and hr_recruitment_extract, the client will now send a webhook URL as part of the request that the extraction server will call once the results are ready. task-2886616 Related server-side task: 2452019 Forward-Port-Of: odoo/enterprise#32918

Like already done for the account_invoice_extract (task-2416741) and hr_recruitment_extract, the client will now send a webhook URL as part of the request that the extraction server will call once the results are ready.

task-2886616

Related server-side task: 2452019

Forward-Port-Of: odoo/enterprise#32918

Fix multiple bugs in the Accounts Coverage Report: 1. Currently if two expressions use the same accounts but on different date scopes, a false warning will be triggered as they appear as duplicated. For example, this is often the case when we have a line "Previous Years Profit" in the Balance Sheet that cross references the value of the Profit & Loss report. These two duplicated expressions will match the same accounts, however they will have different date scope resulting in a false warn

Fix multiple bugs in the Accounts Coverage Report:

1.
Currently if two expressions use the same accounts but on different date scopes, a false warning will be triggered as they appear as duplicated.

For example, this is often the case when we have a line "Previous Years Profit" in the Balance Sheet that cross references the value of the Profit & Loss report. These two duplicated expressions will match the same accounts, however they will have different date scope resulting in a false warning.

To fix this, we add a condition based on the date_scope before marking lines as candidate duplicates.

2.
Same as 1. but for subformula

3.
The excluded account codes were not correctly matched with a wildcard.
I.e. `['!', ('code', '=like', '1%')]` should be used instead of `[('code', 'not like', '1%')]`

4.
The following domain would crash
`['&', ('debit', '>', 0.0), ('account_id.code', '=like', '2679%')]`
This is because we skip tuples that do not target the `account_id`.
However if the tuple is precedeed by an unary operator, we must also skip it, otherwise we would have an incorrect domain.

5.
Fix a missing unpack star for the common domain for other reports than the BS or P&L

Forward-Port-Of: odoo/enterprise#32821

Forward-Port-Of: odoo/enterprise#32985 Forward-Port-Of: odoo/enterprise#32946

Forward-Port-Of: odoo/enterprise#32985
Forward-Port-Of: odoo/enterprise#32946

Originally, there's up to 3 vertically nested and 1 horizontal scrollbars around the worksheet displayed in the tablet view. https://drive.google.com/file/d/1rOqM8Lfaq8nd4msqoXgQl5ZsUF4Cgfiz/view?usp=sharing **The outer vertical scrollbar was due to an overflow:auto on the div with class `o_tablet_document` :** > This overflow only allow to scroll under the worksheet, where there's nothing to display,except a little margin, so it doesn't hurt anything to set it to hidden. **One vertical

Originally, there's up to 3 vertically nested and 1 horizontal scrollbars around the worksheet displayed in the tablet view.
https://drive.google.com/file/d/1rOqM8Lfaq8nd4msqoXgQl5ZsUF4Cgfiz/view?usp=sharing
**The outer vertical scrollbar was due to an overflow:auto on the div with class `o_tablet_document` :**

> This overflow only allow to scroll under the worksheet, where there's nothing to display,except a little margin, so it doesn't hurt anything to set it to hidden.

**One vertical and the horizontal scrollbar were due to the forced margin of -2.5em applied on each side of the `#mainContainer` of the `PdfViewerField` :**

> This negative margin is intended to recover the place taken by the hidden toolbar to maximize the space available for the worksheet.
> However, when applied on each side of the `#maincontainer`, its width overflow the parent width, leading to an horizontal scrollbar which in turn leads to a vertical scrollbar.
> As the hidden toolbar only take place on the top, we restrict the margin to this side.

**The last vertical scrollbar remaining is totally normal and needed to browse the worksheet** 
Task:2985735

Forward-Port-Of: odoo/enterprise#32991

Field `recurring_next_date` on `sale.order` has been replaced with `next_invoice_date`, but some sms templates did not reflect this change. https://github.com/odoo/enterprise/commit/8fe6c96558bc9fb9f3655fa52fcbea3fea38afdd Forward-Port-Of: odoo/enterprise#32792

Field `recurring_next_date` on `sale.order` has been replaced with `next_invoice_date`, but some sms templates did not reflect this change.

https://github.com/odoo/enterprise/commit/8fe6c96558bc9fb9f3655fa52fcbea3fea38afdd

Forward-Port-Of: odoo/enterprise#32792

Steps to reproduce: - create a vendor bill; - realize a payment with a larger amount; - reconcile manually the both using an account with 0% tax. Issue: In journal items, the amount of tax (and therefore the corresponding write-off) is not equal to zero. Cause: When we prepare the move line for the manual reconciliation, we don't detect if the value of the tax is zero percent. Solution: Check that we are in the case of a 0% tax and if so, don't create a move line

Steps to reproduce:
   - create a vendor bill;
   - realize a payment with a larger amount;
   - reconcile manually the both using an account with 0% tax.

Issue:
   In journal items, the amount of tax (and therefore the corresponding write-off) is not equal to zero.

Cause:
   When we prepare the move line for the manual reconciliation, we don't detect if the value of the tax is zero percent.

Solution:
   Check that we are in the case of a 0% tax and if so, don't create a move line.

opw-2990051

Forward-Port-Of: odoo/enterprise#32002

Originally, if there's a worksheet but no step set on an operation, the worksheet is not displayed in the tablet view. Even if the `get worksheetData()` method in tablet.js is made to handle the case where there's no step, it was never called from the xml as it was required to have a step there. The DocumentViewer block is moved in parent to solve this issue, however, as we don't want to show the DocumentViewer in same time as the SummaryStep, the display condition in the xml evolve a little

Originally, if there's a worksheet but no step set on an operation, the worksheet is not displayed in the tablet view. 
Even if the `get worksheetData()` method in tablet.js is made to handle the case where there's no step, it was never called from the xml as it was required to have a step there. 
The DocumentViewer block is moved in parent to solve this issue, however, as we don't want to show the DocumentViewer in same time as the SummaryStep, the display condition in the xml evolve a little.

Task: 2985735

Forward-Port-Of: odoo/enterprise#33001

Remove the "employee_cost" and the "total cost" fields from the Work Order form view displayed when the associated Work Center has the option "Requires Log In" (allow_employee) set to True. Task : 2985735 Forward-Port-Of: odoo/enterprise#32956

Remove the "employee_cost" and the "total cost" fields from the Work Order form view displayed when the associated Work Center has the option "Requires Log In" (allow_employee) set to True.
Task : 2985735

Forward-Port-Of: odoo/enterprise#32956

Following commit c3ff4851eb4f2ea79887d50f938e6bec72117581 no gift message was shown anymore. task-3035037 Forward-Port-Of: odoo/enterprise#32987

Following commit c3ff4851eb4f2ea79887d50f938e6bec72117581 no gift message was shown anymore.

task-3035037

Forward-Port-Of: odoo/enterprise#32987

Forward-Port-Of: odoo/enterprise#32515

Forward-Port-Of: odoo/enterprise#32515

Due to a bad syntax, changing of step in the workorder tablet view didn't update the page of the worksheet. "this.props.resField" is now replace by its value rather than being written as is. Task:2985735 Forward-Port-Of: odoo/enterprise#32986

Due to a bad syntax, changing of step in the workorder tablet view didn't update the page of the worksheet. 
"this.props.resField" is now replace by its value rather than being written as is.
Task:2985735

Forward-Port-Of: odoo/enterprise#32986