Ediversa - Sale Order Import
This module extends the base edi_ediversa_oca module to fetch and process Ediversa sale order files.
auto_awesome What this module does
AI-generated from the code · Odoo 17.0Automatically imports sales orders sent by Ediversa into Odoo, creating the customer, delivery and invoice addresses and the order lines from the received file.
This module connects Odoo to the Ediversa EDI platform so that sales orders sent by customers are turned into real sales orders without manual entry.
A scheduled job named "EDI Ediversa: Import Sales" checks the Ediversa platform for each company that has Ediversa enabled and a user and password configured. It looks for documents of type ORDERS and creates an exchange record for each one that has not been imported before, so the same order is never imported twice.
When a record is received, the file is downloaded from Ediversa and marked as downloaded on the platform. The file is then processed: the customer is searched by its Ediversa identifier and created if it does not exist, and the same is done for the delivery and invoice addresses, which are linked to the customer. The order header gets the Ediversa order name as the source document, the order date and the expected delivery date, and any notes. Each order line is matched to a product by barcode; if no product is found with that barcode, the import stops with an error. Quantities, unit prices and descriptions are taken from the file.
The module adds an exchange type "Ediversa - Sale Order Input" and works on sale.order, res.partner and edi.exchange.record. The scheduled job is created inactive, so it must be enabled before it runs.
Depends on
Models and fields (3)
- ediversa.api · extends an existing model
- ediversa.process.sale.order · new model
- ediversa.receive.sale.order · new model
Text generated by AI (DeepSeek) from reading the Odoo 17.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: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 17.0
Confirmed on 2026-11-03 in branch 17.0 of OCA/edi-ediversa.
terminal Installation and usage
OCA documentation · Odoo 17.0Configuration
Source · Odoo 17.0To configure this module, you need to go to Settings \> User & Companies \> Companies and edit a company. Introduce the following information:
- Use Edi Ediversa. Activate this option to use the Ediversa services. Keep in mind that this module does nothing on its own, so it needs to be used along with other modules.
- Edi Ediversa Test. Activate this option if you need to activate the test environment.
- Edi Ediversa User. Ediversa account username. This information can be provided by ediversa.
- Edi Ediversa Password. Ediversa account password. This information can be provided by ediversa.
Usage
Source · Odoo 17.0The fetching/processing flow of the Ediversa sale order files is as follows:
- The scheduled action "EDI Ediversa: Import Sales" generates the EDI exchange records used to fetch the Ediversa sale order file.
- The scheduled action "Edi exchange check input sync" performs 2 actions:
- It fetches the Ediversa sale order files of those EDI exchange records with pending files.
- It creates the sale order records from the EDI exchange records whose Ediversa sale order files have been fetched. In this part of the process, new contacts can be created in case they do not exist in the database yet.
No verified information in OCA: Installation.
Installation 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.