<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/ec/onlinemanual/000065" xml:lang="en">
   <Header>
      <Title>External EDI network communication</Title>
      <Keyword type="header" order="d1e311652">
         <Level1>External EDI network communication</Level1>
      </Keyword>
      <Keyword type="header" order="d1e311655">
         <Level1>Network communication</Level1>
      </Keyword>
      <Keyword type="header" order="d1e311658">
         <Level1>Communication</Level1>
      </Keyword>
      <Keyword type="header" order="d1e311661">
         <Level1>External EDI</Level1>
      </Keyword>
   </Header>
   <GeneralSection>
      <Paragraph>Whenever the interchange
						controller initiates the <GUIRef href="/baanerp/ec/edi/ecedi7205m000" role="session">Direct Network Communication (ecedi7205m000)</GUIRef> session, the interchange controller uses
						semaphores to indicate to the external software/communication software that it
						is currently processing messages.</Paragraph>
      <Paragraph>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.</Paragraph>
      <Paragraph>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).</Paragraph>
      <Paragraph>If the external EDI
						network is set up to generate <Link href="/baanerp/ec/glossary/glossary#000004" role="glossary">EDI messages</Link> 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.</Paragraph>
      <Paragraph>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.</Paragraph>
      <Paragraph>The
						translation/communication software reads any messages created by EDI and
						generates any messages received from external business partners.</Paragraph>
      <Paragraph>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.</Paragraph>
   </GeneralSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/ec/onlinemanual/000064" role="manual">Using the interchange controller</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/ec/onlinemanual/000028" role="manual">Communication</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>