<?xml version="1.0" encoding="utf-8"?>
<Glossary ID="/baanerp/tt/glossary/glossary" xml:lang="en">
	<Header>
		<Title xmlns:HTML="http://www.w3.org/TR/REC-html40">Glossary for the TT package</Title>
	</Header>
	<GlossaryEntry ID="3GLscript.tt" Version="7.2a" ContextApps="tt"><Term>3GL script</Term>
		<Definition>A <Link href="#progscript.tt" role="internal">program script</Link> that can be linked to sessions without forms, or that is not linked to a session at all. 4GL statements and sections cannot be used in 3GL scripts. In other words the entire program flow, including the main function, needs to be specified.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100092" Version="7.3adoc1" ContextApps="tt"><Term>4GL engine</Term>
		<Definition>The program that provides default functionality for a session to prevent application programmers from having to develop a session from scratch. The 4GL Engine, formerly called standard program (STP), is used because essentially sessions are alike. In addition to providing default functionality, the 4GL Engine also provides a mechanism to change the 4GL Engine's default behavior, and to program dedicated functionality for a specific session. Each time a session is started, a separate 4GL Engine instance is activated to handle the session.</Definition>
		<Synonym>standard program</Synonym>
		<Acronym>STP</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="4GLscript.tt" Version="7.2a" ContextApps="tt"><Term>4GL script</Term>
		<Definition>An event-oriented <Link href="#progscript.tt" role="internal">Program script</Link> that is linked to a session. The instructions can be specified in program sections, form sections, field sections, main table input/output sections, choice sections, zoom from sections, and functions.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="ads"><Term>Active Directory Service</Term>
		<Definition>Active Directory is an implementation of LDAP directory services by Microsoft for use in Windows environments. Active Directory allows administrators to assign enterprise wide policies, deploy programs to many computers, and apply critical updates to an entire organization. An Active Directory stores information and settings relating to an organization in a central, organized, accessible database. Active Directory networks can vary from a small installation with a few hundred objects, to a large installation with millions of objects.</Definition>
		<Acronym>ADS</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="100243" Version="7.4a" ContextApps="tt"><Term>Additional file</Term>
		<Definition>A generic component, such as an XML schema file, a GIF image, and so on. From ERP LN 6.0a on, additional files are stored in a specific package, module, and package VRC.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAXBHTB"><Term>ADS</Term>
		<Definition>See: <Link href="#ads" role="internal">Active Directory Service</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDABDHTB"><Term>AFC</Term>
		<Definition>See: <Link href="#100063" role="internal">Application Foundation Classes</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100065" Version="7.2a" ContextApps="tt"><Term>Algorithm</Term>
		<Definition>A detailed finite sequence of actions that must be performed to accomplish some task.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAUIHTB"><Term>AMS</Term>
		<Definition>See: <Link href="#000015" role="internal">Authorization Management System</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDANDHTB"><Term>API</Term>
		<Definition>See: <Link href="#100064" role="internal">Application Programming Interface</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100063" Version="7.2a" ContextApps="tt"><Term>Application Foundation Classes</Term>
		<Definition>Microsoft's Application Foundation Classes, a collection of Java classes for creating full-fledged application programs. AFC is a comprehensive set of Java class libraries providing user-interface controls, graphics and effects classes, and the ability to create and extract cabinet (CAB) files.</Definition>
		<Acronym>AFC</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="000004" Version="7.3adoc1" ContextApps="tt"><Term>Application help</Term>
		<Definition>Help that tells you how the application works. An online manual contains an overview of the packages and the modules in each package and explains the functionality of each module in detail, describing the underlying concepts and applied methods.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100064" Version="7.2a" ContextApps="tt"><Term>Application Programming Interface</Term>
		<Definition>A set of methods that can be invoked by other applications. An application's API enables other programs to retrieve data or to carry out functionality from that application.</Definition>
		<Acronym>API</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="asm" Version="7.2a" ContextApps="tt"><Term>Application Services Manager</Term>
		<Definition>A stand-alone product that can start and stop ERP LN application services.</Definition>
		<Acronym>ASM</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="000011" Version="7.2a" ContextApps="tt"><Term>Array</Term>
		<Definition>A list of data items of the same type with the same name. An element in the array can be referenced by an expression composed of the array name and an index expression. Multilevel arrays are used for data storage in tables.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAZDHTB"><Term>ASM</Term>
		<Definition>See: <Link href="#asm" role="internal">Application Services Manager</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100066" Version="7.2a" ContextApps="tt"><Term>Asynchronous communication</Term>
		<Definition>Communication between processes, where the process that sends the message does not expect, or wait, for a reply from the receiving process.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000032" Version="7.3adoc1" ContextApps="tt"><Term>Attachments</Term>
		<Definition>Allows you to create or view documents that are attached to the selected record. If you use object data management, you can attach documents to ERP LN records such as items, production orders, and service orders.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100068" Version="7.2a" ContextApps="tt"><Term>Attribute</Term>
		<Definition>Literally, a characteristic. In databases, the name or structure of a field is considered an attribute of a record. Structure refers to its size and datatype. For example, LASTNAME, 50 characters, text. In screen displays, additional information stored with each character in character mode that controls the background and foreground colors of the character, blinking, and underlining.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100069" Version="7.2a" ContextApps="tt"><Term>Audit</Term>
		<Definition>To create an audit trail that traces all activities that affect a piece of information, such as a data record, from the time it is entered into the ERP LN database to the time it is removed.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100238" Version="7.4a" ContextApps="tt"><Term>Audit category</Term>
		<Definition>A group of audit profiles, used to group audit profiles of the same functional area.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100048" Version="7.2a" ContextApps="tt"><Term>Audit data dictionary</Term>
		<Definition>A representation of the definition of an audited table in the data dictionary at a certain point of time. When a sequence file is created, the audit DD is kept in the sequence file's header. When the data dictionary changes in a way that affects the table, a new sequence file is created and the new audit DD is added.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100239" Version="7.4a" ContextApps="tt"><Term>Audit host</Term>
		<Definition>The system where the audit server runs.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100070" Version="7.2a" ContextApps="tt"><Term>Audit management</Term>
		<Definition>A management system that controls the auditing process. Audit management can be used, for example, to specify for which database tables an audit trail must be created and where the audit trail's data must be stored.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100237" Version="7.4a" ContextApps="tt"><Term>Audit profile</Term>
		<Definition>A group of audit settings, configured for specific companies, tables and fields.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100072" Version="7.2a" ContextApps="tt"><Term>Audit server</Term>
		<Definition>A program that creates the audit trail.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100020" Version="7.2a" ContextApps="tt"><Term>Audit trail</Term>
		<Definition>A means of tracing all activities affecting information, such as data records in a database, for a defined time interval. The information is stored in the audit files.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100240" Version="7.4a" ContextApps="tt"><Term>Audit type</Term>
		<Definition>The setting that defines when a field is audited.</Definition>
		<SimpleSection><List><ListIntro>You can choose to audit a field 'always', or only when it is 'changed':</ListIntro>
				<ListItem>If a field is audited 'always', the field is logged each time when the content of the field, or the content of any other audited field, changes.</ListItem>
				<ListItem>If a field is audited when it is 'changed', the field is logged only when the content of the field itself changes.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000015" Version="7.2a" ContextApps="tt"><Term>Authorization Management System</Term>
		<Definition>An authorization system in ERP LN that defines the permissions of a normal User. The user is assigned to a group of users with the same role and/or sub role in an organization. ERP LN links the authorizations to the role of the user group, not to the individual users in the group.</Definition>
		<Acronym>AMS</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="000014" Version="7.2a" ContextApps="tt"><Term>Authorizations</Term>
		<Definition>A set of permissions that limit the access to various objects in ERP LN. For example, access can be denied to sessions, tables, and companies.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100110"><Term>Base Language</Term>
		<Definition>The fallback language that is used to display application data.</Definition>
		<SimpleSection><ProcedureList><ListIntro>
                                    ERP LN uses the following fallback mechanism:</ListIntro>
				<ListItem>
                                    ERP LN displays the application data in the data language that is specified in your user data.</ListItem>
				<ListItem>If no data language is specified in your user data, ERP LN displays the application data in the data language that is linked to your software language.</ListItem>
				<ListItem>If no data language is linked to your software language, ERP LN displays the application data in the base language.</ListItem>
			</ProcedureList>
			<Paragraph class="Default">For more information, refer to <Link href="/baanerp/tt/onlinemanual/mle_multi_language_application_data" role="manual">Multilanguage Application Data</Link>.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="100249" Version="7.5a" ContextApps="tt"><Term>Base VRC</Term>
		<Definition>A means in PMC to identify products in a unique way. Updates at the distributor side are provided with the base VRC identifier. A base VRC can contain the code of the physical VRC in which the related master product is installed, for example, B61_a, but can also be a code not related to a physical VRC, for example, 7.6_a_tt. At the recipient side, every update VRC is linked to a base VRC identifier. The installation process checks if the base VRC identifier of the update matches with the base VRC identifier of the update VRC. If not, you cannot install the update in that update VRC.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="base_vrc_combination" Version="7.5a" ContextApps="tt"><Term>Base VRC combination</Term>
		<Definition>A <Link href="/baanerp/tt/glossary/glossary#100249" role="glossary">Base VRC</Link> combination is defined at the PMC distributor side and consists of a set of related base VRCs. A base VRC combination controls the creation of co-requisites between base VRCs. You can only define co-requisites between base VRCs that are part of the same base VRC combination. Base VRC combinations prevent the unwanted creation of co-requisites between base VRCs.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100078" Version="7.2a" ContextApps="tt"><Term>Batch-oriented replication</Term>
		<Definition>A time-driven data replication method, as opposed to the real-time data replication. The batch-oriented replication process is started based on a schedule, for example, every hour or every week.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAZRITB"><Term>BECS</Term>
		<Definition>See: <Link href="#100079" role="internal">
                              Infor Environment and Configuration Selector
                           </Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100035" Version="7.2a" ContextApps="tt"><Term>Bi-directional language support</Term>
		<Definition>A function that is necessary to support languages that are read and written from right to left. For example, Arabic, and Hebrew.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100081" Version="7.2a" ContextApps="tt"><Term>Blocking process</Term>
		<Definition>A process that must be completed before other processes can continue.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAZMHTB"><Term>BOI</Term>
		<Definition>See: <Link href="#100082" role="internal">Business Object Interface</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDALNHTB"><Term>BOL</Term>
		<Definition>See: <Link href="#100260" role="internal">Business Object Layer</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAXOHTB"><Term>BOR</Term>
		<Definition>See: <Link href="#100204" role="internal">Business Object Repository</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAXFKTB"><Term>BSE</Term>
		<Definition>See: <Link href="#100051" role="internal">
                              ERP LN software environment</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000025" Version="7.2a" ContextApps="tt"><Term>BSE path</Term>
		<Definition>An environment variable containing the directory where the ERP LN software is installed.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAJFKTB"><Term>bshell</Term>
		<Definition>See: <Link href="#100050" role="internal">
                              ERP LN shell</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100032" Version="7.2a" ContextApps="tt"><Term>Business Object</Term>
		<Definition>A Business Object is an object understandable by the business, such as a purchase order or an organizational unit. A Business Object has information stored in the Business Object attributes, such as the purchase order number or the organizational unit name. A Business Object also contains a set of actions, known as Business Object methods, that can manipulate the Business Object attributes, such as create purchase order and list organizational units.</Definition>
		<SimpleSection><Paragraph class="Default">From a development perspective, a Business Object is a collection of tables and functions that manipulate these tables that are implemented simultaneously as one group during the development phase. A Business Object is identified by the combination of a package code, module code, and Business Object code.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="100082" Version="7.2a" ContextApps="tt"><Term>Business Object Interface</Term>
		<Definition>Business Object interfaces provide a connection between partner applications and third-party applications and the ERP LN software, as well as connecting ERP LN functional components. Business Object interfaces are developed for situations where the ERP LN software acts principally as a server, and a client software invokes the methods in the objects.</Definition>
		<Acronym>BOI</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="100260" Version="7.4a" ContextApps="tt"><Term>Business Object Layer</Term>
		<Definition>A set of standard DLLs from ERP LN 6.0 onwards. The Business Object Layer invokes ERP LN business logic methods that handle the persistency of a <Link href="#100032" role="internal">Business Object</Link>
		</Definition>
		<Acronym>BOL</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="100262" Version="7.6a" ContextApps="tt"><Term>Business Object meta data</Term>
		<Definition>Describes the structure and content of a <Link href="#100032" role="internal">Business Object</Link> and its mapping to ERP LN tables and DLLs.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100204" Version="7.6a" ContextApps="tt"><Term>Business Object Repository</Term>
		<Definition>A persistency system that stores the <Link href="#100262" role="internal">Business Object meta data</Link>. The BOR is a virtual space in which <Link href="#100032" role="internal">Business Objects</Link> are modeled. The runtime objects of the Business Objects are stored in the <Link href="#100260" role="internal">Business Object Layer</Link>.</Definition>
		<Acronym>BOR</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAJGKTB"><Term>BW</Term>
		<Definition>See: <Link href="#100083" role="internal">
                              ERP LN windows interface</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100084" Version="7.2a" ContextApps="tt"><Term>C</Term>
		<Definition>A structured programming language. C is a compiled language that contains a small set of built-in functions that are machine dependent. The rest of the C functions are machine independent and are contained in libraries that can be accessed from C programs. C programs are composed of one or more functions defined by the programmer.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100038" Version="7.2a" ContextApps="tt"><Term>Character set</Term>
		<Definition>The smallest component of a written language that has semantic value (that is, linguistic meaning). A character set is the collection of characters that is used in a given language. As well as the alphabet, a character set includes numerals, mathematical and currency symbols and punctuation marks. The character set that you select determines how texts are displayed and printed by your computer, for example as Latin or Arabic characters. Examples of character sets include ASCII and ISO 8859-1.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100009" Version="7.2a" ContextApps="tt"><Term>Chart</Term>
		<Definition>A graphic or diagram that displays data or the relationships between sets of data in pictorial rather than numeric form. The data can be presented in a graph, a line, or a pie, and can include titles, legends, and footnotes.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100014" Version="7.2a" ContextApps="tt"><Term>Chart application</Term>
		<Definition>A program that is used to send data from a ERP LN session to the Chart Manager. A chart application is linked to a package VRC to customize the attributes that are specified in the chart.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100010" Version="7.2a" ContextApps="tt"><Term>Chart type</Term>
		<Definition>The chart type determines what the chart looks like.</Definition>
		<SimpleSection><List><ListIntro>For example, it defines the type of graph, the thickness of lines, the size of bars, and the colors. The following default chart types are present in ERP LN:</ListIntro>
				<ListItem>Bar</ListItem>
				<ListItem>Layer</ListItem>
				<ListItem>Line</ListItem>
				<ListItem>Pie</ListItem>
				<ListItem>Scatter</ListItem>
				<ListItem>Stacked bar</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="checki.tt" Version="7.2a" ContextApps="tt"><Term>Check in</Term>
		<Definition>A process that releases the checked-out software component and copies the software component from the <Link href="#dvrc.tt" role="internal">Development VRC</Link> to the <Link href="#ovrc.tt" role="internal">Original VRC</Link>. This process also stores a historical version.</Definition>
		<SimpleSection><Paragraph class="Default">A revision text for the changed software component is required for a check-in process.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="checko.tt" Version="7.2a" ContextApps="tt"><Term>Check out</Term>
		<Definition>A process that locks the software component for other developers. During the check-out phase, other related components are locked as well while the component can be updated and tested. A copy of the component is made from the original VRC to the <Link href="/baanerp/tt/glossary/glossary#dvrc.tt" role="glossary">Development VRC</Link>.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="childfield.tt" Version="7.2a" ContextApps="tt"><Term>Child field</Term>
		<Definition>A table field that is part of a combined field. A combined field contains two or more table fields, which are the child fields of the same table field.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="" Version="7.2a" ContextApps="tt"><Term>Class</Term>
		<Definition>In Object Oriented Programming, a class is a generalized category that describes a group of more specific items, called objects, that can exist within it. A class is a template definition of the methods and properties (variables) in a particular kind of object. Thus, an object is a specific instance of a class that contains real values instead of variables. The class is one of the defining ideas of object-oriented programming. Among the important ideas about classes are: A class can have subclasses that can inherit all or some of the characteristics of the class. In relation to each subclass, the class becomes the superclass. Subclasses can also define their own methods and variables that are not part of their superclass. The structure of a class and its subclasses is called the class hierarchy</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100209" Version="7.4a" ContextApps="tt"><Term>Client</Term>
		<Definition>A user, program or system that requests the execution of a specific task from another program or system. See also server.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100085" Version="7.2a" ContextApps="tt"><Term>Client/server environment</Term>
		<Definition>A distributed system in which software is split between server tasks and client tasks. A client sends requests to a server, according to a protocol, asking for information or action, and the server responds.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100257" Version="7.5a" ContextApps="tt"><Term>Collection</Term>
		<Definition>In PMC, a collection is a group of individual solutions. At the PMC distributor side, you can perform grouping in various ways, for example, manual grouping based on a functional topic or grouping based on solutions created in a particular period etc. You cannot define dependencies between collections. At the recipient side, the entity collection is not available. When a collection is scanned, the individual solutions are added to the PMC registry and can be processed individually.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="combfield.tt" Version="7.2a" ContextApps="tt"><Term>Combined field</Term>
		<Definition>A combination of two or more child fields of the same <Link href="#table.tt" role="internal">Table</Link>.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100008" Version="7.2a" ContextApps="tt"><Term>Commercial product</Term>
		<Definition>A set of tools, directories, or sessions which you can deliver to a customer.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100086" Version="7.2a" ContextApps="tt"><Term>Commit</Term>
		<Definition>An action to successfully complete a transaction in order to make the database changes permanent.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100087" Version="7.2a" ContextApps="tt"><Term>Commit protocol</Term>
		<Definition>An action to successfully complete a transaction in order to make the database changes permanent.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000016" Version="7.2a" ContextApps="tt"><Term>Common user data</Term>
		<Definition>The parts of the user data that are similar for a group of users. The authorization data is not included in this definition. The user authorizations are defined in the <Link href="#000015" role="internal">Authorization Management System</Link>.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000023" Version="7.2a" ContextApps="tt"><Term>Company</Term>
		<Definition>A means to store data separately in ERP LN. Every company has its own tables with its own data.</Definition>
		<SimpleSection><Paragraph class="Default">Example: An Item with Item Code "X" can be stored in the Item Master Table of several different companies. In each company this Item Code "X" can have different data.</Paragraph>
		</SimpleSection>
		<Note><SectionTitle>
                                 Note
                              </SectionTitle>
			<Paragraph class="Default">Company number 000 is reserved by Infor to store the Enterprise Server (Tools) data. Several company numbers below 100 are used by Infor as demo companies or base companies. Infor advises you to use only company numbers equal to or greater than 100 to store your production data.</Paragraph>
		</Note>
	</GlossaryEntry>
	<GlossaryEntry ID="comm.tt" Version="7.2a" ContextApps="tt"><Term>Component management</Term>
		<Definition>A system that a developer uses to lock software components, that will be changed, for other users.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="co-requisite" ContextApps="tt"><Term>Co-requisite</Term>
		<Definition>In general, co-requisites are defined between solutions of a standard product and derived products. Co-requisites guarantee that related products are updated simultaneously under the condition that the update VRCs of the related products are linked to the same VRC combination. The order of installation is not relevant. The solutions can have the same <Link href="/baanerp/tt/glossary/glossary#100249" role="glossary">base VRC</Link>, or different base VRCs.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000011" Version="7.3adoc1" ContextApps="tt"><Term>Customer</Term>
		<Definition>A code that identifies a customized software package. For example, B61O_a_cus1, where 'B61O' represents the version, 'a' represents the release, and 'cus1' represents the customer extension of the customized software.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="customization" ContextApps="tt"><Term>Customization</Term>
		<Definition>A derived product, meant to fulfill the requirements of a specific customer or group of customers.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAUZHTB"><Term>da</Term>
		<Definition>See: <Link href="#100223" role="internal">Data Director</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000026" Version="7.2a" ContextApps="tt"><Term>Daemon</Term>
		<Definition>A program associated with the UNIX operating system that permanently runs in the background. A daemon handles requests that are issued by other programs and is activated only when needed. For example, the job daemon runs permanently on the ERP LN server. If the Job Daemon detects that a job is present, it executes the job at the job's scheduled time.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDA2YHTB"><Term>DAL</Term>
		<Definition>See: <Link href="#100224" role="internal">Data Access Layer</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100224" Version="7.4a" ContextApps="tt"><Term>Data Access Layer</Term>
		<Definition>A <Link href="#dll.tt" role="internal">Dynamic Link Library</Link> that is linked to a ERP LN database table.</Definition>
		<Acronym>DAL</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="100005" Version="7.2a" ContextApps="tt"><Term>Data Dictionary</Term>
		<Definition>A database containing data about all the databases in a database system. Data dictionaries store all the various schema and file specifications and their locations. They also contain information about which programs use which data and which users are interested in which reports.</Definition>
		<Acronym>DD</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="100223" Version="7.4a" ContextApps="tt"><Term>Data Director</Term>
		<Definition>The ERP LN package that contains the Exchange module.</Definition>
		<Acronym>da</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="100029" Version="7.2a" ContextApps="tt"><Term>Data label</Term>
		<Definition>Contains the name or the value of a data point.</Definition>
	</GlossaryEntry>
	<GlossaryEntry Version="7.2a" ContextApps="tt" ID="100111"><Term>Data Language</Term>
		<Definition>The language in which the application data is displayed. Data languages can be linked to users and to software languages.</Definition>
		<SimpleSection><Paragraph class="Default">A data language consists of an ISO 639-1 language code and, optionally, an ISO 3166-1 country code.</Paragraph>
			<Paragraph class="Default">For more information, refer to <Link href="/baanerp/tt/onlinemanual/mle_multi_language_application_data" role="manual">Multilanguage Application Data</Link>.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="100030" Version="7.2a" ContextApps="tt"><Term>Data point</Term>
		<Definition>A point in a chart that represents a value and is made visible by means of a symbol, bar, pie segment, or a step in a line. The data point value is determined by the chart series, the category, and the data value.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000043"><Term>Data replication</Term>
		<Definition>A method of table sharing in which every modification of a table is copied to the companies that share the table.</Definition>
		<SimpleSection><Paragraph class="Default">In ERP LN, you can perform <Link href="#100078" role="internal">Batch-oriented replication</Link> by using the <GUIRef href="/baanerp/da/xch" role="module">Exchange</GUIRef> module.</Paragraph>
		</SimpleSection>
		<Synonym>replication</Synonym>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000019" Version="7.2a" ContextApps="tt"><Term>Database</Term>
		<Definition>A collection of data that is organized so that its contents can easily be accessed, managed, and updated. A database has tools to search for data in the database, sort the data in the database, and so on.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000020" Version="7.2a" ContextApps="tt"><Term>Database administrator</Term>
		<Definition>The individual responsible for the installation, planning, configuration, management control, and maintenance of the relational database.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100002" Version="7.2a" ContextApps="tt"><Term>Database authorizations</Term>
		<Definition>The set of sessions that can be used to print, display, maintain and convert the authorizations that a group of users with the same role, has for specific tables and table fields in the database.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000021" Version="7.2a" ContextApps="tt"><Term>Database group</Term>
		<Definition>A group of database users with the same authorizations and rights. When you add a database user to a database group, the user automatically receives the group's authorizations and rights.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100226" Version="7.4a" ContextApps="tt"><Term>Database Management System</Term>
		<Definition>A software interface between the database and the application software. A database management system handles user requests for database actions and allows for control of security and data integrity requirements.</Definition>
		<Acronym>DBMS</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000022" Version="7.2a" ContextApps="tt"><Term>Database user</Term>
		<Definition>An ERP LN user that is also authorized to access the database. The configuration information for the database user contains all the necessary settings to log on to a database. When the user logs on, these settings are automatically loaded. Every database user must belong to a database group.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAP3HTB"><Term>DBMS</Term>
		<Definition>See: <Link href="#100226" role="internal">Database Management System</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAIZHTB"><Term>DD</Term>
		<Definition>See: <Link href="#100005" role="internal">Data Dictionary</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000010" Version="7.2a" ContextApps="tt"><Term>Dependency</Term>
		<Definition>In PMC, the relation between solutions. Dependencies are defined at the PMC distributor side and are part of the meta data of a PMC solution and guarantee that PMC solutions are installed in the correct configuration and sequence at the PMC recipient side.</Definition>
		<SimpleSection><Paragraph class="Default">The following values indicate the dependency type between solutions.</Paragraph>
			<List><ListIntro>Three dependency types are available:</ListIntro>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#pre-requisite" role="glossary">Pre-requisites</Link>
				</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#co-requisite" role="glossary">Co-requisites</Link>
				</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#post-requisite" role="glossary">Post-requisites</Link>
				</ListItem>
			</List>
			<Paragraph class="Default">You can only install solutions that are dependent on other solutions if the other solutions are already present, or are also installed.</Paragraph>
			<Paragraph class="Default">The same dependency types exist between <Link href="/baanerp/tt/glossary/glossary#100256" role="glossary">Patches</Link>. However, to keep the descriptions readable, only solutions are mentioned, but patches are meant as well. One exception applies: the post-requisite type is not applicable to patches.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="derived_product" ContextApps="tt"><Term>Derived product</Term>
		<Definition>A product that is derived from a parent master product. The parent product can, for example, be a main ERP version such as ERP LN 6.1. In general, the derived product contains a subset of components from the parent product that are changed and possibly a number of new software components.</Definition>
		<SimpleSection><List><ListIntro>There are three categories of derived products:</ListIntro>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#100258" role="glossary">Localizations</Link>
				</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#extension" role="glossary">Extensions</Link>
				</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#customization" role="glossary">Customizations</Link>
				</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="details_session" Version="7.2a" ContextApps="tt"><Term>Details session</Term>
		<Definition>A dialog box that shows all the details (fields) of the line (record) selected in the associated overview session. Use a details session to view, enter, or change the data of one record.</Definition>
		<SimpleSection><Paragraph class="Default">A details session can contain a number of tabs to group related fields.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="dvrc.tt" Version="7.2a" ContextApps="tt"><Term>Development VRC</Term>
		<Definition>In PMC a physical VRC, derived from the <Link href="/baanerp/tt/glossary/glossary#100254" role="glossary">Export VRC</Link>, in which checked-out software components are temporarily stored during a change process.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100021" Version="7.2a" ContextApps="tt"><Term>Device</Term>
		<Definition>A generic term for a computer subsystem. For example, a printer, serial port, or a disk drive.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAMEITB"><Term>DLL</Term>
		<Definition>See: <Link href="#dll.tt" role="internal">Dynamic Link Library</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="domain.tt" Version="7.2a" ContextApps="tt"><Term>Domain</Term>
		<Definition>A domain describes the properties of table fields. The main property of a field is the data type, e.g. string, long, double, date, UTC. Other properties are, for example, the length of a string, the alignment of a string, and the date and time format.</Definition>
		<SimpleSection><Paragraph class="Default">In the Chart Manager, a range with an initial value, an end value, and a step size. Domains indicate the valid values for an attribute and are used to define the scale division of the axes or to verify data.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="100025" Version="7.2a" ContextApps="tt"><Term>Driver</Term>
		<Definition>A hardware device or program that controls other devices. A printer driver, for example, is designed to enable other programs to work with a specific printer regardless of the printer's hardware specifications or language.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100007" Version="7.2a" ContextApps="tt"><Term>Dump</Term>
		<Definition>To copy data to an external source.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000001" Version="7.3adoc1" ContextApps="tt"><Term>Dynamic form</Term>
		<Definition>A form with a dynamic form definition.</Definition>
		<SimpleSection><Paragraph class="Default">The developer does not need to determine exactly where fields must be placed, or what they must look like. Instead, the developer defines:</Paragraph>
			<List><ListItem>The form contents.</ListItem>
				<ListItem>The form structure.</ListItem>
				<ListItem>The sequence of the objects on the form.</ListItem>
			</List>
			<Paragraph class="Default">At runtime, the dynamic form displays only those fields for which the user is authorized.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="dll.tt" Version="7.2a" ContextApps="tt"><Term>Dynamic Link Library</Term>
		<Definition>A means of sharing commom functions between several programs. This library contains functions for common use. The library can be linked to the object as a function call at run time. Implementation of a dynamic link library reduces the size of objects to a minimum because dynamic link libraries are not included in a programs object.</Definition>
		<Acronym>DLL</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="100049" Version="7.3adoc1" ContextApps="tt"><Term>Dynamic session</Term>
		<Definition>A session with a dynamic form definition. Depending on specific settings, a dynamic session can: -Either start as a details session or as an overview session. -Start as a details session only. -Start as an overview session only.</Definition>
		<SimpleSection><Paragraph class="Default">In the dynamic form definition, the developer does not need to determine exactly where fields must be placed, or what they must look like. Instead, the developer defines: -The form contents. -The form structure. -The sequence of the objects on the form.</Paragraph>
			<Paragraph class="Default">At runtime the dynamic form displays only those fields for which the user is authorized.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000008" Version="7.2a" ContextApps="tt"><Term>Element</Term>
		<Definition>A general term used for entities defined in ERP LN, such as items, business partners, currencies, and so on. The details of an element are registered in the database as a record. In an overview session each element or record is represented by a line.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100073" Version="7.2a" ContextApps="tt"><Term>eMessage connector</Term>
		<Definition>An interface between ERP LN and various messaging providers, which is based on XML and independent of the message protocol. For example, fax, telex, e-mail, SITA, or SMS.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100017" Version="7.2a" ContextApps="tt"><Term>Encryption</Term>
		<Definition>The process of encoding data to prevent unauthorized access, especially during the transmission of data. You usually need a key to decode encrypted data.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100076" Version="7.2a" ContextApps="tt"><Term>
                              ERP LN 3GL</Term>
		<Definition>A third-generation proprietary programming language that is a mix of Basic and C.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100077" Version="7.2a" ContextApps="tt"><Term>
                              ERP LN 4GL</Term>
		<Definition>A fourth-generation language is a programming language designed for interacting with the programmer used with relational databases. 4GLs are event-driven.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100050" Version="7.2a" ContextApps="tt"><Term>
                              ERP LN shell</Term>
		<Definition>The ERP LN shell is a program that runs the ERP LN applications. The ERP LN shell serves as an interface program between the ERP LN applications, operating system, user interface, and database. This open systems architecture allows the ERP LN applications to operate on all supported combinations of operating systems, user interfaces, and databases.</Definition>
		<Acronym>bshell</Acronym>
		<Synonym>virtual machine</Synonym>
	</GlossaryEntry>
	<GlossaryEntry ID="100051" Version="7.2a" ContextApps="tt"><Term>
                              ERP LN software environment</Term>
		<Definition>The directory structure on the operating system that contains the ERP LN software and data dictionary.</Definition>
		<Acronym>BSE</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000023" Version="7.2a" ContextApps="tt"><Term>
                              ERP LN user</Term>
		<Definition>A person who uses the ERP LN application.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100083" Version="7.2a" ContextApps="tt"><Term>
                              ERP LN windows interface</Term>
		<Definition>A windows-based interface program between the user and the ERP LN servers. The ERP LN windows interface runs on the user workstation and communicates with the <Link href="#100050" role="internal">Bshell</Link>.</Definition>
		<Acronym>BW</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="000041" ContextApps="tt"><Term>Expired</Term>
		<Definition>If a software component, such as a session or a table, is set to expired in a certain VRC, it cannot be used anymore in that VRC and in later VRCs which were derived from the VRC where the component was set to expired.</Definition>
		<SimpleSection><Paragraph class="Default">A software component that was set to expired is still available in preceding VRCs.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="100254" Version="7.5a" ContextApps="tt"><Term>Export VRC</Term>
		<Definition>The physical VRC from which components that belong to a PMC solution must be exported at the PMC distributor side. Each <Link href="/baanerp/tt/glossary/glossary#100249" role="glossary">base VRC</Link> has an export VRC linked, so components for different products are exported from different physical VRCs.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100006" Version="7.2a" ContextApps="tt"><Term>Expression</Term>
		<Definition>A combination of symbols that produces a result upon evaluation. For example, identifiers, values, and operators. The resulting value can then be assigned to a variable, passed as an argument, tested in a control statement, or used in another expression.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="extension" ContextApps="tt"><Term>Extension</Term>
		<Definition>A derived product meant to fulfill requirements of a particular line of business.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="feature_pack"><Term>Feature Pack</Term>
		<Definition>See <Link href="/baanerp/tt/glossary/glossary#service_pack" role="glossary">Service Pack</Link>.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100241" Version="7.4a" ContextApps="tt"><Term>Field</Term>
		<Definition>In table definitions, a field refers to a column. In a session, a field is a specified area of a record used for a particular category of data.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000003" Version="7.2a" ContextApps="tt"><Term>Field help</Term>
		<Definition>Help that explains the field's value and how it is used in the session. Field help also mentions the default values and which values are possible or allowed. Related topics point you to the related functionality in the online manual.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000003" Version="7.3adoc1" ContextApps="tt"><Term>Filter</Term>
		<Definition>A means to selectively display specific information.</Definition>
		<SimpleSection><List><ListIntro>In ERP LN, two types of filters exist:</ListIntro>
				<ListItem>A way in which ERP LN users can display and sort a specific subset of records in an overview session.</ListItem>
				<ListItem>A program that suppresses the display of specific fields in a session, depending on the user's authorizations. These form field authorization filters are used during the form definition. The filters are determined by the roles that you specify in the Authorization Management System.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000013" Version="7.2a" ContextApps="tt"><Term>Float</Term>
		<Definition>A data type name used to declare variables that can store floating-point numbers, that is, any number containing a decimal point, with a maximum of 15 significant digits (8 bytes).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100022" Version="7.2a" ContextApps="tt"><Term>Font</Term>
		<Definition>A set of characters of the same typeface, style, and weight. For example Arial, in italic, and bold.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="form.tt" Version="7.2a" ContextApps="tt"><Term>Form</Term>
		<Definition>A screen that appears when a session is started. A form interacts with the database, and provides the user interface that is used to manipulate the data on the form.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100053" Version="7.2a" ContextApps="tt"><Term>Form command</Term>
		<Definition></Definition>
		<SimpleSection><List><ListIntro>A command:</ListIntro>
				<ListItem>that starts a session, function or (sub)menu by means of which a user can carry out a particular task.</ListItem>
				<ListItem>that, as opposed to standard menu commands such as the <GUIRef href="" role="manual">Exit</GUIRef> command, must be especially defined for a session tab.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000015" Version="7.2a" ContextApps="tt"><Term>Form field</Term>
		<Definition>A field that is shown on a form. A form field is selected from the available fields of an input table and its reference tables.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100056" Version="7.3adoc1" ContextApps="tt"><Term>Function</Term>
		<Definition>A piece of program code that makes up part of a program script.</Definition>
		<SimpleSection><Paragraph class="Default">A function is a self-contained software routine that can perform a task for the program in which the function is written, or for another program.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000006" Version="7.2a" ContextApps="tt"><Term>Glossary</Term>
		<Definition>Definitions of the terms used in ERP LN.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100024" Version="7.2a" ContextApps="tt"><Term>Graph</Term>
		<Definition>A graphical representation of information in a coordinate system. Quantities are represented by bars, lines, symbols, or combinations of these.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100028" Version="7.2a" ContextApps="tt"><Term>Graph series</Term>
		<Definition>A number of data points that are linked graphically by means of a line, a number of symbols, bars, or combinations of these.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000005" Version="7.2a" ContextApps="tt"><Term>Group</Term>
		<Definition>A set of form objects grouped together. Examples of form objects are form fields and child groups.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000006" Version="7.2a" ContextApps="tt"><Term>Group-by field</Term>
		<Definition>A field on an overview form that is positioned above the grid. The Group-by field determines what is shown in the grid of an overview form. Only the records that belong to the Group-by fields are shown in the grid, for example, all orders that belong to a specific customer. The name of the customer is shown in the Group-by field, the records are shown in the grid.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100045" Version="7.2a" ContextApps="tt"><Term>Help components</Term>
		<Definition>Several sorts of online Help used in ERP LN.</Definition>
		<SimpleSection><List><ListIntro>The Help components in ERP LN are:</ListIntro>
				<ListItemHead>Session Help</ListItemHead>
				<ListItem>Describes the general purpose of a session and how the session must be used.</ListItem>
				<ListItemHead>Field Help</ListItemHead>
				<ListItem>Describes the meaning of the field and helps you to enter a correct value in the field.</ListItem>
				<ListItemHead>Domain Help</ListItemHead>
				<ListItem>Describes the option list values of a field.</ListItem>
				<ListItemHead>Command Help</ListItemHead>
				<ListItem>Describes the command buttons, toolbar buttons, and menu commands.</ListItem>
				<ListItemHead>Glossary</ListItemHead>
				<ListItem>Describes a definition of terms that are frequently used in ERP LN.</ListItem>
				<ListItemHead>Online manuals</ListItemHead>
				<ListItem>Describes the concepts and methods that are used in ERP LN.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="100042" Version="7.2a" ContextApps="tt"><Term>Help topic</Term>
		<Definition>The code of the help text that is used to link help texts to software components. Each text has a help text code and belongs to a package VRC.</Definition>
		<SimpleSection></SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="index.tt" Version="7.2a" ContextApps="tt"><Term>Index</Term>
		<Definition>One or more table fields used to sort and search records in a <Link href="/baanerp/tt/glossary/glossary#table.tt" role="glossary">table</Link>. A table must have at least one index. The first index is always the <Link href="#primarykey.tt" role="internal">Primary key</Link>.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100079" Version="7.2a" ContextApps="tt"><Term>
                              Infor Environment and Configuration Selector
                           </Term>
		<Definition>A tool that makes it possible to run different <Link href="#100083" role="internal">BW</Link> versions on a single client.</Definition>
		<Acronym>BECS</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="installation_run"><Term>Installation run</Term>
		<Definition>In PMC, a group of solutions that were installed together. This can be a range of solutions, a solution with <Link href="/baanerp/tt/glossary/glossary#pre-requisite" role="glossary">pre-requisites</Link>, or a combination of both.</Definition>
		<SimpleSection></SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="100200" Version="7.3adoc1" ContextApps="tt"><Term>Integrated session</Term>
		<Definition>The session and the session's form are integrated into one object. The form is a subcomponent of the session.</Definition>
		<SimpleSection><Paragraph class="Default">When you perform an operation, for example, copy, delete, check-in, or checkout, on an integrated session, you also perform the operation on the integrated session's form.</Paragraph>
			<Paragraph class="Default">A non-integrated session's form is a separate object.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000025" Version="7.2a" ContextApps="tt"><Term>Job</Term>
		<Definition>One or more sessions and/or shell scripts that ERP LN executes without user interaction. You can schedule jobs to run periodically or at a specified time.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100041" Version="7.2a" ContextApps="tt"><Term>Job calendar</Term>
		<Definition>A calendar that consists of a number of dates/times, which are used to indicate the dates/time a periodical job must be executed.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="label.tt" Version="7.2a" ContextApps="tt"><Term>Label</Term>
		<Definition>A code that is used instead of language-dependent text in forms, reports, and menus. A label consists of a name and a content description. The content of a label can differ by language, but the label name remains the same for all languages.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100201" Version="7.3adoc1" ContextApps="tt"><Term>Language number</Term>
		<Definition>A conversion of the language code to a number between 0 and 61. The language number eliminates problems caused by the use of uppercase and lowercase language codes. The language code corresponds to the language number by the following convention: Language code range Corresponding language number range 0 to 9 0 to 9 a to z 10 to 35 A to Z 36 to 61.</Definition>
		<ExampleSection><SectionTitle>
                                 Example
                              </SectionTitle>
			<Paragraph class="Default">Language code b = Language number 11 Language code B = Language number 37</Paragraph>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAHWITB"><Term>LDAP</Term>
		<Definition>See: <Link href="#ldap" role="internal">Lightweight Directory Access Protocol</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="library.tt" Version="7.2a" ContextApps="tt"><Term>Library</Term>
		<Definition>A collection of files, computer programs, or subroutines.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100003" Version="7.2a" ContextApps="tt"><Term>Library authorizations</Term>
		<Definition>The set of sessions that can be used to print, display, maintain, and convert the authorizations of a group with the same role has for specific Dynamic Link Libraries.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100015" Version="7.2a" ContextApps="tt"><Term>License</Term>
		<Definition>A means to validate the system configuration request of the customer.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="ldap"><Term>Lightweight Directory Access Protocol</Term>
		<Definition>In computer networking, the Lightweight Directory Access Protocol, or LDAP, is a standardized networking protocol designed for querying and modifying directory services.</Definition>
		<Acronym>LDAP</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="100043" Version="7.2a" ContextApps="tt"><Term>Locale</Term>
		<Definition>The character set and language used by a system.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100258" ContextApps="tt"><Term>Localization</Term>
		<Definition>A derived product meant to fulfill country specific requirements.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100229" Version="7.4a" ContextApps="tt"><Term>Log</Term>
		<Definition>verb: To create a record of transactions or activities that take place on a computer system. noun: A record of transactions or activities that take place on a computer system.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000040" ContextApps="tt"><Term>Logical company</Term>
		<Definition>Company as seen by the application. The sessions and program scripts of ERP LN use the logical companies without having to know the physical company where the tables are actually stored.</Definition>
		<SimpleSection><Paragraph class="Default">In the most simple situation, a table in a logical company is linked to a physical company with the same company number as the logical company. In that case, the logical company and the physical company are the same company. If you use logical logical table linking, a table in a logical company is linked to a physical company with a different company number.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="LogicalPrint.tt" Version="7.2a" ContextApps="tt"><Term>Logical printer</Term>
		<Definition>A logical printer is a set of printer devices. In some environments several printers may be located in close proximity to one another ( same room/floor). They can be grouped together as a logical printer. When output is directed to a logical printer, the printer daemon will check the paper type of each printer. It will automatically direct output to the first printer that contains the required paper type.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100244" Version="7.5a" ContextApps="tt"><Term>Long</Term>
		<Definition>A data type specified in ERP LN as any whole number from -2147483648 to 2147483647.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="menu.tt" Version="7.2a" ContextApps="tt"><Term>Menu</Term>
		<Definition>A list of options from which a user can make a selection to perform a desired action, such as starting sessions, other menus, and queries. A start-up menu is defined for each user. Using this start-up menu, the user can access all sub-menus attached to the start-up menu tree.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100057" Version="7.2a" ContextApps="tt"><Term>Merge</Term>
		<Definition>A process which creates a target VRC from a source VRC.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100247" Version="7.5a" ContextApps="tt"><Term>Message</Term>
		<Definition>A notification that informs you about something. More specifically, a message attends you to an event, error, warning, and so on. Messages usually appear in a message window or logged in a file. If displayed in a window, a message requires a confirmation: Click OK. Messages are distinguished from <Link href="/baanerp/tt/glossary/glossary#100248" role="glossary">Questions</Link>, which always require a choice response.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100089" Version="7.2a" ContextApps="tt"><Term>Message server</Term>
		<Definition>A server that stores and sends messages to clients</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100004" Version="7.2a" ContextApps="tt"><Term>Module</Term>
		<Definition>A part of a package consisting of a number of related software components, such as sessions, tables, program scripts, reports, forms and menus. For example, the <GUIRef href="/baanerp/tf/gld" role="module">General Ledger</GUIRef> module in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>.</Definition>
		<SimpleSection><Paragraph class="Default">A module code consists of three characters. For example, the <GUIRef href="/baanerp/tf/gld" role="module">General Ledger</GUIRef> has the code "gld".</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000018" Version="7.2a" ContextApps="tt"><Term>Multi occurrence</Term>
		<Definition>A session that lists the available elements or records of one type, and some of their details (fields). You can use an overview session to view, sort, add, change, copy, and remove records.</Definition>
		<SimpleSection><Paragraph class="Default">When you add or change a record a details session usually starts. In some cases, you can add and change records directly using the overview session.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="100040" Version="7.2a" ContextApps="tt"><Term>Native Language Support</Term>
		<Definition>Native Language Support. The system to convert character sets between different computer systems. In ERP LN it normally refers to conversion between the character set of the operating system (for example Windows NT or Unix) and the bshell. The native language is the character set which is used by the operating system on which ERP LN is running.</Definition>
		<Acronym>NLS</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="nis"><Term>Network Information Service</Term>
		<Definition>The Network Information Service or NIS is Sun Microsystems' "Yellow Pages" (YP) client-server directory service protocol for distributing system configuration data such as user and host names between computers on a computer network. NIS/YP is used for keeping a central directory of users, hostnames and most other useful things in a computer network. For example, in a common UNIX environment, the list of users (for authentication) is placed in /etc/passwd. Using NIS adds another "global" user list which is used for authenticating users on any host.</Definition>
		<Acronym>NIS</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAI0ITB"><Term>NIS</Term>
		<Definition>See: <Link href="#nis" role="internal">Network Information Service</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDA4ZITB"><Term>NLS</Term>
		<Definition>See: <Link href="#100040" role="internal">Native Language Support</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="obsolete_solution" ContextApps="tt"><Term>Obsolete solution</Term>
		<Definition>Obsolete solutions are an administrative aid to manage the synchronization of updates at the PMC recipient side when you install a <Link href="/baanerp/tt/glossary/glossary#service_pack" role="glossary">Service Pack</Link>. An obsolete solution does not contain software components.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100058" Version="7.2a" ContextApps="tt"><Term>Operator</Term>
		<Definition>A symbol or other character indicating an operation that acts on one or more elements.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="ovrc.tt" Version="7.2a" ContextApps="tt"><Term>Original VRC</Term>
		<Definition>The VRC that contains the software components that have to be modified. These software components will be changed in the <Link href="#dvrc.tt" role="internal">Development VRC</Link>.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="multi-occ.tt" Version="7.2a" ContextApps="tt"><Term>Overview session</Term>
		<Definition>A session that lists the available elements or records of one type, and some of their details (fields). You can use an overview session to view, sort, add, change, copy, and remove records.</Definition>
		<SimpleSection><Paragraph class="Default">When you add or change a record a details session usually starts. In some cases, you can add and change records directly using the overview session.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000008" Version="7.2a" ContextApps="tt"><Term>Package</Term>
		<Definition>A set of related modules that implements a complete part of the functionality, for example, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>, <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>, or <GUIRef href="/baanerp/wh" role="package">Warehouse Management</GUIRef>. Packages are designed to function as independent as possible, to enable a customer to implement only particular packages.</Definition>
		<SimpleSection><Paragraph class="Default">A package code consists of two characters. For example, tt is the code of the <GUIRef href="/baanerp/tt" role="package">Tools</GUIRef> package.</Paragraph>
			<Paragraph class="Default">Each package has a unique version structure, the VRC structure.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000012" Version="7.2a" ContextApps="tt"><Term>Package combination</Term>
		<Definition>A combination of several different packages with specific VRCs. A package combination represents a complete usable version of ERP LN.</Definition>
		<SimpleSection><Paragraph class="Default">In the <Link href="/baanerp/tt/aad/ttaad2500m000" role="session">User Data (ttaad2500m000)</Link> session, each user is linked to a package combination, that determines which version of the software the user can use. In the <Link href="/baanerp/tt/aad/ttaad1100m000" role="session">Companies (ttaad1100m000)</Link> session, each company is linked to a package combination, to indicate which version of ERP LN is appropriate to handle the data in that company.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAPZKTB"><Term>package VRC</Term>
		<Definition>See: <Link href="#100016" role="internal">Version - Release - Customer</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000013" Version="7.2a" ContextApps="tt"><Term>Package VRC</Term>
		<Definition>A version of a package, for example, <GUIRef href="" role="manual">tc B61O a cus1</GUIRef>. In general, one version of a software component, such as a session, a table, or a form, is stored in one particular package VRC.</Definition>
		<SimpleSection><Paragraph class="Default">A developer can usually modify software components only in a particular package VRC.</Paragraph>
			<List><ListIntro>The code of a package VRC consists of:</ListIntro>
				<ListItem>Package code, for example, 'tc'</ListItem>
				<ListItem><List><ListIntro>A version (VRC) code, for example 'B61O a cus1', built up of:</ListIntro>
						<ListItem>Version</ListItem>
						<ListItem>Release</ListItem>
						<ListItem>Customer</ListItem>
					</List>
				</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAJDJTB"><Term>PAM</Term>
		<Definition>See: <Link href="#pam" role="internal">Pluggable Authentication Modules</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100013" Version="7.2a" ContextApps="tt"><Term>Paper type</Term>
		<Definition>A particular type of paper that must be used for a printer. The paper type must correspond with the paper type in the printer.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000026" Version="7.2a" ContextApps="tt"><Term>Password</Term>
		<Definition>A password is a form of secret authentication data that is used to control access to a resource. The password is kept secret from those not allowed access, and those wishing to gain access are tested on whether or not they know the password and are granted or denied access accordingly.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="password_aging"><Term>Password aging</Term>
		<Definition>Password aging is a technique used by system administrators to defend against bad passwords within an organization. Password aging means that after a set amount of time, usually 90 days, the user will be prompted to come up with a new password. The theory behind this is that if a user is forced to change his password periodically, a cracked password is only useful to an intruder for a limited amount of time. The downside to password aging, however, is that users are more likely to write their passwords down. With password aging the system administrator can set minimum and maximum lengths of time for which the password is valid. Maximum time lengths force users to change passwords regularly. Minimum lengths prevent users from quickly changing the passwords back.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100256" ContextApps="tt"><Term>Patch</Term>
		<Definition>In PMC, a patch is a collection of <Link href="/baanerp/tt/glossary/glossary#solution" role="glossary">Solutions</Link>. In general a patch contains solutions created in a larger time period. The patch entity is both known at the <Link href="/baanerp/tt/glossary/glossary#pmc_distributor" role="glossary">PMC distributor</Link> and <Link href="/baanerp/tt/glossary/glossary#pmc_recipient" role="glossary">PMC recipient</Link> side. Patches are an indivisible set of solutions. You cannot install or uninstall individual solutions that belong to a patch at the PMC recipient. You can only install or uninstall patches as a whole. Yo can define dependencies between patches. Patches leave the <Link href="/baanerp/tt/glossary/glossary#100249" role="glossary">Base VRC</Link> that is linked to the <Link href="/baanerp/tt/glossary/glossary#100255" role="glossary">update VRC</Link> at the PMC recipient unchanged. The existing PMC registry will remain and will be extended with data of the newly installed patch. Patches only permit the most recent version of software components to be maintained. Patches in general mainly contain corrective solutions.</Definition>
		<Note><SectionTitle>
                                 Note
                              </SectionTitle>
			<Paragraph class="Default">In <Link href="/baanerp/tt/glossary/glossary#pmc_version" role="glossary">PMC versions</Link> earlier than ERP LN 6.1, the synonym Service Packs was often used for patches.</Paragraph>
		</Note>
	</GlossaryEntry>
	<GlossaryEntry ID="100036" Version="7.2a" ContextApps="tt"><Term>Periodical job</Term>
		<Definition>A job that can be executed more than once. For a periodical job, you must specify a time interval or calendar. If desired, the job can be automatically reactivated.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100055" Version="7.2a" ContextApps="tt"><Term>Physical company</Term>
		<Definition>The company where the data is actually stored. You can link tables in <Link href="/baanerp/tt/glossary/glossary#000040" role="glossary">Logical companies</Link> to the corresponding tables of a physical company.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100034" Version="7.2a" ContextApps="tt"><Term>Pie segment</Term>
		<Definition>Represents a percentage of the total pie chart.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="pam"><Term>Pluggable Authentication Modules</Term>
		<Definition>Pluggable authentication modules or PAM are a mechanism to integrate multiple low-level authentication schemes into a high-level API, which allows for programs that rely on authentication to be written independently of the underlying authentication scheme. PAM were first developed by Sun Microsystems, and are currently supported in AIX, HP-UX, Solaris, Linux, FreeBSD and NetBSD.</Definition>
		<Acronym>PAM</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAIIJTB"><Term>PMC</Term>
		<Definition>See: <Link href="#pmc" role="internal">Product Maintenance and Control</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="pmc_distributor"><Term>PMC distributor</Term>
		<Definition>The functional part of PMC that manages the creation of <Link href="/baanerp/tt/glossary/glossary#update" role="glossary">Updates</Link>. PMC Distributor is especially used by software vendors who create updates.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="pmc_recipient"><Term>PMC recipient</Term>
		<Definition>The functional part of PMC that manages the installation of <Link href="/baanerp/tt/glossary/glossary#update" role="glossary">Updates</Link>. Customers, who install updates in particular use PMC recipient.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="pmc_version"><Term>PMC version</Term>
		<Definition>The PMC version is linked to every <Link href="/baanerp/tt/glossary/glossary#update" role="glossary">Update</Link> and is intended to quarantee that various formats of PMC solution dumps are handled by the right version of the PMC software.</Definition>
		<SimpleSection><List><ListItem>PMC version 0 : does not support Service Packs</ListItem>
				<ListItem>PMC version 1 : supports Service Packs</ListItem>
			</List>
		</SimpleSection>
		<Note><SectionTitle>
                                 Note
                              </SectionTitle>
			<Paragraph class="Default">Dumps created for a higher PMC version cannot be processed at the recipient side if PMC recipient has not been upgraded to that PMC version.</Paragraph>
			<Paragraph class="Default">Dumps of lower PMC versions can always be processed.</Paragraph>
		</Note>
	</GlossaryEntry>
	<GlossaryEntry ID="100018" Version="7.2a" ContextApps="tt"><Term>Porting set</Term>
		<Definition>A collection of objects such as bshell, database, drivers, printer daemon and so on, which can only run on the machines/operating systems for which they are compiled/ported.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="post-requisite" ContextApps="tt"><Term>Post-requisite</Term>
		<Definition>Post-requisites are mainly meant to prevent the installation of bad solutions. In general, a post-requisite is a link from an earlier, bad solution to a more recent, correct solution.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="pre-requisite" ContextApps="tt"><Term>Pre-requisite</Term>
		<Definition>Pre-requisites mainly steer the sequence in which solutions are installed. In general a pre-requisite is the link from a more recent solution to a predecessing solution. Pre-requisites are the most common type of dependencies. A pre-requisite dependency exists between two solutions if one solution must have been installed before the other solution is installed. In that case, the first solution is a pre-requisite for the other solution. Typically, pre-requisite dependencies exist between a solution and a previous solution, if these solutions have one or more components in common. Pre-requisite dependencies can only be created to solutions in the same <Link href="/baanerp/tt/glossary/glossary#100249" role="glossary">Base VRC</Link>.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="primarykey.tt" Version="7.2a" ContextApps="tt"><Term>Primary key</Term>
		<Definition>The unique identification for a record in a <Link href="#table.tt" role="internal">Table</Link>.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100012" Version="7.2a" ContextApps="tt"><Term>Printer daemon</Term>
		<Definition>A networking program that permanently runs in the background and handles the print requests issued by the users. When output is directed to a logical printer, the printer daemon checks the paper type of each printer, and then directs the output automatically to the first printer that contains the required paper type.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="pmc"><Term>Product Maintenance and Control</Term>
		<Definition>Product Maintenance and Control (PMC) is a tool that helps a customer manage the updates of the ERP LN system.</Definition>
		<SimpleSection><Paragraph class="Default">With the PMC tool, you can check all patches against the customer's ERP LN system to verify their completeness, check any potential interference with the customization, and detect dependencies.</Paragraph>
			<Paragraph class="Default">These capabilities ensure the complete and accurate installation of each software patch and Service Pack. In addition, using the PMC tool enhances the quality of the support being available to customers.</Paragraph>
			<Paragraph class="Default">PMC consists of a <Link href="/baanerp/tt/glossary/glossary#pmc_distributor" role="glossary">PMC distributor</Link> part and a <Link href="/baanerp/tt/glossary/glossary#pmc_recipient" role="glossary">PMC recipient</Link> part.</Paragraph>
		</SimpleSection>
		<Acronym>PMC</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="progscript.tt" Version="7.2a" ContextApps="tt"><Term>Program script</Term>
		<Definition>A sequence of instructions that is used to program a number of actions that must take place in addition to the standard program. Two different program scripts are available, namely 3GL scripts and 4GL scripts.</Definition>
		<Synonym>UI script</Synonym>
	</GlossaryEntry>
	<GlossaryEntry ID="IDANZKTB"><Term>PVRC</Term>
		<Definition>See: <Link href="#100016" role="internal">Version - Release - Customer</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100052" Version="7.2a" ContextApps="tt"><Term>Query</Term>
		<Definition>The process of extracting information from a database and presenting it in a report.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100248" Version="7.5a" ContextApps="tt"><Term>Question</Term>
		<Definition>A notification that requires a choice response. For example, a question can prompt you to confirm or cancel a delete action. If you do not respond to a question, the process that prompted the question cannot continue. Questions are distinguished from <Link href="#100247" role="internal">Messages</Link>, which offer no choice and do not necessarily require a response.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000027" Version="7.2a" ContextApps="tt"><Term>Question mark button</Term>
		<Definition>Changes the pointer into a question mark. To display pop-up Help that briefly describes the command, click a menu command, a command button, or a toolbar button with the question mark pointer.</Definition>
		<SimpleSection><Paragraph class="Default">To display the field Help, click a field with the question mark pointer.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAUSJTB"><Term>RCS</Term>
		<Definition>See: <Link href="#rcs.tt" role="internal">Revision Control System</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAKKJTB"><Term>RDBMS</Term>
		<Definition>See: <Link href="#000000000000024" role="internal">Relational Database Management System</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100059" Version="7.2a" ContextApps="tt"><Term>Record</Term>
		<Definition>A data structure that is a collection of fields (elements), each with its own name and type. The elements of a record represent different types of information and are accessed by name. A record can be accessed as a collective unit of elements, or the elements can be accessed individually.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDACRKTB"><Term>reference</Term>
		<Definition>See: <Link href="#000046" role="internal">Table reference</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000047" ContextApps="tt"><Term>Reference mode</Term>
		<Definition>The way in which a reference restricts the contents of a table field.</Definition>
		<SimpleSection><List><ListIntro>A reference can have one of the following reference modes:</ListIntro>
				<ListItemHead><GUIRef href="/baanerp/tt/domains/adv.refm#compulsory" role="option">Mandatory</GUIRef>
				</ListItemHead>
				<ListItem>The field must contain a code that is found the reference table.</ListItem>
				<ListItemHead><GUIRef href="/baanerp/tt/domains/adv.refm#unless.empty" role="option">Mandatory unless empty</GUIRef>
				</ListItemHead>
				<ListItem>The field can be empty. If the field is not empty, the field must contain a code that is found the reference table.</ListItem>
				<ListItemHead><GUIRef href="/baanerp/tt/domains/adv.refm#not.compulsory" role="option">Not mandatory</GUIRef>
				</ListItemHead>
				<ListItem>The field can be filled with a code that is not found in the reference table. The reference only serves to expedite queries.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000050" ContextApps="tt"><Term>Reference table</Term>
		<Definition>The table to which some table field refers.</Definition>
		<ExampleSection><SectionTitle>
                                 Example
                              </SectionTitle>
			<Paragraph class="Default">One of the fields of the <GUIRef href="" role="manual">Items – General</GUIRef> table is the <GUIRef href="" role="manual">Country of Origin</GUIRef> (coor) field. This field can contain a country code. (The field can also be left empty.) ERP LN stores country codes in the <GUIRef href="" role="manual">Countries</GUIRef> table. To control this connection, the table field <GUIRef href="" role="manual">Country of Origin</GUIRef> in the <GUIRef href="" role="manual">Items – General</GUIRef> table has a reference to the <GUIRef href="" role="manual">Countries</GUIRef> table.</Paragraph>
			<Paragraph class="Default"><GUIRef href="" role="manual">Items – General</GUIRef> is the <Emphasis>referral table</Emphasis> and <GUIRef href="" role="manual">Countries</GUIRef> is the <Emphasis>reference table</Emphasis>.</Paragraph>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000048" ContextApps="tt"><Term>Reference type</Term>
		<Definition>The means by which a reference is defined.</Definition>
		<SimpleSection><List><ListItemHead><GUIRef href="/baanerp/tl/domains/tsm.reft#hard" role="option">Hard</GUIRef>
				</ListItemHead>
				<ListItem>If the reference type is <GUIRef href="/baanerp/tl/domains/tsm.reft#hard" role="option">Hard</GUIRef>, the reference is defined in the table definition. This reference type is the most common.</ListItem>
				<ListItemHead><GUIRef href="/baanerp/tl/domains/tsm.reft#soft" role="option">Soft</GUIRef>
				</ListItemHead>
				<ListItem>If the reference type is <GUIRef href="/baanerp/tl/domains/tsm.reft#soft" role="option">Soft</GUIRef>, the reference is not defined in the table definition, but programmed in a program script or dll.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000051" ContextApps="tt"><Term>Referral table</Term>
		<Definition>The table that has a field that refers to another table.</Definition>
		<ExampleSection><SectionTitle>
                                 Example
                              </SectionTitle>
			<Paragraph class="Default">One of the fields of the <GUIRef href="" role="manual">Items – General</GUIRef> table is the <GUIRef href="" role="manual">Country of Origin</GUIRef> (coor) field. This field can contain a country code. (The field can also be left empty.) ERP LN stores country codes in the <GUIRef href="" role="manual">Countries</GUIRef> table. To control this connection, the table field <GUIRef href="" role="manual">Country of Origin</GUIRef> in the <GUIRef href="" role="manual">Items – General</GUIRef> table has a reference to the <GUIRef href="" role="manual">Countries</GUIRef> table.</Paragraph>
			<Paragraph class="Default"><GUIRef href="" role="manual">Items – General</GUIRef> is the <Emphasis>referral table</Emphasis> and <GUIRef href="" role="manual">Countries</GUIRef> is the <Emphasis>reference table</Emphasis>.</Paragraph>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000024" Version="7.2a" ContextApps="tt"><Term>Relational Database Management System</Term>
		<Definition>A relational database or database management system that consists of tables made up of rows and columns. In a relational database, the rows of a table represent records and the columns represent fields with the particular attributes of a record. The records are collections of information about separate items. The attributes of the records are represented in the columns. The relational database management system uses data in a specified column of one table to find additional data in another table.</Definition>
		<Acronym>RDBMS</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000010" Version="7.3adoc1" ContextApps="tt"><Term>Release</Term>
		<Definition>An update in a version. For example, 'B61 a', where 'B61' represents the version code, and the 'a' represents the release code. Each update results in a new release with a new release code.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDA11HTB"><Term>replication</Term>
		<Definition>See: <Link href="#000043" role="internal">Data replication</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="report.tt" Version="7.2a" ContextApps="tt"><Term>Report</Term>
		<Definition>A report is used to present data from the database, usually on paper. The report can be sent to a device, such as a physical printer, a display, or to a file.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="rcs.tt" Version="7.2a" ContextApps="tt"><Term>Revision Control System</Term>
		<Definition>A tool, that is used by <GUIRef href="/baanerp/tt" role="package">Tools</GUIRef> to store revisions of scripts, libraries, includes and report scripts.</Definition>
		<Acronym>RCS</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="000017" Version="7.2a" ContextApps="tt"><Term>Role</Term>
		<Definition>From a user point of view, a function, or part of a function in an organization. For example, manager, secretary, and so on. From an authorization point of view, an identifying name for a group of users. A role can contain several sub roles.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAB4JTB"><Term>SCM</Term>
		<Definition>See: <Link href="#scm.tt" role="internal">Software Configuration Management</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100074" Version="7.2a" ContextApps="tt"><Term>SCM group</Term>
		<Definition>A <Link href="#scm.tt" role="internal">Software Configuration Management</Link> group in ERP LN that identifies a development group that has a separate development environment.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="SSPI"><Term>Security Support Provider Interface</Term>
		<Definition>Security Support Provider Interface (SSPI) allows an application to use various security models available on a computer or network without changing the interface to the security system. SSPI does not establish logon credentials because that is generally a privileged operation handled by the operating system. A security support provider (SSP) is contained in a dynamic-link library (DLL) that implements SSPI by making one or more security packages available to applications. Each security package provides mappings between the SSPI function calls of an application and the functions of an actual security model. Security packages support security protocols such as Kerberos authentication and LAN Manager.</Definition>
		<Acronym>SSPI</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="100242" Version="7.4a" ContextApps="tt"><Term>Sequence file</Term>
		<Definition>The file in which (a part of) the audit trail is stored.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100234" Version="7.4a" ContextApps="tt"><Term>Server</Term>
		<Definition>A program or system that performs a predefined task at request of a user or another program or system. See also client.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="service_pack" ContextApps="tt"><Term>Service Pack</Term>
		<Definition>In PMC, a Service Pack is a collection of solutions. In general, a Service Pack contains solutions created in a larger time period. In PMC the term 'patch' is also applied for Service Packs. The patch entity is both known at the PMC distributor and PMC recipient side. A property in the patch entity makes the difference between patches and Service Packs. Service Packs are an indivisible set of solutions. You cannot install or uninstall solutions that belong to a Service Pack at the PMC recipient. You can only install or uninstall Service Packs as a whole. You can define dependencies between Service Packs. Service Packs are intended to enable you to maintain multiple <Link href="/baanerp/tt/glossary/glossary#100249" role="glossary">Base VRCs</Link> in parallel. Service Packs change the base VRC that is linked to the update VRC at the PMC recipient. The existing PMC registry for the update VRC will be moved to history and a new registry will be started for the update VRC. This type of patch in general contains a significant amount of functional changes.</Definition>
		<Note><SectionTitle>
                                 Note
                              </SectionTitle>
			<Paragraph class="Default">Service Packs as described in the preceding definition do not exist in PMC versions earlier than ERP LN 6.1.</Paragraph>
		</Note>
		<Acronym>SP</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="100090" Version="7.2a" ContextApps="tt"><Term>Service provider</Term>
		<Definition>The software application that enables messaging, such as Outlook or Fenestrae.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="session.tt" Version="7.2a" ContextApps="tt"><Term>Session</Term>
		<Definition>An elementary part of ERP LN the user can start to run an application's functionality. Usually, a session is linked to a main database table and a program script. In addition, a session uses zero or more forms, reports, and charts.</Definition>
		<SimpleSection><Paragraph class="Default">The code of a session consists of a package code, a module code, four digits that indicate the main table number and the session type, an m or an s, and three additional digits, for example, <GUIRef href="/baanerp/tc/mcs/tcmcs0510m000" role="session">Countries (tcmcs0510m000)</GUIRef>.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="100000" Version="7.2a" ContextApps="tt"><Term>Session authorizations</Term>
		<Definition>The set of sessions that can be used to print, display, maintain and convert the authorizations that a group of users, that are identified by a role, have for specific sessions.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100047" Version="7.2a" ContextApps="tt"><Term>Session group</Term>
		<Definition>A group of sessions that are automatically started when a user starts the bshell.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000002" Version="7.2a" ContextApps="tt"><Term>Session help</Term>
		<Definition>Help that tells you how to use the session and what the result will be. Notes and remarks draw your attention to any special information. Related topics point you to a description of the related functionality in the online manual.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100091" Version="7.2a" ContextApps="tt"><Term>Shared memory</Term>
		<Definition>A part of physical memory intended for common use. Programs communicate with each other through shared memory. The use of shared memory results in faster access to the components loaded in shared memory. Before starting the application, shared memory must be initialized and setup. A prerequisite for using shared memory is that it should be supported by the hardware besides having sufficient internal memory at its disposal.</Definition>
		<SimpleSection><List><ListIntro>The following components can be loaded into shared memory:</ListIntro>
				<ListItem>report objects</ListItem>
				<ListItem>program objects</ListItem>
				<ListItem>table definitions</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="100026" Version="7.2a" ContextApps="tt"><Term>Shell command</Term>
		<Definition>The program, at operating system level, which is executed before the output is (re) written to a file. For example, this program can be a conversion program to filter the input data.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000017" Version="7.2a" ContextApps="tt"><Term>Single occurrence</Term>
		<Definition>A dialog box that shows all the details (fields) of the line (record) selected in the associated overview session. Use a details session to view, enter, or change the data of one record.</Definition>
		<SimpleSection><Paragraph class="Default">A details session can contain a number of tabs to group related fields.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="SSO"><Term>Single sign-on</Term>
		<Definition>Single sign-on (SSO) is a specialized form of software authentication that enables a user to authenticate once and gain access to the resources of multiple software systems.</Definition>
		<SimpleSection><List><ListIntro>There are at least five major types of SSO or reduced signon systems in common use at the time of this writing (2005):</ListIntro>
				<ListItemHead>Enterprise single sign-on</ListItemHead>
				<ListItem>(E-SSO), also called legacy single sign-on, after primary user authentication, intercepts login prompts presented by secondary applications, and automatically fills in fields such as a login ID or password. E-SSO systems allow for interoperability with applications that are unable to externalize user authentication, essentially through "screen scraping."</ListItem>
				<ListItemHead>Web single sign-on</ListItemHead>
				<ListItem>(Web-SSO), also called Web access management (Web-AM) works strictly with applications and resources accessed with a web browser. Access to web resources is intercepted, either using a web proxy server or by installing a component on each targeted web server. Unauthenticated users who attempt to access a resource are diverted to an authentication service, and returned only after a successful sign-on. Cookies are most often used to track user authentication state, and the Web-SSO infrastructure extracts user identification information from these cookies, passing it into each web resource.</ListItem>
				<ListItemHead>Kerberos</ListItemHead>
				<ListItem>is a popular mechanism for applications to externalize authentication entirely. Users sign into the Kerberos server, and are issued a ticket, which their client software presents to servers that they attempt to access. Kerberos is available on Unix, Windows and mainframe platforms, but requires extensive modification of client/server application code, and is consequently not used by many legacy applications.</ListItem>
				<ListItemHead>Federation</ListItemHead>
				<ListItem>is a new approach, also for web applications, which uses standards-based protocols to enable one application to assert the identity of a user to another, thereby avoiding the need for redundant authentication. Standards to support federation include SAML and WS-Security.</ListItem>
				<ListItemHead>OpenID</ListItemHead>
				<ListItem>is a distributed and decentralized SSO process, where identity is tied to an easily-processed URL which can be verified by any server using the protocol.</ListItem>
			</List>
		</SimpleSection>
		<Acronym>SSO</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="software_component"><Term>Software component</Term>
		<Definition>The ERP LN software exists of the following separate software components:</Definition>
		<SimpleSection><List><ListItem><Link href="/baanerp/tt/glossary/glossary#100247" role="glossary">Message</Link>
				</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#report.tt" role="glossary">Report</Link>
				</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#label.tt" role="glossary">Label</Link>
				</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#100056" role="glossary">Function</Link>
				</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#100032" role="glossary">Business Object</Link>
				</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#100009" role="glossary">Chart</Link>
				</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#100200" role="glossary">Integrated session</Link>
				</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#100243" role="glossary">Additional file</Link>
				</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#100248" role="glossary">Question</Link>
				</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#session.tt" role="glossary">Session</Link>
				</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#domain.tt" role="glossary">Domain</Link>
				</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#table.tt" role="glossary">Table</Link>
				</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#menu.tt" role="glossary">Menu</Link>
				</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#form.tt" role="glossary">Form</Link>
				</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#progscript.tt" role="glossary">Program script</Link>
				</ListItem>
				<ListItem><Link href="/baanerp/tt/glossary/glossary#library.tt" role="glossary">Library</Link>
				</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="scm.tt" Version="7.2a" ContextApps="tt"><Term>Software Configuration Management</Term>
		<Definition>With software configuration management, a developer can modify and test an own revision of a software component. Using a check-out and check-in functionality, a software component is locked for others developers. This method guarantees that no more than one developer can modify the same software component at the same time.</Definition>
		<Acronym>SCM</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="100112"><Term>Software Language</Term>
		<Definition>The language in which the software components, such as forms and reports, are displayed. For each user, the default software language is defined in the ERP LN user data.</Definition>
		<SimpleSection><Paragraph class="Default">For more information, refer to <Link href="/baanerp/tt/onlinemanual/mle_multi_language_application_data" role="manual">Multilanguage Application Data</Link>.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="solution" ContextApps="tt"><Term>Solution</Term>
		<Definition>In PMC, the smallest, indivisible type of update. A solution is identified both at the distributor and recipient side by a unique solution code. The term individual solution is also frequently used and has the same meaning.</Definition>
		<Note><SectionTitle>
                                 Note
                              </SectionTitle>
			<Paragraph class="Default">In the PMC software the term solution is often used as an alternative for the term update. A solution can then be an individual solution, which is the smallest, indivisible type of an update, or a patch.</Paragraph>
		</Note>
	</GlossaryEntry>
	<GlossaryEntry ID="solution_status_distributor"><Term>Solution status distributor</Term>
		<Definition>The following statuses describe the progress of the maintenance of solutions, <Link href="/baanerp/tt/glossary/glossary#100257" role="glossary">Collections</Link>, and <Link href="/baanerp/tt/glossary/glossary#100256" role="glossary">patches</Link>. To keep the descriptions readable, only solutions are described. However, in each case, collections and patches are intended as well, unless explicitly excepted.</Definition>
		<SimpleSection><Paragraph class="Default">The status of the solution is only used at the distributor side. A history of status changes is recorded in the <GUIRef href="" role="manual">Maintenance History</GUIRef> table.</Paragraph>
			<Paragraph class="Default">To distinguish maintained solutions at the distributor side from imported solutions at the recipient side, the status is cleared when the solution is imported. This also applies to patches, but not to collections. The reason is that a collection is not known as such at the recipient side. Only the solutions contained in the collection are known at the recipient side.</Paragraph>
			<List><ListItemHead>In progress</ListItemHead>
				<ListItem>The initial status of the solution upon creation.</ListItem>
				<ListItemHead>Dependencies defined</ListItemHead>
				<ListItem>The dependencies between the various solutions are defined, and the solution is ready to be exported. You must select this status manually, because you might want to create dependencies that cannot be created automatically.</ListItem>
				<ListItemHead>Exported</ListItemHead>
				<ListItem>The solution is exported. The system handles this status. You cannot set the status manually. However, you can set a solution with the status Exported back to In Progress, Solved, Completed, or Dependencies Defined. If you change anything in an exported solution, the status is always set back to Dependencies Defined, and you must export the solution again. Before you can release a solution, the status must be Exported.</ListItem>
				<ListItemHead>Released</ListItemHead>
				<ListItem>The solution is released, which means that the solution is frozen. You can no longer change anything in the solution. To release a solution, you must change the status from Exported to Released, and you must save the solution with this status.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="solution_status_recipient"><Term>Solution status recipient</Term>
		<Definition>The following statuses indicate the progress of the installation or uninstallation of a solution or <Link href="/baanerp/tt/glossary/glossary#100256" role="glossary">Patch</Link>.</Definition>
		<SimpleSection><Paragraph class="Default">These statuses are only used at the recipient side, and must not be confused with the <Link href="/baanerp/tt/glossary/glossary#solution_status_distributor" role="glossary">Solution status distributor</Link> at the distributor side.</Paragraph>
			<List><ListItemHead>Available</ListItemHead>
				<ListItem>The solution or patch is scanned and available on the system.</ListItem>
				<ListItemHead>To Install</ListItemHead>
				<ListItem>The solution or patch is checked and is ready to be installed.</ListItem>
				<ListItemHead>Saving</ListItemHead>
				<ListItem><Paragraph class="Default">A backup of the components is being saved.</Paragraph>
					<Paragraph class="Default">This status is not applicable for patches.</Paragraph>
				</ListItem>
				<ListItemHead>Installing</ListItemHead>
				<ListItem>During the installing process the solution or patch has this status.</ListItem>
				<ListItemHead>Installed</ListItemHead>
				<ListItem>The solution or patch is installed.</ListItem>
				<ListItemHead>To Uninstall</ListItemHead>
				<ListItem>The solution or patch is checked to be uninstalled.</ListItem>
				<ListItemHead>Uninstalling</ListItemHead>
				<ListItem>During the uninstalling process, the solution or patch has this status.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAFVJTB"><Term>SP</Term>
		<Definition>See: <Link href="#service_pack" role="internal">Service Pack</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAZZJTB"><Term>SSO</Term>
		<Definition>See: <Link href="#SSO" role="internal">Single sign-on</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAYTJTB"><Term>SSPI</Term>
		<Definition>See: <Link href="#SSPI" role="internal">Security Support Provider Interface</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDA1AHTB"><Term>standard program</Term>
		<Definition>See: <Link href="#100092" role="internal">4GL engine</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000019" Version="7.2a" ContextApps="tt"><Term>Start-up menu</Term>
		<Definition>The first menu displayed after ERP LN is started.</Definition>
		<SimpleSection><List><ListIntro>The start-up menu code consists of the:</ListIntro>
				<ListItem>package code</ListItem>
				<ListItem>module code</ListItem>
				<ListItem>menu code</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="100039" Version="7.2a" ContextApps="tt"><Term>Status bar</Term>
		<Definition>A line of information related to the application in the window. Usually located at the bottom of a window.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDA3AHTB"><Term>STP</Term>
		<Definition>See: <Link href="#100092" role="internal">4GL engine</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000012" Version="7.2a" ContextApps="tt"><Term>String</Term>
		<Definition>A data structure that contains a number of characters that represent readable text.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100044" Version="7.2a" ContextApps="tt"><Term>Strip 8th bit</Term>
		<Definition>If you strip the 8th bit from a number, it means to remove the 8th digit in binary notation.</Definition>
		<ExampleSection><SectionTitle>
                                 Example
                              </SectionTitle>
			<Formula space-and-orientation="indented-estimated"><Paragraph class="Default"> 1111 1110 (binary) = FE (hexadecimal) = 254 (decimal) -&gt; 111 1110 (binary) = 7E (hexadecimal) = 126 (decimal) </Paragraph>
			</Formula>
			<Paragraph class="Default">When converting characters between different systems (for example, NLS to TSS), the 8th bit is stripped to obtain the intrinsic character value, which is sometimes needed to address the font.</Paragraph>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="100046" Version="7.2a" ContextApps="tt"><Term>Strip menu</Term>
		<Definition>To set a number of menu choices that do not meet certain conditions, to Inactive.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100027" Version="7.2a" ContextApps="tt"><Term>Substitution table</Term>
		<Definition>A table that consists of two columns: a column with source descriptions and a column with target descriptions. You use substitution tables to do global search and replace actions in ERP LN. The descriptions and helptexts for the software components in ERP LN are searched for the substitution table's source descriptions. The source descriptions that are found, are replaced by the target descriptions.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="superseded_solution"><Term>Superseded solution</Term>
		<Definition>A superseded solution is a solution for which can be said that all software components are also contained in another so-called <Link href="/baanerp/tt/glossary/glossary#superseding_solution" role="glossary">Superseding solution</Link>.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="superseding_solution"><Term>Superseding solution</Term>
		<Definition>A superseding solution is a solution that contains at least the same software components as contained in one or more <Link href="/baanerp/tt/glossary/glossary#superseded_solution" role="glossary">Superseded solutions</Link> and can contain additional software components that are not part of any superseded solution.</Definition>
		<SimpleSection><List><ListIntro>A solution supersedes another solution if the following conditions are met:</ListIntro>
				<ListItem>The superseding solution contains at least all the components of the other solution.</ListItem>
				<ListItem>The superseding solution contains newer versions of these components.</ListItem>
				<ListItem>The superseded solution is not yet installed. If the superseded solution is already installed, speaking of a superseding solution is illogical.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="100033" Version="7.2a" ContextApps="tt"><Term>System administrator</Term>
		<Definition>The person responsible for administering the use of a multi-user computer system, communications system, or both. A system administrator assigns user accounts and passwords, establishes security access levels, and allocates storage space.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="table.tt" Version="7.2a" ContextApps="tt"><Term>Table</Term>
		<Definition>A data structure that is used to store data that consists of a list of records, each entry being identified by a unique key and containing a set of related values. A table contains a number of table fields that belong to a specific domain.</Definition>
		<SimpleSection><Paragraph class="Default">A table code consists of a package code, module code, and three digits.</Paragraph>
		</SimpleSection>
		<ExampleSection><SectionTitle>
                                 Example
                              </SectionTitle>
			<Paragraph class="Default">Table: tc mcs010 <GUIRef href="" role="manual">Countries</GUIRef>
			</Paragraph>
			<TABLE width="90%" border="1" borderstyle="default" space-and-orientation="indented-estimated"><CAPTION>Table fields</CAPTION>
				<THEAD><TR><TH rowspan="1" colspan="1">Code</TH>
						<TH rowspan="1" colspan="1">Label</TH>
						<TH rowspan="1" colspan="1">Length</TH>
						<TH rowspan="1" colspan="1">Data Type</TH>
					</TR>
				</THEAD>
				<TBODY><TR><TD rowspan="1" colspan="1">ccty</TD>
						<TD rowspan="1" colspan="1">Country</TD>
						<TD rowspan="1" colspan="1">3</TD>
						<TD rowspan="1" colspan="1">String</TD>
					</TR>
					<TR><TD rowspan="1" colspan="1">dsca</TD>
						<TD rowspan="1" colspan="1">Description</TD>
						<TD rowspan="1" colspan="1">30</TD>
						<TD rowspan="1" colspan="1">Multibyte String</TD>
					</TR>
					<TR><TD rowspan="1" colspan="1">meec</TD>
						<TD rowspan="1" colspan="1">EU Member State</TD>
						<TD rowspan="1" colspan="1">5</TD>
						<TD rowspan="1" colspan="1">Enumerated</TD>
					</TR>
					<TR><TD rowspan="1" colspan="1">...</TD>
						<TD rowspan="1" colspan="1"></TD>
						<TD rowspan="1" colspan="1"></TD>
						<TD rowspan="1" colspan="1"></TD>
					</TR>
				</TBODY>
			</TABLE>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000045" Version="7.2a" ContextApps="tt"><Term>Table linking</Term>
		<Definition>A method of table sharing that stores a table physically in one company (the physical company) and lets other companies (the logical company) use that same table as if the table is their own.</Definition>
		<SimpleSection><Figure space-and-orientation="indented-estimated"><FigIntro>In the following diagram, company 200 shares some of the tables of company 100.</FigIntro>
				<HTML:IMG width="454" height="428" SRC="../images/tr_graph_glo_table_linking.gif" path="/enterpriseserver/tools/tt/glossary" btb-count="1" btb-count2="1" btb-image-name="tr_graph_glo_table_linking.gif" btb-source-path="C:\SVN\docnl\Technology\EnterpriseServer~8.5\EnterpriseServer" btb-image-path="/enterpriseserver/tools/tt/images/tr_graph_glo_table_linking.gif" ID="IDAZCYBC" alt="[...]" xmlns:HTML="http://www.w3.org/TR/REC-html40"/><FigCaption>Table linking</FigCaption>
			</Figure>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000046" ContextApps="tt"><Term>Table reference</Term>
		<Definition>A link to a table from which something must be selected or where additional information about something is stored.</Definition>
		<ExampleSection><SectionTitle>
                                 Example
                              </SectionTitle>
			<Paragraph class="Default">The <GUIRef href="" role="table">Items - General (tcibd001)</GUIRef> table has a <GUIRef href="" role="tablefield">Country of Origin (tcibd001.ctyo)</GUIRef> field . This field has a reference to the <GUIRef href="" role="table">Countries (tcmcs010)</GUIRef> table.</Paragraph>
			<List><ListIntro>If you enter a country code in this field, ERP LN does the following:</ListIntro>
				<ListItem>Checks whether that code is present in the <GUIRef href="" role="table">Countries (tcmcs010)</GUIRef> table.</ListItem>
				<ListItem>Retrieves the country's description from the <GUIRef href="" role="table">Countries (tcmcs010)</GUIRef> table.</ListItem>
				<ListItem>Displays the country's description on the form.</ListItem>
			</List>
		</ExampleSection>
		<SimpleSection><Paragraph class="Default">Hard references are defined in the table definition.</Paragraph>
			<Paragraph class="Default">Soft references are not defined in the table definition, but programmed in a program script or dll.</Paragraph>
		</SimpleSection>
		<Synonym>reference</Synonym>
	</GlossaryEntry>
	<GlossaryEntry ID="000042" Version="7.2a" ContextApps="tt"><Term>Table sharing</Term>
		<Definition>A method to use the same data by more than one company. If a user in one company creates, modifies, or deletes a record in a shared table, the effect will be visible in all companies that share the table.</Definition>
		<SimpleSection><List><ListIntro>Two techniques can be used to achieve table sharing:</ListIntro>
				<ListItem>Table linking.</ListItem>
				<ListItem>Data replication.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000018" Version="7.2a" ContextApps="tt"><Term>Template</Term>
		<Definition>In the authorization management system (AMS), a method to maintain common data for a group of users with the same role.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000024" Version="7.2a" ContextApps="tt"><Term>Text group</Term>
		<Definition>A means to define how text must be presented in a window by defining the text editor, default window, and dimensions of the window.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000022" Version="7.2a" ContextApps="tt"><Term>Textgroup authorization template</Term>
		<Definition>A set of sessions used to print, display, and maintain authorizations that a group of users share for a specific textgroup.</Definition>
		<SimpleSection><Paragraph class="Default">The text group authorizations template is dumped to the user file of all users who use the specific template.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="100235" Version="7.4a" ContextApps="tt"><Term>Transaction</Term>
		<Definition>A logical unit of work, resulting in one or more changes on a database that are carried out as an atomic entity.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100236" Version="7.4a" ContextApps="tt"><Term>Transaction notification</Term>
		<Definition>A message that states that the data in the source database was changed.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100037" Version="7.2a" ContextApps="tt"><Term>Triton Super Set</Term>
		<Definition>The collection of character sets used internally by ERP LN.</Definition>
		<SimpleSection><Paragraph class="Default">TSS character sets include ASCII (ISO 8859-1) characters and a range of multibyte character sets including sets of Japanese and Hebrew characters.</Paragraph>
			<Paragraph class="Default">Triton the name of a previous version of the ERP LN software.</Paragraph>
		</SimpleSection>
		<Acronym>TSS</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAEUKTB"><Term>TSS</Term>
		<Definition>See: <Link href="#100037" role="internal">Triton Super Set</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100253" Version="7.5a" ContextApps="tt"><Term>Tuple</Term>
		<Definition>In the business object repository, a tuple is an instance of a component. In the context of databases, a tuple is row in a table. The tuple contains logically related data. The term originated as an abstraction of the sequence: single, double, triple, quadruple, quintuple, ... n-tuple.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAUIJTB"><Term>UI script</Term>
		<Definition>See: <Link href="#progscript.tt" role="internal">Program script</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="undochecko.tt" Version="7.2a" ContextApps="tt"><Term>Undo check-out</Term>
		<Definition>A command of <Link href="#scm.tt" role="internal">Software Configuration Management</Link> that deletes the checked-out software component from the <Link href="#dvrc.tt" role="internal">Development VRC</Link>.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100246" Version="7.5a" ContextApps="tt"><Term>Universal Time Coordinated</Term>
		<Definition>A time/date format. ERP LN stores dates and times in UTC format. It stores both date and time in a single <Link href="#100244" role="internal">Long</Link> integer referred to as the UTC long format. This integer represents the number of seconds since 0:00 hour, January 1, 1970 (in UTC).</Definition>
		<Acronym>UTC</Acronym>
	</GlossaryEntry>
	<GlossaryEntry ID="update" Version="7.5a" ContextApps="tt"><Term>Update</Term>
		<Definition>In PMC, an update is a set of changed software components, including PMC metadata, which is required to install the update in a safe and correct way. An update can contain corrective changes or functional enhancements.</Definition>
		<SimpleSection><List><ListIntro>Updates can be delivered in four different configurations:</ListIntro>
				<ListItem>Solutions</ListItem>
				<ListItem>Collections</ListItem>
				<ListItem>Patches</ListItem>
				<ListItem>Service Packs</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="100255" Version="7.5a" ContextApps="tt"><Term>Update VRC</Term>
		<Definition>A physical VRC at the PMC recipient side in which updates are installed. Every update VRC has a <Link href="/baanerp/tt/glossary/glossary#100249" role="glossary">base VRC</Link> linked.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000020" Version="7.2a" ContextApps="tt"><Term>User data template</Term>
		<Definition>A template that contains system data and authorizations related to a group of users. The data contained by the template is dumped to the user file of all users who use the specific template.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDAVVKTB"><Term>UTC</Term>
		<Definition>See: <Link href="#100246" role="internal">Universal Time Coordinated</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000009" Version="7.2a" ContextApps="tt"><Term>Version</Term>
		<Definition>An upgrade of a package, for example, B61. Each change in the functionality of a package results in a new version. A version can contain several releases.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100016" Version="7.3adoc1" ContextApps="tt"><Term>Version - Release - Customer</Term>
		<Definition>The version - release - customer (VRC) code is an identification of a stage in the development of the ERP LN software. An example of a VRC is <Emphasis>B61_a_ams</Emphasis>.</Definition>
		<SimpleSection><List><ListIntro>A VRC code consists of:</ListIntro>
				<ListItemHead>Version</ListItemHead>
				<ListItem>A stage in the development in which a major part of the software is modified.</ListItem>
				<ListItemHead>Release</ListItemHead>
				<ListItem>A stage in the development in which a minor part of the software is modified.</ListItem>
				<ListItemHead>Customer</ListItemHead>
				<ListItem>An <Link href="/baanerp/tt/glossary/glossary#extension" role="glossary">Extension</Link>, <Link href="/baanerp/tt/glossary/glossary#100258" role="glossary">Localization</Link>, or <Link href="/baanerp/tt/glossary/glossary#customization" role="glossary">Customization</Link> of the software for a single customer or a small group of customers.</ListItem>
			</List>
		</SimpleSection>
		<SimpleSection><Paragraph class="Default">A VRC can be derived from a preceding VRC. Every software component that is contained in the preceding VRC and not explicitly modified or set to expired in the current VRC will also be available in the current VRC.</Paragraph>
		</SimpleSection>
		<Acronym>VRC</Acronym>
		<Acronym>PVRC</Acronym>
		<Synonym>package VRC</Synonym>
	</GlossaryEntry>
	<GlossaryEntry ID="IDALFKTB"><Term>virtual machine</Term>
		<Definition>See: <Link href="#100050" role="internal">
                              ERP LN shell</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="IDALZKTB"><Term>VRC</Term>
		<Definition>See: <Link href="#100016" role="internal">Version - Release - Customer</Link>
		</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="100259" Version="7.5a" ContextApps="tt"><Term>VRC combination</Term>
		<Definition>A VRC Combination is defined at the PMC recipient side and consists of a set of related <Link href="/baanerp/tt/glossary/glossary#100255" role="glossary">Update VRCs</Link>. The VRC Combination will guarantee that, if required, the related update VRCs are updated simultaneously at the PMC recipient side. In this way, you can avoid compatibility problems between related update VRCs. For example, if you use the standard application and you also have an extension installed, you will have two update VRCs defined. If a co-requisite dependency is defined between a standard solution and a solution for the extension, PMC installs both solutions in one run if you linked the update VRCs for both standard and extension in one VRC combination.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000001" Version="7.2a" ContextApps="tt"><Term>What's this?</Term>
		<Definition>The pop-up Help that tells you briefly the functions of a tool bar button, command button, or menu command.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000007" Version="7.2a" ContextApps="tt"><Term>Zoom session</Term>
		<Definition>The session in which you can browse through the available records and select a record. A zoom session is an overview session in read-only mode.</Definition>
		<SimpleSection><Paragraph class="Default">You can use a zoom session to enter the code of an existing record (for example, an item, order type, or warehouse) in another session. Click the browse arrow button behind the field or press CTRL+B to start a zoom session.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
</Glossary>
