About Outbound Transactions
Outbound processes include the following:
- Creating records in Infor SyteLine EDI
- Sending data to the translator
- Resending outbound transactions
- Creating outbound reports
- Purging outbound transactions
Posting or printing an appropriate transaction in SyteLine initiates the outbound data flow. This action drives data into the EDI database tables.
The interface then extracts transactions from the EDI database tables and formats them into flat ASCII files that the translator will process.
You may send a customer purchase order acknowledgments. As the interface is processing an incoming purchase order, the system checks to see if the customer is to be sent purchase order acknowledgments. The purchase order acknowledgments are created in the database at the time the purchase orders are posted from EDI to SyteLine or by running the standard system Order Verification Report after the purchase order becomes a customer order in SyteLine.
Demand EDI Outbound Transactions
The Infor SyteLine EDI interface supports the outbound transactions to your customers that are described in these topics:
- Transmitting PO Acknowledgments (Outbound 855/ORDRSP): A copy of the customer order as accepted into SyteLine.
- Creating an EDI Invoice (Outbound 810/INVOIC): A copy of an SyteLine invoice.
- Creating an EDI Advance Ship Notice (Outbound 856/DESADV): A copy of the bill of lading.
Supply EDI Outbound Transactions
The Infor SyteLine EDI interface supports the outbound transactions to your vendors that are described in these topics:
- Creating an EDI Planned Purchase Order (Outbound 830/DELFOR): These transactions are generated from planned orders, which are created by the MRP Planning or APS Planning activity. The Extract EDI Planning Schedules utility reads through the EDI Vendor Profiles records, searching for vendors who are to be sent Planning Schedules. The utility then searches through the Vendor Contracts data for any records where the selected vendor is ranked first (RANK 1). When these items have been identified, the system reads through the EDI planned purchase orders and creates a record for the date and quantity of the planned order.
- Creating an EDI Purchase Order (Outbound 850/ORDERS): These transactions are generated from the SyteLine Purchase Order files. All regular purchase orders are extracted as 850/ORDERS transactions. Blanket purchase orders may be sent as 850/ORDERS if the Export Blanket as Ship Sched field on EDI Vendor Profiles is not selected. When the purchase order print routine is run, the system checks to see if the vendor is to be sent EDI purchase orders. If so, the data is extracted to the EDI database tables for further processing.
- Creating an Outbound EDI Shipping Schedule (Outbound 862/DELJIT): These transactions are generated from blanket purchase orders for vendors who have the Export Blanket as Ship Sched field on EDI Vendor Profiles selected. As is the case with the 850/ORDERS transaction, the data is exported to the EDI database tables when the purchase order print routine is run.
Creating Records in EDI
Infor SyteLine EDI creates a transaction record for outbound files.
Sending Data to the Translator
Data from the EDI database tables is formatted into a flat ASCII file. This formatted file is exported to the translator. The files are named as listed below, where the XXX suffix for datafiles corresponds to the Trading Partner code from the EDI Parameters form (both Supply and Demand), and the HHMM.JJJ indicates the time and Julian date for the archive file.
This table displays the file names for outbound transaction types.
| Trans Type | Data Dir Filename | Archive Dir Filename |
|---|---|---|
| 810 (Header) | IINV_HDR.XXX | INVH(HHMM.JJJ) |
| 810 (Detail) | IINV_DTL.XXX | INVD(HHMM.JJJ) |
| 830 | 830_WRK.XXX | 830(HHMM.JJJ) |
| 850 | 850_WRK.XXX | 850(HHMM.JJJ) |
| 855 | 855_IMP.XXX | ACK(HHMM.JJJ) |
| 856 (Header) | SSEQ_HDR.XXX | SEQH(HHMM.JJJ) |
| 856 (Detail) | SSEQ_DTL.XXX | SEQD(HHMM.JJJ) |
| 862 | 862_WRK.XXX | 862(HHMM.JJJ) |
Resending Outbound Transactions
If necessary, Infor SyteLine EDI can resend the outbound file. You can determine the range of information to be included in the files, and the program sets the Posted flag to No, at which time you can resend the outbound transactions.
Creating Outbound Reports
Infor SyteLine EDI creates reports on the outbound transactions according to the ranges that you specify.
Purging Outbound Transactions
Infor SyteLine EDI's purge utilities allow you to purge outbound files according to selected ranges. You can delete posted transactions only.