<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/da/xch/daxch0121s000" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Table Relations (Import) (daxch0121s000)</Title>
	</Header>
	<HelpTopic xml:lang="en"><AimSection><Paragraph class="Default">
                                 Use this session to create a relation between ERP LN tables, <Link href="/baanerp/da/glossary/glossary#000006" role="glossary">logical ASCII files</Link>, and <Link href="/baanerp/da/glossary/glossary#000011" role="glossary">physical ASCII files</Link> per <Link href="/baanerp/da/glossary/glossary#000002" role="glossary">batch</Link> in an <Link href="/baanerp/da/glossary/glossary#000003" role="glossary">exchange scheme</Link>.</Paragraph>
		</AimSection>
		<GeneralSection><Paragraph class="Default">Define in the <Link href="/baanerp/da/glossary/glossary#000032" role="glossary">table relation</Link> the <Link href="/baanerp/da/glossary/glossary#000006" role="glossary">logical ASCII files</Link> to which the data from the ERP LN table must be transferred, and assign a name to the <Link href="/baanerp/da/glossary/glossary#000011" role="glossary">physical ASCII file</Link>.</Paragraph>
			<Paragraph class="Default">You can also run an external program or an ERP LN session as part of an <Link href="/baanerp/da/glossary/glossary#000003" role="glossary">exchange scheme</Link>, instead of using the exchange import functionality for a <Link href="/baanerp/da/glossary/glossary#000032" role="glossary">table relation</Link>.</Paragraph>
			<ProcedureList><ListIntro>To create a table relation, do as follows:</ListIntro>
				<ListItem>Enter the sequence number, ERP LN table, <Link href="/baanerp/da/glossary/glossary#000006" role="glossary">logical ASCII</Link> file and the <Link href="/baanerp/da/glossary/glossary#000011" role="glossary">physical ASCII file</Link> name.</ListItem>
				<ListItem>Select the <GUIRef href="/baanerp/da/xch/daxch0121s000#daxch021.actv" role="manual">Active</GUIRef> check box to make the relation active and define an execute <Link href="/baanerp/da/glossary/glossary#000009" role="glossary">condition</Link>.</ListItem>
				<ListItem>Specify under <GUIRef href="" role="manual">Permitted Operations</GUIRef> the actions that are allowed for this <Link href="/baanerp/da/glossary/glossary#000032" role="glossary">table relation</Link>, and the appropriate <Link href="/baanerp/da/glossary/glossary#000009" role="glossary">conditions</Link>.</ListItem>
				<ListItem>Select the <GUIRef href="/baanerp/da/xch/daxch0121s000#daxch021.scon" role="manual">Stop Condition</GUIRef> check box to activate the stop mechanism and define the appropriate stop <Link href="/baanerp/da/glossary/glossary#000009" role="glossary">condition</Link>.</ListItem>
				<ListItem>If you want to use an external program, select the External Program check box and define the program name in the following field. If you want to run an ERP LN session, do not select the check box but enter a session or object code in the following field.</ListItem>
				<ListItem>Enter the number of the <Link href="/baanerp/da/glossary/glossary#000012" role="glossary">index</Link> when one of the <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII file</Link> fields is based on <Link href="/baanerp/da/glossary/glossary#000013" role="glossary">increment</Link>.</ListItem>
			</ProcedureList>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">The relations on field level are created in the <GUIRef href="/baanerp/da/xch/daxch0522m000" role="session">Field Relations (Import) (daxch0522m000)</GUIRef> session.</Paragraph>
			</Note>
		</GeneralSection>
		<RelatedTopics><SectionTitle>
                                 Related topics
                              </SectionTitle>
			<RelTopic><Link href="/baanerp/da/onlinemanual/000003" role="manual">Introduction to the import module</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/da/onlinemanual/000009" role="manual">To use conditions in the exchange module</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>
		</RelatedTopics>
	</HelpTopic>
	<Fields><FieldHelp ID="daxch021.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>
			<SimpleSection><Paragraph class="Default">The exchange scheme is created in the <GUIRef href="/baanerp/da/xch/daxch0501m000" role="session">Exchange Schemes (daxch0501m000)</GUIRef> session.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="daxch021.cbat"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Batch</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/da/glossary/glossary#000002" role="glossary">batch</Link> in an <Link href="/baanerp/da/glossary/glossary#000003" role="glossary">exchange scheme</Link>.</FuncDesc>
			<SimpleSection><Paragraph class="Default">A batch is created in the <GUIRef href="/baanerp/da/xch/daxch0104m000" role="session">Batches (daxch0104m000)</GUIRef> session.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="daxch021.batl"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Table Rel. (Imp.)</Title>
			</Header>
			<FuncDesc>The identification number of the <Link href="/baanerp/da/glossary/glossary#000032" role="glossary">table relation</Link> in the <Link href="/baanerp/da/glossary/glossary#000002" role="glossary">batch</Link> during an exchange process.</FuncDesc>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">The number is increased automatically: when you define a new table relation, ERP LN enters a number of value ten greater than the table relation with the highest value.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="daxch021.seqn"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Sequence Number</Title>
			</Header>
			<FuncDesc>The sequence number of the <Link href="/baanerp/da/glossary/glossary#000032" role="glossary">table relation</Link> in the <Link href="/baanerp/da/glossary/glossary#000002" role="glossary">batch</Link> during an exchange process.</FuncDesc>
			<SimpleSection><Paragraph class="Default">Sequence numbers are used to indicate the processing order of the table relations in a batch. The sequence number does not have to be unique in a table relation.</Paragraph>
				<Paragraph class="Default">If two table relations with an identical sequence number are used in a batch, the relation with the lower table relation number is processed first.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">The number is increased automatically: when you define a new table relation, ERP LN enters a number of value ten greater than the table relation with the highest value.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="daxch021.ttbl"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Table</Title>
			</Header>
			<FuncDesc>Enter the code of the table in ERP LN that contains data from the <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII file</Link> during an <Link href="/baanerp/da/glossary/glossary#000015" role="glossary">import procedure</Link>.</FuncDesc>
			<SimpleSection><Paragraph class="Default">Use multiple table relations to write data from more than one <Link href="/baanerp/da/glossary/glossary#000011" role="glossary">physical ASCII file</Link> to one ERP LN table.</Paragraph>
				<Paragraph class="Default">The ERP LN table name is defined by the package code, a module code and a table number. For example, tcibd001.</Paragraph>
			</SimpleSection>
			<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="daxch021.casf"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">ASCII File</Title>
			</Header>
			<FuncDesc>Enter the code of the <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII file</Link>, that contains data that must be transferred to an ERP LN table, in an <Link href="/baanerp/da/glossary/glossary#000015" role="glossary">import procedure</Link>.</FuncDesc>
			<SimpleSection><Paragraph class="Default">To create the field relations of the <Link href="/baanerp/da/glossary/glossary#000032" role="glossary">table relation</Link> Automatically, it is necessary that the code of the ASCII file is the same as the code of the ERP LN table. This is an option if you do not have a data <Link href="/baanerp/da/glossary/glossary#000007" role="glossary">definition file</Link> of the ASCII file.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">The ASCII file code represents the <Link href="/baanerp/da/glossary/glossary#000006" role="glossary">logical ASCII file</Link>. The ASCII code is created in the <GUIRef href="/baanerp/da/xch/daxch0102m000" role="session">ASCII Files (daxch0102m000)</GUIRef> session.</Paragraph>
			</Note>
			<RelatedTopics><SectionTitle>
                                    Related topics
                                 </SectionTitle>
				<RelTopic><Link href="/baanerp/da/onlinemanual/000001" role="manual">Introduction to the Exchange module</Link>
				</RelTopic>
			</RelatedTopics>
		</FieldHelp>
		<FieldHelp ID="daxch021.nasf"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">ASCII File Name</Title>
			</Header>
			<FuncDesc>Enter the name of the <Link href="/baanerp/da/glossary/glossary#000011" role="glossary">physical ASCII file</Link>.</FuncDesc>
			<SimpleSection><Paragraph class="Default">The entered file name is an extension on the default path. The default path is defined in the field <GUIRef href="/baanerp/da/xch/daxch0101s000#daxch001.spth" role="manual">ASCII Files</GUIRef> under Paths on the <GUIRef href="" role="manual">General</GUIRef> tab in the <GUIRef href="/baanerp/da/xch/daxch0101s000" role="session">Exchange Schemes (daxch0101s000)</GUIRef> session.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<List><ListItem>This path can also be an <Link href="/baanerp/da/glossary/glossary#000017" role="glossary">absolute path</Link>. If that is the case, the default path is not used.</ListItem>
					<ListItem>The maximum length of the file name is 11 characters.</ListItem>
					<ListItem>You do not have to generate the import program again if this field is changed.</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="daxch021.actv"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Active</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, the table relation is active and it can be used for data processing in an import process.</FuncDesc>
			<SimpleSection><Paragraph class="Default">
                                    If this check box is cleared, the table relations are kept for reference purposes but they are not used during the import process.</Paragraph>
				<Paragraph class="Default">You can also select this check box if you want to test the <Link href="/baanerp/da/glossary/glossary#000003" role="glossary">exchange scheme</Link>, a single <Link href="/baanerp/da/glossary/glossary#000032" role="glossary">table relation</Link>, or only a few table relations.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">You do not have to generate the import program again if this field is changed.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="daxch021.econ"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Execute Condition</Title>
			</Header>
			<FuncDesc>Execute conditions are used to check whether the table relation must be executed when running the import process. If the <GUIRef href="/baanerp/da/xch/daxch0121s000#daxch021.actv" role="manual">Active</GUIRef> check box is selected, the execute condition is checked before running the table relation. If the execute condition returns true, the table relation will be executed. If the execute condition returns false, the table relation will be skipped.</FuncDesc>
			<SimpleSection><Paragraph class="Default">The Execute condition is executed before the table relation is started, but after the previous table relations have been finished. If the import is based on audit or indicators the Execute Condition is executed at the start of a batch.</Paragraph>
				<Paragraph class="Default">If the <GUIRef href="/baanerp/da/xch/daxch0121s000#daxch021.actv" role="manual">Active</GUIRef> check box is selected, but no execute condition is specified the table relation will always be executed when the batch is run.</Paragraph>
				<Paragraph class="Default">A button is available to generate a new condition or edit the specified condition. If a new execute condition is generated, the condition code will be equal to the ASCII file code with the extension .EXE.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<List><ListItem>The condition must be of type <GUIRef href="/baanerp/da/domains/xch.type#bool" role="option">Boolean</GUIRef>.</ListItem>
					<ListItem>Whether the import is based on audit or indicators depends upon the check boxes in the <GUIRef href="/baanerp/da/xch/daxch0101s000" role="session">Exchange Schemes (daxch0101s000)</GUIRef> session and the setting of the batch in the <GUIRef href="/baanerp/da/xch/daxch0104m000" role="session">Batches (daxch0104m000)</GUIRef> session.</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>
				<RelTopic><Link href="/baanerp/da/onlinemanual/000013" role="manual">Relation between logical ASCII files and physical ASCII files</Link>
				</RelTopic>
			</RelatedTopics>
		</FieldHelp>
		<FieldGroup><Title>Permitted Operations</Title>
			<FieldHelp ID="daxch021.addn"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Add</Title>
				</Header>
				<FuncDesc>
                                    If this check box is selected,, inserts (that is: all records in case of full import, and records having indicator i in case of import based on audit or based on indicators) are imported if the record does not yet exist in the database. If the add condition is empty, all inserts will be processed. If an add condition is specified, only the records that meet the add condition are processed.</FuncDesc>
				<SimpleSection><Paragraph class="Default">
                                       If this check box is cleared, inserts are not imported. If a record to be inserted is encountered in the ASCII file it will be skipped.</Paragraph>
				</SimpleSection>
			</FieldHelp>
			<FieldHelp ID="daxch021.acon"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Add Condition</Title>
				</Header>
				<FuncDesc>If a condition is specified, a new record will only be added to the database if the return value of the condition is true.</FuncDesc>
				<SimpleSection><List><ListIntro>The following preconditions hold when an add condition is executed:</ListIntro>
						<ListItem>Type of action is insert (this is true for all records in case of a full import, and for those records having indicator I, in case of an import based on audit or indicators)</ListItem>
						<ListItem>All <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII file</Link> fields are filled</ListItem>
						<ListItem>The record does or does not already exist in the database</ListItem>
						<ListItem>The keyfields of the target ERP LN table are filled, and other fields contain non-valid values</ListItem>
					</List>
					<Paragraph class="Default">IMPORTANT: In case the record already exists, the add condition is Executed. This is because Exchange first tries to insert the record before checking whether it already exists (for performance reasons).</Paragraph>
					<Paragraph class="Default">A button is available to generate a new condition, or edit the specified condition. If a new condition is generated the condition code will be equal to the ASCII file code with the extension .ADD.</Paragraph>
				</SimpleSection>
				<Note><SectionTitle>
                                       Note
                                    </SectionTitle>
					<List><ListItem>This field can only be maintained if Add Record is selected.</ListItem>
						<ListItem>The condition must be of type <GUIRef href="/baanerp/da/domains/xch.type#bool" role="option">Boolean</GUIRef>.</ListItem>
						<ListItem>Whether the import is based on audit or indicators depends upon the check boxes in the <GUIRef href="/baanerp/da/xch/daxch0101s000" role="session">Exchange Schemes (daxch0101s000)</GUIRef> session and the setting of the batch in the <GUIRef href="/baanerp/da/xch/daxch0104m000" role="session">Batches (daxch0104m000)</GUIRef> session.</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="daxch021.ovwr"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Overwrite</Title>
				</Header>
				<FuncDesc>
                                    If this check box is selected,, inserts (that is: all records in case of full import, and records having indicator i in case of import based on audit or based on indicators) are imported if the record already exists in the database. If the add condition is empty, the already existing records are overwritten. If an overwrite condition is specified, existing records are only overwritten if the records to be imported meets the overwrite condition.</FuncDesc>
				<SimpleSection><Paragraph class="Default">
                                       If this check box is cleared, inserts are not imported if the record already exists in the database. If a record to be inserted from the ASCII file already exists in the database it will be skipped.</Paragraph>
				</SimpleSection>
			</FieldHelp>
			<FieldHelp ID="daxch021.ocon"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Overwrite Condition</Title>
				</Header>
				<FuncDesc>If a condition is specified, an existing record will only be overwritten if the return value of the condition is true.</FuncDesc>
				<SimpleSection><List><ListIntro>The following preconditions hold when an overwrite condition is executed:</ListIntro>
						<ListItem>If Add Records is selected then the add condition (if any) has already been executed before the overwrite condition is executed.</ListItem>
						<ListItem>Type of action is insert (this is true for all records in case of a full import, and for the records having indicator 'i' in case of an import based on audit or indicators).</ListItem>
						<ListItem>All <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII file</Link> fields are filled.</ListItem>
						<ListItem>The record already exists in the database.</ListItem>
						<ListItem>The ERP LN table fields are filled with the existing record.</ListItem>
					</List>
					<Paragraph class="Default">A button is available to generate a new condition or edit the specified condition. If a new condition is generated the condition code will be equal to the ASCII file code with the extension .OVR.</Paragraph>
				</SimpleSection>
				<Note><SectionTitle>
                                       Note
                                    </SectionTitle>
					<List><ListItem>This field can only be maintained if Overwrite Record is selected.</ListItem>
						<ListItem>The condition must be of type <GUIRef href="/baanerp/da/domains/xch.type#bool" role="option">Boolean</GUIRef>.</ListItem>
						<ListItem>Whether the import is based on audit or indicators depends upon the check boxes in the <GUIRef href="/baanerp/da/xch/daxch0101s000" role="session">Exchange Schemes (daxch0101s000)</GUIRef> session and the setting of the batch in the <GUIRef href="/baanerp/da/xch/daxch0104m000" role="session">Batches (daxch0104m000)</GUIRef> session.</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="daxch021.updt"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Update</Title>
				</Header>
				<FuncDesc>
                                    If this check box is selected, updates (records having indicator u) are imported. If the update condition is empty, all updates will be processed. If an update condition is specified only the records that meet the update condition are processed.</FuncDesc>
				<SimpleSection><Paragraph class="Default">
                                       If this check box is cleared, updates are not imported. If a record to be updated is encountered in the ASCII file, it is skipped.</Paragraph>
				</SimpleSection>
				<Note><SectionTitle>
                                       Note
                                    </SectionTitle>
					<Paragraph class="Default">This field is only relevant when exchanging based on audit or based on indicators.</Paragraph>
				</Note>
			</FieldHelp>
			<FieldHelp ID="daxch021.ucon"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Update Condition</Title>
				</Header>
				<FuncDesc>If a condition is specified, an update (that is, a record having indicator u) will only be processed if the return value of the condition is true.</FuncDesc>
				<SimpleSection><List><ListIntro>The following preconditions hold when an update condition is executed:</ListIntro>
						<ListItem>Type of action is update.</ListItem>
						<ListItem>The primary key fields and the fields that are changed by the update action are filled.</ListItem>
						<ListItem>The record that must be updated exists in the database.</ListItem>
						<ListItem>The ERP LN table fields are filled with the existing record.</ListItem>
					</List>
					<Paragraph class="Default">A button is available to generate a new condition or edit the specified condition. If a new condition is generated, the condition code will be equal to the ASCII file code with the extension .UPD.</Paragraph>
				</SimpleSection>
				<Note><SectionTitle>
                                       Note
                                    </SectionTitle>
					<List><ListItem>This field can only be maintained if Update Record is selected, and it is only relevant in case of an import based on audit or indicators.</ListItem>
						<ListItem>The condition must be of type <GUIRef href="/baanerp/da/domains/xch.type#bool" role="option">Boolean</GUIRef>.</ListItem>
						<ListItem>Whether the import is based on audit or indicators depends on the check boxes in the <GUIRef href="/baanerp/da/xch/daxch0101s000" role="session">Exchange Schemes (daxch0101s000)</GUIRef> session and the setting of the batch in the <GUIRef href="/baanerp/da/xch/daxch0104m000" role="session">Batches (daxch0104m000)</GUIRef> session.</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="daxch021.dlte"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Delete</Title>
				</Header>
				<FuncDesc>
                                    If this check box is selected, the delete records (those having indicator d) are imported. If the delete condition is empty, all deletes will be processed. If a delete condition is specified, only the records that meet the delete condition are processed.</FuncDesc>
				<SimpleSection><Paragraph class="Default">
                                       If this check box is cleared, deletes are not imported. If a record to be deleted is encountered in the ASCII file it is skipped.</Paragraph>
				</SimpleSection>
				<Note><SectionTitle>
                                       Note
                                    </SectionTitle>
					<Paragraph class="Default">This field is only relevant when exchanging based on indicators or based on audit.</Paragraph>
				</Note>
			</FieldHelp>
			<FieldHelp ID="daxch021.dcon"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Delete Condition</Title>
				</Header>
				<FuncDesc>If a condition is specified, a delete (that is a record having indicator d) will be processed only if the return value of the condition is true.</FuncDesc>
				<SimpleSection><List><ListIntro>The following preconditions hold when a delete condition is executed:</ListIntro>
						<ListItem>Type of action is delete.</ListItem>
						<ListItem>All <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII file</Link> fields are filled, including the ones that are not part of the primary key.</ListItem>
						<ListItem>The record that must be deleted exists in the database</ListItem>
						<ListItem>The ERP LN table fields are filled with the existing record</ListItem>
					</List>
					<Paragraph class="Default">A button is available to generate a new condition or edit the specified condition. If a new condition is generated, the condition code will be equal to the ASCII file code with the extension .DEL.</Paragraph>
				</SimpleSection>
				<Note><SectionTitle>
                                       Note
                                    </SectionTitle>
					<List><ListItem>This field can only be maintained if Delete Record is selected, and it is only relevant in case of an import based on audit or indicators.</ListItem>
						<ListItem>The condition must be of type <GUIRef href="/baanerp/da/domains/xch.type#bool" role="option">Boolean</GUIRef>.</ListItem>
						<ListItem>Whether the import is based on audit or indicators depends on the check boxes in the <GUIRef href="/baanerp/da/xch/daxch0101s000" role="session">Exchange Schemes (daxch0101s000)</GUIRef> session and the setting of the batch in the <GUIRef href="/baanerp/da/xch/daxch0104m000" role="session">Batches (daxch0104m000)</GUIRef> session.</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>
		</FieldGroup>
		<FieldHelp ID="daxch021.stop"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Stop Mechanism</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, the import process is stopped if the return value of the stop <Link href="/baanerp/da/glossary/glossary#000009" role="glossary">condition</Link> is true.</FuncDesc>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">You do not have to generate the import program again if this field is changed.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="daxch021.scon"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Stop Condition</Title>
			</Header>
			<FuncDesc>The import process is stopped if the return value of the Stop <Link href="/baanerp/da/glossary/glossary#000009" role="glossary">condition</Link> is true. If the return value is false, the import process continues with the next batch line. The stop condition is executed at the end of each table relation.</FuncDesc>
			<SimpleSection><Paragraph class="Default">You can automatically generate a stop condition. In that case, the stop <Link href="/baanerp/da/glossary/glossary#000009" role="glossary">condition</Link> code is the same as the <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII file</Link> code with the extension .STP. This condition is of the <GUIRef href="/baanerp/da/domains/xch.type#bool" role="option">Boolean</GUIRef> type.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldGroup><Title>Data Access Layer</Title>
			<FieldHelp ID="daxch021.dalu"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Import via Data Access Layer</Title>
				</Header>
				<FuncDesc>Select this check box to use the Data Access Layer (DAL) for the current table. By using the DAL, an import carries out all the constraint checks, integrity checks and side effects, such as updates on other tables, that are programmed into the DAL. This guarantees database integrity, saves programming time, and avoids the errors that can occur in condition scripts.</FuncDesc>
				<SimpleSection><Paragraph class="Default">Refer to <Link href="/baanerp/da/onlinemanual/000150" role="manual">Import using the Data Access Layer (DAL)</Link> for details.</Paragraph>
				</SimpleSection>
			</FieldHelp>
			<FieldHelp ID="daxch021.dalc"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">DAL Property Checks</Title>
				</Header>
				<FuncDesc>Select this check box to use the Data Access Layer (DAL) property checks. Using property checks is safer, but you can turn them off to boost performance.</FuncDesc>
				<SimpleSection><Paragraph class="Default">Refer to <Link href="/baanerp/da/onlinemanual/000150" role="manual">Import using the Data Access Layer (DAL)</Link> for details.</Paragraph>
				</SimpleSection>
			</FieldHelp>
			<FieldHelp ID="daxch021.dalf"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Update Dependent Fields</Title>
				</Header>
				<FuncDesc>
                                    If this check box is selected, the DAL 2 field dependencies are used. When a field is updated, the dependent fields are updated automatically. For details, refer to "DAL2 Field dependencies" in the <DocRef>ERP LN 6.1 Programmer's Guide</DocRef>.</FuncDesc>
				<Important><SectionTitle>
                                       Important!
                                    </SectionTitle>
					<Paragraph class="Default">The dependent fields should not be included in the Field Relations (Import).</Paragraph>
				</Important>
				<SimpleSection><Paragraph class="Default">It is recommended to select this check box.</Paragraph>
				</SimpleSection>
			</FieldHelp>
		</FieldGroup>
		<FieldGroup><Title>User Defined Program</Title>
			<FieldHelp ID="daxch021.unix"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">External Program</Title>
				</Header>
				<FuncDesc>
                                    If this check box is selected, an external program is used in this table relation.</FuncDesc>
				<SimpleSection><Paragraph class="Default">A table relation can perform functions other than importing data. It can also run an external program or a ERP LN session. External programs can be used to correct, update or load multiple ERP LN tables without any user input.</Paragraph>
					<Paragraph class="Default">
                                       If this check box is cleared, a ERP LN session can be used in this table relation.</Paragraph>
				</SimpleSection>
				<Note><SectionTitle>
                                       Note
                                    </SectionTitle>
					<Paragraph class="Default">You do not have to generate this import program again if this field is changed.</Paragraph>
				</Note>
			</FieldHelp>
			<FieldHelp ID="daxch021.prog"><Header>
					<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Program Name</Title>
				</Header>
				<FuncDesc>An external program or ERP LN session that is used to bypass the import program. The program is only executable in an active table relation.</FuncDesc>
				<SimpleSection><Paragraph class="Default">If you leave this field empty, exchange will activate the <Link href="/baanerp/da/glossary/glossary#000032" role="glossary">table relation</Link> during the import process. If you fill in an (external) program, exchange will not take care of importing the <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII file</Link>, but will activate the (external) program instead. The program is activated with a number of arguments. Please refer to the Exchange Scheme Designers information for more details.</Paragraph>
				</SimpleSection>
				<Note><SectionTitle>
                                       Note
                                    </SectionTitle>
					<List><ListItem>You do not have to generate the import program again if this field is changed.</ListItem>
						<ListItem>To run the program during an import, make sure this table relation is active by selecting the <GUIRef href="/baanerp/da/xch/daxch0121s000#daxch021.actv" role="manual">Active</GUIRef> check box.</ListItem>
					</List>
				</Note>
				<RelatedTopics><SectionTitle>
                                       Related topics
                                    </SectionTitle>
					<RelTopic><Link href="/baanerp/da/onlinemanual/000020" role="manual">Exchange scheme designers information</Link>
					</RelTopic>
				</RelatedTopics>
			</FieldHelp>
		</FieldGroup>
		<FieldHelp ID="daxch021.indx"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Sort on Index</Title>
			</Header>
			<FuncDesc>Enter an <Link href="/baanerp/da/glossary/glossary#000012" role="glossary">index</Link> number of the ERP LN table that is filled with data from the <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII file</Link>.</FuncDesc>
			<SimpleSection></SimpleSection>
			<Note><SectionTitle>
                                    Note
                                 </SectionTitle>
				<Paragraph class="Default">The <Link href="/baanerp/da/glossary/glossary#000012" role="glossary">index</Link> number is only relevant if one of the ASCII file fields is based on <Link href="/baanerp/da/glossary/glossary#000013" role="glossary">increment</Link>. This field allows you to define an increment field on secondary, but unique, indices.</Paragraph>
			</Note>
			<SimpleSection><Paragraph class="Default">Refer to <GUIRef href="/baanerp/da/xch/daxch0122s000" role="session">Field Relations (Import) (daxch0122s000)</GUIRef> session for more information.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="text.available"><Header>
				<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Text</Title>
			</Header>
			<FuncDesc>
                                 If this check box is selected, more information is added to the table relation. Click Text to start the text editor.</FuncDesc>
		</FieldHelp>
	</Fields>
</Session>
