Generic Export - Overview
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
The Generic Export capability provides the means to send transactions from SYSPRO to other systems which do not support standard EDI transactions while using the existing EDI infrastructure and transaction processing capabilities. Transactions coming from SYSPRO to other systems may use XML format, or a user-defined format (for example, .csv, text file, etc.) The generic exports use a template system. This is similar to the label control files used by the shipping solution. The templates look like the desired output, but where information needs to be exports, one of the tokens listed below will be used. Some of the tokens such as OrderStart, OrderEnd are not replaced with actual information, but are used to mark loops within the document to allow for multiple orders, shipments, items, packs, etc. If the export format is XML, It is suggested to use these within a <? ?> XML comment to avoid blank lines. Template Tokens |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Tokens are anything within {} within the template file. Each token will be translated to the actual information during the export. Most of the tokens are available to all generic exports, however some are specific to one of the exports. The tokens are not case sensitive.
Click here for an EDI XML-In and Generic Output use case overview PDF |