A problem occurs when deleting a cash rounding method linked to a Point Of Sale configuration. After deleting the cash rounding, the following error message appears: “The cash rounding strategy of the point of sale Shop must be: 'Add a rounding line'.” because the rounding method is empty. The main issue arises when the cash rounding method is deleted while the POS session is open: it prevents the session from closing or modifying the cash rounding, locking the user out. Steps to reprod

A problem occurs when deleting a cash rounding method linked to a Point Of Sale configuration.

After deleting the cash rounding, the following error message appears: “The cash rounding strategy of the point of sale Shop must be: 'Add a rounding line'.” because the rounding method is empty.

The main issue arises when the cash rounding method is deleted while the POS session is open: it prevents the session from closing or modifying the cash rounding, locking the user out.

Steps to reproduce:
- Add a cash rounding for a POS
- Open the POS session
- Delete the cash rounding
- Try to enter the POS
- Error occurs

This fix ensures that the deleted cash rounding is no longer linked to any POS configuration.

opw-4651976

Forward-Port-Of: odoo/odoo#205654
Forward-Port-Of: odoo/odoo#202477

Ensure only Peppol-type proxies are retrieved when performing Peppol operations. Steps to reproduce: - Install Peppol and IT EDI - Register Peppol and IT EDI users - In Accounting, on the Vendor Bill journal, click "Fetch from Peppol" Odoo will attempt requests for all users, including an invalid call to 'False/api/peppol/1/get_all_documents'. This is not an issue in V17 but causes problems in V18. This fix makes sense in both versions as it prevents unnecessary requests a

Ensure only Peppol-type proxies are retrieved when performing Peppol operations.

Steps to reproduce:
- Install Peppol and IT EDI
- Register Peppol and IT EDI users
- In Accounting, on the Vendor Bill journal, click "Fetch from Peppol"

Odoo will attempt requests for all users, including an invalid call  
to 'False/api/peppol/1/get_all_documents'. This is not an issue in V17  
but causes problems in V18.  

This fix makes sense in both versions as it prevents unnecessary  
requests and avoids error messages in the logs.  

opw-4624633

Forward-Port-Of: odoo/odoo#203881
Forward-Port-Of: odoo/odoo#203734

When the warehouse is set to pbm_sam, MOs are assigned the procurement group name if the move origin differs from the group_id. This causes a validation error when confirming a sales order with a client_order_ref, as MO references must be unique per company. For example, if an SO has a reference S00011 - test_client_order_ref, it differs from S00011, leading to an MO name conflict. This fix ensures that MO names are always generated using the picking type sequence instead of inheriting the pr

When the warehouse is set to pbm_sam, MOs are assigned the procurement group name if the move origin differs from the group_id. This causes a validation error when confirming a sales order with a client_order_ref, as MO references must be unique per company.

For example, if an SO has a reference S00011 - test_client_order_ref, it differs from S00011, leading to an MO name conflict. This fix ensures that MO names are always generated using the picking type sequence instead of inheriting the procurement group name, preventing duplicate references or incorrectly setting the MO name as the SO name.

Current behavior before PR:
If there is more than one sale order line with MTO products:
We get a duplicate name error

If there is one sale order line with an MTO product:
We get a MO.name == SO.name

Desired behavior after PR is merged:
Both cases are resolved and the MO(s) are successfully created with the appropriate name

Steps to reproduce:
1.) Install sales; inventory; manufacturing
2.) Enable multi-step routes
3.) Unarchive MTO
4.) Set warehouse manufacture steps to:
Pick components, manufacture, then store products (3 steps)
(manufacture_steps == 'pbm_sam')
5.) Unarchive MTO
6.) Create two storable products (enable manufacture and mto routes)
7.) Create an SO with both products
8.) Add any text to the Customer Reference on the sales order (client_order_ref)
9.) Try to confirm the SO

Validation Error
The operation cannot be completed: Reference must be unique per Company!

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

Forward-Port-Of: odoo/odoo#203823

Before this PR, Setting the on-hand quantity from the product form would correctly set the product's quantity but also reset the inventory quantity to 0. While this behavior is correct,it caused a line decoration warning to appear in the Inventory Adjustment tree view. Steps to Reproduce =================== - Create a storable, non-tracked product. - Update its quantity by clicking the "Update Quantity" button, ensuring multi-location is disabled. - Go to Inventory Adjustment and

Before this PR, Setting the on-hand quantity from the product form 
would correctly set the product's quantity but also reset the inventory
quantity to 0. While this behavior is correct,it caused a line decoration 
warning to appear in the Inventory Adjustment tree view.

Steps to Reproduce
===================
- Create a storable, non-tracked product.
- Update its quantity by clicking the "Update Quantity" button, ensuring 
  multi-location is disabled.
- Go to Inventory Adjustment and locate the newly created product. 
  The inventory quantity is correctly set to 0, but it is highlighted with a warning.

Issue
======
Although the inventory quantity is correctly set to 0, the `inventory quantity set` 
field is not reverted, causing the line decoration warning to appear.

This commit resolves the issue by using an existing method that clears the 
inventory quantity and sets the `inventory quantity set` field to false.


task: [4579053](https://www.odoo.com/odoo/my-tasks/4579053)

Forward-Port-Of: odoo/odoo#199598

The demo product 'Drawer' was initially configured to be tracked by quantity, but a lot was incorrectly created, and the stock quant was subsequently created for the 'Drawer' with lot. Steps to reproduce =============== - Install the 'stock' module with demo data. - Navigate to Inventory > Products > Products and search for 'Drawer'. - Observe that 'Drawer' is set to track by quantity (Tracking field). - Check Inventory > Operations > Physical Inventory and locate the stock quant

The demo product 'Drawer' was initially configured to be tracked by quantity, 
but a lot was incorrectly created, and the stock quant was subsequently created 
for the 'Drawer' with lot.

Steps to reproduce
===============
- Install the 'stock' module with demo data.
- Navigate to Inventory > Products > Products and search for 'Drawer'.
- Observe that 'Drawer' is set to track by quantity (Tracking field).
- Check Inventory > Operations > Physical Inventory and locate the 
  stock quant for 'Drawer'.
- Note that a lot exists and is linked to the product 'Drawer', despite 
  the quantity tracking setting.

This commit modifies the demo data to enable lot tracking for the product, 
aligning its configuration with the existing lot and stock quant data for consistency.

Forward-Port-Of: odoo/odoo#204803

The `sale_subscription` module defines a template used on the website, but it was not marked as being a frontend module. Therefore the translations were not loaded on the website and the template was never translated. In this commit we add this module to the frontend modules, so its templates displayed on the website are properly translated. Forward-Port-Of: odoo/enterprise#83349 Forward-Port-Of: odoo/enterprise#82489

The `sale_subscription` module defines a template used on the website, but it was not marked as being a frontend module. Therefore the translations were not loaded on the website and the template was never translated.

In this commit we add this module to the frontend modules, so its templates displayed on the website are properly translated.

Forward-Port-Of: odoo/enterprise#83349
Forward-Port-Of: odoo/enterprise#82489