SyteLine is integrated with anEDI translator. The system imports inbound transactions from the translator and exports outbound transactions to the translator.
The EDI translator interface supports six demand side and six supply side transaction sets. Infor SyteLine EDI complies with the American National Standards Institute (ANSI) X12 and EDIFACT (International) standards. For more information, seeAbout EDI Standards.
The supported transactions are listed below.
| Transaction | X12 Transaction Number | EDIFACT Transaction Name |
|---|---|---|
| Purchase Order (Inbound) | 850 | ORDERS |
| Planning Order (Inbound) | 830 | DELFOR |
| Shipping Order (Inbound) | 862 | DELJIT |
| PO Acknowledgment (Outbound) | 855 | ORDRSP |
| Advance Ship Notice (ASN) (Outbound) | 856 | DESADV |
| Invoice (Outbound) | 810 | INVOIC |
| Transaction | X12 Transaction Number | EDIFACT Transaction Name |
|---|---|---|
| Purchase Order (Outbound) | 850 | ORDERS |
| Planning Order (Outbound) | 830 | DELFOR |
| Shipping Order (Outbound) | 862 | DELJIT |
| PO Acknowledgment (Inbound) | 855 | ORDRSP |
| Advance Ship Notice (ASN) (Inbound) | 856 | DESADV |
| Invoice (Inbound) | 810 | INVOIC |
The SyteLine application database includes tables whose names start with "edi..." that contain the following data:
Data is exchanged between SyteLine and the translator using flat ASCII files. The translator exports orders, which SyteLine imports into its EDI database tables.
To import data from all flat files currently in the IB-Inbound directory into the EDI database tables, use the EDI Transaction Load Routine utility. These files are also archived during the import process.
You can also automatically post EDI customer orders into SyteLine during the import process, if you set up the EDI Customer Profiles form to allow this for certain trading partners. Otherwise, you need to post them manually from the EDI Customer Orders form.
Errors that occur during the import process are sent to the log file (editrans.log). To view any import transmission errors while you are in the EDI Customer Orders form, select Actions > List Error Log.
EXAMPLE: Sample editrans.log
Outbound EDI document data is stored in the EDI database tables. Use the EDI Transaction Unload Routine form to export the data to the corresponding flat ASCII files in the OB-Outbound directory, where it can then be imported into the translator.
If you need to retransmit any outbound document that was already exported, use the Retransmit utilities in SyteLine.
NOTE: You must import any exported data from either SyteLine or the translator to the corresponding system before you can perform any further importing/exporting from either system. This practice ensures data integrity between SyteLine and the translator.