<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ec/edi/ecedi0100s000" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">EDI Parameters (ecedi0100s000)</Title>
	</Header>
	<HelpTopic><AimSection><Paragraph>Use this session to set <Link href="/baanerp/tc/glossary/glossary#Parameters.tc" role="glossary">parameters</Link> that determine how the Electronic Data Interchange (EDI) module operates.</Paragraph>
		</AimSection>
		<RelatedTopics><SectionTitle>Related topics</SectionTitle>
			<RelTopic><Link href="/baanerp/basictasks/000005" role="manual">To use a details session</Link>
			</RelTopic>
		</RelatedTopics>
	</HelpTopic>
	<Fields><FieldHelp ID="ecedi000.indt"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Effective Date</Title>
			</Header>
			<FuncDesc>The date and time that the parameters are valid. The parameters are valid up to the effective date of a more recent parameter setting.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ecedi000.dsca"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Description</Title>
			</Header>
			<FuncDesc>The description or name of the code.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ecedi000.iedi"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">EDI Implemented</Title>
			</Header>
			<FuncDesc>If this check box is selected, EDI is implemented.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ecedi000.path"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Standard Path</Title>
			</Header>
			<FuncDesc>The directory in which all EDI-related data is located. The actual messages for your company are stored in a series of subdirectories, which will be defined at a later stage (at the network level).</FuncDesc>
			<SimpleSection><List><ListIntro>The directory defined here is the directory:</ListIntro>
					<ListItem>In which the <GUIRef href="/baanerp/ec/edi/ecedi6220m000" role="session">Import EDI Data (ecedi6220m000)</GUIRef> session will search for the defaults.edi file.</ListItem>
					<ListItem>To which the <GUIRef href="/baanerp/ec/edi/ecedi6221m000" role="session">Export EDI Data (ecedi6221m000)</GUIRef> session will write files.</ListItem>
					<ListItem>That serves as the default value for the directories (paths) defined at the network level.</ListItem>
				</List>
			</SimpleSection>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>The directory entered in this field must exist on your system. Once you begin transmitting messages, do not change the standard path identification.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="ecedi000.neta"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Our Identification</Title>
			</Header>
			<FuncDesc>Your own <Link href="/baanerp/ec/glossary/glossary#000013" role="glossary">network address</Link>.</FuncDesc>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>For internal EDI, you can use the company number as an address. For external EDI, the translation/communication software can use the communication address to identify you as the sender of the message.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="ecedi000.orap"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Fixed Part</Title>
			</Header>
			<FuncDesc>The fixed part of your <Link href="/baanerp/ec/glossary/glossary#000015" role="glossary">reference number</Link>.</FuncDesc>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>Once you begin transmitting messages, do not change the way the reference number is created.</Paragraph>
			</Note>
			<RelatedTopics><SectionTitle>Related topics</SectionTitle>
				<RelTopic><Link href="/baanerp/ec/onlinemanual/000017" role="manual">Structuring reference numbers</Link>
				</RelTopic>
			</RelatedTopics>
		</FieldHelp>
		<FieldHelp ID="form.ordp"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Date Format</Title>
			</Header>
			<FuncDesc>The date format used as part of the <Link href="/baanerp/ec/glossary/glossary#000015" role="glossary">reference number</Link>.</FuncDesc>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>When selecting the date format, remember that the reference number consists of 14 positions. Once you begin transmitting messages, do not change the way the reference number is created.</Paragraph>
			</Note>
			<RelatedTopics><SectionTitle>Related topics</SectionTitle>
				<RelTopic><Link href="/baanerp/ec/onlinemanual/000017" role="manual">Structuring reference numbers</Link>
				</RelTopic>
			</RelatedTopics>
		</FieldHelp>
		<FieldHelp ID="ecedi000.orfn"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">First Free Number</Title>
			</Header>
			<FuncDesc>The first free number used in the reference number of the next outgoing message.</FuncDesc>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>You can manually adjust the first free number. Once you begin transmitting messages, do not change the way the reference number is created.</Paragraph>
			</Note>
			<RelatedTopics><SectionTitle>Related topics</SectionTitle>
				<RelTopic><Link href="/baanerp/ec/onlinemanual/000017" role="manual">Structuring reference numbers</Link>
				</RelTopic>
			</RelatedTopics>
		</FieldHelp>
		<FieldHelp ID="ecedi000.afnd"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Action on First Message on New Date</Title>
			</Header>
			<FuncDesc>Choose how to increment sequence numbers.</FuncDesc>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>Because the date is included in the reference number, the number will be unique on a new date, even if the incrementing number is repeated with 0 or 1. You can also keep incrementing the number. In that case, that number tells you how many messages have been generated so far.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="ecedi000.recv"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Store All Received Messages</Title>
			</Header>
			<FuncDesc>If this check box is selected, all received EDI messages are logged in a special ( <Link href="/baanerp/ec/glossary/glossary#000088" role="glossary">store_recv</Link> ) directory.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ecedi000.sent"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Store All Sent Messages</Title>
			</Header>
			<FuncDesc>If this check box is selected, all sent EDI messages are logged in a special ( <Link href="/baanerp/ec/glossary/glossary#000089" role="glossary">store_sent</Link> ) directory.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ecedi000.setl"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Suppress Blank Text Lines on Generation</Title>
			</Header>
			<FuncDesc>If this check box is selected, the empty lines in the text blocks of an outgoing EDI message are suppressed. This function limits the text content to significant information.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ecedi000.segt"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Suppress Blank Generated Text Fields</Title>
			</Header>
			<FuncDesc>If this check box is selected, the blank text lines received in incoming messages are suppressed when creating text on internal documents, limiting the message content to significant information.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ecedi000.sead"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">]</Title>
			</Header>
			<FuncDesc>The order series to use for address codes that are automatically generated by EDI, when specific address information is received on incoming EDI messages.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ecedi000.sesc"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">]</Title>
			</Header>
			<FuncDesc>The user-defined series that will be used when generating incoming sales schedules for incoming EDI schedule-related messages.</FuncDesc>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>This is the series used to create schedule records. Do not confuse this series with the series used to create schedule releases, which is specified at the message by business partner level.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="ecedi000.intm"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Interchange Message</Title>
			</Header>
			<FuncDesc>The name of the dummy message used in various organizations to describe the layout of the interchange header and the joint message overhead.</FuncDesc>
			<RelatedTopics><SectionTitle>Related topics</SectionTitle>
				<RelTopic><Link href="/baanerp/ec/onlinemanual/000015" role="manual">Collecting messages by business partner</Link>
				</RelTopic>
			</RelatedTopics>
		</FieldHelp>
		<FieldHelp ID="ecedi000.intc"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Interchange Header Conversion Setup</Title>
			</Header>
			<FuncDesc>The name of the conversion setup in which the interchange header layout is described. Note This conversion setup must be included in the dummy message in the Interchange Message field.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ecedi000.ovhc"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Message Overhead Conversion Setup</Title>
			</Header>
			<FuncDesc>The name of the conversion setup that contains the layout of the joint message overhead. Note The conversion setup must be included in the dummy message in the Interchange Message field. The conversion setup can identify the overhead in all other messages.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="ecedi000.tryn"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Make Use of Tracefile</Title>
			</Header>
			<FuncDesc>If this check box is selected, <Link href="/baanerp/ec/glossary/glossary#000014" role="glossary">trace files</Link> are generated.</FuncDesc>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>In case of a read or generation error, the log file can provide more insight into the problem. Typically this field is selected during the implementation and testing phases of EDI.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="ecedi000.traf"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Name of Tracefile</Title>
			</Header>
			<FuncDesc><Link href="/baanerp/ec/glossary/glossary#000014" role="glossary" Update="No">trace file</Link>
			</FuncDesc>
			<RelatedTopics><SectionTitle>Related topics</SectionTitle>
				<RelTopic><Link href="/baanerp/ec/onlinemanual/000016" role="manual">Naming tracefiles</Link>
				</RelTopic>
			</RelatedTopics>
		</FieldHelp>
	</Fields>
</Session>
