Integration Steps

1. EDI Table integration (From EDI menu)

You need to mention the required details for the incoming/outgoing table.

• Odoo Model: Which Odoo model would you like to perform the operation on?

• Type: Incoming/Outgoing, this table will be used for which kind of operation.

• Main table: You need to enable this option if your configuration is main. For example, to add a sale order record, create a configuration record with the main table option enabled for the sale order model. Additionally, create a separate configuration for the sale order line without enabling the main table option.

• File Type If your XML file having single record then select single. - If your XML file having multiple records then select multiple.

• XML Header: You need to specify the main header name in the XML.

• Search record from this value: To check an existing record, Set the XML element name(s) here. Use the provided value(s) to check if existing records are available. You can specify multiple XML elements, separated by commas.

• Default value: During the import/export process, if you want to include specific values along with the processed data, you should enter these values in dictionary format.

• Auto Apply Shipping Method : Select the delivery carrier that should be automatically applied to the sale order during import.

• Confirm Order? : Enable this option if you want the sale order to be automatically confirmed after it is successfully imported.

• Error/Failure Activity User: Choose the user who will receive an activity notification when an error or failure occurs during the import process.

• Create record if any value not found? : Enable this option if you want the system to create a new record automatically when one or more matching values are not found during the import process.

In Mapping XML Elements with Fields table

• XML Element: You need to enter the exact XML element you want to map with the Odoo field.You can also access values from an XML tag or its attributes using special notation.

  1. For an element like <CustomerName xml:lang="en">Lumber Inc</CustomerName>, use CustomerName/#text to read the value Lumber Inc.

  2. Use @ followed by the attribute name to read an attribute value. For an element like <CustomerReference ref="Customer123"></CustomerReference>, use CustomerReference/@ref to read the value Customer123.

• Selected Model fields: You need to select the field with which you want to map the XML data.

• Field to search for M2O: This field is optional. If you choose a Many2one field for mapping, you have the option to set the inner field of that Many2one model. This helps you search records based on that field; otherwise, the search will use the name field of the Many2one model.

• Is Address?: This field is optional. If you have selected any Address field in the "Selected Model Fields" and you want to check that if that address exists in Odoo or not. If address exists then use that address and if it is not then create that address in the Odoo and use it. If you select this field, you have to enter the subtable as well. Sub table should be of Contact model and configuration will be same as any sub table.

• Sub Table:For a One2Many field, you need to select a subtable where a separate configuration is available for the One2Many fields. (In the subtable, follow the same concept, but you do not need to enable the Main table option. If the "Search record from this value" field is left empty, it will create duplicate One2Many records from the CSV. If you select this option, it will update existing records.)

Main Table

Sub Table

Contact Sub Table for Is Address Field

2. Import Records Process (From FTP/SFTP to Odoo)

Fetch Inner files/attachments from directories through button "Sync Inner Files"

We have also provided a scheduled action option for automation. A scheduled action will be created for each FTP/SFTP configuration, and you can review it using the smart button within the form view. You can configure the execution time according to your requirements.

Before pressing the button or executing the scheduled action, certain configurations must be completed. The details are provided below.

First, in the directory list view, specify which directory will be used for the Download operation, so from those directory we will fetch inner files.

In the directory configuration, there's an option stating, "Daily new file coming in this directory". If a directory receives new files with the same name every day, and you need to fetch and process them in Odoo daily, you should enable this checkbox.

Second, in the directory itself you need to select Mapping Model/Table if you don't want to search using XML header.

We’ve added a feature that allows automatic mapping table search using an XML file’s header. Enable the "Search mapping table using XML header" option in the directory form view to support multiple file formats in one directory. Ensure the mapping table is configured for different XML headers.

After making these selections of download option & mapping Model/table you need to press 'Sync Inner Files' button, that process fetch inner files/attachments from the directories chosen for downloading will be fetched into Odoo, creating Odoo attachments.

Along with FTP/SFTP attachments, EDI transaction records will also be created. (Those records will be processed when the scheduled action executes.)

Additionally, we have implemented a directory-wise auto-sync feature. If you have numerous files across different directories that are marked for download, there is a possibility where the common scheduled action of sync inner files encounters timeouts due to Odoo's processing limits, resulting in incomplete synchronization.

To address this issue, we have provided an option to enable auto-sync on a per-directory basis. Simply click the "Generate Auto Sync" button in the desired directory, and the sync process will run individually for the files within that directory, ensuring complete synchronization. You can review it using the smart button within the form view.

3. To process EDI Transactions through Scheduled Action (Cron)

From the scheduled action, all EDI transactions in the draft state are processed based on the type.

• Incoming type: Records will be created in Odoo.

On successful EDI transaction processed that record will move to the done state, if any issue arises then it will move into the failed state & log will generated to check issue.

Scheduled Action

Incoming record created of Sale Order

Incoming record created of Purchase Order

4. Log management

A log is created for reference in case of any faults during the import/export process.

We also set a scheduled action to delete log records older than 13 days.

5. Sample XML files

Sample Sale order file which gets imported from FTP.

1. Export Records Process (From Odoo to FTP/SFTP)

Firstly you need to do some configuration.

Inside FTP/SFTP Syncing form view you need to enable Upload option beside those directory in which you want to export files from Odoo to FTP/SFTP.

In Configuration table of type outgoing, you need to select partner whom records you need to export.

Fields for Export only

• Add additional search domain: If you want to get the specific records for selected partner to export then you can add the filter here in the form of list of tuples.

• Server Type: Which Server you would like to use for export purpose: FTP/SFTP.

• Trading Partner: When the type is outgoing, you need to select the trading partner/contact from which records of the particular model will be fetched and then exported to FTP/SFTP.

• Export file to FTP/SFTP Directory: When the type is outgoing, and server is FTP or SFTP you need to select the FTP/SFTP directory where you want to export files.

Mapping XML elements level Fields

• Required: If it's enabled, the element is required and will cause an error if the value is missing.

• Character length max: This option allows you to limit the number of characters for a field.

A scheduled action has been created to fetch export records based on the EDI Table configuration of the Trading Partner and Odoo Model, which will then create EDI transaction records in ‘Draft’ state. (Those records will be processed when the scheduled action executes.)

If something goes wrong or required field values are missing, those EDI transaction records will be set to a failed state, and a log will be generated for them. After rectifying the issue, you can recompute the XML content by clicking the 'Re-compute' button. Upon successful recomputation, the XML content will be available, and the state will change to draft.

2. To process EDI Transactions through Scheduled Action (Cron)

From the scheduled action, all EDI transactions in the draft state are processed based on the type.

• Outgoing type: Records will be exported/uploaded to FTP/SFTP from Odoo. Based on the configuration table, the XML file will be uploaded to the directory specified in the configuration.

On successful EDI transaction processed that record will move to the done state, if any issue arises then it will move into the failed state & log will generated to check issue.

Scheduled Action

Outgoing record: XML file is generated and exported to the configured FTP/SFTP directory.

3. Log management

A log is created for reference in case of any faults during the export process.

We also set a scheduled action to delete log records older than 13 days.

1. We are managing a distinct configuration setup for the import multiple records in a single file.

• File Type: Select the option that says "In one file multiple records" to import the multiple records form the same file.

In Mapping XML Elements with Fields table

• XML Element: Enter the exact XML element to map with the Odoo field. Use '/' to separate elements for nested levels.

• Sub EDI Import Table: For importing multiple records in a file, create a table without enabling the main table option, inside that table map Odoo fields to XML elements, and select that table here.

Main Table of Import multiple records in a file

Sub Table

Sub Table of Import Quants

Sample Product file which gets imported from SFTP & having multiple products data in single file.

Sample file of Import Quants

1. Main Table of Export multiple product records in a file

2. Export Multiple Product Records Process

We have given separate process for it, you need to click on 'Export Records' menu, a wizard like this will open.

You need to select mapping model of product variant which you created.

You can select single/multiple product records in products field.

Upon completion of the process, EDI transactions will be created for the Outgoing type. These transactions can be processed manually or automatically through a scheduled action.

Submit a Support Ticket

If you encounter any issues while using our app that are caused by the app itself, we offer complimentary support for 90 days from the date of purchase.

To create a support ticket, please register via the Vraja Technologies Support Email and provide the necessary details so we can assist you in resolving the issue.

Email Us

COPY LINK

support@vrajatechnologies.com

Contact Us

COPY LINK

vrajatechnologies.com/contactus

Support

COPY LINK

vrajatechnologies.com/support-policy