Odoo Changelog — 2026-03-12

Thursday, March 12, 2026

3 changes · saas-18.2

Bug Fixes(3)

Resolved issues and error corrections

[FIX] l10n_ec_edi: Corrected the hardcoded string for the RIMPE Emprendedor regime

Enterprisesaas-18.2l10n_ec_ediMedium

This update corrects a technical issue preventing electronic invoices in the RIMPE Emprendedor regime from being properly processed. The change ensures the correct string value is used for the 'contribuyenteRimpe' tag, resolving a validation error that was causing invoice processing failures. This ensures compliance with SRI regulations and proper invoice submission.

Original PR description

Corrected the hardcoded string for the RIMPE Emprendedor regime to match the SRI structure According to SRI technical specifications, the <contribuyenteRimpe> tag only accepts two specific values:…

Corrected the hardcoded string for the RIMPE Emprendedor regime to match the SRI structure

According to SRI technical specifications, the <contribuyenteRimpe> tag only accepts two specific values:
CONTRIBUYENTE RÉGIMEN RIMPE (Fixed value)
CONTRIBUYENTE NEGOCIO POPULAR - RÉGIMEN RIMPE

Steps to reproduce:

Install l10n_ec_edi module
Go to Settings > Invoicing > Ecuadorian Localization
In Electronic Invoicing > Regime, select rimpe_emprendedor
In Electronic Invoicing > Regime, configure a SRI Connection
Post an customer invoice

**Validation error occurring during the electronic signing process (using .p12 certificates):**
`35 - Se encontró el siguiente error en la estructura del comprobante: cvc-pattern-valid: Value 'CONTRIBUYENTE EMPRENDEDOR - RÉGIMEN RIMPE' is not facet-valid with respect to pattern 'CONTRIBUYENTE RÉGIMEN RIMPE|CONTRIBUYENTE NEGOCIO POPULAR - RÉGIMEN RIMPE' for type 'contribuyenteRimpe'.. - ARCHIVO NO CUMPLE ESTRUCTURA XML - ERROR `

Forward-Port-Of: odoo/enterprise#109147

#Ecuador#RIMPE#Invoice#SRI

[FIX] stock_barcode_mrp: barcode MO BoM UoM fixes

PR #109723

Enterprisesaas-18.2stockMedium

This update resolves a bug where manufacturing orders created through the barcode app incorrectly used product UoMs instead of the specified BoM UoMs. Previously, this caused inaccurate stock movements. The fix ensures that BoM UoMs are correctly applied, improving the reliability of manufacturing order creation within the barcode app.

Original PR description

Previous behaviour:
* Traceback if MO created with a BoM whose lines have UoMs that don't correspond to those of the products, then UoM setting disabled and MO viewed in the barcode app.
* BoM line UoMs ignored in favour of product UoMs when creating MO in the barcode app.

New behaviour:
* No traceback.
* Stock moves in MOs properly created with the corresponding BoM line UoMs.

Task ID: [4674196](https://www.odoo.com/odoo/my-tasks/4674196)

Forward-Port-Of: odoo/enterprise#108504
Forward-Port-Of: odoo/enterprise#90408

#stock_management#barcode#manufacturing

[FIX] mrp_mps: Use BoM defined on product Schedule

PR #110289

Enterprisesaas-18.2mrp_mpsMedium

This update fixes an issue where the MPS wasn't accurately reflecting demand for dependent components. Previously, the system defaulted to the oldest BoM, regardless of the user's chosen configuration. This change ensures that component demand is correctly calculated and updated within the MPS, leading to more accurate production planning.

Original PR description

## Issue: When computing the product tree, the system would use `_bom_find` to find the BoM. However, it's possible to have multiple BoM for the same product, and the user should have chosen which…

## Issue:
When computing the product tree, the system would use `_bom_find` to find the BoM. However, it's possible to have multiple BoM for the same product, and the user should have chosen which BoM he wants to use. `_bom_find` ignores the user configuration in MPS, and simply select the first (oldest) BoM in the list. This means that the components in the MPS would not be correctly updated.

---

## How to reproduce:


https://github.com/user-attachments/assets/c7e6f4d4-332a-4e2b-a40a-1b831daeb6c8


- Create Products FNS & CMP
- Create BoM for FNS without bom line (V1)
- Create BoM for FNS with CMP in bom lines (V2)
- Add FNS to MPS using bom V2
- Set Forecast Qty of FNS to 10 
- => Indirect Demand Qty for CMP is not shown (because it's 0)

---

## Test Result without fix:
```
2026-03-05 15:00:24,601 52396 INFO oes_test_18.0 odoo.addons.mrp_mps.tests.test_mrp_mps: Starting TestMpsMps.test_indirect_multiple_boms ... 
2026-03-05 15:00:24,742 52396 INFO oes_test_18.0 odoo.addons.mrp_mps.tests.test_mrp_mps: ====================================================================== 
2026-03-05 15:00:24,742 52396 ERROR oes_test_18.0 odoo.addons.mrp_mps.tests.test_mrp_mps: FAIL: TestMpsMps.test_indirect_multiple_boms
Traceback (most recent call last):
  File "/home/odoo/Odoo/src/18.0/enterprise/mrp_mps/tests/test_mrp_mps.py", line 1556, in test_indirect_multiple_boms
    self.assertEqual(forecast_cmp['forecast_ids'][0]['indirect_demand_qty'], 10)
AssertionError: 0.0 != 10
 ```

---

OPW-5979738

Forward-Port-Of: odoo/enterprise#109693

Corrected the hardcoded string for the RIMPE Emprendedor regime to match the SRI structure According to SRI technical specifications, the <contribuyenteRimpe> tag only accepts two specific values: CONTRIBUYENTE RÉGIMEN RIMPE (Fixed value) CONTRIBUYENTE NEGOCIO POPULAR - RÉGIMEN RIMPE Steps to reproduce: Install l10n_ec_edi module Go to Settings > Invoicing > Ecuadorian Localization In Electronic Invoicing > Regime, select rimpe_emprendedor In Electronic Invoicing > Regime, configure a SRI Connection Post an customer invoice **Validation error occurring during the electronic signing process (using .p12 certificates):** `35 - Se encontró el siguiente error en la estructura del comprobante: cvc-pattern-valid: Value 'CONTRIBUYENTE EMPRENDEDOR - RÉGIMEN RIMPE' is not facet-valid with respect to pattern 'CONTRIBUYENTE RÉGIMEN RIMPE|CONTRIBUYENTE NEGOCIO POPULAR - RÉGIMEN RIMPE' for type 'contribuyenteRimpe'.. - ARCHIVO NO CUMPLE ESTRUCTURA XML - ERROR ` Forward-Port-Of: odoo/enterprise#109147

Previous behaviour: * Traceback if MO created with a BoM whose lines have UoMs that don't correspond to those of the products, then UoM setting disabled and MO viewed in the barcode app. * BoM line UoMs ignored in favour of product UoMs when creating MO in the barcode app. New behaviour: * No traceback. * Stock moves in MOs properly created with the corresponding BoM line UoMs. Task ID: [4674196](https://www.odoo.com/odoo/my-tasks/4674196) Forward-Port-Of: odoo/enterprise#108504 Forward-Port-Of: odoo/enterprise#90408

## Issue: When computing the product tree, the system would use `_bom_find` to find the BoM. However, it's possible to have multiple BoM for the same product, and the user should have chosen which BoM he wants to use. `_bom_find` ignores the user configuration in MPS, and simply select the first (oldest) BoM in the list. This means that the components in the MPS would not be correctly updated. --- ## How to reproduce: https://github.com/user-attachments/assets/c7e6f4d4-332a-4e2b-a40a-1b831daeb6c8 - Create Products FNS & CMP - Create BoM for FNS without bom line (V1) - Create BoM for FNS with CMP in bom lines (V2) - Add FNS to MPS using bom V2 - Set Forecast Qty of FNS to 10 - => Indirect Demand Qty for CMP is not shown (because it's 0) --- ## Test Result without fix: ``` 2026-03-05 15:00:24,601 52396 INFO oes_test_18.0 odoo.addons.mrp_mps.tests.test_mrp_mps: Starting TestMpsMps.test_indirect_multiple_boms ... 2026-03-05 15:00:24,742 52396 INFO oes_test_18.0 odoo.addons.mrp_mps.tests.test_mrp_mps: ====================================================================== 2026-03-05 15:00:24,742 52396 ERROR oes_test_18.0 odoo.addons.mrp_mps.tests.test_mrp_mps: FAIL: TestMpsMps.test_indirect_multiple_boms Traceback (most recent call last): File "/home/odoo/Odoo/src/18.0/enterprise/mrp_mps/tests/test_mrp_mps.py", line 1556, in test_indirect_multiple_boms self.assertEqual(forecast_cmp['forecast_ids'][0]['indirect_demand_qty'], 10) AssertionError: 0.0 != 10 ``` --- OPW-5979738 Forward-Port-Of: odoo/enterprise#109693