Table of Contents
The previous chapter showed how to set up xTuple Connect to send Invoices to a particular Customer. However, xTuple Connect is capable of much more. Electronic Data Interchange, or EDI, is a general term that means different things to different people. xTuple Connect has the following EDI capabilities:
Table 5.1. xTuple Connect EDI Summary
File Format | Send by FTP | Send by Email | Receive and Import by FTP | Receive and Import by Email |
---|---|---|---|---|
Comma Separated Values (CSV) with header line | X | X | X | X (requires manual intervention) |
Tab Separated Values (TSV) with header line | X | X | ||
Any single character with header line | X | X | ||
Comma Separated Values (CSV) without header line | X | X | X | X (requires manual intervention) |
Tab Separated Values (TSV) without header line | X | X | ||
Any single character delimiter without header line | X | X | ||
XML | X | X | X | X (requires manual intervention) |
HTML with header line | X | X | X (treat as XML) | X (requires manual intervention) |
HTML without header line | X | X | ||
X | X |
In this chapter we will explore the following aspects of EDI configuration:
More details on building EDI Profiles
Using FTP as the delivery method
Sending delimited text files (e.g. CSV)
Sending HTML and XML files
Designing reusable EDI Profiles
Receiving EDI
Much of the information in this chapter is technical in nature. If you have trouble following the steps described here, please contact your system administrator for assistance.