<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/da/onlinemanual/000015" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Differences and resemblances between regular and non-regular exchanges</Title>
		<Keyword ContextSensitive="No"><Level1>Regular export</Level1>
		</Keyword>
		<Keyword ContextSensitive="No"><Level1>Non-regular export</Level1>
		</Keyword>
	</Header>
	<GeneralSection><Paragraph class="Default">
                              ERP LN provides the possibility to exchange data on a <Link href="/baanerp/da/glossary/glossary#000004" role="glossary">regular</Link> or on a <Link href="/baanerp/da/glossary/glossary#000005" role="glossary">non-regular</Link> basis. They perform the same operations, and the resulting <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII files</Link> contain the same data, but they are stored in a different way.</Paragraph>
		<Paragraph class="Default">During an exchange on a non-regular basis, ERP LN uses sequential file directories that are defined in the <GUIRef href="/baanerp/da/xch/daxch0101s000" role="session">Exchange Schemes (daxch0101s000)</GUIRef> session in the <GUIRef href="/baanerp/da/xch/daxch0101s000#daxch001.spth" role="manual">ASCII Files</GUIRef> field. During an exchange on a regular basis, additional subdirectories are used for every run of an exchangescheme to avoid overwriting <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII files</Link> of previous records.</Paragraph>
		<Paragraph class="Default">An exchange on a non-regular basis is often used to test <Link href="/baanerp/da/glossary/glossary#000003" role="glossary">exchange schemes</Link> before they are used on a regular basis in a multisite environment. During an exchange on a non-regular basis, you can select a range of batches or a range of batch sequence numbers that are used to restrict the exchange.</Paragraph>
		<Paragraph class="Default">In an exchange based on a regular basis only complete exchange programs are used. It is not possible to select a range of batches. Complete exchange programs are used to make sure that it is impossible to run only part of an exchange program and to lose any data during the exchange.</Paragraph>
		<Paragraph class="Default">It is important that during data exchanges on a regular basis the correct ASCII files are used. The exchanged ASCII files are stored in additional subdirectories to separate the import program from the export program.</Paragraph>
		<List><ListIntro>These subdirectories are defined as:</ListIntro>
			<ListItem>&lt;the <GUIRef href="/baanerp/da/xch" role="module">Exchange</GUIRef> module-scheme&gt;.&lt;Run number&gt;.i for an import process</ListItem>
			<ListItem>&lt;the <GUIRef href="/baanerp/da/xch" role="module">Exchange</GUIRef> module-scheme&gt;.&lt;Run number&gt;.e for an export process</ListItem>
		</List>
		<Paragraph class="Default">These default subdirectories can be overruled by specifying other names in the <GUIRef href="/baanerp/da/xch/daxch0101s000" role="session">Exchange Schemes (daxch0101s000)</GUIRef> session.</Paragraph>
		<Paragraph class="Default">The subdirectory is not created if the <Link href="/baanerp/da/glossary/glossary#000011" role="glossary">physical ASCII files</Link> that are stored in the directories for exchanges on a regular and non-regular basis do not contain an <Link href="/baanerp/da/glossary/glossary#000017" role="glossary">absolute path</Link> in their path. This means that overwriting is still possible.</Paragraph>
		<Paragraph class="Default">The physical ASCII files are defined in the <GUIRef href="/baanerp/da/xch/daxch0521m000" role="session">Table Relations (Import) (daxch0521m000)</GUIRef> and <GUIRef href="/baanerp/da/xch/daxch0531m000" role="session">Table Relations (Export) (daxch0531m000)</GUIRef> sessions in the <GUIRef href="/baanerp/da/xch/daxch0531m000#daxch031.casf" role="manual">ASCII File</GUIRef> field.</Paragraph>
		<Paragraph class="Default">Unlike the regular export job support, this session is not able to import several exchange runs in one job execution. Thus the job period must be the same as the export period on the other site.</Paragraph>
	</GeneralSection>
</ManualTopic>
