View source | Discuss this page | Page history | Printable version   

Module:External Data Integration



This module can be used by other extension modules to implement processes to load data from external resources or to extract data to other systems. Typical scenarios are clients where master data like products or customers is managed outside Openbravo or clients that require to send all the transactions (sales, invoices, paymetns,...) to another system. The implementation of these processes can be very different but all of them have a common user interface that is described in this guide.


The configuration is done in the EDL Configuration window for each Client. A record for each EDL Process that is used on the Client has to be created. The header only has the EDL Process field. Note that the module that implements the selected process might include additional fields to fill.

In case the EDL Process generates an output it has to be configured the Output tab. In this tab have to be configured all the output processes required to be executed for each EDL Process. The EDL module includes 2 output types: Debug and WSRest. Debug prints a INFO in the Openbravo log with the output generated by the EDL Process. WSRest allows to configure a REST WebService to send the result of the EDL Process.

In case the EDL Process has the retry enabled it is possible to configure it by checking the Retry Enabled flag. When this is checked 2 additional fields appear:

Bulbgraph.png   Configure the retry options with caution. High numbers can lead to blocks that might affect the performance of other processes until all the retry attempts are done.

The retry is an ability aimed for WSRest output type processes where the configured WebService can be temporarily unreachable.


EDL Requests

Each execution of a EDL Process is called a EDL Request. All the requests are registered in the EDL Request window. The header contains all the information about each request, the main fields are:


If the EDL Process of the request is Asynchronous the data is divided in batches of items. Each batch is stored in a Request Line. Relevant information that can be checked in the Request Line tab is:


If the EDL Process is configured with a Output Process that stores the generated content it can be reviewed in the Output Content tab. Relevant information that can be checked in this tab is:



When a EDL Request process fails it is possible to execute some processes to solve the issues.

Process (request header tab)
It executes again the EDL Request. If the process is asynchronous it is possible to select to execute all the request lines or only those in Error status. Available also in Success requests for example in case it is a Extract process that has failed in the external system so it is required to resend it. Some processes might not be able to reprocess if the required raw data is not properly stored or available.
Available when the Request is in Error status. It discards the EDL Request by updating the status to Voided.
Process (request line tab)
Multiple selection button that processes all the selected request lines.

Retrieved from ""

This page has been accessed 4,196 times. This page was last modified on 27 May 2020, at 12:13. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.