**Steps to reproduce:**
* Install  `stock` module.
* Go to the > Settings*, enable *Packages* and
  *Storage Locations*(warehouse).
* Create a storable product and set *Tracking Inventory* to
  **By Quantity** and set some *barcode*
* Update the on-hand quantity for the product and assign it to one packages.
* Open *Barcode > Operations > Internal Transfer* and create a new
  transfer.
* Click the *gear icon* in the top-right corner to open the barcode
  scanning flow.
* manually enter the created product barcode and apply it.
* Click the **Back** button multiple times in quick succession.
* Go to the backend and open the created internal transfer.

**Observed behavior:**
* The internal transfer is created with *double quantities*
 compared to what was added in the barcode interface.

**Cause:**
* When clicking the *Back* button, the following flow is triggered:
  `exit()` → `beforeQuit()` → `save()`.
https://github.com/odoo/enterprise/blob/07ede9bda567d94da27da79b945e2189fa5aca6e/stock_barcode/static/src/components/main.js#L406-L414

https://github.com/odoo/enterprise/blob/07ede9bda567d94da27da79b945e2189fa5aca6e/stock_barcode/static/src/models/barcode_model.js#L473-L475

https://github.com/odoo/enterprise/blob/07ede9bda567d94da27da79b945e2189fa5aca6e/stock_barcode/static/src/models/barcode_picking_model.js#L828-L832

https://github.com/odoo/enterprise/blob/07ede9bda567d94da27da79b945e2189fa5aca6e/stock_barcode/static/src/models/barcode_model.js#L477-L483
* If the button is clicked multiple times rapidly, `exit()` is called
  again before the previous `save()` RPC completes.
* This results in multiple `save()` calls being executed, causing
  duplicated quantities on the picking.

reference - https://github.com/odoo/enterprise/pull/103999/changes/b791239c154deb6a25f85d65ebc72e3ac53b6c74

**Fix:**

 * Prevent rapidly clicking the Back button multiple times
 does not multiply quantities.

---
opw-5375899

Forward-Port-Of: odoo/enterprise#109013
Forward-Port-Of: odoo/enterprise#103130

An error is thrown when we try to generate a payslip for an employee that changed contract on a period before the contract change

Steps to reproduce:
1. Install l10n_mx and l10n_mx_hr_payroll modules
2. Switch to INNOVACION VALOR... company
3. Go to Employees and open Cecilia Miranda Sanchez
4. Go to Payroll tab, set the end of the contract to Jan 31 and save
5. Create a new contract from Feb 1
6. Go to Payroll > Payslips > Payslips and create a new pay run
7. Select Salary Structure 'Mexico: Regular Pay', Pay Schedule 'Bi-weekly' and Period 'Jan 1 -> Jan 15'
8. Click on Continue, select Cecilia and click on Select
9. An error is thrown

Problem:
In `_compute_integration_factor` we try to compute the number of years the employee has worked by accessing the start date on the employee but this date might be earlier than the start date of the employee's current contract if the employee has changed contract. This will throw an error when we try to access the holidays count for 0 year because `payslip._rule_parameter('l10n_mx_holiday_tables')` doesn't have an entry for 0

Solution:
Use the start date of the first contract of the employee, take gaps in between the employee's contracts into consideration to correctly compute the number of years worked

opw-5931355

Forward-Port-Of: odoo/enterprise#108495

Steps to Reproduce  
------------------  
1. Open the Planning Gantt view.
2. Click a cell that belongs to a resource with **no** scheduled shifts.  
3. The Plan dialog opens with an empty list.  
  
Issue  
-----  
A previous change  keeps the clicked resource in the dialog context; the Gantt 
model turns it into a default search filter, so only shifts already linked to 
that resource are shown. Unassigned shifts are therefore hidden, preventing 
planners from assigning them by role or availability.  
  
Current Behaviour  
-----------------  
The Plan dialog is always filtered by `resource_id`, which returns no results 
for unscheduled resources, even when they have the right roles.
  
Expected Behaviour  
------------------  
The dialog should list all unscheduled shifts that match the resource’s roles, 
or every unscheduled shift if the resource has no roles, while still preserving
full context for scheduling once a shift is selected.  
  
Fix  
---  
Remove the automatic resource filter from the dialog context in 
`getSelectCreateDialogProps()`. This prevents the unwanted search restriction; 
role defaults remain, so the dialog now displays the correct shifts.  
  
Task-4922525  
Issue – https://github.com/odoo/enterprise/pull/87424/commits/a218a7cedce61f992fbe76284c273be8f937d28d

Forward-Port-Of: odoo/enterprise#92100

Issue:
Sending PUE payments to CFDI/SAT is no more suitable

Step to reproduce:
- In a Mexican company
- Create an invoice (Invoice A)
- Add a line
- Set Payment Terms to "Immediate payment"
- Confirm
- Duplicate (Invoice B)
- Confirm
- Duplicate again (Invoice C)
- Set Payment Terms to "30 days"
- Confirm
- Go to Invoice A
- Pay it. It should appear as "Paid"
- Send it to CFDI
- Go to Accounting > Customer > Invoices
- Select Invoice B and C
- Pay and select the "Group Payments". They should appear as paid.
- In every invoice, click the "Update Payment" button

Current behavior:
- In Invoice A -> Sheet CFDI: A button "Force CFDI" allow sending the payment to CFDI
- In Invoice B/C -> sheet CFDI: Click on the "Download" part of the Payment line, the XML that was sent to CFDI include both invoice B and C

Expected behavior:
- It shouldn't be possible to send payment for invoice A to CFDI.
- Payment for invoice B shouldn't be sent to CFDI

Cause:
Payment for invoice paid in less than 30 days, referred as PUE, shouldn't be sent to CFDI.

Solution:
Disable the force sending to CFDI

About tests:
l10n_mx_edi_cfdi_invoice_try_update_payments already send payment to CFDI for PPD invoices. Calling action_force_payment_cfdi was pointless and causing a mess.

opw-5381600

Forward-Port-Of: odoo/enterprise#109105
Forward-Port-Of: odoo/enterprise#104628