Odoo Changelog — 2025-11-08

Saturday, November 8, 2025

1 change · saas-18.2

Bug Fixes(1)

Resolved issues and error corrections

[FIX] l10n_mx_edi_stock_30: fix Carta Porte print

Enterprisesaas-18.2l10n_mx_edi_stockMEDIUM

This update ensures the CCP ID shown in the printed Carta Porte stays the same as the one already submitted to the government. It prevents a new identifier and QR code from being generated each time the document is printed, avoiding confusion and mismatched records.

Original PR description

**Steps to reproduce:**
- Install Accounting and l10n_mx_edi_stock_30
- Switch to a Mexican company (e.g. ESCUELA KEMPER URGATE)

- In Accounting settings, select "Solucion Factible" as PAC
- Create a product:
  * Product Name: XYZ
  * Product Type: Storable Product
  * UNSPSC Category: 25101929 Mobile office van
  * Tariff Fraction: 0101299999 Los demás.
  * UMT Aduana: Units
  * Weight: 1.00

- Go to "Inventory / Operations / Transfers / Deliveries"
- Create a delivery:
  * Delivery Address: [a Mexican contact] (e.g. INMOBILIARIA CVA)
  * Product: Product XYZ
  * Transport Type: Federal Transport
  * Vehicle Setup: [something] (e.g. [ABC123] DEMOPERMIT)
  * Gross Vehicle Weight: [anything]
  * Distance to Destination (KM): [anything]
- Validate the delivery
- Generate Delivery Guide
=> CFDI document should be created and signed by the government
- Print Carta Porte

**Issue:**
The "CCP ID" in the PDF is different than the one in the CFDI sent to the government.
Each time the Carta Porte is printed, a new "CCP ID" is generated and use in the PDF.
This also leads to a different QR-code in each PDF.

**Cause:**
When the Carta Porte is printed, instead of fetching the data from the existing CFDI document, they are recomputed.
The problem is that "l10n_mx_edi_idccp" field is a non-stored computed field and its value is a RFC 4122 identifier.
Each time the compute method is called, a new identifier is generated.

**Solution:**
When printing the Carta Porte, retrieve "CCP ID" from the existing CFDI document.

opw-5208648

Forward-Port-Of: odoo/enterprise#99034
Forward-Port-Of: odoo/enterprise#98920

#Mexico#Carta Porte#CFDI#printing#QR code

**Steps to reproduce:** - Install Accounting and l10n_mx_edi_stock_30 - Switch to a Mexican company (e.g. ESCUELA KEMPER URGATE) - In Accounting settings, select "Solucion Factible" as PAC - Create a product: * Product Name: XYZ * Product Type: Storable Product * UNSPSC Category: 25101929 Mobile office van * Tariff Fraction: 0101299999 Los demás. * UMT Aduana: Units * Weight: 1.00 - Go to "Inventory / Operations / Transfers / Deliveries" - Create a delivery: * Delivery Address: [a Mexican contact] (e.g. INMOBILIARIA CVA) * Product: Product XYZ * Transport Type: Federal Transport * Vehicle Setup: [something] (e.g. [ABC123] DEMOPERMIT) * Gross Vehicle Weight: [anything] * Distance to Destination (KM): [anything] - Validate the delivery - Generate Delivery Guide => CFDI document should be created and signed by the government - Print Carta Porte **Issue:** The "CCP ID" in the PDF is different than the one in the CFDI sent to the government. Each time the Carta Porte is printed, a new "CCP ID" is generated and use in the PDF. This also leads to a different QR-code in each PDF. **Cause:** When the Carta Porte is printed, instead of fetching the data from the existing CFDI document, they are recomputed. The problem is that "l10n_mx_edi_idccp" field is a non-stored computed field and its value is a RFC 4122 identifier. Each time the compute method is called, a new identifier is generated. **Solution:** When printing the Carta Porte, retrieve "CCP ID" from the existing CFDI document. opw-5208648 Forward-Port-Of: odoo/enterprise#99034 Forward-Port-Of: odoo/enterprise#98920