Communications

The Communications functionality enables the file transfer to and from the application. The files can also be sent as attachments in emails.

To configure the communications, these directories must be created at the root level, on the computers used to send and receive files:

  • send: The files to be sent must be saved in this directory.
  • receive: The files that are received are saved in this directory after the files in the work directory are processed.
  • work: The received files are saved in this directory.
  • archive: The copies of the sent files are saved in this directory after the files are sent from the send directory. The files are deleted from the send directory.

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

Mandatory prerequisites

  • Host Computers

    A computer profile must be created for a machine that is used to send or receive files. To configure the host, you must know the IP Address of the computer.

  • Document Profile

    A document profile must be created for each document type to be received. The document profile is used to determine the document type (ASNs, requirements, purchase orders, receipts, mail, and trigger files) and the format (CSV , XML , X12 , EDIFACT , or TEXT ) for which the file is received by the computer.

    You can set up email alerts to notify the suppliers when the files are published. Files in the specified file format can also be attached to an alert. The alerts can be established with or instead of the file transfer.

  • EDI Setup

    For EDIFACT or X12 Users Only If the received files are in EDIFACT or X12 format, you must be set as a trading partner. When a trading partner data is specified, the Supplier Exchange data can be mapped to your files in the EDIFACT or X12 format.

    Note: Set up EDI only if these file formats are used.

Optional prerequisites

  • Schedule

    If you receive files, these files are pushed to your machine as the files are published. For example, if you configure to receive your customer's published demand, when the customer publishes demand, it is stored in the 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 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 the files are sent. The scripts on your computer are written and maintained by you.

    If you use the remote processes, you must set up 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 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.