This fix prevents an error when a cashier barcode is scanned while employee-based login is turned off in Point of Sale. It helps keep checkout workflows stable even when that optional staff login setting is disabled.

Before this commit, if logging with employee was disabled, scanning a cashier barcode would raise an error.

opw-5437310

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

Forward-Port-Of: odoo/odoo#241131

This change corrects an internal Point of Sale test setup so it no longer fails when demo data is not installed. It improves the reliability of automated checks and helps prevent false failures during development and release validation.

The test `test_07_product_combo` with no demo data raised a traceback because a product record was being accessed after it had been implicitly deleted.

The issue occurred because the product was initially created via `product.product` instead of `product.template` in the test setup: https://github.com/odoo/odoo/blob/6cc757147aebfe98db95ce6aafccdddc8483a5c6/addons/point_of_sale/tests/test_frontend.py#L1074 The link to the record was broken during the test execution, leading to the access error.

runbot-234758

This update corrects a typo in the l10n_ec_edi_pos module, ensuring that the correct partner (Deco Addict) is selected when processing refunds in the Point of Sale system. The previous error caused the system to default to a generic 'Consumidor Final' option, leading to incorrect reporting. This fix ensures accurate financial transactions.

Step to reproduce:
-  install l10n_ec_edi_pos
- start pos and settle order with specific partner(ex. Deco Addict)
- process the refund for this order

Observation:
- on product screen, "Consumidor Final" is selected instead of Deco addict.

Cause and Fix:
- Fixed a typo: it used `final_consumer_id` instead of `_final_consumer_id`

opw-5412346

Forward-Port-Of: odoo/enterprise#102202

This update resolves an issue that prevented users from creating payslips for contracts without a defined work schedule in the Belgian payroll module. The fix ensures that the system defaults to the company's standard calendar when a contract lacks a specific schedule, preventing a technical error and allowing payslips to be generated correctly.

Currently, a traceback occurs when a user tries to create a payslip for a contract 
that has no working schedule in a Belgian company.

**Steps to reproduce this issue:**

1) Install l10n_be_hr_payroll and hr_attendance and switch to BE company 
2) Create an employee with no working hours.
3) Create a contract for that employee with:
   - Work entry source as Attendance
   - No Working Schedule
   - State should be open/running 
4) Click the Payslip smart button to create a new payslip for that contract. 
5) A traceback occurs

**Error:**
```
ValueError: Expected singleton: resource.calendar()
```
**Cause:**
When creating a payslip for a contract with no resource_calendar_id, 
the method `_get_work_hours_split_half` calls `_get_max_number_of_hours` 
through self.resource_calendar_id. Since the contract's calendar lacks a 
resource_calendar_id, this triggers a ValueError in `_get_max_number_of_hours`. https://github.com/odoo/enterprise/blob/193b51ded0dfa46ed75f6c0020f0f5609f4a0f99/l10n_be_hr_payroll/models/hr_contract.py#L472

**Solution:**
If the contract or employee does not have a resource_calendar_id, 
use the default resource_calendar_id from the company instead.

opw-5237559

Forward-Port-Of: odoo/enterprise#99217

This update resolves a restriction imposed by Mexican tax authorities (SAT) regarding the format of CuentaPredial numbers. The previous regex was no longer compliant, and this change ensures Odoo correctly processes these numbers according to current SAT regulations. This update maintains compliance and avoids potential issues with tax reporting.

SAT has declared the restriction [0-9a-zA-Z]{1,150} for CuentaPredial node

Specification: https://www.sat.gob.mx/sitio_internet/cfd/4/cfdv40.xsd

Forward-Port-Of: odoo/enterprise#102981