Minimal module used only to avoid issues on the migration to the new splitted model of edi_oca.
Might be removed on 19 but we keep it as part of the transition after the split between EDI and components.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0This module bundles the split EDI framework modules back together so existing installations keep working after the EDI framework was divided into separate parts.
This is a glue module. It does not add any new screen, menu, button, report or business rule of its own; it only makes Odoo load three other modules at the same time: the EDI core, the EDI components and the EDI queue.
Because of this, everything a user sees or does with electronic document exchange comes from those three modules, not from this one. This module exists so that databases and other modules that still expect the old single "edi_oca" package continue to install and upgrade without errors during the transition to the new split structure.
- No new models are defined here.
- No menus, views, actions or scheduled jobs are added here.
- It simply declares a dependency on
edi_core_oca,edi_component_ocaandedi_queue_oca.
The small utility file only re-uses existing helper functions from the core and queue modules (checksum and string normalisation, and the exact job identity for exchange records); it does not introduce new behaviour.
In short: if you install this module, you get the combined EDI functionality provided by its dependencies, and nothing extra. It is intended as a compatibility layer and may be removed in a later version.
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: 6 confirmed, 3 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.