The payroll accounting test for Belgian salary advances now includes the required journal setup, so it no longer fails when demo data is not installed. This improves reliability of automated testing without changing behavior for end users.

Before this fix, the salary advance test was failing when no demo data was installed due to a missing journal on the structure. This commit adds a journal to the structure to avoid test failure without demo data.

task-4672827

This fixes an internal automated test issue in the recruitment appointment module when demo data is not available. It helps keep validation checks reliable so future updates can be tested without false failures.

runbot-160911

This draft refactor removes remaining field service references from several business areas, helping simplify the product and reduce maintenance around a discontinued scope. The change touches manufacturing work orders, sales planning, spreadsheets, and Studio tests, with limited direct impact expected for end users.

Spreadsheet test helpers now use a faster pivot insertion approach by default. This reduces waiting time during automated test runs, helping developers validate spreadsheet changes more quickly without changing customer-facing behavior.

This commit changes the default insertion mode of the pivot in the tests helpers, to use the dynamic pivot instead of the static one. It allows to avoid to wait for the pivot to be loaded before actually inserting it.

The gain is about 20% of the time for spreadsheet tests, 15% for spreadsheet_edition tests (enterprise) and 5% for the whole spreadsheet test suite.

Task: 4655122

Steps to reproduce: - Open Expenses. - Upload a sample expense pdf. The blue ribbon shows up saying “” - Do not click on the refresh button. Instead, put in some value for the amount and submit and approve the expense. - Go back to the expenses list view Issue: Notice this expense is at the top of the list and grayed out Cause: The order is determined by the extract_state_processed field: https://github.com/odoo/enterprise/blob/ba06e216ab73c73e3a67fd917623c6ad357b869f/hr_expense_ext

Steps to reproduce:
- Open Expenses.
- Upload a sample expense pdf. The blue ribbon shows up saying “”
- Do not click on the refresh button. Instead, put in some value for the amount and submit and approve the expense.
- Go back to the expenses list view

Issue:
Notice this expense is at the top of the list and grayed out

Cause:
The order is determined by the extract_state_processed field:
https://github.com/odoo/enterprise/blob/ba06e216ab73c73e3a67fd917623c6ad357b869f/hr_expense_extract/models/hr_expense.py#L21

An expense is muted when this field is set to `True`:
https://github.com/odoo/enterprise/blob/1df090289f3c45c200d133734989a6d9a8073145/hr_recruitment_extract/views/hr_applicant_views.xml#L67

Solution:
We override `iap_extract` method
https://github.com/odoo/enterprise/blob/2e3113562309bf4d440e12ab09eaf94d0b302f1f/iap_extract/models/extract_mixin.py#L69
If the expense is not in draft, it indicates that the process continued without waiting for the extraction process to complete (values were manually entered).
To ensure a consistent extraction state, we extend the "Check OCR Status" logic to prevent an infinite waiting_extraction status.

opw-4239404

Forward-Port-Of: odoo/enterprise#80705
Forward-Port-Of: odoo/enterprise#75202

Steps to reproduce: - With an ES company setup - Create and confirm invoice with: - Spanish partner - Amount > 3005.06 (mod347 threshold) - Type for mod 347: Regular operation - Create and confirm a jounral entry with: - Payable account, debit 4000 - Receivable account, credit 4000 - Type for mod 347: Regular operation - Check Mod 347 Tax Report Issue: 'Total number of persons and entities' shows 0 This occurs because some lines of mod 347 report need to be grouped by

Steps to reproduce:
- With an ES company setup
- Create and confirm invoice with:
  - Spanish partner
  - Amount > 3005.06 (mod347 threshold)
  - Type for mod 347: Regular operation
- Create and confirm a jounral entry with:
  - Payable account, debit 4000
  - Receivable account, credit 4000
  - Type for mod 347: Regular operation
- Check Mod 347 Tax Report

Issue: 'Total number of persons and entities' shows 0

This occurs because some lines of mod 347 report need to be grouped by partner, only keeping the partners whose balance for the line is above 3005.06€, so we first get all the partners that match the domain but don't reach the threshold. We exclude these partners with a 'NOT IN' clause. However, when the partner is not set, a NULL values is retrieved causing the clause to be evaluated NULL instead of False and the total count will be 0

opw-4544950

Forward-Port-Of: odoo/enterprise#81954
Forward-Port-Of: odoo/enterprise#81687

Forward-Port-Of: odoo/enterprise#82033 Forward-Port-Of: odoo/enterprise#81564

Forward-Port-Of: odoo/enterprise#82033
Forward-Port-Of: odoo/enterprise#81564

Steps to reproduce: 1. In recruitment app, generate an offer for an applicant. 2. Send the offer by email and sign it by both parties. Bug: The generated sign request is not linked to the offer using the reference_doc field. Fix: Link the offer to the sign request upon creation in the submit endpoint. task-4607475 Forward-Port-Of: odoo/enterprise#80391

Steps to reproduce:
1. In recruitment app, generate an offer for an applicant.
2. Send the offer by email and sign it by both parties. 

Bug: The generated sign request is not linked to the offer using the reference_doc field.

Fix: Link the offer to the sign request upon creation in the submit endpoint.

task-4607475

Forward-Port-Of: odoo/enterprise#80391

Before this commit: The "I Take It" button visibility was inconsistent across different view because different conditions were used to determine its visibility in each view. After this commit: This commit enhance the visibility of the "I Take It" button now it has consistent visibility across the views by follow same condition for every view. task-4455488 Forward-Port-Of: odoo/enterprise#81950 Forward-Port-Of: odoo/enterprise#79319

Before this commit:
The "I Take It" button visibility was inconsistent across different view because different conditions were used to determine its visibility in each view.

After this commit:
This commit enhance the visibility of the "I Take It" button now it has consistent visibility across the views by follow same condition for every view.

task-4455488

Forward-Port-Of: odoo/enterprise#81950
Forward-Port-Of: odoo/enterprise#79319

This test tour fails on sunday. Reason: - Here in the test create timesheets in previous week to check overtime in timesheets. - The formula works as today - current week day --> gives monday of this week - But on when it sunday it gives monday of previous week. - Timesheets are further created the previous weeks if given monday. - But we only go one week previous to check Fix: - Selecting next monday if weekday is sunday as we go back one previous week in tour. task-4667966

This test tour fails on sunday.

Reason:

- Here in the test create timesheets in previous week to check overtime in timesheets.
- The formula works as today - current week day --> gives monday of this week
- But on when it sunday it gives monday of previous week.
- Timesheets are further created the previous weeks if given monday.
- But we only go one week previous to check

Fix:

- Selecting next monday if weekday is sunday as we go back one previous week in tour.

task-4667966

Forward-Port-Of: odoo/enterprise#81975

Since there is no else condition, the rule raises an error on payslip computation. Forward-Port-Of: odoo/enterprise#81979

Since there is no else condition, the rule raises an error on payslip computation.

Forward-Port-Of: odoo/enterprise#81979

Issue: cannot groupby status on appraisal analysis neither filter by state in graph view Solve: update the state field values of report to match the original model Task: 4653149 Forward-Port-Of: odoo/enterprise#81600

Issue: cannot groupby status on appraisal analysis neither filter by state in graph view

Solve: update the state field values of report to match the original model

Task: 4653149

Forward-Port-Of: odoo/enterprise#81600

Fixed the `Request Owner` field to list all users in the selected companies. The previous domain was based on `company_id`, which was computed from the selected `category_id`. However, if no category was selected (`category_id` was null), no `request_owner_id` was listed. The new fix computes all selected companies from `self.env`. task-4637199 Forward-Port-Of: odoo/enterprise#81096

Fixed the `Request Owner` field to list all users in the selected companies. The previous domain was based on `company_id`, which was computed from the selected `category_id`. However, if no category was selected (`category_id` was null), no `request_owner_id` was listed. The new fix computes all selected companies from `self.env`.

task-4637199

Forward-Port-Of: odoo/enterprise#81096

### Issue: Currently, the `use_create_components_lots` of the manufacturing picking type is not used in barcode to allow/forbid the creation of new lots. ### Steps to reproduce: - Inventory > Configuration > Warehouse Management > Operation Types - Manufacturing > uncheck: Create New Lots/Serial Numbers for Component - Create a product tracked by SN and put one SN in stock. - Create and confirm an MO for an other product using your tracked product as component. - Go to the barcode a

### Issue:

Currently, the `use_create_components_lots` of the manufacturing picking type is not used in barcode to allow/forbid the creation of new lots.

### Steps to reproduce:

- Inventory > Configuration > Warehouse Management > Operation Types
- Manufacturing > uncheck: Create New Lots/Serial Numbers for Component
- Create a product tracked by SN and put one SN in stock.
- Create and confirm an MO for an other product using your tracked product as component.
- Go to the barcode app > Manufacturing > your MO
- Click on the component line and scan a string that do not correspond to an existing SN of your tracked product.
> The Scanned string is added as a "lot_name" on a new line. In
   particular, at validation a new move line without lot and with a
   set lot_name will be created. This line without lot will be used in
   all the `pre_button_mark_done` checks like: `_check_sn_uniqueness`
   which btw will fail if you scanned 2 non-existing lots. And, if you
   manage to pass all check for instance by scanning a non-existing lot
   and the initially reserved one, the validation of the new move line
   will create the lot.

Cause of the issue:

Scanning the non existing lot will correctly fail to find a match via the barcode parser:
https://github.com/odoo/enterprise/blob/026a5b8a83bd6b94588baa9a35530495d9e067cd/stock_barcode/static/src/models/barcode_model.js#L963 As such and since a line is selected, you will end up setting the barcode as a lotName:
https://github.com/odoo/enterprise/blob/026a5b8a83bd6b94588baa9a35530495d9e067cd/stock_barcode/static/src/models/barcode_model.js#L1018-L1034 This happens notably because you `this.canCreateNewLot` is always set to `True` on productions but should not:
https://github.com/odoo/enterprise/blob/026a5b8a83bd6b94588baa9a35530495d9e067cd/stock_barcode_mrp/static/src/models/barcode_mrp_model.js#L126-L128

opw-4618963

Forward-Port-Of: odoo/enterprise#81681
Forward-Port-Of: odoo/enterprise#81272

Issue ===== When validating an uncompleted return in Barcode, an error is raised. How to reproduce ================ - Open Barcode app > Operations > Receipts and create a new receipt; - Scan at least two times the same product's barcode; - Validate. - Re-open the same receipt and click on "Return Products"; - Scan one product then validate -> The return is correctly validated but an "Invalid Operation" error is raised. Cause of the issue ================== The return's move is d

Issue
=====
When validating an uncompleted return in Barcode, an error is raised.

How to reproduce
================
- Open Barcode app > Operations > Receipts and create a new receipt;
- Scan at least two times the same product's barcode;
- Validate.
- Re-open the same receipt and click on "Return Products";
- Scan one product then validate -> The return is correctly validated but an "Invalid Operation" error is raised.

Cause of the issue
==================
The return's move is done but `_split` is called and calling this method on a done move is forbidden.

How to fix
==========
In the `split_uncompleted_moves` move's method, done and cancel move are skipped.
Also, the JS method who call `post_barcode_process` will now doesn't call it if operation is done or cancelled or if there is no moves (to avoid to do useless RPC.)

[OPW-4535205](https://www.odoo.com/odoo/project/49/tasks/4535205)
[OPW-4535257](https://www.odoo.com/odoo/project/49/tasks/4535257)

Forward-Port-Of: odoo/enterprise#81531
Forward-Port-Of: odoo/enterprise#81312

# HOW TO REPRODUCE: - Create products FNS & CMP - Set available quantity of CMP to 2 - Create MO of 1 FNS and 2 CMP -> Confirm - Open MO in barcode - Set FNS quantity to 1 - Set CMP quantity to 1 (1/2 of the demand) -> Produce MO => The CMP move has 2 lines of 1 unit, so 2 unit have been consumed instead of the 1 put on the barcode. https://github.com/user-attachments/assets/237c81bc-f342-4293-bc76-008b5c7cf876 OPW-4517284 Forward-Port-Of: odoo/enterprise#81912 Forward-Port-Of

# HOW TO REPRODUCE:
- Create products FNS & CMP
- Set available quantity of CMP to 2
- Create MO of 1 FNS and 2 CMP -> Confirm
- Open MO in barcode
  - Set FNS quantity to 1
  - Set CMP quantity to 1 (1/2 of the demand) -> Produce MO => The CMP move has 2 lines of 1 unit, so 2 unit have been consumed instead of the 1 put on the barcode.

https://github.com/user-attachments/assets/237c81bc-f342-4293-bc76-008b5c7cf876


OPW-4517284

Forward-Port-Of: odoo/enterprise#81912
Forward-Port-Of: odoo/enterprise#81343

Steps to reproduce: 1. In recruitment app, generate an offer for an applicant. 2. Send the offer by email and sign it by both parties. Bug: The generated sign request is not linked to the offer using the reference_doc field. Fix: Link the offer to the sign request upon creation in the submit endpoint. task-4607475 Forward-Port-Of: odoo/enterprise#80391

Steps to reproduce:
1. In recruitment app, generate an offer for an applicant.
2. Send the offer by email and sign it by both parties. 

Bug: The generated sign request is not linked to the offer using the reference_doc field.

Fix: Link the offer to the sign request upon creation in the submit endpoint.

task-4607475

Forward-Port-Of: odoo/enterprise#80391

Steps to reproduce the bug: - create a storable product “P1” and “C1” - create a quality point for C1: - Operation type: Manufacturing - Control per: quantity - Control Frequency: all - Partial Test: 10% - Type: pass-fail - Create a manufacturing order: - Finished product: 2 units of P1 - Components: C1 -> 10 units - Confirm the MO - go to the quality check Problem: A quality check is created, but the quantity to test is based on the manufacturin

Steps to reproduce the bug:
- create a storable product “P1” and “C1”
- create a quality point for C1:
    - Operation type: Manufacturing
    - Control per: quantity
    - Control Frequency: all
     - Partial Test: 10%
     - Type: pass-fail

- Create a manufacturing order:
    - Finished product: 2 units of P1
    - Components: C1 -> 10 units

- Confirm the MO
- go to the quality check

Problem:
A quality check is created, but the quantity to test is based on the manufacturing order's produced quantity instead of the stock move line quantity linked to the quality check.

opw-4527413

Forward-Port-Of: odoo/enterprise#81773