<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ec/edi/ecedi0111s000" xml:lang="en">
   <Header>
      <Title>EDI Messages Supported by Business Partner (ecedi0111s000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to define <Link href="/baanerp/ec/glossary/glossary#000007" role="glossary">EDI messages</Link> supported by
		  business partners.</Paragraph>
      </AimSection>
      <GeneralSection>
         <List>
            <ListIntro>You can define:</ListIntro>
            <ListItem>Message-related data
			 and processing information.</ListItem>
            <ListItem>Sales-order type and
			 series for incoming messages.</ListItem>
            <ListItem>Item-code system and
			 character conversion for outgoing messages.</ListItem>
         </List>
      </GeneralSection>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>If you want to collect
		  sales orders on EDI invoices, the print settings must be the same for the
		  various sales orders. If not, sales orders cannot be collected on the same
		  invoice.</Paragraph>
      </Note>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/ec/onlinemanual/000007" role="manual">Using EDI messages by business partner</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/ec/onlinemanual/000008" role="manual">Using business partners</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="ecedi011.bpid">
         <Header>
            <Title>Business Partner</Title>
         </Header>
         <FuncDesc>The business partner that will use the <Link href="/baanerp/ec/glossary/glossary#000004" role="glossary">EDI message</Link>.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ec/onlinemanual/000008" role="manual">Using business partners</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tccom100.nama">
         <Header>
            <Title>Business Partner</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi011.orga">
         <Header>
            <Title>Organization</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/ec/glossary/glossary#000003" role="glossary">organization</Link> for which the
		  message code is valid.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>Because several EDI
			 organizations can use the same message, you must link each organization to the
			 supported messages.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="ecedi003.dsca">
         <Header>
            <Title>Organization</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi011.mess">
         <Header>
            <Title>EDI Message</Title>
         </Header>
         <FuncDesc>The code that identifies a <Link href="/baanerp/ec/glossary/glossary#000002" role="glossary">supported EDI message</Link>, as
		  defined in the <GUIRef href="/baanerp/ec/edi/ecedi0105s000" role="session">EDI Messages (ecedi0105s000)</GUIRef> session.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ec/onlinemanual/000002" role="manual">Using supported EDI messages</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="ecedi005.dsca">
         <Header>
            <Title>EDI Message</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi011.io">
         <Header>
            <Title>Direction</Title>
         </Header>
         <FuncDesc>The direction of the EDI message.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi011.koor">
         <Header>
            <Title>Order Type</Title>
         </Header>
         <FuncDesc>The standard external <Link href="/baanerp/ec/glossary/glossary#000017" role="glossary">order type</Link> for a specific <Link href="/baanerp/ec/glossary/glossary#000004" role="glossary">EDI message</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi200.dsca">
         <Header>
            <Title>Order Type</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi011.netw">
         <Header>
            <Title>Network</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/ec/glossary/glossary#000009" role="glossary">network</Link> that is used for the
		  combination of business partner and message.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi020.dsca">
         <Header>
            <Title>Network</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi011.cvsu">
         <Header>
            <Title>Conversion Setup</Title>
         </Header>
         <FuncDesc>A code that defines the layout of the ASCII file that contains
		the message data. This code contains information on the mapping of data
		elements between ERP application tables and the ASCII files. Although
		predefined conversion setups are available, you can create your own custom
		conversion setups.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi500.dsca">
         <Header>
            <Title>Conversion Setup</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi011.user">
         <Header>
            <Title>Person Responsible</Title>
         </Header>
         <FuncDesc>The user assigned to the combination of business partner and
		  message.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>This is for
			 information and reporting purposes, and can be used for approving saved
			 messages to be received.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="user.name">
         <Header>
            <Title>Person Responsible</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi011.nrgr">
         <Header>
            <Title>Number Group</Title>
         </Header>
         <FuncDesc>The number group to which the series applies. The number group
		  is displayed on reports for information, and is used to validate the series
		  entered for incoming and outgoing orders, schedule releases, and shipment
		  notices. The number group entered here for incoming orders, schedule releases,
		  and shipment notices must be consistent with the number group specified for
		  these documents in their respective parameters. Specifically, the number group
		  entered here for incoming orders, must be the number group specified for sales
		  orders in the Number Group Sales Orders field in the <Link href="/baanerp/td/sls/tdsls0100s400" role="session">Sales Order Parameters (tdsls0100s400)</Link> session. The number group specified here for incoming schedule releases must be
		  the number group specified for sales-schedule releases in the Number Group
		  Schedule Releases field in the <Link href="/baanerp/td/sls/tdsls0100s300" role="session">Sales Contract Parameters (tdsls0100s300)</Link> session. The number group specified for incoming shipment notices must be the
		  number group specified for shipments in the Number Group for Shipments field in
		  the <GUIRef href="/baanerp/wh/inh/whinh0100m000" role="session">Inventory Handling Parameters (whinh0100m000)</GUIRef> session.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>Number groups are
			 used to split orders into groups.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tcmcs051.dsca">
         <Header>
            <Title>Number Group</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi011.prnt">
         <Header>
            <Title>Print</Title>
         </Header>
         <FuncDesc>If this check box is selected, a report is printed that contains the data
		  received (incoming message) or the document (outgoing message).</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi011.ptyp">
         <Header>
            <Title>Processing Type</Title>
         </Header>
         <FuncDesc>The way in which the incoming EDI messages will be processed,
		  automatically or interactively.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi011.bloc">
         <Header>
            <Title>Block</Title>
         </Header>
         <FuncDesc>If this check box is selected, the order is blocked for further processing
		  after receipt.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>This applies to
			 incoming orders only. The order must be released before it can be processed any
			 further.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="ecedi011.msno">
         <Header>
            <Title>Check Duplicate Order Numbers</Title>
         </Header>
         <FuncDesc>If this check box is selected, LN checks if a document was received earlier.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListIntro> LN checks:</ListIntro>
               <ListItem>Whether a message
				reference was received earlier from the same business partner.</ListItem>
               <ListItem>If the document
				number (order, invoice) has been previously received.</ListItem>
            </List>
         </Note>
      </FieldHelp>
      <FieldHelp ID="ecedi011.aerr">
         <Header>
            <Title>Automatically Prepare Error Notification</Title>
         </Header>
         <FuncDesc>If this check box is selected, error notification messages will be
		  automatically prepared if errors are found during the validation of the
		  incoming message.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>This only applies to
			 incoming messages.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="ecedi011.sotp">
         <Header>
            <Title>Sales Order Type</Title>
         </Header>
         <FuncDesc>A code used to determine the character or function of an order
		and, consequently, of the message.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>Examples:</ListIntro>
               <ListItem>Normal order versus return order</ListItem>
               <ListItem>Invoice versus credit note</ListItem>
            </List>
            <Paragraph>The classification that determines which sessions (in which
		  sequence) are part of the order procedure. You can also assign one of the
		  following categories to the order type: cost order, collect order, return
		  order, and subcontracting order.</Paragraph>
            <List>
               <ListIntro>Order type codes are required in the ERP EDI messages that
			 relate to a single order. EDI messages that relate to single orders include
			 messages that process:</ListIntro>
               <ListItem>Orders (ANSI X12 850, UN/EDIFACT ORDERS).</ListItem>
               <ListItem>Order changes (ANSI X12 860, UN/EDIFACT ORDCHG).</ListItem>
               <ListItem>Order acknowledgments (ANSI X12 855 and 865, UN/EDIFACT
			 ORDRSP).</ListItem>
               <ListItem>Invoices (ANSI X12 810, UN/EDIFACT INVOIC).</ListItem>
            </List>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>This field is only
			 used for incoming order messages.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="so.dsca">
         <Header>
            <Title>Sales Order Type</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi011.seri">
         <Header>
            <Title>Series</Title>
         </Header>
         <FuncDesc>The number series for the documents. This applies to incoming
		  orders, schedule releases, and shipment notices.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>Number series are
			 defined with the <GUIRef href="/baanerp/tc/mcs/tcmcs0150m000" role="session">First Free Numbers (tcmcs0150m000)</GUIRef> session.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tcmcs050.dsca">
         <Header>
            <Title>Series</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi011.citt">
         <Header>
            <Title>Item Code System</Title>
         </Header>
         <FuncDesc>The item code system that will be used to convert item codes in
		  outgoing messages. The item code can be converted to its alternative item,
		  based on this item code system and the data defined in the <Link href="/baanerp/tc/ibd/tcibd0504m000" role="session">Item Codes by Item Code System (tcibd0504m000)</Link> session. If no value is specified here for the item code
		  system, the default value of the Qualifier 1 field for the item code in the
		  conversion setups will be used to derive the item code system used to convert
		  the item. In this case, the default value for the qualifier is checked against
		  the <GUIRef href="/baanerp/ec/edi/ecedi2132m000" role="session">Item Code IDs (ecedi2132m000)</GUIRef> session to derive the item code system.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcibd006.dsca">
         <Header>
            <Title>Item Code System</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi011.ccon">
         <Header>
            <Title>Character Conversion</Title>
         </Header>
         <FuncDesc>A code used to define how characters from the application
		environment should be transferred to the ASCII files. For example, characters
		can be converted to uppercase, or specific punctuation marks can be ignored in
		an EDI message.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi408.dsca">
         <Header>
            <Title>Character Conversion</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ecedi011.gtcp">
         <Header>
            <Title>Generate - To Company</Title>
         </Header>
         <FuncDesc>If, in a multi-site environment, EDI messages must be sent to
		  another company than the business partner's <Link href="/baanerp/tc/glossary/glossary#AffiliCompan_tc" role="glossary">affiliated company</Link>, use this field to enter the required <Link href="/baanerp/tc/glossary/glossary#Company_tc" role="glossary">company</Link>.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListItem>You can only fill this field if the message is outgoing and
				the entered network is a multi-company network.</ListItem>
               <ListItem>After the company number is entered, LN creates the
				necessary sub directories in the network path.</ListItem>
            </List>
         </Note>
      </FieldHelp>
   </Fields>
</Session>