UPS package types are now renamed so users can clearly tell the standard UPS carrier option apart from the legacy UPS option when grouping by carrier. This reduces confusion during package type selection and helps teams choose the correct UPS configuration.

Steps to reproduce:
- open package type and group by carrier
- No way to distinguish rest and legacy ups

Fix:
rename package type to match carrier and distinguish it from rest ups

opw-3911171

This cleanup removes an obsolete internal option from several document extraction areas because it is no longer used. It has no expected impact on day-to-day users, but it simplifies maintenance and reduces unnecessary code paths.

Since commit d225e77, this parameter is unused.

This draft updates the underlying make-to-stock order flow to align with related changes in the main Odoo platform. The work appears focused on restructuring internal behavior rather than introducing a finished business-facing feature, so visible impact may be limited until the draft is completed.

DRAFT

Before, if a bank transaction contain the sale order reference, the reconciliation model will try to reconcile with the invoices created from this sale order but ignore the payment records for those. This leads to situations where it looks like there were two payments on the invoices (one payment record and one bank transaction) while there is just one partial payment. Steps to reproduce: 0/ Have default reconciliation models 1/ Create SO for 100$ and confirm invoice 2/ Partially pay invoi

Before, if a bank transaction contain the sale order reference, the reconciliation model will try to reconcile with the invoices created from this sale order but ignore the payment records for those. This leads to situations where it looks like there were two payments on the invoices (one payment record and one bank transaction) while there is just one partial payment.

Steps to reproduce:
0/ Have default reconciliation models
1/ Create SO for 100$ and confirm invoice
2/ Partially pay invoice for 70$
3/ Create bank transaction with SO ref and same partner for 70$
4/ Match transaction => will match the 30$ residual of the invoice instead of 70$ payment

Now, the system will try to reconcile with the payments of those invoices first before considering invoice reconciliation.

opw-3904177

Forward-Port-Of: odoo/enterprise#62972

In the Payroll app with a Belgian company, we can do Reporting > Paid Time Off Allocation. This opens a wizard and if we filled the department then the time off type, the app would crash because of a terrible sql query. Also, the query was doing unnecessary subqueries that have been removed. Task: 3878904 Forward-Port-Of: odoo/enterprise#62293

In the Payroll app with a Belgian company, we can do Reporting > Paid Time Off Allocation.
This opens a wizard and if we filled the department then the time off type, the app would crash because of a terrible sql query.

Also, the query was doing unnecessary subqueries that have been removed.

Task: 3878904

Forward-Port-Of: odoo/enterprise#62293

The aim of this commit is to make the code more robust and defensive by handling a bad value for the `vat` field. Context: Partners having a `partner.vat=False` were making the compact function crash. Before the commit: The flow crash even if the value shouldn't be processed. After the commit: The flow is smooth. task-id: None Forward-Port-Of: odoo/enterprise#63865

The aim of this commit is to make the code more robust and defensive by handling a bad value for the `vat` field.

Context:
Partners having a `partner.vat=False` were making the compact function crash.

Before the commit:
The flow crash even if the value shouldn't be processed.

After the commit:
The flow is smooth.

task-id: None

Forward-Port-Of: odoo/enterprise#63865

This will add tracking to some employee field that have an impact on withholding taxes. Task: 3879035 Forward-Port-Of: odoo/enterprise#61315

This will add tracking to some employee field that have an impact on withholding taxes.

Task: 3879035

Forward-Port-Of: odoo/enterprise#61315

In the form view, new line were linked to new_id which computed the subscription_state value to a wrong version. Forcing readonly=False ensure the value is fetched from the origin and thus correct when computing the discount. task-id: 3699064 Forward-Port-Of: odoo/enterprise#58604

In the form view, new line were linked to new_id which computed the subscription_state value to a wrong version.

Forcing readonly=False ensure the value is fetched from the origin and thus correct when computing the discount.

task-id: 3699064

Forward-Port-Of: odoo/enterprise#58604

Before this commit, when adding an outdated activity from kanban activity widget, it crashed with the following errors: `TypeError: cannot read property of undefined (reading `mail_template_ids`)` `TypeError: Cannot read properties of undefined (reading 'toLocaleString')` Steps to reproduce: - on crm lead schedule call activity and make sure that activity is at least 1 month old - book activity and save it - try to access/edit activity This happens because when the `get_today_call_a

Before this commit, when adding an outdated activity from kanban activity widget, it crashed with the following errors:

`TypeError: cannot read property of undefined (reading `mail_template_ids`)`
`TypeError: Cannot read properties of undefined (reading 'toLocaleString')`

Steps to reproduce:
- on crm lead schedule call activity and make sure that activity is at least 1 month old
- book activity and save it
- try to access/edit activity

This happens because when the `get_today_call_activities` function is called. Function fetches fields during the records formatting, but it doesn't fetch `date_deadline` and `mail_template_ids`, therefore those fields remain undefined, hence the errors rise.

task-3945492

Forward-Port-Of: odoo/enterprise#63792

In the salary configurator, we use a meal voucher amount by default: 7 .45€/worked day. It should really copy the meal voucher amount from the contract instead. Task: Forward-Port-Of: odoo/enterprise#63851 Forward-Port-Of: odoo/enterprise#61655

In the salary configurator, we use a meal voucher amount by default: 7 .45€/worked day.
It should really copy the meal voucher amount from the contract instead.

Task:

Forward-Port-Of: odoo/enterprise#63851
Forward-Port-Of: odoo/enterprise#61655

Steps to reproduce: - Install sign - Add two document to sign for the Marc Demo - Sign in as Marc Demo - Go to the sign app and sign both documents Issues: There's no button to close the dialog box, you are forced to close the window. opw-3847269 Forward-Port-Of: odoo/enterprise#63671 Forward-Port-Of: odoo/enterprise#61380

Steps to reproduce:
- Install sign
- Add two document to sign for the Marc Demo
- Sign in as Marc Demo
- Go to the sign app and sign both documents

Issues:
There's no button to close the dialog box, you are forced to close the window.

opw-3847269

Forward-Port-Of: odoo/enterprise#63671
Forward-Port-Of: odoo/enterprise#61380

The issue: When importing a FEC file, the created COAs lack correct translation for languages other than English. This discrepancy arises because the xml_id generated during COA creation does not match the xml_id produced by the _load_translations function. The new COAs' xml_id is a composite of the module ('l10n_fr_fec_import' in this case), company ID, prefix ('account' in this case), and a key derived from the account number code in the CSV file (not Odoo's default code). Consequently, when

The issue:
When importing a FEC file, the created COAs lack correct translation for languages other than English. This discrepancy arises because the xml_id generated during COA creation does not match the xml_id produced by the _load_translations function. The new COAs' xml_id is a composite of the module ('l10n_fr_fec_import' in this case), company ID, prefix ('account' in this case), and a key derived from the account number code in the CSV file (not Odoo's default code). Consequently, when calling the _load_translations function, it attempts to update translations using a different xml_id, causing failure in locating records.

The fix:
Include the template_data, if available, during COA translation, as it is more efficient than loading and parsing the entire CSV file. This template data already contains the necessary information, including the correct xml_id. Additionally, introduce a key 'is_xml_generated' in the context to prevent the generation of an incorrect xml_id.

Community PR: https://github.com/odoo/odoo/pull/152090

opw-3646861

Forward-Port-Of: odoo/enterprise#55537

Fix "Buisness" and "Busoness" typo in the account view form. related PR: odoo/enterprise#54483 Task-3973541 Forward-Port-Of: odoo/enterprise#63896

Fix "Buisness" and "Busoness" typo in the account view form.

related PR: odoo/enterprise#54483

Task-3973541

Forward-Port-Of: odoo/enterprise#63896

Steps to reproduce: 1. Install the planning module and open it. 2. Open events in calendar view. 3. Click on any event. 4. In the calendar popover, observe the spacing around the percentage (%). Issue: There is inconsistency in spacing around the percentage (%). Solution: Add a space before the percentage and remove the space after it in the common calendar popover. task-3908815 Forward-Port-Of: odoo/enterprise#62083

Steps to reproduce:
1. Install the planning module and open it.
2. Open events in calendar view.
3. Click on any event.
4. In the calendar popover, observe the spacing around the percentage (%).

Issue:
There is inconsistency in spacing around the percentage (%).

Solution:
Add a space before the percentage and remove the space after it in the common calendar popover.

task-3908815

Forward-Port-Of: odoo/enterprise#62083