Skip to Content
Menu

ANSI X12 EDI Odoo Integration

by
Odoo

625.76

v 17.0 Third Party
Live Preview
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Purchase (purchase)
Invoicing (account)
Discuss (mail)
Inventory (stock)
Community Apps Dependencies
Lines of code 1842
Technical Name edi_ansi_x12_odoo_integration
LicenseOPL-1
Websitehttps://www.vrajatechnologies.com
Versions 16.0 17.0 18.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Purchase (purchase)
Invoicing (account)
Discuss (mail)
Inventory (stock)
Community Apps Dependencies
Lines of code 1842
Technical Name edi_ansi_x12_odoo_integration
LicenseOPL-1
Websitehttps://www.vrajatechnologies.com
Versions 16.0 17.0 18.0
Enterprise Community Odoo.sh

ANSI X12 EDI Odoo Integration

Automates EDI ANSI X12 integration by exporting Purchase Orders and importing Bills and ASN PO acknowledgement, PO Functional acknowledgement and, Vendor Pricelist via FTP, ensuring accurate data synchronization with Odoo.

Recommended Solutions

Export different version of the Purchase Orders.
Import Functional acknowledgement, PO acknowledge, bill, ASN and vendor Pricelist.
Utilize the EDI ANSI X12 file format for seamless data exchange.
Supports FTP communication protocols for secure data transfer.

Upon Installing the application, you can see the FTP/SFTP Syncing menu.

You have to configure the FTP on the left side and on the right side you have to configure the file paths for import and export with Receiver ID. You also have to create schedule actions for import purpose.

These are your schedule actions for importing file and process them accordingly.

This is where you have to give partner's ID to reflect in import/export format.

You can export 850 at the time of PO in RFQ state from provided button.

After successfully exporting the 850 format, you can see the confirmation on chatter box with FTP used to export PO in page view. Now, 860 export button is also visible and PO state becomes RFQ Sent.

If you have selected the 997 confirmation required, then you should run this schedule action to validate the 850 PO.

After successfully validating the PO you can see that in the chatter box that PO is functionally validated.

If changes in PO, you can export 860 as well. You have to choose from the selection on a given field what you have changed from 850.

After export, you can see that file in the chatter box with the message suggesting the same.

After successfully validating the PO you can see that in the chatter box that PO is functionally validated.

Now, This schedule action is for PO Acknowledgement.

After successfully acknowledgement of the PO, you can see that PO is confirmed with message that shows the file name from which it was confirmed as well.

This schedule action is for importing the bill for PO.

After successfully importing of the bill, you can see that smart button on the PO.

This is the vendor bill created from the imported file.

This schedule action is for importing the ASN (Advanced Ship Notice).

You can jump to the receipts of the PO from this smart button.

After successfully importing of the ASN, you can see the tracking number on the receipt.

The delivered Quantities are also updated from the ASN import schedule action.

This Schedule action is for importing the vendor price list to the Odoo database for your products.

This vendor pricelist is created from the schedule action that fetches pricelist from the FTP.

You can view the logs under the FTP/SFTP Syncing menu under Log Details.

I need an extra customization in this application, how can I get it?
  • Yes, you can contact us on support@vrajatechnologies.com or can schedule a DEMO with our team to customize additional features.
Is the application compatible with Odoo Enterprise and Community?
  • Yes, this application module is supported by both. It is also compatible with test and production environments.
Do I get free upgrades and support if I purchase this application?
  • We provide free support for the first 90 days following the purchase date.
Is technical knowledge required to set up the integration?
  • While some technical understanding may be helpful, the integration is designed to be user-friendly. Detailed documentation and support may be provided to aid in the setup process.
Is this free customization and implementation?
  • Our team has produced a support video that guides you through the implementation process step by step. If you encounter any issues, please feel free to contact us for assistance.
Which protocol you have used to transfer file?
  • We have used FTP protocol to transfer files.
Have we used the functional Acknowledgement for this process.
  • Yes, We have used the proper flow that includes the Functional Validation as well.
Can we see the exported file? If yes, where?
  • Yes, you can view or download the exported file from the Purchase Order message post as shown in the screenshots.
Do we get any confirmation or message after schedule action performs its tasks?
  • Yes, we have managed logs for all the process whether it is export or import.
Can we create/update the vendor Pricelist ?
  • Yes, you can create/update the vendor Pricelist from its schedule 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

Vraja Technologies Services 

Odoo Implementation
Odoo App  Integration Services
Odoo Customization
Odoo Consultation
Odoo Support & Maintenance
Odoo Developer Outsourcing

GET INSTANT PERSONALIZED DEMO

Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.