<?xml version="1.0" encoding="utf-8"?>
<Glossary ID="/baanerp/da/glossary/glossary" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Glossary for the DA package</Title>
	</Header>
	<GlossaryEntry ID="000017" Version="B60asy04" ContextApps="tu"><Term>absolute path</Term>
		<Definition>The route that is followed from the root directory to a specific file, for example a physical ASCII file or a log file.</Definition>
		<SimpleSection><Paragraph class="Default">An absolute path always starts with, for example, \, c:\,/,or ${BSE}.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000041" Version="B60asy04" ContextApps="tu"><Term>action ID</Term>
		<Definition>A sequence number of a database action in a <Link href="/baanerp/tt/glossary/glossary#100235" role="glossary">transaction</Link>. The action ID is unique for each action per transaction.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000014" Version="B60asy04" ContextApps="tu"><Term>array</Term>
		<Definition>A list of data items of the same type that have the same name and are identified by a number.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000001" Version="B60asy04" ContextApps="tu"><Term>ASCII file</Term>
		<Definition>A text file that uses the ASCII standard code to represent characters and punctuation marks as numbers. The ASCII code also includes control characters to indicate carriage return, backspace and so on.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000008" Version="B60asy04" ContextApps="tu"><Term>audit procedure</Term>
		<Definition>A procedure that can be used during a regular data export, for example in a multisite environment.</Definition>
		<SimpleSection><Paragraph class="Default">The <Link href="/baanerp/tt/glossary/glossary#100072" role="glossary">audit server</Link> creates export files. Only the changes on the data over a specified period are exported. This procedure reduces processing time.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000002" Version="B60asy04" ContextApps="tu"><Term>batch</Term>
		<Definition>A set of table revisions that is processed as a unit. A batch contains a number of tables relations between ERP LN tables and ASCII files that are imported or exported.</Definition>
		<SimpleSection><Paragraph class="Default">Every table relation in a batch has a sequence number.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000046" Version="B60asy04" ContextApps="tu"><Term>batch lines to import</Term>
		<Definition>This entity contains the import batch lines of a batch to import, and is used by the import process to copy the files to be imported from the source system. For each batch line the source file is stored.</Definition>
		<Note><SectionTitle>
                                 Note
                              </SectionTitle>
			<Paragraph class="Default">The batch line is also known as table relation.</Paragraph>
		</Note>
	</GlossaryEntry>
	<GlossaryEntry ID="000045" Version="B60asy04" ContextApps="tu"><Term>batches to import</Term>
		<Definition>A target batch that can be run because the source batch has been run. The files to be imported are ready. The batch to import is removed as soon as the files have been copied from the source site to the target site.</Definition>
		<SimpleSection><Paragraph class="Default">You can also remove the batch to import manually. In such a case, an import done message is sent to the source site. The batches to import are stored at the target site in the same environment and company as the import batch.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="63" Version="7.2a" ContextApps="tt"><Term>BW</Term>
		<Definition>A windows-based interface program between the user and the ERP LN servers. The windows interface runs on the user workstation and communicates with the Bshell.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="52" Version="3.1a" ContextApps="tu"><Term>change</Term>
		<Definition>The creation, change (update), or deletion of an entity. For example, creating a sales order, adding or deleting order lines, or deleting a sales order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000009" Version="B60asy04" ContextApps="tu"><Term>condition</Term>
		<Definition>A piece of code in the ERP LN programming language. Within a condition, all features of the ERP LN programming language are available. As a result, you can perform calculations, read additional data by using embedded SQL, update the database, or call functions from existing Dynamic Link Libraries.</Definition>
		<SimpleSection><List><ListIntro>Two types of conditions are used in Exchange:</ListIntro>
				<ListItem>Boolean conditions. These conditions return either true of false, and are used to decide whether a specific action must be executed or not. For example, an overwrite condition determines whether existing records must be overwritten, or an execute condition determines whether a batch line must be executed.</ListItem>
				<ListItem>Value conditions. These conditions can return any value, for example, a string, a long or a double, and are used to determine the value for a specific field.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="55" Version="3.3ac6" ContextApps="da"><Term>configuration library</Term>
		<Definition>A library from an ERP LN application package that contains the configuration for a synchronization object. It defines, for example, which components and attributes must be included, which filters must be applied, and which transformations must be carried out.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="67" Version="3.1a" ContextApps="tu"><Term>data warehouse</Term>
		<Definition>A database, often remote, containing recent snapshots of corporate data. Planners and researchers can use this database freely without worrying about slowing down daily operations of the OLTP database.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000007" Version="B60asy04" ContextApps="tu"><Term>definition file</Term>
		<Definition>A file where the complete format of an ASCII file is stored. This file contains the field names, type, length, and position of the fields in a record.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000030" Version="B60asy04" ContextApps="tu"><Term>environment</Term>
		<Definition>A definition of a site in the Exchange module. The environment can be an application server on which one or more exchange schemes are stored for importing or exporting data.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000031" Version="B60asy04" ContextApps="tu"><Term>exchange link</Term>
		<Definition>The relation between source and target sites in a multisite environment. The link is stored at the target site in the same environment and company that contains the import batch.</Definition>
		<Note><SectionTitle>
                                 Note
                              </SectionTitle>
			<Paragraph class="Default">If the exchange link is used on a single site, the source system must be equal to the system on which it is stored.</Paragraph>
		</Note>
	</GlossaryEntry>
	<GlossaryEntry ID="000003" Version="B60asy04" ContextApps="tu"><Term>exchange scheme</Term>
		<Definition>A blueprint that defines the general parameters that are used during a data-exchange process, such as the location of files, the use of an audit trail, and other default settings. The exchange scheme contains all definitions of the data that must be exported and/or imported. The ASCII files, conditions, batches, table and field relations, ranges, and conversions that belong together are grouped in an exchange scheme.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000039" Version="B60asy04" ContextApps="tu"><Term>exchange subscription</Term>
		<Definition>An arrangement for receiving an export batch. This means that an import batch exists that wants to import the results of the export batch. Whenever you run an export batch, the import batch is notified that the files can be imported.</Definition>
		<SimpleSection><Paragraph class="Default">The subscription is stored at the source site in the same environment and company as the export batch.</Paragraph>
			<Paragraph class="Default">Note that the term "subscription" has another meaning in the context of the Synchronization Server.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000016" Version="B60asy04" ContextApps="tu"><Term>export procedure</Term>
		<Definition>A transfer of data from a ERP LN table to ASCII files.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000015" Version="B60asy04" ContextApps="tu"><Term>import procedure</Term>
		<Definition>A transfer of data from ASCII Files to a ERP LN table.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000013" Version="B60asy04" ContextApps="tu"><Term>increment</Term>
		<Definition>A unit that is used to increase the value that is stored in a field when it is imported.</Definition>
		<SimpleSection><Paragraph class="Default">For example If the start value for a field-relation serial number is 10 and it is incremented by 2, the value for this field in subsequently imported records will increase to 12, 14, 16, 18, and so on.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000012" Version="B60asy04" ContextApps="tu"><Term>index</Term>
		<Definition>A list or a table that contains reference information pointing to a stored value. The index allows direct access to a multi element data-structure such as a database table without the need for a sequential search through the collection of elements.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000006" Version="B60asy04" ContextApps="tu"><Term>logical ASCII file</Term>
		<Definition>An ASCII file that describes the structure and layout of the data that is exported or imported during an exchange process. The file also specifies the format of the physical ASCII file.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000043" Version="B60asy04" ContextApps="tu"><Term>multisite control</Term>
		<Definition>A way of linking and synchronizing export processes and import processes. The export and import process can (but need not) be running on multiple sites. By using multisite control, you can link the batch that exports the data to the batch that imports the data. This mechanism ensures that the files created by the export process move to the target site and are made available to the import process. This procedure results in importing the exported data in the correct order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="71" Version="3.1a" ContextApps="tu"><Term>net change</Term>
		<Definition>A combination of multiple changes on the same entity. Two updates on the same data can be combined into a single update. When adding an entity and then updating it, the net result is a new entity. When adding an entity and then removing it again, the net result is empty. For example, first create a sales order, then add two order lines, then update the order header, then update one order line and delete the other order line. In this case, the net change will be a new sales order having one order line.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="56" Version="3.3ac6" ContextApps="da"><Term>NetList</Term>
		<Definition>In Baan5.2a and earlier, a method of the Business Object Interface to retrieve the net changes on a business object since the last time the NetList method was called.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000005" Version="B60asy04" ContextApps="tu"><Term>non-regular</Term>
		<Definition>An exchange of data that is not done according to schedule but only once. For example, to convert data or to test a batch that will run on a regular basis. The process is identical to the regular process, but it does not have the checks to determine if previous exchanges were successfully.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="72" Version="3.1a" ContextApps="tu"><Term>Online Analytical Processing</Term>
		<Definition>Fast, interactive analysis of shared multidimensional information. Its objective is to analyze relationships in corporate data and look for patterns, trends, and exceptions, in order to make better decisions. OLAP software often makes use of a data warehouse. Acronym: OLAP.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="73" Version="3.1a" ContextApps="tu"><Term>Online Transaction Processing</Term>
		<Definition>Any processing by an application that results in changes to the database. Acronym: OLTP.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000020" Version="B60asy04" ContextApps="tu"><Term>operator</Term>
		<Definition>A symbol or other character that indicates an operation that acts on one or more elements. In this case, the elements are the old value in the Value From field and the other value in the Range Value To field.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000010" Version="B60asy04" ContextApps="tu"><Term>parameter</Term>
		<Definition>The <Link href="/baanerp/da/glossary/glossary#000001" role="glossary">ASCII file</Link> fields of a record that must be imported, are not automatically defined in a condition script. To use the value of an ASCII file field, you must define that field in the condition script. They are defined as parameters in the condition script.</Definition>
		<SimpleSection><Paragraph class="Default">The parameter name must be identical to the name of the ASCII file field to which it refers. The data type must also be identical to that of the ASCII file field.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000011" Version="B60asy04" ContextApps="tu"><Term>physical ASCII file</Term>
		<Definition>The ASCII file where the exported data, or data to be imported is actually stored on disk.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="61" Version="3.3ac6" ContextApps="da"><Term>PublishChanges</Term>
		<Definition>A method to ask ERP LN to start publishing change events on a requested data set for a business object.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="60" Version="3.3ac6" ContextApps="da"><Term>PublishList</Term>
		<Definition>A method to ask ERP LN to publish the requested data set for a business object.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000004" Version="B60asy04" ContextApps="tu"><Term>regular</Term>
		<Definition>An exchange of data based on a schedule. This exchange can be used, for example, to replicate data in a multisite environment where it is important that no information is lost, overwritten, or exchanged in an incorrect order.</Definition>
		<SimpleSection><Paragraph class="Default">Every time an exchange is carried out, the process is identified by a unique run number. This number makes it possible to separate the different exchanges</Paragraph>
			<Paragraph class="Default">This process also checks if previous exchanges were successfully.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000018" Version="B60asy04" ContextApps="tu"><Term>relative path</Term>
		<Definition>A path that is relative to another (absolute) path. For example, if the default path is \data\exchange or /data/exchange, and the relative path is Myfiles, the resulting path is \data\exchange\Myfiles or /data/exchange/Myfiles.</Definition>
		<SimpleSection><Paragraph class="Default">A relative path does not start with, for example, \, c:\,/,or ${BSE}.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000019" Version="B60asy04" ContextApps="tu"><Term>run number</Term>
		<Definition>A consecutive number linked to an export or import run. The run number is unique for each combination of an exchange batch and an exchange type. Each exchange run is written to the log table by using the run number. The log table is then used to determine the run number of the next export or import run.</Definition>
		<SimpleSection><Paragraph class="Default">In regular export or import, the run number is used to avoid importing the same ASCII file twice or overwriting existing ASCII files.</Paragraph>
			<Paragraph class="Default">In multisite control, the run number is also used to ensure that data is replicated in the correct sequence.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="57" Version="3.3ac6" ContextApps="da"><Term>run-time server</Term>
		<Definition>A server that is running to collect and publish change events for a synchronization object</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000026" Version="B60asy04" ContextApps="tu"><Term>source batch</Term>
		<Definition>In multisite control, this is the batch that exports data that is to be imported by one or more target batches.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000024" Version="B60asy04" ContextApps="tu"><Term>source company</Term>
		<Definition>In multisite control, this is the ERP LN company in which the source batch is stored. The source company resides in the source environment.</Definition>
		<Note><SectionTitle>
                                 Note
                              </SectionTitle>
			<Paragraph class="Default">The target company does not need to be the same as the company to which the data is written during an import procedure.</Paragraph>
		</Note>
	</GlossaryEntry>
	<GlossaryEntry ID="000023" Version="B60asy04" ContextApps="tu"><Term>source environment</Term>
		<Definition>The environment where the source batch is stored. An environment is defined by a system name and a BSE path name, or by a system name and a server name.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000025" Version="B60asy04" ContextApps="tu"><Term>source exchange scheme</Term>
		<Definition>The exchange scheme that contains the source batch.</Definition>
		<SimpleSection><Paragraph class="Default">An exchange scheme is a collection of batches that can be run as a whole during the exchange process. This collection contains general parameters and default settings such as the location of files and programs, the layout of the ASCII files and ASCII file fields, and so on.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000047" Version="B60asy04" ContextApps="tu"><Term>source file</Term>
		<Definition>The name of the file that has been exported by the table relation at the source site. It includes the complete path name for the directory where the file is stored.</Definition>
		<SimpleSection><Paragraph class="Default">Note Because this path name is expanded, it cannot contain terms like ${HOME} or ${BSE}. This is because the environment variables of the source site are not known at the target site.</Paragraph>
			<Paragraph class="Default">The source file does not contain the system name, such as host!/path/file, because this is stored in batches to import.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000027" Version="B60asy04" ContextApps="tu"><Term>source run</Term>
		<Definition>The run number of the export process. This number is used to process the data in the correct order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000044" Version="B60asy04" ContextApps="tu"><Term>source system</Term>
		<Definition>The system that stores the source batch. The source batch contains the data that must be exported to the target batch.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000028" Version="B60asy04" ContextApps="tu"><Term>source try</Term>
		<Definition>The run number of the exchange process. This number is used to process the data in the correct order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="81"><Term>subscription</Term>
		<Definition>An <Link href="/baanerp/da/glossary/glossary#000039" role="glossary">exchange subscription</Link>.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="58" Version="3.3ac6" ContextApps="da"><Term>synchronization object</Term>
		<Definition>Object to be synchronized between ERP LN and one or more other applications. This can be a business object, but synchronization objects can be configured flexibly. For example, for the Item business object, we can define two synchronization objects: PlannerItem and FrontOfficeItem.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="59" Version="3.3ac6" ContextApps="da"><Term>synchronization server</Term>
		<Definition>A server that enables the publishing of change events on business object data from ERP LN to other applications. The product is comparable to the Net Change Server in Baan5.0c. However, in ERP LN clients do not pull (net) changes from ERP, but instead the change events are published.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000032" Version="B60asy04" ContextApps="tu"><Term>table relation</Term>
		<Definition>A definition of the relation between a database table and an ASCII file.</Definition>
		<SimpleSection><List><ListIntro>There are two types of table relations:</ListIntro>
				<ListItem>Table relation (export)</ListItem>
				<ListItem>Table relation (import)</ListItem>
			</List>
			<Paragraph class="Default">A table relation contains field relations, which define the relation between a database table field and an ASCII file field.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000036" Version="B60asy04" ContextApps="tu"><Term>target batch</Term>
		<Definition>In multisite control this batch imports data that has been exported by one or more source batches.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000034" Version="B60asy04" ContextApps="tu"><Term>target company</Term>
		<Definition>In multisite control, this is the ERP LN company in which the source batch is stored. The source company resides in the source environment.</Definition>
		<Note><SectionTitle>
                                 Note
                              </SectionTitle>
			<Paragraph class="Default">The target company does not need to be the same as the company to which the data is written during an import procedure.</Paragraph>
		</Note>
	</GlossaryEntry>
	<GlossaryEntry ID="000033" Version="B60asy04" ContextApps="tu"><Term>target environment</Term>
		<Definition>The ERP LN environment where a target batch is stored. An environment is defined by a system name and a BSE path name, or by a system name and a server name.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000035" Version="B60asy04" ContextApps="tu"><Term>target exchange scheme</Term>
		<Definition>The exchange scheme that contains the target batch.</Definition>
		<SimpleSection><Paragraph class="Default">An exchange scheme defines the general parameters that are used during an data-exchange process, such as the location of files, the use of an audit trail, and other default settings. The exchange scheme contains all definitions of the data that is to be exported and/or imported. The ASCII files, conditions, batches, table and field relations, ranges, and conversions that belong together are grouped in an exchange scheme.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000037" Version="B60asy04" ContextApps="tu"><Term>target run</Term>
		<Definition>The run number of the export process. This number is used to process the data in the correct order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000029" Version="B60asy04" ContextApps="tu"><Term>target system</Term>
		<Definition>The system that stores the target batch. The target batch receives data from the source batch.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000038" Version="B60asy04" ContextApps="tu"><Term>target try</Term>
		<Definition>The try number of the export process. This number is used to process the data in the correct order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000040" Version="B60asy04" ContextApps="tu"><Term>transaction ID</Term>
		<Definition>An identifier of a database <Link href="/baanerp/tt/glossary/glossary#100235" role="glossary">transaction</Link>. The transaction ID is identical for all database actions in the transaction.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000022" Version="B60asy04" ContextApps="tu"><Term>try number</Term>
		<Definition>A consecutive number that is unique within an exchange run. Each run starts with try number 1. When the same run is continued, reprocessed or restarted, the run number remains the same and the try number is incremented by 1.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="62" Version="3.3ac6" ContextApps="da"><Term>UnpublishChanges</Term>
		<Definition>A method to ask ERP LN to stop publishing change events for a business object.</Definition>
	</GlossaryEntry>
</Glossary>
