**Problem:**
when the product in the sale order linked to a field service task is a kit and the task is marked as done, the delivery is not validate (as it would for a non kit product)

**Steps to reproduce:**
- Create a product and set up a Kit-type Bill of Materials for it (with at least two components)
- Create a service-type product.
- Set the Invoicing Policy to Prepaid/Fixed
- set the "create on order" field to Task
- assign the Project to Field Service.
- Create a Sales Order using the service product.
- Confirm the Sales Order.
- In the linked task, click on the Products smart button
- add the kit-type product from step 1.
- Mark the task as done.

**Current behavior:**
On the sale order, the delivered quantity for the kit product is 0.
If you click on the delivery smart button, you'll see that the picking is not validated yet

**Expected behavior:**
the picking should be validated

**Cause of the issue:**
https://github.com/odoo/enterprise/blob/d8dc0cabd83a29d0522cb5fd25c6956968d4408b/industry_fsm_stock/models/project_task.py#L23 the orer_line is considered as an exception because the order_line product_uom_qty is smaller than total_qty (the sum of the move_ids' product_uom_qty)
But this is normal in the case of a kit

opw-4848444

Forward-Port-Of: odoo/enterprise#89616
Forward-Port-Of: odoo/enterprise#88363

**Step to reprocduce :**
1. Install sale_project module
2. Create a product
        - type: Service
        - Invoice policy: based on the milestones
        - Create on order: Project & Task.
3. Create a sale order with that product and add two SO lines with different descriptions.
4. Confirm the sale order.
5. Click on the Tasks smart button in the sale order to open the generated tasks.
6. From one of the tasks (e.g., m1)
7. Manually remove the existing milestone and sales order item from the task.
8. Then assign a different milestone (e.g., m2) to the task.
9. The sale order item set different (e.g., m1) instead of the newly set milestone.

**Issue:**

When a task has its `milestone_id` and `sale_line_id` manually cleared, and a new milestone
is later assigned, the task does not get the correct Sales Order Item.

**Cause:**
In the `_compute_sale_line` method, the logic priority the parent task and project when
computing the `sale_line_id`, and only uses the `milestone_id.sale_line_id` as a fallback.

https://github.com/odoo/odoo/blob/259f7eafb15882807640a00cf6939129f27c8fbb/addons/sale_project/models/project_task.py#L109-L113

**Solution :** 

To fix this `_compute_sale_line` method to priority the milestone's `sale_line_id` 
when a milestone is explicitly set. This ensures that if the task’s milestone 
changes, its sale line reflects the one from the milestone, even for subtasks.

opw-4701106

The "show warning when bus connection encounters issues" test simulates a disconnected WebSocket that fails to reconnect. In this scenario, an alert is shown to warn the user that some features may be unavailable or slow.

However, the websocket worker’s initial reconnect delay is 1.5s, with an added random jitter up to 1 second which means the first reconnect attempt can take up to 2.5s.

The test waits up to 2.5s for the alert to show, which is not always enough. The reconnect attempt alone may be that long, and under high CPU load, processing the resulting event can take even longer.

This commit reduces the initial reconnect delay and the jitter during this test, ensuring that the reconnect attempt fails and the alert is shown within the expected time.

fixes runbot-226443

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

Steps to reproduce
------------------
1. Create a Sales Order, add a product with QTY = X
2. Open PoS
3. Load this same Sales order (by clicking "Settle the order"-> QTX is
   X as expected
4. Return to Sales order (in the sales app)
5. Edit QTY from X to Y and save
6. Go back to PoS
7. Delete the laoded Sales Order and load it again
   -> Notice that QTY is still X and not the updated Y!!

Other Flow in frontend
----------------------
1. Create a Sales Order, add a product with QTY = X
2. Open PoS
3. Load this same Sales order (by clicking "Settle the order"-> QTY
   is X as expected
4. Change the quantity manually, to pay for X - 1
5. Validate and pay for the order
6. Load the same Sales order again with "Settle the order"
   -> The quantity is still X and the price is the unit price times X!!

Why the issue
-------------
When settling the order, we get its value using _getSaleOrder
which basically reads it from the cache. So it will read the old
order lines having the old qty, and not the updated one.

The fix
-------
Instead of reading the lines from the cache, we read them direcly from
the backend, to accomodate for cases where the data might have been
changed on another device or has not been updated in the cache.

opw-4819708
opw-4913397

Co-authored-by: Arthur Nanson <artn@odoo.com>

**Step to Reproduce:**
1. Install `sale_loyalty` and `sale`
2. Enable the `Pricelists` option in the settings.
3. Create a pricelist named demo.
4. Create a Discount & Loyalty named `test program` with type `Discount Code`,
5. Assign the demo pricelist to the loyalty program.
6. Copy the discount code from the program’s conditional rules.
7. Archive the demo pricelist.
8. create sale order for any product.
9. Try to apply the copied coupon code.

**Observation:**
- An error is shown: "This code is invalid".
- check loyalty program `test program` pricelist field is empty, that suggesting it's valid for all pricelists, but the coupon still fails.

**Issue:**
- When a linked pricelist is archived, it's hidden in the UI, but the relation still exists in the relational table.
```17_sale=# select id,name,active from product_pricelist;
 id |                name                | active 
----+------------------------------------+--------
  1 | {"en_US": "Default USD pricelist"} | t
  2 | {"en_US": "new"}                   | f
(2 rows)

17_sale=# select * from loyalty_program_product_pricelist_rel;
 loyalty_program_id | product_pricelist_id 
--------------------+----------------------
                  5 |                    2
(1 row)
```
- While filtering the domain for coupon, the condition is not satisfied due to the program's pricelist.

https://github.com/odoo/odoo/blob/94d727bd9ba38116d3e14188c730c7566744e9f0/addons/sale_loyalty/models/sale_order.py#L636-L647

**Solution:**
- Display a validation error to the user when trying to archive a pricelist
  that is linked to any active promotional programs.

opw-4841678



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

Forward-Port-Of: odoo/odoo#214968

Description
-----------
On databases that had `sale_amazon` installed in the past, were used for sales for a certain period, then had the module uninstalled, and later attempted to re-install it, a memory error will occur.

The peak memory usage stems from `sale.order.line._compute_is_service`. The reason the compute is triggered is because of the "re-creation" of the master data products `default_product` & `shipping_product`, which writes `type`, which the compute depends on. So the compute will be triggered for all `sale.order.line` records that had those products.

This commit avoids the excessive memory usage by explicitly fetching the fields that are needed for the compute, which avoids fetching large fields like the different products' HTML descriptions.

Benchmark
---------
On a database with 400k+ `sale.order.line` with an amazon related product, installing `sale_amazon` peak memory usage was:

|        | Peak Mem. |
|--------|-----------|
| Before | 3.8 GiB   |
| After  | 580 MiB   |

Reference
---------
opw-4915892

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

### Issue:
BIS3 XML is not valid for Peppol

### Steps to reproduce:
- Install l10n_fr_facturx_chorus_pro and switch to french company
- Activate peppol
- Create a French customer
- Under Sales and Purchase tab, set SIRET to "11000201100044"
- Under Accounting tab, set the following:
	- Invoice sending = Peppol
	- Einvoice format = BIS Billing 3.0
	- peppol_eas = France SIRET
	- peppol endpoint = 11000201100044
- Use Invoice/Invoiced smart button, then select New to create an invoice for this french customer
- Add any non-zero invoice line, then confirm
- Send and print, send to peppol
- Download the XML. The /PartyIdentification/ID element will have the schemeName attribute set.

### Cause:
Previous [commit](https://github.com/odoo/odoo/commit/0f3a9dee5cf15fa978a1857c184413003147c4a6#diff-10c62c279423109c43458eab15a3177ff5592d6570451f890fead74389bc3740) added `schemeName`. But Peppol doesn't want any `schemeName`, see the [doc](https://docs.peppol.eu/poacc/billing/3.0/rules/ubl-tc434/UBL-DT-08/).

### Solution:
The correct attribute here seems to be `schemeID`. See an [example from the docs of Peppol](https://docs.peppol.eu/poacc/billing/3.0/bis/#_parties_2). Change `schemeName` to `schemeID`.

opw-4934436

## [PERF] hr_referral: Send refusal notification to referrer's users

Description
-----------
Following https://github.com/odoo/enterprise/commit/764f9b6f513c90eb79935d9e8469989ea704b61b, `_send_notification` will not attach the message on the `hr.applicant` itself, so a `model` was provided.
But due to a missing `res_id`, `message_notify` will set both `model` & `res_id` to `False` since both are not specified. This leads to the creation of a `mail.message` with no `res_id` and no `model` (as `self` is an empty `mail.thread` recordset).

This leads to a performance regression when mail references need to be computed to attach to the notification in `_notify_by_email_get_base_mail_values`, due to the missing `model` and `res_id` of the message.

This commit attaches the notification to the referrer's users instead, providing its `model` and `res_id`.

Reference
---------
opw-4943488

---

## [FIX] hr_referral: Do not send notif when opening the refuse wizard

Description
-----------
Currently, when opening the refusal wizard for an applicant, a call to `archive_applicant` is made. However, there is an override of it in `hr_referral` to send a notification for the applicant's refusal, and closing the `referral_state`, even though the applicant may have not been provided a reason for refusal, and the HR can simply close the wizard instead of confirming it.

This commit removes the override of `archive_applicant` and moves its logic into `action_refuse_reason_apply` which is called when the wizard is confirmed.

Reference
---------
opw-4943488

Forward-Port-Of: odoo/enterprise#90309

## How to reproduce:

https://github.com/user-attachments/assets/bf44f9fd-0402-4d70-8b55-5baf192d42e8


- Enable Consignment
- On Receipt operation type, enable 'Use existing lots'

- Create product P, tracked by lot
- Create lot SN-001 & SN-002
- Add 1 unit on hand with lot SN-001
- Create Receipt for 10 units of P -> Confirm
- Open receipt on Barcode App
- Scan "SN-002" => 'undefined' value added to 'dbQuantCache'
- Scan "SN-001" => Uncaught Promise > quantsByLocation is not iterable (cannot read property undefined)

---

## Test result without fix:
```
2025-07-18 09:30:33,801 20801 ERROR oes_test_18 odoo.addons.stock_barcode.tests.test_barcode_client_action_picking: FAIL: TestPickingBarcodeClientAction.test_barcode_lazy_cache_scan_two_lots
Traceback (most recent call last):
  File "/home/odoo/projects/odoo-src/multiverse/src/18.0/enterprise/stock_barcode/tests/test_barcode_client_action_picking.py", line 3508, in test_barcode_lazy_cache_scan_two_lots
    self.start_tour(url, 'test_barcode_lazy_cache_scan_two_lots', login='admin')
  File "/home/odoo/projects/odoo-src/multiverse/src/18.0/odoo/odoo/tests/common.py", line 2264, in start_tour
    return self.browser_js(url_path=url_path, code=code, ready=ready, timeout=timeout, success_signal="tour succeeded", **kwargs)
  File "/home/odoo/projects/odoo-src/multiverse/src/18.0/odoo/odoo/tests/common.py", line 2235, in browser_js
    self.fail('%s\n\n%s' % (message, error))
AssertionError: The test code "odoo.startTour('test_barcode_lazy_cache_scan_two_lots', {"stepDelay": 0, "keepWatchBrowser": false, "debug": false, "startUrl": "/odoo/147/action-stock_barcode.stock_barcode_picking_client_action", "delayToCheckUndeterminisms": 0})" failed

TypeError: quantsByLocation is not iterable (cannot read property undefined)
    at LazyBarcodeCache.getQuants (http://127.0.0.1:8565/web/assets/3d6bda7/web.assets_web.min.js:21482:279)
    at BarcodePickingModel._processBarcode (http://127.0.0.1:8565/web/assets/3d6bda7/web.assets_web.min.js:21748:631)
    at async http://127.0.0.1:8565/web/assets/3d6bda7/web.assets_web.min.js:21661:75
 
```

OPW-4942192

In version 17.3, the analytic mixin was introduced in budget.line model to allow to link a budget line to multiple analytic accounts belonging to different analytic plans. The issue is that we have not adapted the code in project profitability, to take those changes into account. A problematic situation could be the following:

1. We have a project where the account "X" is set to the main project plan (the first one) "Projects" BUT the account "X" actually belongs to the analytic plan "Departments" (yes, it's possible that there is a mismatch between the project plan and the analytic plan, especially after the 18.0 upgrade where "analytic_account_id" just became "account_id", no matter in which plan it was).

2. We have a budget line linked to the account "X" for the plan "Departments".

3. We want to display the budget lines in project profitability, but this line does not appear. That's because we currently only look for the budget lines belonging to the analytic plan "Projects" aka the main/first plan, that match the account "X" of the project. But as account "X" actually belongs to the analytic plan "Departments", no budget lines are found.

task-4901400
version-18.0