EDI File Transmission Report
This report is in the EDI group of reports.
The EDI File Transmission (Edisend) report selects vendors designated as X12 capable vendors and transmits serial claim files, book order files, or serial order files to those vendors.
The EDI File Transmission report contains the following tabs.
| • | Basic Tab: Reports |
| • | Vendor Selection Tab |
| • | Vendor Cycle Selection Tab |
By default, vendors with extended information in a NOTE field with the text X12 CAPABLE are selected. When vendors are X12 capable, they have EDI Address fields in their vendor record that determines communication information like the type of transfer such as ftp, login and password information for the vendor, directories where the serial claim file is placed and picked up, and other information used in contacting the vendor. Using the login and directory information in the vendor EDI Address fields, this report automatically transmits the outgoing X12 transaction files to each X12 capable vendor. Transaction types are mapped differently based on the .map files in the REC_TRANS entry of the EDI address.
When the EDI File Transmission report starts to run, the report validates the vendor EDI address fields. If no errors are found, the report log will contain the following messages.
The vendor EDI address will be checked for entries XFER_ADDR, XFER_USER, and XFER_PASS.
0 vendors had missing EDI address entries.
If any of the vendor addresses to be processed by the report is missing the EDI address entries that the report requires, messages similar to the following display in the report log. Supply the missing information, and run the report again.
The vendor EDI address will be checked for entries XFER_ADDR, XFER_USER, and XFER_PASS.
**vendor ID: MAIN|FCT missing required entry XFER_ADDR
**vendor ID: MAIN|FCT missing required entry XFER_USER
**vendor ID: MAIN|FCT missing required entry XFER_PASS
1 vendor record(s) considered.
1 vendors had missing EDI address entries.
When the report runs, the report log includes messages to show how many files were read, how many files were sent, and how many files failed (if any).
Once this file has been sent, you should receive a functional acknowledgment from the vendor, which you may retrieve using the EDI File Retrieval via FTP and process using the EDI File Receipt (Edireceive) report.
For serials claims, prior to running the EDI File Transmission report, prepare the prediction records as usual using the reports in the Serial Group of reports. Run the Prediction as Late (Issuelate) report to mark the issues that are late. Generate the X12 claim file for each X12 capable vendor by running the X12 Serial Claim Transactions (Serclaimx12) report which formats the claim data into the standard X12 format for export.
For book orders, prior to running the EDI File Transmission report, run the Book X12 Orders (Bookorderx12) report in the Acquisitions Group of reports. For serials orders, run the Serials X12 Orders (Serorderx12) report in the Serial Group. These reports create the order files that are to be sent to the vendor.
Related topics