This update improves manufacturing planning and shop floor workflows by making replenishment needs and work order filters behave as expected. Teams can more reliably identify products that still need replenishment and find the right shop floor work orders without manual workarounds.

Description of the issue/feature this PR addresses: This PR fixes three Shop Floor and MPS bugs provided in task [4104208](https://www.odoo.com/odoo/project/966/tasks/4104208).

Current behavior before PR:
1. Shop Floor ignores the `workcenter_id` context parameter and the user always lands on the same workcenter (the first one in defined).
2. Products that are marked as replenished won't appear under the 'to replenish' filter even if the replenishment is insufficient due to later demand. (underreplenishment)
3. The max replenish option is remains off even if a max replenish quantity is already set.
4. WO filters in Shop Floor for the waiting, pending and done states don't work as intended.
5. Accessing the Shop Floor directly from an MO lands the user in an empty workcenter if All MO isn't enabled.

Desired behavior after PR is merged:
1. ~~The user lands on the 'All MO' virtual workcenter if they access Shop Floor through the button in an MO.~~ Nixed.
2. Replenished products will still appear under the 'to replenish' filter if the replenishment turns out to be insufficient.
3. The max replenish option gets automatically toggled on if a max replenish quantity is already specified (ie nonzero), mainly if the product record was added bypassing the form (API, import etc).
4. WO filters are properly implemented. Filtering by the ready and progress states is the default. ~~Entering the Shop Floor through an MO no longer filters by This Station.~~
5. ~~All MO is temporarily enabled if Shop Floor is accessed through an MO and All MO is not enabled. It's also checked on by default in the workcenter selection menu.~~ Nixed.

Task ID: [4104208](https://www.odoo.com/odoo/project/966/tasks/4104208)

**Steps to reproduce:** - Install l10n_cl - Switch to a Chilean company (e.g. CL Company) - Activate a foreign currency (e.g. USD) - Make sure that the rate of the foreign currency is not 1 For example: * Unit per CLP: 0.001057876419 * CLP per Unit:945.29 - Create an invoice in USD with 2 lines having different amount: * 15.80 * 15.00 - Save the invoice - Print the invoice **Issue:** On the printed invoice, a slightly different currency rate is displayed for each invoice l

**Steps to reproduce:**
- Install l10n_cl
- Switch to a Chilean company (e.g. CL Company)
- Activate a foreign currency (e.g. USD)
- Make sure that the rate of the foreign currency is not 1 For example:
  * Unit per CLP: 0.001057876419
  * CLP per Unit:945.29
- Create an invoice in USD with 2 lines having different amount:
  * 15.80
  * 15.00
- Save the invoice
- Print the invoice

**Issue:**
On the printed invoice, a slightly different currency rate is displayed for each invoice line.

**Cause:**
The currency rate to display is computed for each invoice line, based on the following formula: abs(self.balance) / self.price_subtotal However, the value of balance is rounded to the unit because of the CLP currency and therefore it generates a different rate when trying to compute it.

**Solution:**
Compute the rate from the total values instead of the subtotal of each line.
The real rate configured on the currency cannot be used because it can be modified after the creation of the invoice.

opw-4242448


Linked community PR: https://github.com/odoo/odoo/pull/185230

Forward-Port-Of: odoo/enterprise#73120
Forward-Port-Of: odoo/enterprise#73035

This partially redoes odoo/enterprise#64900. Copying tax_ids from the sale order lines to the down payment line on the invoice doesn't work for external tax calculators. Tax percentages returned by tax calculators are only informational. When they return e.g. 5% tax, the actual amount can be different from 5% because of differences in rounding or (partial) exemptions. The authoritative tax is returned as a value amount (e.g. $10). Because of this, we cannot rely on Odoo to calculate the tax from

This partially redoes odoo/enterprise#64900. Copying tax_ids from the sale order lines to the down payment line on the invoice doesn't work for external tax calculators. Tax percentages returned by tax calculators are only informational. When they return e.g. 5% tax, the actual amount can be different from 5% because of differences in rounding or (partial) exemptions. The authoritative tax is returned as a value amount (e.g. $10). Because of this, we cannot rely on Odoo to calculate the tax from account.tax records. It's not always going to match.

It's not possible to fix this by externally calculating taxes on the down payment invoice. The single down payment line cannot accomodate all different tax categories. Creating a down payment line per tax category (e.g. avatax_category_id) was considered, but a specific down payment product would need to be created per used tax category which would clutter the database. On top of that, down payment products are removed in later versions [1] which would complicate this approach even further.

This solves the issue by not calculating taxes on down payments at all. The down payment invoice will not be sent to external tax calculators. The resulting down payment lines on the SO won't have taxes set, and those lines will be excluded from the request to the external tax calculator. The final, "regular invoice" transaction will happen as if no down payments were made. The down payment lines won't be sent, so this will look like a regular invoice from the external calculator's view.

By default, the downpayment lines equal the subtotal of the selected down payment amount. We remove tax_ids from the lines because we cannot count on calculating tax locally (see above). To keep the behavior analogous we override the downpayment wizard to create a single down payment line with a total equal to the entered total in the wizard.

[1] odoo/odoo@9aa52dd6418e5881adc2d96d15d062b55d6150c5

opw-3971513

Forward-Port-Of: odoo/enterprise#73027
Forward-Port-Of: odoo/enterprise#70517

After odoo/odoo@45b90b8b7ce252e1558728f4fc03e52459817565 `test: true` is not a valid tour key anymore Forward-Port-Of: odoo/enterprise#73116

After odoo/odoo@45b90b8b7ce252e1558728f4fc03e52459817565 `test: true` is not a valid tour key anymore

Forward-Port-Of: odoo/enterprise#73116

The check for the sequence of the group_s was always true because the length was not compared. Now it is compared to the max length of the sequence. task-4203261 Forward-Port-Of: odoo/enterprise#72886

The check for the sequence of the group_s was always true because the length was not compared. Now it is compared to the max length of the sequence.

task-4203261

Forward-Port-Of: odoo/enterprise#72886

On the employee, we should clarify the view to tell what is editable or not. On the contract, the index is monetary but shouldn't. Forward-Port-Of: odoo/enterprise#71794

On the employee, we should clarify the view to tell what is editable or not. On the contract, the index is monetary but shouldn't.

Forward-Port-Of: odoo/enterprise#71794

### Description of the issue/feature this PR addresses: It is needed to be able to create Factura B for a foreign customer. Legal reference: Here is some useful documentation : https://servicioscf.afip.gob.ar/publico/abc/ABCpaso2.aspx?id=8555970 https://www.afip.gob.ar/EspaciosdeDialogoInstitucional/documentos/Acta-15-Espacio-de-Dialogo-AFIP-Camaras-Empresariales-14-11.pdf ### Current behavior before PR: It is not possible to create Factura B for a foreign customer. ### Desired

### Description of the issue/feature this PR addresses:
It is needed to be able to create Factura B for a foreign customer.

Legal reference:
Here is some useful documentation :

https://servicioscf.afip.gob.ar/publico/abc/ABCpaso2.aspx?id=8555970
https://www.afip.gob.ar/EspaciosdeDialogoInstitucional/documentos/Acta-15-Espacio-de-Dialogo-AFIP-Camaras-Empresariales-14-11.pdf

### Current behavior before PR:
It is not possible to create Factura B for a foreign customer.

### Desired behavior after PR is merged:
It is possible to create Factura B for a foreign customer.

Task Adhoc side: 30008
Task latam side: 913

Forward-Port-Of: odoo/enterprise#72728
Forward-Port-Of: odoo/enterprise#71562

This command's purpose was to dispatch the event at each individual external step, but it was only used for embedded components, and `onExternalHistorySteps` resource (which handles every batch of collaborative steps) is enough for embedded components, and it is called less often. This commit therefore removes `ADD_EXTERNAL_STEP` command. task-4281356 Forward-Port-Of: odoo/enterprise#72681

This command's purpose was to dispatch the event at each individual external step, but it was only used for embedded components, and `onExternalHistorySteps` resource (which handles every batch of collaborative steps) is enough for embedded components, and it is called less often. This commit therefore removes `ADD_EXTERNAL_STEP` command.

task-4281356

Forward-Port-Of: odoo/enterprise#72681

Steps: Create a ticket with no partner. Click on 'Plan Intervention'. The modal opens. Issue: See that a partner "@" has been created and set. Cause: Clicking on the button calls `action_generate_fsm_task`, which calls `_find_or_create_partner`, but the args, `self.partner_name` and `self.partner_email`, are empty. Solution: Not try to create a partner when the fields both empty. Also, if there was no partner on the ticket, it takes the value of the wizard's partner when savin

Steps:
Create a ticket with no partner.
Click on 'Plan Intervention'.
The modal opens.

Issue:
See that a partner "@" has been created and set.

Cause:
Clicking on the button calls `action_generate_fsm_task`,
which calls `_find_or_create_partner`,
but the args, `self.partner_name` and `self.partner_email`, are empty.

Solution:
Not try to create a partner when the fields both empty.
Also, if there was no partner on the ticket,
it takes the value of the wizard's partner when saving the wizard
(clicking on "Create (& View) Task".

task-4265584

Forward-Port-Of: odoo/enterprise#72304

Steps ----- - Install timesheet_grid - Set monday as the first day of the week in the language settings - Set the timezone of the user's working schedule to a more advanced timezone, e.g. UTC+10 - Go to Timesheets and add some hours on monday -> The under/over time is calculated relative to a lower number of hours than the real number of working hours for that day. Cause ----- `get_daily_working_hours` uses UTC's start/end of day for the start and end of the period, causing some workin

Steps
-----
- Install timesheet_grid
- Set monday as the first day of the week in the language settings
- Set the timezone of the user's working schedule to a more advanced timezone, e.g. UTC+10
- Go to Timesheets and add some hours on monday -> The under/over time is calculated relative to a lower number of hours than the real number of working hours for that day.

Cause
-----
`get_daily_working_hours` uses UTC's start/end of day for the start and end of the period, causing some working hours near the start/end of the period to be missed.

opw-4163183

Forward-Port-Of: odoo/enterprise#73010
Forward-Port-Of: odoo/enterprise#72526

Versions: ------------ 17.0 Steps to Reproduce: ----------------------------- 1. go to sign document 2. add sign item in document 3. click on sign document now 4. click on start seems be not working properly 5. video link: https://nimb.ws/WKMlFjB Issue: ------- stacking order of sign item navigator seems to be low Solution: ------------ increase z-index value of `o_sign_sign_item_navigator`. task-4191542 Forward-Port-Of: odoo/enterprise#70170

Versions:
------------
17.0

Steps to Reproduce:
-----------------------------
1. go to sign document
2. add sign item in document
3. click on sign document now
4. click on start seems be not working properly
5. video link: https://nimb.ws/WKMlFjB

Issue:
-------
stacking order of sign item navigator seems to be low

Solution:
------------
increase z-index value of `o_sign_sign_item_navigator`.

task-4191542

Forward-Port-Of: odoo/enterprise#70170

Since #69952 the name of the final amount has been changed in the dict from `amount_total` to `total_amount` but not in the get. task-id: 4242134 Forward-Port-Of: odoo/enterprise#72120

Since #69952 the name of the final amount has been changed in the dict from `amount_total` to `total_amount` but not in the get.

task-id: 4242134

Forward-Port-Of: odoo/enterprise#72120

The module was removed in odoo/enterprise@53098e18 Forward-Port-Of: odoo/enterprise#73084

The module was removed in odoo/enterprise@53098e18

Forward-Port-Of: odoo/enterprise#73084

**Steps to reproduce:** Create a folder in 'My Drive' e.g: "New". Add 2 files in New folder. Open the folder and only select those 2 files and move them to trash. Now, go back to My drive, select that empty New folder and move it to Trash. Go to Trash workspace. Select one of the file and try to restore it. **Technical:** The folder whose parent has a folder_id 'False'. In the domain, we check the id and active status for the folder_id but since there is no folder_id, that record will no

**Steps to reproduce:**
Create a folder in 'My Drive' e.g: "New".
Add 2 files in New folder.
Open the folder and only select those 2 files and move them to trash. Now, go back to My drive, select that empty New folder and move it to Trash. Go to Trash workspace.
Select one of the file and try to restore it.

**Technical:**
The folder whose parent has a folder_id 'False'. In the domain, we check the id and active status for the folder_id but since there is no folder_id, that record will not be considered as archived_top_parent_documents.

**Specifications:**
Show the appropriate error message when restoring from TRASH, consistent with the error for other documents.

Task-4274176

Forward-Port-Of: odoo/enterprise#72469

Specs: Replace the pin icons with the 'v' tick icon from the drop-down items. Technical: Remove the '<i class='fa fa-thumb-tack me-1'/>' pin icon and, based on a condition, add the 'selected' class to the existing 'o-dropdown-item dropdown-item' element. Task-4266470 Forward-Port-Of: odoo/enterprise#72250

Specs:
Replace the pin icons with the 'v' tick icon from the drop-down items.

Technical:
Remove the '<i class='fa fa-thumb-tack me-1'/>' pin icon and, based on a condition, add the 'selected' class to the existing 'o-dropdown-item dropdown-item' element.

Task-4266470

Forward-Port-Of: odoo/enterprise#72250