External EDI network communication

Whenever the interchange controller initiates the Direct Network Communication (ecedi7205m000) session, the interchange controller uses semaphores to indicate to the external software/communication software that it is currently processing messages.

The semaphore mechanism uses empty files in the command directory of the network to indicate that a certain process is active or ready for activation. This mechanism ensures that ERP EDI and the communication/translation software do not try to simultaneously access the same files in the same directory.

When the translation/communication software (translator) becomes active, it creates a file called Comm.yes in the command directory. This file lets ERP EDI know that a translator is active (but not necessarily processing).

If the external EDI network is set up to generate EDI messages in addition to importing messages during direct network communication, EDI will first generate outgoing messages. Next, EDI creates a file called Command.fil in the command directory after EDI finishes generating the outgoing messages.

If the process is not currently generating outgoing messages, it will create the Command.fil file upon the activation of direct network communication. The existence of the Command.fil file lets the translation/communication software know that EDI is finished processing and that the translation/communication software is free to begin processing.

The translation/communication software reads any messages created by EDI and generates any messages received from external business partners.

Once the messages have been generated, EDI deletes the Command.fil file from the command directory. The lack of the Command.fil file lets EDI know that the translation/communication software has completed its processing and that EDI is free to begin reading incoming messages.