|
xTuple Connect Product Guide |
|
|
xTuple Connect Product Guide |
| 3.2.2. EDI Forms | ||
|---|---|---|
 | 3.2. Create a Simple EDI Profile |  |
Each EDI Profile needs additional information to describe what information should be sent for different Document Types. These extra details are described using EDI Forms. There should be one EDI Form for each Document Type you want to send using an EDI Profile. For example, our sample EDI Profile is only used to send Invoices, so we created exactly one EDI Form for this EDI Profile.
Our sample EDI Form screen shows the basic information for sending an xTuple ERP report when sending Invoices electronically. This EDI Form definition has the following components:
This EDI Form describes what to do when sending Invoices. The same EDI Profile could have other EDI Forms for sending other Document Types.
Invoices for this EDI Profile will be sent as PDF files generated by running a report. In this case, that report will be whatever the Customer Form Assignment says to use. In this case that will be the report named "Invoice".
The file name is used by the xTuple Connect Batch Manager to create a temporary file and as the name of the email attachment. If not given here, the xTuple Connect Batch Manager will add an appropriate suffix. In this case, the file name will start with the abbreviated type of document, which will be followed by the document number. Since this is a report, the suffix .pdf will be appended. The end result, as you can see in Section 2, “Receiving Invoice Emails with Attachments”, is IN60096.pdf.
| |  | |
| 3.2.1. EDI Tokens |  | 3.3. Setting Up a Customer to Use A Profile |