Currently, an error occurs when a user creates an attendance for an employee.

**Steps to Reproduce ([Video](https://drive.google.com/file/d/1vm89hHBOVcliYwZjP7fwNOzwC68V3B1l/view)):**
 - Install the `hr_attendance` module.
 - Go to `Overtime Rulesets` and create a `new overtime ruleset` by adding an `overtime rule`. 
    Set Based on to `Timing`. 
    Set the `Start time greater than the Stop time` (ex, Start = 10 and Stop = 5).
 - Go to `Employees`, open `any employee record`, and assign this `Overtime Ruleset` to the employee.
 - Now go to `Attendances` and `create an attendance` for that employee.

`TypeError: '>' not supported between instances of 'datetime.datetime' and 'int'`

**Cause:**
This error occurs when a user sets the overtime rule on an employee and then creates an attendance. At that point, the system tries to calculate the overtime intervals based on the timing rule. Because the rule’s start time is greater than the stop time, it attempts to calculate the interval for the remaining working period of the day. However, the start date and end date are calculated in datetime format [1], while integer and float values are passed as arguments [2] for day in interval calulation. Since the interval expects values of the same data type, than it raise the error [3].

**Fix:**
This commit ensures that the day start and day end values are passed in datetime format.

[1]: https://github.com/odoo/odoo/blob/67191cf0915081df352331a698be47b7e3ecd505/addons/hr_attendance/models/hr_attendance_overtime_rule.py#L524

[2]- https://github.com/odoo/odoo/blob/67191cf0915081df352331a698be47b7e3ecd505/addons/hr_attendance/models/hr_attendance_overtime_rule.py#L530

[3]: https://github.com/odoo/odoo/blob/67191cf0915081df352331a698be47b7e3ecd505/odoo/tools/intervals.py#L138-L154

sentry-7166788786

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

Forward-Port-Of: odoo/odoo#242491

**Steps to reproduce:**
* Install the **Repair** module with demo data.
* From Setting -> enable 'Discounts' and 'Pricelists'
* From the home screen, search for Pricelist and open it.
* Open the default USD pricelist and go to Configuration →
`Show public price & discount to the customer`
* Open the *Repair* app.
* Create a **Repair Order with parts**.
* Click **Create Quotation** button from the repair order.
* In the quotation,  order line and set a **discount**.
* Return to the repair order using the **Repairs** smart button.
* Confirm the repair order, then **Start repair** and **End repair**  order.

**Observed behavior:**
* The discount added on the quotation line disappears from the linked sale order line.

**Cause:**
* The `discount` field on `sale.order.line` is computed by `_compute_discount`,
  which `depends` on `product_id`, `product_uom`, and `product_uom_qty`.
  When `product_uom_qty` is written during `action_repair_done`, the
  compute method is triggered and the `discount` is recalculated.
https://github.com/odoo/odoo/blob/49169c4c4fec57d78cd82c4c9366de9d69540e6a/addons/repair/models/repair.py#L457

**Fix:**
* Remove the for loop that calls `write()` on the sale order lines, as it
  is functionally incorrect and causes the discount to be reset.

---
opw-5352567

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

Forward-Port-Of: odoo/odoo#243075
Forward-Port-Of: odoo/odoo#238410

### Issue:
When running the scheduled action "Payroll: Generate pdfs" for several payslips, nothing is generated and a traceback can be seen in the logs.

### Steps to reproduce:
- Disable scheduled action: "Payroll: Generate pdfs" (to avoid side effect in next step)
- Refuse all time off for "Anita Oliver" (to avoid side effect in next step)
- Create a user for the employee "Anita Oliver"
- Link the employee and the user
- Create 2 payslips
	- 1 for "Mitchell Admin"
	- 1 for "Anita Oliver"
- Compute sheet and confirm both payslips
- Run scheduled action: "Payroll: Generate pdfs"
- Nothing happens

### Cause:
The traceback is raised on the line `self._get_document_partner().id`
 because `_get_document_partner()` can return a recordset.

### Solution:
Call `ids` instead of `id`.

### Note:
Calling `_get_document_partner()` on a recordset [here](https://github.com/odoo/enterprise/blob/a0729c8d42ca93016b23e331d8f38c1f4fa88f12/hr_payroll/models/hr_payslip.py#L444) seems unexpected as, if only one payslip in the recordset has `self.employee_id.user_id.partner_id` evaluating to `True`, then it will return only this partner, completely ignoring the other part checking `self.employee_id.work_contact_id`.

The final code works fine as `_check_create_documents()` is called again individually [here](https://github.com/odoo/enterprise/blob/a0729c8d42ca93016b23e331d8f38c1f4fa88f12/documents/models/ir_attachment.py#L86).

opw-5213979

Forward-Port-Of: odoo/enterprise#103749
Forward-Port-Of: odoo/enterprise#101911

**Steps to reproduce**
On a local DB, with demo data:
- Change your machine's time to a late part of the day (e.g. 6pm)
- Install `mrp_workorder`
- Set the "Standard 40 hours/week" (used by a workcenter) as flexible.
- From the Shop Floor, start the "WH/MO/00003 - Manual Assembly"
workorder.

"Validation Error: The start date of the time off must be earlier than
the end date."

**Cause**
`_calculate_date_finished` in mrp is calling `plan_hours` and under
certain conditions with a flexible resource, it is possible for
`plan_hours` to return a datetime before the `day_dt` parameter.
This happens because for flexible resources,
`_attendance_intervals_batch` can return attendance intervals with
start or end datetimes outside of the start_dt -> end_dt window.
For example, a flexible calendar with 8h/day will return the
8:00->16:00 interval, even if start_dt is later than 8:00.

**Change**
Don't return attendance intervals outside of the [start_dt, end_dt]
interval by shifting them if necessary.

opw-5123230

Forward-Port-Of: odoo/odoo#243101
Forward-Port-Of: odoo/odoo#233169

[FIX] website_sale, adding website_id in portal controller

Version: 17.0+e

Steps to reproduce
------------------
The database has two different websites.

A payment provider is enabled for just one of them (website1).

When a sale order is created on the sales app and the customer accesses it in its portal on the website2, he is able to pay with the payment provider which is only enabled on website1.

The problem also occurs when previewing the customer’s portal view.

Why it's happening
------------------
When accessing an order via “/my/orders/<int:order\_id>”, the portal_order_page method calls _get_compatible_providers without passing the website_id. The overriding logic in website_payment then defaults to considering all activated payment methods as compatible, regardless of website restrictions.

As no website_id is provided, the overriding method from the payment_provider extension in website_payment module considers every activated payment methods as compatible.

The Fix
-------
We now add the current website's id to the method if none has been added before.


opw-5172444, “Payment provider visible on sales order portal"


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

Forward-Port-Of: odoo/odoo#242955
Forward-Port-Of: odoo/odoo#235954

Steps to reproduce:
- With a PE Company setup
- Create an Invoice with "Document Type" set to "(01) Factura"
- Set a discount on the invoice line
- Confirm and send for validation
- Create the credit note
- Confirm the credit note and send for validation

Issue:

Credit note validation will fail with error
`3271|El valor de venta por ítem difiere de los importes consignados. -
Detalle: xxx.xxx.xxx value='ticket: 1767185167086 error: Error en la
linea: 1: 3271 (nodo: "cac:CreditNoteLine/cbc:LineExtensionAmount"
valor: "600.00")'`

This occurs because while UBL standard allows AllowanceCharge in credit
notes, SUNAT does not.
Credit notes are treated as pure amount adjustments, not price recalculations.
Discounts were already applied in the invoice, so SUNAT ignores
AllowanceCharge in CN, causing error 3271.

With this commit we introduce a check to ensure users won't post edi credit
or debit notes containing line discounts

opw-5414766

Forward-Port-Of: odoo/enterprise#103106

**Issue:**
Payslips show blank worked days for employees with contracts without a `resource_calendar_id` (fully flexible, despite having valid work entries

**Cause:**
`_get_worked_day_lines()`  skips worked day computation if the contract has no calendar

https://github.com/odoo/enterprise/blob/1a10e0444fdb71a072262a1f14f0bfc766d109c6/hr_payroll/models/hr_payslip.py#L665-L674

**Steps to Reproduce:**
- Assign an employee a fully flexible contract with attendance as work entry source.
- Create work entries based on the attendance records of the employee record
- Go to employees > contracts > new Payslip Worked Days section is empty, even though attendance shifts are showing up on top.

**Fix:**
removing the calendar requirement in the main method and adding a fallback calendar in the called utility method

**Note:** same issue happens if work entry source of the contract is Planning

opw-4931972

Forward-Port-Of: odoo/enterprise#98941
Forward-Port-Of: odoo/enterprise#93935