Menu Access
Character: EDI 3 3
GUI: EDI; Tasks or Transactions
This function is used to create documents from transaction sets (i.e.,a group of records
that contain information about a particular invoice, purchase order, etc.) that were
generated by trading partners.
At present, the system can process the following types of incoming documents:
| Transaction Set ID | Description | Converts to |
| 810 | Invoices | A/P Vouchers ("payable-reg" records) |
| 820 | Payment Remittance | Suspended Payments |
| 823 | Lockbox | Suspended Payments |
| 850 | Purchase Orders | Quotations or Sales Orders |
| 864 | Text Messages | Text messages ("edi-txt-msg" records) |
| 875 | Purchase Orders (UCS) | Sales Orders |
| 997 | Functional Acknowledgements | Acknowledges documents that have been sent via EDI |
Note that Suspended Payments (820, 823)
documents and Text Messages (864) create EDI
documents within the EDI module. See their respective topics for more information on how
to handle these documents. The 810 and 850 will create MXP/FrameWORX documents.
The system can process transaction sets from the input files specified for the range of
file locations entered, the transaction set holder file,
or both.
If your communications script has created multiple files to be input then you can set up
the file location to receive them from the same input directory. You may do this by
putting wildcards in the input file name when setting up the file location. Consult the EDI File Location Maintenance function for more
information.
For a more detailed discussion of the receive function see the Receiving EDI Data topic.
Last updated October 20, 2006