Communications

The Communications component facilitates file transfer to and from the application. Files can be sent (imported) to Supplier Exchange or received (extracted) from Supplier Exchange. Additionally, files can be attached to emails and sent to contact users.

Before configuring the communications, four directories must be created at the root level on the computers used to send and receive files. The directories must be named: send, receive, work, and archive.

Place files to be sent in the send directory. When files are transferred from the send directory, the directory is emptied and copies of the sent files are placed in the archive directory. When files are received to your computer, they are placed in the work directory until fully processed. Then they are moved to the receive directory and the work directory is emptied.

If you are using the same computer to send and receive files, you are only required to create the four directories one time.

Mandatory Components

Host Computers
A computer profile must be created for any machine used to send or receive files. To configure a host computer, you must know the IP Address of your machine.
Document Profile
A document profile record must be created for each document type to be received. In the document profile, you determine which document types (e.g. ASNs, requirements, purchase orders, receipts, mail, and trigger files) are to be received by which computers and their format (CSV, XML, X12, EDIFACT, or TEXT).

In the document profile, you can set up email alerts to alert contact users when files are published. Optionally, the alert can contain the files as an attachment in the specified file format. the alerts can be established with or instead of the file transfer.
EDI Setup - For EDIFACT or X12 Users Only
If the files you receive are in EDIFACT or X12 format, you must set up your customer as a trading partner. Establishing a trading partner record helps map Supplier Exchange data to you and your customer's EDIFACT or X12 format. Do not set up EDI if you do not use either of those formats.

Optional Components

Schedule. If you receive files, they are pushed to your machine as they are published. For example, if you configure Supplier Exchange to receive your customer's published demand, when the customer publishes demand, it is stored in the Supplier Exchange database and then sent through FTP to your computer.
You can choose to manually initiate the file transfer or schedule a receive. This ensures that if there is an error during your customers initial publish, you can still receive the files.
Remote Processes/Trigger Files - For Pre-Processing. Remote processes are not required to successfully integrate Supplier Exchange data into your system. The remote processes provide a way to create trigger files. For the purposes of sending data, trigger files are sent to your host computer to kick off scripts to pre-process data files before they are sent. The scripts on your computer are written and maintained by you.
If you use the remote processes, you must set up Supplier Exchange for you to receive the pre-processing trigger file. You must set up the trigger file as a document profile and schedule it to be periodically transferred.
Remote Processes/Trigger File - For Post-Processing. Remote processes are not required to successfully integrate Supplier Exchange data into your system. The remote processes provide a way to create trigger files. For the purposes of receiving data, a trigger file is sent to your host computer to kick off scripts to post-process data files. The scripts on your computer are written and maintained by you. If you use the remote processes, you must set up the trigger file as a document profile and schedule it to be periodically transferred.