Handle purchase exchanges with the EDI framework.
This module is mostly a glue module for purchase_order_ubl with edi_oca.
Allows you to generate and send purchase orders as UBL XML files with a simple configuration.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Lets you generate purchase orders as UBL XML files and send them to suppliers through the EDI framework, using a simple exchange type configuration.
This module connects the purchase order UBL export with the EDI framework, so purchase orders can be produced as UBL XML documents and sent out automatically.
- It adds a generator named
edi.output.ubl.purchase.orderthat turns a purchase order into a UBL XML string. - The generator reads the document type and UBL version from the purchase order, then builds the XML file.
- It is meant to be used from an EDI exchange type configured with direction "output" and the XML file extension, as shown in the demo data.
- The generated file name follows a pattern based on the record name, the exchange type code and the date.
- If the purchase order has no UBL document type, the generation stops with an error instead of producing an invalid file.
It touches the purchase order model through the UBL helpers and the EDI exchange type configuration. No new menus or screens are added by this module; the feature is used through the existing EDI exchange configuration and the purchase order UBL actions.
Models and fields (1)
- edi.output.ubl.purchase.order · new model
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/edi-framework.
terminal Installation and usage
No verified informationInstallation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.