<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/da/xch/daxch0101s000" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Exchange Schemes (daxch0101s000)</Title>
	</Header>
	<HelpTopic xml:lang="en"><AimSection><Paragraph class="Default">
                                 Use this session to maintain <Link href="/baanerp/da/glossary/glossary#000003" role="glossary">exchange schemes</Link>.</Paragraph>
		</AimSection>
		<GeneralSection><Tip><SectionTitle>Tip</SectionTitle>
				<Paragraph class="Default">Use multilevel <Link href="/baanerp/da/glossary/glossary#000003" role="glossary">exchange schemes</Link> to avoid copying a complete <Link href="/baanerp/da/glossary/glossary#000003" role="glossary">exchange scheme</Link> structure.</Paragraph>
			</Tip>
			<Paragraph class="Default">To create an <Link href="/baanerp/da/glossary/glossary#000003" role="glossary">exchange scheme</Link>, do as follows: Use the <GUIRef href="" role="manual">General</GUIRef> tab to define general data.</Paragraph>
			<ProcedureList><ListItem>Define the location of the exchange programs and <Link href="/baanerp/da/glossary/glossary#000011" role="glossary" Update="No">physical ASCII files</Link> under <GUIRef href="" role="manual">Paths</GUIRef>
				</ListItem>
				<ListItem>Specify the details of the <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII files</Link> under <GUIRef href="" role="manual">ASCII File Configuration</GUIRef>
				</ListItem>
			</ProcedureList>
			<Paragraph class="Default">Use the <GUIRef href="" role="manual">Special</GUIRef> tab to define additional data, if required.</Paragraph>
			<Paragraph class="Default">Enter the name of the parent <Link href="/baanerp/da/glossary/glossary#000003" role="glossary">exchange scheme</Link> if you are using a multilevel <Link href="/baanerp/da/glossary/glossary#000003" role="glossary">exchange scheme</Link> Define the subdirectories that can be overruled under <GUIRef href="" role="manual">Overrule Subdirectories</GUIRef> Define additional details under <GUIRef href="" role="manual">Text, Multi-Byte, Float and Log settings</GUIRef>
			</Paragraph>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">If you want to add more information, click the Text button on the toolbar to start the text editor.</Paragraph>
			</Note>
		</GeneralSection>
		<RelatedTopics><SectionTitle>
                                 Related topics
                              </SectionTitle>
			<RelTopic><Link href="/baanerp/basictasks/000005" role="manual">To use a details session</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/da/onlinemanual/000001" role="manual">Introduction to the Exchange module</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/da/onlinemanual/000002" role="manual">Introduction to the master data business object</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/da/onlinemanual/000012" role="manual">To use multilevel exchange schemes</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/da/onlinemanual/000013" role="manual">Relation between logical ASCII files and physical ASCII files</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/da/onlinemanual/000014" role="manual">To store exchange programs and files in BAAN</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/da/onlinemanual/000015" role="manual">Differences and resemblances between regular and non-regular exchanges</Link>
			</RelTopic>
		</RelatedTopics>
	</HelpTopic>
	<Fields><FieldHelp ID="daxch001.cxch"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Exchange Scheme</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/da/glossary/glossary#000003" role="glossary">exchange scheme</Link> code.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="daxch001.dsca"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Description</Title>
			</Header>
			<FuncDesc>Enter a description for the <Link href="/baanerp/da/glossary/glossary#000003" role="glossary">exchange scheme</Link>.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="daxch001.ownr"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Owner</Title>
			</Header>
			<FuncDesc>With the <GUIRef href="/baanerp/da/xch/daxch0501m000#daxch001.ownr" role="manual">Owner</GUIRef> field, you can group and sort exchange schemes in a company.</FuncDesc>
			<SimpleSection><Paragraph class="Default">The default value is your ERP LN user code. This way you can use this field to specify the ERP LN user who owns the exchange scheme. However, the value you define does not have to be an ERP LN user. You can use any name to group the exchange schemes, such as 'actual' for schemes that are actually in use, and 'test' for schemes being tested. Or 'financials' for schemes transferring financial data and 'logistics' for schemes transferring logistical data. On the <GUIRef href="/baanerp/da/xch/daxch0501m000" role="session">Exchange Schemes (daxch0501m000)</GUIRef> overview session’s <GUIRef href="" role="manual">View</GUIRef> menu you can select <GUIRef href="" role="manual">Sort by &gt; Exchange Scheme by Owner</GUIRef>.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="text.available"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Exchange Scheme Text</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, additional information is available for this <Link href="/baanerp/da/glossary/glossary#000003" role="glossary">exchange scheme</Link>. The information is generated in the text editor.</FuncDesc>
			<SimpleSection><Paragraph class="Default">Click Text to start the text editor.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="daxch001.opth"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Exchange Programs</Title>
			</Header>
			<FuncDesc>Define the path where the exchange programs are stored.</FuncDesc>
			<SimpleSection><Paragraph class="Default">You can define a path here once and ERP LN will automatically use it on the fields where the exchange program is required. So, you do not have to enter the full path again.</Paragraph>
				<Paragraph class="Default">The path must always be an <Link href="/baanerp/da/glossary/glossary#000017" role="glossary">absolute path</Link>, starting from the root directory.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<List><ListItem>If this field is changed you do not have to generate the import program or the export program again.</ListItem>
					<ListItem>The character # in the path is converted to the current company number during compilation and during execution.</ListItem>
					<ListItem>Environment variables must be placed between {}. For example, ${HOME}/exchange.</ListItem>
				</List>
			</Note>
		</FieldHelp>
		<FieldHelp ID="daxch001.epth"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Errors / Log Files</Title>
			</Header>
			<FuncDesc>Define the path where the error log files are stored.</FuncDesc>
			<SimpleSection><Paragraph class="Default">You can define a path here once and ERP LN will automatically use it on the fields where the exchange program is required. So, you do not have to enter the full path again.</Paragraph>
				<Paragraph class="Default">The path must always be an <Link href="/baanerp/da/glossary/glossary#000017" role="glossary">absolute path</Link>, starting from the root directory.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<List><ListItem>If this field is changed you do not have to generate the import program or the export program again.</ListItem>
					<ListItem>The character # in the path is converted to the current company number during compilation and during execution.</ListItem>
					<ListItem>Environment variables must be placed between {}. For example, ${HOME}/exchange.</ListItem>
				</List>
			</Note>
			<RelatedTopics><SectionTitle>
                                    Related topics
                                 </SectionTitle>
				<RelTopic><Link href="/baanerp/da/onlinemanual/000009" role="manual">To use conditions in the exchange module</Link>
				</RelTopic>
			</RelatedTopics>
		</FieldHelp>
		<FieldHelp ID="daxch001.spth"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">ASCII Files</Title>
			</Header>
			<FuncDesc>Define the path where the sequential <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII files</Link> are stored. These files are also referred to as <Link href="/baanerp/da/glossary/glossary#000011" role="glossary" Update="No">physical ASCII files</Link>.</FuncDesc>
			<SimpleSection><Paragraph class="Default">You can define a path here once and ERP LN will automatically use it on the fields where the exchange program is required. So, you do not have to enter the full path again.</Paragraph>
				<Paragraph class="Default">The path must always be an <Link href="/baanerp/da/glossary/glossary#000017" role="glossary">absolute path</Link>, starting from the root directory.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<List><ListItem>If this field is changed you do not have to generate the import program or the export program again.</ListItem>
					<ListItem>The character # in the path is converted to the current company number during compilation and during execution.</ListItem>
					<ListItem>Environment variables must be placed between {}. For example, ${HOME}/exchange.</ListItem>
				</List>
			</Note>
			<RelatedTopics><SectionTitle>
                                    Related topics
                                 </SectionTitle>
				<RelTopic><Link href="/baanerp/da/onlinemanual/000013" role="manual">Relation between logical ASCII files and physical ASCII files</Link>
				</RelTopic>
			</RelatedTopics>
		</FieldHelp>
		<FieldHelp ID="daxch001.dpth"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Definition Files</Title>
			</Header>
			<FuncDesc>Define the path where the data <Link href="/baanerp/da/glossary/glossary#000007" role="glossary">definition file</Link> of the sequential <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII files</Link> is stored.</FuncDesc>
			<SimpleSection><Paragraph class="Default">You can define a path here once and ERP LN will automatically use it on the fields where the exchange program is required. So, you do not have to enter the full path again.</Paragraph>
				<Paragraph class="Default">The path must always be an <Link href="/baanerp/da/glossary/glossary#000017" role="glossary">absolute path</Link>, starting from the root directory.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<List><ListItem>If this field is changed you do not have to generate the import program or the export program again.</ListItem>
					<ListItem>The character # in the path is converted to the current company number during compilation and during execution.</ListItem>
					<ListItem>Environment variables must be placed between {}. For example, ${HOME}/exchange.</ListItem>
				</List>
			</Note>
			<SimpleSection><Paragraph class="Default">If you leave this field empty you must enter the full pathname in the <Link href="/baanerp/da/glossary/glossary#000007" role="glossary">definition file</Link> field in the <GUIRef href="/baanerp/da/xch/daxch0102m000" role="session">ASCII Files (daxch0102m000)</GUIRef> session. If you enter the path of the definition file, you only have to define the file code of the definition file in the <GUIRef href="/baanerp/da/xch/daxch0102m000" role="session">ASCII Files (daxch0102m000)</GUIRef> session.</Paragraph>
				<Paragraph class="Default">This path is always an <Link href="/baanerp/da/glossary/glossary#000017" role="glossary">absolute path</Link>, starting from the root directory. The character # in a <Link href="/baanerp/da/glossary/glossary#000018" role="glossary">relative path</Link> is converted to the company number of the current company to make it absolute.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">Environment variables can be used between brackets.</Paragraph>
			</Note>
			<SimpleSection><Paragraph class="Default">For example: ${HOME}/exchange.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="daxch001.adon"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Based on Audit</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, the data is imported or exported from audit files, instead of ERP LN tables. This option is useful in a multisite environment. This option only shows that an audit is carried out on one or more tables that are imported or exported. There is no check built into the system.</FuncDesc>
			<SimpleSection><Paragraph class="Default">The <Link href="/baanerp/da/glossary/glossary#000008" role="glossary">audit procedure</Link> can be overruled for batches in an <Link href="/baanerp/da/glossary/glossary#000003" role="glossary">exchange scheme</Link> in the <GUIRef href="/baanerp/da/xch/daxch0104m000" role="session">Batches (daxch0104m000)</GUIRef> session. For example, the audit is overruled if a batch contains tables that do not use the <Link href="/baanerp/da/glossary/glossary#000008" role="glossary">audit procedure</Link>.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">If this field is changed, you do not have to generate the import program or the export program again.</Paragraph>
			</Note>
			<RelatedTopics><SectionTitle>
                                    Related topics
                                 </SectionTitle>
				<RelTopic><Link href="/baanerp/da/onlinemanual/000010" role="manual">To use audits in the exchange module</Link>
				</RelTopic>
			</RelatedTopics>
		</FieldHelp>
		<FieldHelp ID="daxch001.audt"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Based on Indicators</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, the first field of each record indicates if the record in the ASCII file must be added, modified, or deleted.</FuncDesc>
			<SimpleSection><Paragraph class="Default">For example: i = insert or add d = delete u = update or modify n = new value</Paragraph>
				<Paragraph class="Default">If the <Link href="/baanerp/da/xch/daxch0101s000#daxch001.adon" role="formfield">Based on Audit</Link> check box is selected, the <Link href="/baanerp/da/xch/daxch0101s000#daxch001.audt" role="formfield">Based on Indicators</Link> check box is automatically selected. The <Link href="/baanerp/da/xch/daxch0101s000#daxch001.ddft" role="formfield">Default Date Format</Link> field is automatically set to <GUIRef href="/baanerp/da/domains/xch.dfor#triton.num" role="option">Date Number</GUIRef>.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="daxch001.ctrl"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Control Character</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, a &lt;CTRL&gt; character is used to separate the <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII file</Link> fields with variable lengths in an ASCII file.</FuncDesc>
			<SimpleSection><Paragraph class="Default">For example, if the letter A is defined in the following field as the separator character, it reads &lt;CTRL&gt;A in the ASCII file.</Paragraph>
				<Paragraph class="Default">If the ASCII file field has a fixed length, this check box is not selected.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">If this field is changed, you do not have to generate the import program or the export program again.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="daxch001.sepa"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Separator Character</Title>
			</Header>
			<FuncDesc>Enter a character to separate the <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII file</Link> fields with variable lengths in an ASCII file.</FuncDesc>
			<AllowedValues><SectionTitle>
                                    Allowed values
                                 </SectionTitle>
				<List><ListItem>Letters in the range [A-Z] if the <GUIRef href="/baanerp/da/xch/daxch0101s000#daxch001.ctrl" role="manual">Control Character</GUIRef> check box is selected.</ListItem>
					<ListItem>Characters like \, ], ^, and _</ListItem>
				</List>
			</AllowedValues>
			<SimpleSection><Paragraph class="Default">For example, if the letter A is defined in the following field as the separator character, it reads &lt;CTRL&gt;A in the ASCII file.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<List><ListItem>If this field is changed, you do not have to generate the import program or the export program again.</ListItem>
					<ListItem>Do NOT use characters that are used in the data fields that have to be exchanged.</ListItem>
				</List>
			</Note>
		</FieldHelp>
		<FieldHelp ID="daxch001.ench"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Enclosing Character</Title>
			</Header>
			<FuncDesc>Define a character to enclose strings in an <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII file</Link>; for example, " ".</FuncDesc>
			<SimpleSection><SectionTitle>
                                    Example
                                 </SectionTitle>
				<Paragraph class="Default">An ASCII file for currency data has a field separator character | and an enclosing character ".</Paragraph>
				<Paragraph class="Default">The record looks as follows:</Paragraph>
				<Formula space-and-orientation="indented-estimated"><Paragraph class="Default"> "USD"|"American Dollars"|"US$"|1.95 </Paragraph>
				</Formula>
				<Paragraph class="Default">The currency code is USD, the description is American Dollars, the currency symbol is US$, and the conversion rate is 1.95.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<List><ListItem>Only use enclosing characters if separator characters are used. It makes no difference if an ASCII file with a fixed record length is used.</ListItem>
					<ListItem>If this field is changed, you do not have to generate the import program or the export program again.</ListItem>
				</List>
			</Note>
		</FieldHelp>
		<FieldHelp ID="daxch001.ddft"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Default Date Format</Title>
			</Header>
			<FuncDesc>The Date Format is defined per field in the <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII file</Link> that is used in an <Link href="/baanerp/da/glossary/glossary#000003" role="glossary">exchange scheme</Link>. If no date format is defined for an ASCII file field, the Default Date Format will be used.</FuncDesc>
			<SimpleSection><Paragraph class="Default">If the ASCII file field is created using ERP LN audit files, the <GUIRef href="" role="manual">Default Date Format</GUIRef> will be set to <GUIRef href="" role="manual">Date Number</GUIRef>.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">If this field is changed, you do not have to generate the import program or the export program again.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="daxch001.mxch"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Parent Exchange Scheme</Title>
			</Header>
			<FuncDesc>Enter the code of the <Link href="/baanerp/da/glossary/glossary#000003" role="glossary">exchange scheme</Link> that is used as the parent in a multilevel exchange scheme.</FuncDesc>
			<SimpleSection><Paragraph class="Default">A parent exchange scheme is useful if you want to make small changes to an existing exchange scheme. You only copy those parts of the scheme that you want to change. The batches and table relations that you do not copy are inherited from the parent exchange scheme.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="daxch001.cpim"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Copy Files before Regular Import from</Title>
			</Header>
			<FuncDesc>Specify the common directory from which you want to import your exchange scheme’s regular import data. Leave this field empty if you don't want to use a common directory. If you want to import the data from an external application, enter the directory used by that application.</FuncDesc>
			<SimpleSection><List><ListIntro>If you define a common directory from which to copy your Exchange Scheme’s regular import files:</ListIntro>
					<ListItem>
                                       ERP LN copies the files from the common directory to the subdirectory of the current import run before the actual import is done.</ListItem>
					<ListItem>
                                       ERP LN only copies files with a file name used in one of you regular import’s active table relations.</ListItem>
					<ListItem>If any files already exist in the subdirectory of the regular import run with the same file name as the files you want to import, the files you import overwrite the existing files.</ListItem>
				</List>
			</SimpleSection>
			<RelatedTopics><SectionTitle>
                                    Related topics
                                 </SectionTitle>
				<RelTopic><Link href="/baanerp/da/onlinemanual/000062" role="manual">Advanced file handling using common directories</Link>
				</RelTopic>
			</RelatedTopics>
		</FieldHelp>
		<FieldHelp ID="daxch001.cpex"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Copy Files after Regular Export to</Title>
			</Header>
			<FuncDesc>Specify a common directory to which ERP LN copies the files of an exchange scheme’s regular export run. Leave this field empty if you don't want to use a common directory. If you want to export the data to an external application, enter the directory used by that application.</FuncDesc>
			<SimpleSection><List><ListIntro>If you define a common directory for your Exchange scheme’s regular exports:</ListIntro>
					<ListItem>
                                       ERP LN copies the files from the subdirectory of the current export run to the common directory after the actual export is done.</ListItem>
					<ListItem>
                                       ERP LN overwrites existing files from your exchange scheme’s previous regular export run, but only in the common directory, not in the regular export directory. ERP LN only overwrites files whose file name occurs in the regular export’s active table relation. This enables you to copy more than one exchange schemes regular export files to the same common directory, so that another ERP LN exchange scheme or external application can combine files of more than one Exchange Scheme.</ListItem>
					<ListItem>If an error in the regular export results in the failure to create a file, the file in the common directory from the regular export’s previous export run is still removed. This prevents the re-importation of the same (old) file from the common directory that was not replaced by the failed file. The error log shows the file creation failed, in which case you must run a non-regular export (and a corresponding non regular import) to exchange the data in the failed file.</ListItem>
				</List>
				<Paragraph class="Default">The files of your Exchange Scheme’s regular export are also exported and stored in a subdirectory (identified by the run number) of the directory you specify in the <GUIRef href="" role="manual">Regular Export Directory</GUIRef> field of the <GUIRef href="" role="manual">Exchange Schemes (daxch0501m000)</GUIRef> details session. ERP LN does not overwrite the files in the <GUIRef href="" role="manual">Regular Export Directory</GUIRef>. You can only remove the files explicitly via the <GUIRef href="" role="manual">Remove ASCII Files (daxch2202m000)</GUIRef> session, which ensures the safety of your regular export data. You can use the <GUIRef href="" role="manual">Regular Export Directory</GUIRef> files to check previous regular export runs.</Paragraph>
			</SimpleSection>
			<RelatedTopics><SectionTitle>
                                    Related topics
                                 </SectionTitle>
				<RelTopic><Link href="/baanerp/da/onlinemanual/000062" role="manual">Advanced file handling using common directories</Link>
				</RelTopic>
			</RelatedTopics>
		</FieldHelp>
		<FieldHelp ID="daxch001.diri"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Regular Import Directory</Title>
			</Header>
			<FuncDesc>Enter the subdirectory that must overrule the default subdirectory for a data import on a regular basis. This enables you to use the same directories for import and export, so that you can directly import the exported <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII files</Link> without moving them to another directory if the <Link href="/baanerp/da/glossary/glossary#000019" role="glossary">run numbers</Link> of the import and export run are identical.</FuncDesc>
			<SimpleSection><Paragraph class="Default">The ASCII files are placed in the default subdirectory during a data export on a regular basis (&lt;exchange scheme&gt;.&lt;run number&gt;.i).</Paragraph>
				<Paragraph class="Default">If the overruling subdirectory already contains files, the ASCII file is placed in the default directory &lt;export subdirectory&gt;.&lt;run number&gt;.</Paragraph>
				<Paragraph class="Default">The subdirectory is located in the ASCII file directory. Exchange reads this parameter at runtime.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<List><ListItem>The subdirectory can only be overruled if the ASCII file name specified in the <GUIRef href="/baanerp/da/xch/daxch0121s000" role="session">Table Relations (Import) (daxch0121s000)</GUIRef> session does not contain an absolute path.</ListItem>
					<ListItem>If this field is changed, you do not have to generate the import program or the export program again.</ListItem>
				</List>
			</Note>
		</FieldHelp>
		<FieldHelp ID="daxch001.dire"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Regular Export Directory</Title>
			</Header>
			<FuncDesc>Enter the subdirectory that must overrule the default subdirectory for a data export on a regular basis. This enables you to use the same directories for import and export, so that you can directly import the exported <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII files</Link> without moving them to another directory if the <Link href="/baanerp/da/glossary/glossary#000019" role="glossary">run numbers</Link> of the import and export run are identical.</FuncDesc>
			<SimpleSection><Paragraph class="Default">The ASCII files are placed in the default subdirectory during a data export on a regular basis (&lt;exchange scheme&gt;.&lt;run number&gt;.i).</Paragraph>
				<Paragraph class="Default">If the overruling subdirectory already contains files, the ASCII file is placed in the default directory &lt;export subdirectory&gt;.&lt;run number&gt;.</Paragraph>
				<Paragraph class="Default">The subdirectory is located in the ASCII file directory. Exchange reads this parameter at runtime.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<List><ListItem>The subdirectory can only be overruled if the ASCII file name specified in the <GUIRef href="/baanerp/da/xch/daxch0121s000" role="session">Table Relations (Import) (daxch0121s000)</GUIRef> session does not contain an absolute path.</ListItem>
					<ListItem>If this field is changed, you do not have to generate the import program or the export program again.</ListItem>
				</List>
			</Note>
		</FieldHelp>
		<FieldHelp ID="daxch001.itxt"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Increase Text Number</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, the text numbers increase when text tables are imported. If this check box is cleared, the text number is not changed. Existing texts are overwritten if this is allowed in the table and field relations. Thus, tables are handled in the same way as other tables.</FuncDesc>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">If this field is changed, you must generate the import program or the export program again.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="daxch001.mbco"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Multi-Byte Conversions</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, table fields of the Multibyte string type are converted to the local character type.</FuncDesc>
			<SimpleSection><Paragraph class="Default">The conversion is done directly after reading the characters in the ASCII file during a data import. When you export, a conversion is done just before the value is written to the ASCII file.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<List><ListItem>Errors during multibyte conversions are not logged.</ListItem>
					<ListItem>If this field is changed, you must generate the import program or the export program again.</ListItem>
				</List>
			</Note>
		</FieldHelp>
		<FieldHelp ID="daxch001.ffmt"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Convert Floats/Doubles</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, the values of the db.float and db.double table fields are converted.</FuncDesc>
			<SimpleSection><Paragraph class="Default">Use this option if you have problems exporting data based on an <Link href="/baanerp/da/glossary/glossary#000008" role="glossary">audit procedure</Link> in a client/server environment that combines a non-Intel application server with an Intel database server.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<List><ListItem>If this field is changed, you do not have to generate the import program or the export program again.</ListItem>
				</List>
			</Note>
		</FieldHelp>
		<FieldHelp ID="daxch001.logs"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Do Additional Logging</Title>
			</Header>
			<FuncDesc>This option is currently not used.</FuncDesc>
		</FieldHelp>
	</Fields>
</Session>
