<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ec/edi/ecedi0105s000" xml:lang="en">
   <Header>
      <Title>EDI Messages (ecedi0105s000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to define <Link href="/baanerp/ec/glossary/glossary#000004" role="glossary">messages</Link> used in
		  EDI.</Paragraph>
      </AimSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/basictasks/000005" role="manual">To use a details session</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/ec/onlinemanual/000005" role="manual">Creating EDI messages</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/ec/onlinemanual/000006" role="manual">Using EDI messages</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/ec/onlinemanual/000019" role="manual">Using a single ASCII file</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/ec/onlinemanual/000020" role="manual">Using multiple ASCII files</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/ec/onlinemanual/000018" role="manual">EDI message levels and file layouts</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="ecedi005.mess">
         <Header>
            <Title>EDI Message</Title>
         </Header>
         <FuncDesc>An electronic document (for example, an electronic order
		acknowledgment) that consists of an organization and a message.</FuncDesc>
         <SimpleSection>
            <Paragraph>Incoming and/or outgoing messages are processed in specific
		  libraries invoked by EDI communication sessions (for example, in the Sales
		  Control (SLS), Sales Invoicing (SLI), Accounts Payable (ACP), Cash Management
		  (CMG), Purchase Control (PUR), Inventory Handling (INH), and Electronic Data
		  Interchange (EDI) modules).</Paragraph>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>Depending on the
			 direction, it identifies an incoming or outgoing message.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="ecedi005.dsca">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi005.chgo">
         <Header>
            <Title>Change Order</Title>
         </Header>
         <FuncDesc>If this check box is selected, the message represents or refers
		  to an order change request.</FuncDesc>
         <SimpleSection>
            <Paragraph>If this check box is
			 cleared, the message represents or refers to a new order request.</Paragraph>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>This field is
			 relevant for the order and order acknowledgment messages: outgoing purchase
			 orders, incoming sales orders, and incoming and outgoing order acknowledgments.</Paragraph>
         </Note>
         <SimpleSection>
            <SectionTitle>Example</SectionTitle>
            <Paragraph>If the message is an
			 incoming order, an existing sales order will be updated with the data specified
			 in the message (examples of this include the ANSI X12 860 and the UN/EDIFACT
			 ORDCHG). If the message is an outgoing order acknowledgment, this field can be
			 used to indicate that the message is in response to a received order change
			 message, for example the ANSI X12 865. If the message is an incoming order, a
			 new sales order will be generated with the data specified in the message
			 (examples of this include the ANSI X12 850 and the UN/EDIFACT ORDERS). If the
			 message is an outgoing order acknowledgment, this field can be used to indicate
			 that the message is in response to a received new order request, for example
			 the ANSI X12 855, and the UN/EDIFACT ORDRSP.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="ecedi005.sesi">
         <Header>
            <Title>Library Incoming</Title>
         </Header>
         <FuncDesc>The object name of the library (DLL) that is used to convert
		  incoming messages into data in the ERP Enterprise application. Examples of libraries
		  used to process the EDI messages, converting message data from and to the ERP Enterprise application include the following:</FuncDesc>
         <SimpleSection>
            <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
               <THEAD noTR="1">
                  <TR no="1" isLast="true">
                     <TD rowspan="1" colspan="1">-</TD>
                     <TD rowspan="1" colspan="1">Incoming</TD>
                     <TD rowspan="1" colspan="1">Outgoing</TD>
                  </TR>
               </THEAD>
               <TBODY noTR="10">
                  <TR no="1" isLast="false">
                     <TD rowspan="1" colspan="1">Orders</TD>
                     <TD rowspan="1" colspan="1">otdslsdll4280</TD>
                     <TD rowspan="1" colspan="1">otdpurdll4280</TD>
                  </TR>
                  <TR no="2" isLast="false">
                     <TD rowspan="1" colspan="1">Acknowledgments</TD>
                     <TD rowspan="1" colspan="1">otdpurdll4281</TD>
                     <TD rowspan="1" colspan="1">otdslsdll4281</TD>
                  </TR>
                  <TR no="3" isLast="false">
                     <TD rowspan="1" colspan="1">Shipment Notices</TD>
                     <TD rowspan="1" colspan="1">owhinhdll3201</TD>
                     <TD rowspan="1" colspan="1">owhinhdll4231</TD>
                  </TR>
                  <TR no="4" isLast="false">
                     <TD rowspan="1" colspan="1">Error Notifications</TD>
                     <TD rowspan="1" colspan="1">owhinhdll4232</TD>
                     <TD rowspan="1" colspan="1">oecedidll3201</TD>
                  </TR>
                  <TR no="5" isLast="false">
                     <TD rowspan="1" colspan="1">Receipt Discrepancies</TD>
                     <TD rowspan="1" colspan="1">owhinhdll3221</TD>
                     <TD rowspan="1" colspan="1">owhinhdll3220</TD>
                  </TR>
                  <TR no="6" isLast="false">
                     <TD rowspan="1" colspan="1">Invoices</TD>
                     <TD rowspan="1" colspan="1">otfacpdll1250</TD>
                     <TD rowspan="1" colspan="1">ocislidll2003</TD>
                  </TR>
                  <TR no="7" isLast="false">
                     <TD rowspan="1" colspan="1">Schedules (planning and shipping releases)</TD>
                     <TD rowspan="1" colspan="1">otdslsdll4284</TD>
                     <TD rowspan="1" colspan="1">otdpurdll4283</TD>
                  </TR>
                  <TR no="8" isLast="false">
                     <TD rowspan="1" colspan="1">Sequenced Schedules</TD>
                     <TD rowspan="1" colspan="1">owhinhdll4283</TD>
                     <TD rowspan="1" colspan="1">otdpurdll4283</TD>
                  </TR>
                  <TR no="9" isLast="false">
                     <TD rowspan="1" colspan="1">Remittance Advice</TD>
                     <TD rowspan="1" colspan="1">otfcmgdll5201</TD>
                     <TD rowspan="1" colspan="1">-</TD>
                  </TR>
                  <TR no="10" isLast="true">
                     <TD rowspan="1" colspan="1">Receive Message Status</TD>
                     <TD rowspan="1" colspan="1">ecedidll7280</TD>
                     <TD rowspan="1" colspan="1">-</TD>
                  </TR>
               </TBODY>
            </TABLE>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="sesi.dsca">
         <Header>
            <Title>Library Incoming</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi005.seso">
         <Header>
            <Title>Library Outgoing</Title>
         </Header>
         <FuncDesc>The object name of the library (DLL) that is used to convert
		  data from the ERP Enterprise application into message data. Examples of libraries used
		  to process the EDI messages, converting message data from and to the ERP Enterprise application include the following:</FuncDesc>
         <SimpleSection>
            <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
               <THEAD noTR="1">
                  <TR no="1" isLast="true">
                     <TD rowspan="1" colspan="1">-</TD>
                     <TD rowspan="1" colspan="1">Incoming</TD>
                     <TD rowspan="1" colspan="1">Outgoing</TD>
                  </TR>
               </THEAD>
               <TBODY noTR="10">
                  <TR no="1" isLast="false">
                     <TD rowspan="1" colspan="1">Orders</TD>
                     <TD rowspan="1" colspan="1">otdslsdll4280</TD>
                     <TD rowspan="1" colspan="1">otdpurdll4280</TD>
                  </TR>
                  <TR no="2" isLast="false">
                     <TD rowspan="1" colspan="1">Acknowledgments</TD>
                     <TD rowspan="1" colspan="1">otdpurdll4281</TD>
                     <TD rowspan="1" colspan="1">otdslsdll4281</TD>
                  </TR>
                  <TR no="3" isLast="false">
                     <TD rowspan="1" colspan="1">Shipment Notices</TD>
                     <TD rowspan="1" colspan="1">owhinhdll3201</TD>
                     <TD rowspan="1" colspan="1">owhinhdll4231</TD>
                  </TR>
                  <TR no="4" isLast="false">
                     <TD rowspan="1" colspan="1">Error Notifications</TD>
                     <TD rowspan="1" colspan="1">owhinhdll4232</TD>
                     <TD rowspan="1" colspan="1">oecedidll3201</TD>
                  </TR>
                  <TR no="5" isLast="false">
                     <TD rowspan="1" colspan="1">Receipt Discrepancies</TD>
                     <TD rowspan="1" colspan="1">owhinhdll3221</TD>
                     <TD rowspan="1" colspan="1">owhinhdll3220</TD>
                  </TR>
                  <TR no="6" isLast="false">
                     <TD rowspan="1" colspan="1">Invoices</TD>
                     <TD rowspan="1" colspan="1">otfacpdll1250</TD>
                     <TD rowspan="1" colspan="1">ocislidll2003</TD>
                  </TR>
                  <TR no="7" isLast="false">
                     <TD rowspan="1" colspan="1">Schedules (planning and shipping releases)</TD>
                     <TD rowspan="1" colspan="1">otdslsdll4284</TD>
                     <TD rowspan="1" colspan="1">otdpurdll4283</TD>
                  </TR>
                  <TR no="8" isLast="false">
                     <TD rowspan="1" colspan="1">Sequenced Schedules</TD>
                     <TD rowspan="1" colspan="1">owhinhdll4283</TD>
                     <TD rowspan="1" colspan="1">otdpurdll4283</TD>
                  </TR>
                  <TR no="9" isLast="false">
                     <TD rowspan="1" colspan="1">Remittance Advice</TD>
                     <TD rowspan="1" colspan="1">otfcmgdll5201</TD>
                     <TD rowspan="1" colspan="1">-</TD>
                  </TR>
                  <TR no="10" isLast="true">
                     <TD rowspan="1" colspan="1">Receive Message Status</TD>
                     <TD rowspan="1" colspan="1">ecedidll7280</TD>
                     <TD rowspan="1" colspan="1">-</TD>
                  </TR>
               </TBODY>
            </TABLE>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="seso.dsca">
         <Header>
            <Title>Library Outgoing</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi005.rtyp">
         <Header>
            <Title>Release Type</Title>
         </Header>
         <FuncDesc>The schedule release type to which this message corresponds.
		  This field is used only in schedule-related messages (the ANSI X12 830, 862,
		  866, or the UN/EDIFACT DELFOR, DELJIT messages).</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi005.ptyp">
         <Header>
            <Title>Incoming Message Processing Type</Title>
         </Header>
         <FuncDesc>Indicate the way in which the incoming EDI messages will be
		  processed.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>The value defined
			 here, at the message level, serves as the default value for the <GUIRef href="/baanerp/ec/edi/ecedi0111s000" role="session">EDI Messages Supported by Business Partner (ecedi0111s000)</GUIRef> session.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="ecedi005.file">
         <Header>
            <Title>File Layout</Title>
         </Header>
         <FuncDesc>The type of <Link href="/baanerp/ec/glossary/glossary#000006" role="glossary">file layout</Link> used for the
		  specific EDI message.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ec/onlinemanual/000019" role="manual">Using a single ASCII file</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/ec/onlinemanual/000020" role="manual">Using multiple ASCII files</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="ecedi005.ipos">
         <Header>
            <Title>Level Identification Position</Title>
         </Header>
         <FuncDesc>The position in the message (ASCII file) record of the Level
		  Identification field defined in the <Link href="/baanerp/ec/edi/ecedi5112m000" role="session">Conversion Setups (Relationships) (ecedi5112m000)</Link> session. This can be the starting position of the field
		  or the field number, depending on the field type specified in the <GUIRef href="/baanerp/ec/edi/ecedi0120s000" role="session">Networks (ecedi0120s000)</GUIRef> session.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>You must check the
			 message's conversion setup definition to ensure that no other field is defined
			 as residing in the same position(s). This field only applies if the File Layout
			 field is Single, and is used in the processing of incoming single-file
			 messages.</Paragraph>
         </Note>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ec/onlinemanual/000018" role="manual">EDI message levels and file layouts</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="ecedi005.leng">
         <Header>
            <Title>Level Identification Length</Title>
         </Header>
         <FuncDesc>The length of the Level Identification field defined in the <GUIRef href="/baanerp/ec/edi/ecedi5112m000" role="session">Conversion Setups (Relationships) (ecedi5112m000)</GUIRef> session.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>The maximum length
			 is six. This field only applies if the File Layout field is Single and the
			 Field Type field in the <GUIRef href="/baanerp/ec/edi/ecedi0120s000" role="session">Networks (ecedi0120s000)</GUIRef> session is Fixed Length.</Paragraph>
         </Note>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ec/onlinemanual/000018" role="manual">EDI message levels and file layouts</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
   </Fields>
</Session>