Import EDI Messages

|
Import EDI Messages icon | Refer also to EDI Batch Job in the System Administration Guide. Click the Import EDI Messages icon on the SICS desktop to see the Import EDI Messages window. |

All messages that SICS understands can be read and loaded into the archive from this window. Batches to be imported are read from the Inbox Path folder. When the batch has been loaded successfully, it is moved to the Archive Path folder. The default paths are EDI/Inbox and EDI/Archive. Be sure to create those folders, otherwise you must specify your own paths.

The file list shows all files present in your inbox path folder. If the contents of this folder change, click the Refresh File List button to refresh the list.

Click the Import All button to manually start the import process. To view the contents of a batch that failed the import, select Unparsable from the Status tab in the Find Batch window and click Find Now. Your batch will appear in the display list at the bottom of the window.

When Batches Are Not Processed Properly #

When you click the EDI folder on the SICS desktop, you see an EDI batch icon, an EDI LIMNET message icon and an EDI JVmessage icon. These start the Find: EDI Batches, Find: EDI LIMNET Messages windows and Find: EDI JV Messages windows respectively.

EDI messages are seen at two levels: the batch, and the message level. When you do a search in the Find: Batch window, you are searching at the batch level. You can search for a batch list to determine what to do next in case of a failed validation.

Typically, when you discover that a validation failed, you will go into a Find: Message window to determine what went wrong. If you do not see the source of your problem there, you can check the Find: Batch window and look for the problem at the batch level. It could be, for example, that you received a LIMNET batch number out of sequence.