<?xml version="1.0" encoding="utf-8"?>
<Glossary ID="/baanerp/tg/glossary/glossary" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Glossary for the TG package</Title>
	</Header>
	<GlossaryEntry ID="000187"><Term></Term>
		<Definition>A specification of the number of possible entities per entity type of a pairing.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000023"><Term>activity</Term>
		<Definition>Part of a business process that depending on the type of activity requires a certain action by the system or an ERP user:</Definition>
		<SimpleSection><List><ListItem>Manual activity A task that cannot be automated</ListItem>
				<ListItem>Business process A hierarchical expansion of the business process</ListItem>
				<ListItem>Application A program that can run on the client or server and is defined within a component release</ListItem>
				<ListItem>File-based (client) A file for which, based on the file extension, the associated application on the client is started</ListItem>
				<ListItem>Sending trigger An attached business process that is started without user interaction</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000038"><Term>activity instance</Term>
		<Definition>Represents an (executable) activity within a single enactment of a process instance.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000204"><Term>actual identification</Term>
		<Definition>The name that is given to a business process, workflow attribute, orexternal state during the modeling process.</Definition>
		<SimpleSection><Paragraph>See also: formal identification</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000033"><Term>AO document</Term>
		<Definition>A document that is part of the administrative organization in a company and which you can link to an activity.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000214"><Term>application</Term>
		<Definition>An application that is defined within a component definition.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000308" Version="B60adoc1"><Term>application</Term>
		<Definition>An application that is defined within a component definition.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000147"><Term>apply constraint</Term>
		<Definition>Determines the setting of parameters in the ERP database based on wizard-step answers.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000206"><Term>argument</Term>
		<Definition>Additional information that is delivered to a component, as a result ofwhich predefined actions are carried out.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000120"><Term>associative entity type</Term>
		<Definition>An entity type that is used to link two other entity types that have amany-to-many relationship between them.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000163"><Term>bill of enterprise</Term>
		<Definition>A set of data indicating the various child companies that make up aparent company and that are used to aggregate the value of the parentcompany's performance indicator. The child companies must have the samepackage combination as the parent company.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000135"><Term>buffer</Term>
		<Definition>A stock point that is located on the primary flow in a business control diagram.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000106"><Term>business control diagram</Term>
		<Definition>A graphic design that visualizes the primary process that takes placewithin an organization and shows the business functions that are used to controlthat process.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000068"><Term>business control model</Term>
		<Definition>A part of a reference model or project model that is built from a selection of business control diagrams that are initially created in the repository (library of model items).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000004"><Term>business function</Term>
		<Definition>A model item that defines relevant business issues.</Definition>
		<SimpleSection><Paragraph>A business function is used in business control diagrams to show how the primary process of an organization is controlled. In addition, a business function is the primary part of a business function model, which is a multilevel structure of the functions used in the business control model. A business function model provides a hierarchical breakdown of the business function.</Paragraph>
			<Paragraph>You can also use a business function to transform a function model to a process model.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000006"><Term>business model</Term>
		<Definition>A model that represents the organization. There are two types of business models: reference models and project models. Reference models apply to specific industries or business typologies. Project models apply to a specific organization.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000067"><Term>business process</Term>
		<Definition>A set of one or more activities and states that collectively realize a business objective.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000153"><Term>business-function diagram</Term>
		<Definition>A graphic design that visualizes the multilevel relationships betweenbusiness functions.</Definition>
		<SimpleSection><Paragraph>Note:The lowest level of business functions is used to set the value ofstatic conditions. The level above the lowest level is used to linkbusiness processes to business functions.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000094"><Term>business-function model</Term>
		<Definition>A part of a business model that is built from a selection of business functions that are initially created in the repository.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000302"><Term>business-process diagram</Term>
		<Definition>A graphic design that visualizes the business objective via a process structure in the Petri Net format.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000040"><Term>business-process model</Term>
		<Definition>A part of a reference model or project model built from a selection of business process diagrams that are initially created in the repository (library of business processes).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000159"><Term>calendar code</Term>
		<Definition>Identification of a calendar year that is subdivided into year parts andperiods. The start date and end date of the year can fall in anotheryear than the calendar year.</Definition>
		<SimpleSection><Paragraph>In the calendar, the different periods are defined by their start andend dates.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000210"><Term>category</Term>
		<Definition>A division within a system of classification. Most model items can becategorized.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000200"><Term>central company</Term>
		<Definition>The company in which all DEM model item data is stored. Central storagefacilitates the retrieval of enterprise modeler data.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000138"><Term>child business control diagram</Term>
		<Definition>A business control diagram that is linked to another business controldiagram. One or more child diagrams can be linked to a parent diagram. Achild diagram can also be linked to several parent diagrams.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000305"><Term>child employee group</Term>
		<Definition>An employee group that is linked to another employee group at one level below the latter.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000091"><Term>company</Term>
		<Definition>A working environment in which you can carry out logistic or financial transactions. All the data concerning the transactions is stored in the company's database. Each company has its own database tables and its own data. The company number identifies the data. Depending on the type of data that the company controls, the company is:</Definition>
		<SimpleSection><List><ListItem>A logistic company.</ListItem>
				<ListItem>A financial company.</ListItem>
				<ListItem>Both a logistic and a financial company. In a multisite structure, the company database can partially exist uniquely for the company, and partially consist of database tables that the company shares with other companies.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000213"><Term>component</Term>
		<Definition>A set of applications and their related data.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000216"><Term>component release</Term>
		<Definition>The identification of the issue of a component.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000142"><Term>consistency rule</Term>
		<Definition>An expression containing one or more business functions on the basis of which one or more business functions must be present in the business model.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000092"><Term>control activity</Term>
		<Definition>An activity in the business process that represents a decision moment.The designer of the business process defines with the help of static and dynamicconditions for the outgoing transitions the route through theprocess (which of the succeeding activities will be carried out and inwhich order). The different types of control activities are, forexample, XOR, OR, and AND.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000246"><Term>current modeling version</Term>
		<Definition>The version you currently use to create and modify model items.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000220"><Term>data model</Term>
		<Definition>Consists of one or more entity relationship diagrams that together represent the way the information is stored in a database.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000048"><Term>deadline date/time</Term>
		<Definition>The date and time when a process instance must be finished.</Definition>
		<SimpleSection><Paragraph>See also: target date mode</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000223"><Term>derived-from version</Term>
		<Definition>Defines from which version the model item is derived.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000224"><Term>diarizing</Term>
		<Definition>A Workflow user can diarize a work item, that is to put it inresubmission mode, so that it does not appear in the worklist. If thework item must be carried out, the user must resubmit it. Diarizing canbe done individually per work item, or collectively per process instanceor per folder.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000225"><Term>distribution algorithm</Term>
		<Definition>Distributes activity instances to Workflow users according to amechanism of free definition. The distribution algorithm is defined by a specialscript language and is saved in the Workflow Database.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000226"><Term>dummy</Term>
		<Definition>A place holder. Nothing happens in dummy activities but they are neededto avoid deadlocks in Petri nets.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000026"><Term>dynamic condition</Term>
		<Definition>A condition that can be linked to an outgoing transition of a control activity. The outcome of the condition (true or false) is determined at run time by SSA Workflow and is used to determine the path through a business process.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000227"><Term>Dynamic Enterprise Modeler</Term>
		<Definition>A tool that enables you to create a multilevel structure that represents an organization using ERP software.</Definition>
		<SimpleSection><List><ListIntro>The multilevel structure consistsof the following model items:</ListIntro>
				<ListItem>Enterprise-structure model</ListItem>
				<ListItem>Business models</ListItem>
				<ListItem>Data models</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000162"><Term>dynamic link library</Term>
		<Definition>A feature of operating systems that allows executable routines to bestored separately as files with DLL extensions and to be loaded onlywhen needed by a program.</Definition>
		<SimpleSection><Paragraph>Synonym: DLL</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000228"><Term>dynamic menu browser</Term>
		<Definition>A personal menu structure that shows the business processes andactivities for which an employee is authorized.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000103"><Term>employee</Term>
		<Definition>A human member of an organization model. Typically, employees are Workflow users who carry out activities with the Worklist Handler.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000229"><Term>employee group</Term>
		<Definition>An organizational unit of employees. For example, sales department orpurchase department.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000303"><Term>employee group types</Term>
		<Definition>A label that can be used to categorize employee groups.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000066"><Term>enterprise model</Term>
		<Definition>A complete design that visualizes a multisite organization. An enterprise model consists of an enterprise structure model and related business models.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000230"><Term>enterprise model browser</Term>
		<Definition>A browser that graphically presents (parts of) the enterprise model.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000307"><Term>enterprise modeler editor</Term>
		<Definition>The tool that enables you to create and modify the enterprise-structure diagram (enterprise-structure model), the business-control diagram (part of a business model), the business-function diagram (part of a business model), the business-process diagram (part of a business model), and the entity-relationship diagram (data model).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000169"><Term>enterprise period table</Term>
		<Definition>For each calendar the EIS period table contains the data that definesthe periods within a year and year part. The maximum number of yearparts within a year is 99. The maximum number of periods within a yearpart is 13.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000073"><Term>enterprise unit</Term>
		<Definition>A financially independent part of your organization that consists of entities such as departments, work centers, warehouses, and projects. The enterprise unit's entities must all belong to the same logistic company, but a logistic company can contain multiple enterprise units. An enterprise unit is linked to a single financial company.</Definition>
		<SimpleSection><Paragraph>When you carry out logistic transactions between enterprise units, these are posted in the financial companies to which each enterprise unit is linked. The enterprise-structure models define the relationships between the enterprise units, and the goods transfer that can take place between the enterprise units. To use invoicing and pricing between enterprise units, you must link the enterprise units to internal business partners.</Paragraph>
			<Paragraph>You can use enterprise units to perform separate financial accounting for parts of your business. For example, you can define enterprise units for separate parts of your organization that belong to one logistic company but which are located in different countries. The accounting of each enterprise unit is performed in each country's national currency and in the financial company linked to the enterprise unit.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000061"><Term>enterprise-modeler component</Term>
		<Definition>A building block within Dynamic Enterprise Modeling (DEM).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000020"><Term>enterprise-structure diagram</Term>
		<Definition>A graphic design that shows the geographic location of enterprise units and the relationships between these enterprise units in a multisite organization.</Definition>
		<SimpleSection><Paragraph>You can model various kinds of relationships between enterprise units; this includes goods flows, financial flows, and information flows.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000070"><Term>enterprise-structure model</Term>
		<Definition>An enterprise structure diagram that shows the geographic location of enterprise units and the relationships between these enterprise units in a multisite organization.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000084"><Term>enterprise-unit category type</Term>
		<Definition>Identifies the kind of flow between two enterprise units.</Definition>
		<SimpleSection><List><ListIntro>ERP distinguishes the following category types:</ListIntro>
				<ListItem>A document flow</ListItem>
				<ListItem>A goods flow</ListItem>
				<ListItem>A money flow</ListItem>
				<ListItem>An order flow</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000081"><Term>enterprise-unit relationship</Term>
		<Definition>A description of the relation between two enterprise units.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000074"><Term>entity</Term>
		<Definition>A separate and independent building block for a cluster and/or an enterprise unit. For example, warehouse, work center, employee, sales department, purchase department, project, customer, supplier, financial company.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000088"><Term>entity type</Term>
		<Definition>An object (person, place, thing, or concept) for which you must recordinformation.</Definition>
		<SimpleSection><List><ListIntro>ERP provides the following entity types:</ListIntro>
				<ListItem>Logical entity type: a meaning to the real world and is comprised ofone or more physical entity types.</ListItem>
				<ListItem>Physical entity type: database tables in the SSA application packages.</ListItem>
				<ListItem>Associative entity type: an entity type that is used to link otherentity types.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000119"><Term>entity-relationship diagram</Term>
		<Definition>A graphic design of the relational data model structure. The diagramshows a (multilevel) structure that consists of entity types and entitytype relationships.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000089"><Term>entity-type relationship</Term>
		<Definition>A reason of relevance for associating entities of one or two entitytypes.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000149"><Term>ERP</Term>
		<Definition>An accounting-oriented information system for identifying and planningthe enterprise-wide resources needed to take, make, ship, and accountfor customer orders.</Definition>
		<SimpleSection><Paragraph>An ERP system differs from the typical MRP II system in technicalrequirements, such as graphical user interface, relational database, useof fourth-generation language, and computer-aided software engineeringtools."</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000065"><Term>ERP user</Term>
		<Definition>A person who is authorized to log on to the SSA applications, and for whom data such as a startup menu, an operational language, and roles (authorizations) is defined.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000095"><Term>estimated duration</Term>
		<Definition>Average time needed to finish a business process or an activity.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000133"><Term>external agent</Term>
		<Definition>External parties (such as customers, suppliers, and governments) that affect the business functions in a business-control diagram.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000099"><Term>external code</Term>
		<Definition>A user-definable code that indicates the position of a model item relative to other model items.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000160"><Term>factor by period by seasonal pattern</Term>
		<Definition>The relative ratio for the norm values for the periods within acalendar.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000072"><Term>financial company</Term>
		<Definition>Part of an ERP database in which you can store all data concerning financial transactions.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000233"><Term>fixed date and time formula</Term>
		<Definition>A formula to calculate the target date and time that can be linked to a business process or activity to determine the time frame in which the business process or activity must be accomplished.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000234"><Term>folder</Term>
		<Definition>In DEM, a collection of process instances. These process instances can be derived from different process definitions. A folder can represent a logical group of process instances. For example, a folder for customer Jones.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000235"><Term>formal identification</Term>
		<Definition>A version-specific reference to the actual business process, states, and Workflow attributes to be used in program scripts and during activity modeling.</Definition>
		<SimpleSection><Paragraph>See also: actual identification</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000181"><Term>Ishikawa diagram</Term>
		<Definition>A graphical representation of the hierarchy of used performanceindicators. The Ishikawa diagram is represented as a fish bone chart.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000123"><Term>logical entity type</Term>
		<Definition>An entity type that has a meaning to the real world and that containsseveral physical entity types. For example, an item or a warehouse.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000172"><Term>login</Term>
		<Definition>The logon name (logon code) an employee uses to log on to the server(UNIX, Windows NT) on which the SSA applications run.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000009"><Term>logistic company</Term>
		<Definition>Part of an ERP database in which you can store data concerning logistic transactions.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000242"><Term>logon</Term>
		<Definition>The user ID and password that the Worklist Handler user must enter tolog on to the Workflow Server.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000243"><Term>Main (run-time) project model</Term>
		<Definition>A run-time project model that functions as default for the company to which the project model is linked. There can only be one main project model per company.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000080"><Term>map</Term>
		<Definition>A graphic design that is used to visualize geographical locations of the enterprise units in an enterprise structure diagram.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000244"><Term>model specific help</Term>
		<Definition>Help that is linked to a model item and provides information about the function of that model item in a business model.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000108"><Term>operational enterprise-structure model</Term>
		<Definition>An enterprise structure model of a specific version that reflects the transactions in the current organization (enterprise).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000079"><Term>optimization phase</Term>
		<Definition>A phase in the business-improvement cycle in which new business functions and business processes are implemented in an organization.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000178"><Term>optimization relationship</Term>
		<Definition>A relationship, graphically represented by a curved arrow, connectingtwo business functions.</Definition>
		<SimpleSection><List><ListIntro>The functionallity can either represent:</ListIntro>
				<ListItem>A variant (replaces the business function).</ListItem>
				<ListItem>An option (additional business function).</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000127"><Term>optional relationship</Term>
		<Definition>A relationship between two entity types that is not mandatory. Toidentify the optionality of the relationship, the N side of therelationship is equal to zero.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000104"><Term>organization diagram</Term>
		<Definition>A formal representation of an organization, which distinguishes employee groups, employees, and roles.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000077"><Term>owner</Term>
		<Definition>A ERP user who has created a model item or version, or the ERP user who is responsible for the model or version.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000036"><Term>parameter</Term>
		<Definition>A variable that directs the software to meet the specific requirements of an organization.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000030"><Term>parameter setting rule</Term>
		<Definition>An expression containing business functions and/or business processes whose presence or absence determine the value of one or more parameters in a business model.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000090"><Term>performance indicator</Term>
		<Definition>A value that indicates the achievements of company units. The valuevaries by time unit (such as week and day) and is calculated by means ofa script. If the value is a figure, it is displayed as a chart. If thevalue relates to a collection of data, it is stored in an ASCII file.</Definition>
		<SimpleSection><Paragraph>You can link performance indicators to business functions to monitor and improvethe performance of these business functions.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000165"><Term>performance-indicator data by period</Term>
		<Definition>The results of the calculation process, stored for the particularperiods of the year. It concerns calculated results, norm, minimum, andmaximum values (both periodic and cumulative), but also the owner of theperformance indicator and, if applicable, the reports of output files.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000121"><Term>physical entity type</Term>
		<Definition>Database table definitions of the ERP application, for example thegeneral item (tcibd001) data table.</Definition>
		<SimpleSection><Paragraph>The entity type code is usually equal to the table code.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000140"><Term>position number</Term>
		<Definition>An internal number that indicates the place of the activity, state, orcontrol activity in the business process diagram.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000134"><Term>primary activity</Term>
		<Definition>The representation of an organization's basic activity, situated on the primary flow. Examples are: receipt of raw materials, production of sub-assemblies, final assembly, and delivery of the final products.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000136"><Term>primary flow</Term>
		<Definition>The primary process that is controlled in the business control diagram.Per diagram, only one flow can be inserted. This flow can represent agoods flow, an information flow, or a financial flow. On the primaryflow, primary activities, buffers, and one customer order decouplingpoint can be inserted.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000059"><Term>priority</Term>
		<Definition>An indication of how urgently work items must be processed. The activity instance priority can be the decisive factor for sorting work items in the Worklist Handler.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000037"><Term>process instance</Term>
		<Definition>A single representation of a process definition, which consists of a sequence of activity instances and state instances (connected by transitions). Their relation is defined in the process definition.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000198"><Term>Process Viewer</Term>
		<Definition>A client application that graphically displays a business process. If you have the appropriate authorizations, you can use the Process Viewer to start activities.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000078"><Term>project model</Term>
		<Definition>A model that represents a specific organization.</Definition>
		<SimpleSection><List><ListIntro>. A project model is built from a library (repository) of the following model items:</ListIntro>
				<ListItem>business-control model</ListItem>
				<ListItem>business-function model</ListItem>
				<ListItem>business-process model</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000087"><Term>query</Term>
		<Definition>The act or process of extracting data from a database to present it for use.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000086"><Term>reference model</Term>
		<Definition>A model that represents a line of business or business typology.</Definition>
		<SimpleSection><List><ListIntro>A reference model is built from a library (repository) of the following model items:</ListIntro>
				<ListItem>business-control model</ListItem>
				<ListItem>business-function model</ListItem>
				<ListItem>business-process model</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000093"><Term>repository</Term>
		<Definition>A library of model items.</Definition>
		<SimpleSection><List><ListIntro>ERP distinguishes the following repositories:</ListIntro>
				<ListItem>Business functions</ListItem>
				<ListItem>Business processes</ListItem>
				<ListItem>Business-control diagrams</ListItem>
			</List>
			<Paragraph>In coherence with each other the repository model items can form a business model.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000267"><Term>repository help</Term>
		<Definition>Help that provides general information about a model item. Repository help can also be viewed from a business model.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000268"><Term>reroute</Term>
		<Definition>An authorized Workflow user can reroute work items to another Workflow user, a group, or a role. The Rerouting can be done individually per work item or collectively per process instance or per folder.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000035"><Term>responsibility code</Term>
		<Definition>A task that can be linked to a role, and which is used for authorization purposes. If a responsibility code is linked to a role, at least on of the responsibility codes must have the value Yes to authorize the role.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000124"><Term>reverse engineering</Term>
		<Definition>The opposite of the (normal) engineering process. Instead of creatingnew data for a software product, you extract information from anexisting database.</Definition>
		<SimpleSection><Paragraph>The data structure information is generated and can be used to design anew interface or to describe the current software.</Paragraph>
			<Paragraph>You can either select entity types that were not used before in theentity relationship diagram, or generate a new set of entity types forwhich entity relationships or entity relationship diagrams alreadyexist.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000034"><Term>role</Term>
		<Definition>In DEM a role is a set of specific qualifications and/or skills that an employee must have to be authorized to carry out a business process, activity, or subapplication.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000029"><Term>rule</Term>
		<Definition>An expression.</Definition>
		<SimpleSection><List><ListIntro>A rule is used to:</ListIntro>
				<ListItem>Check the consistency of a business function model (consistency rules).</ListItem>
				<ListItem>Transform a business function model to a business process model (transformation rules).</ListItem>
				<ListItem>Assign a value to the application parameters (parameter setting rules).</ListItem>
				<ListItem>Assign a value to static conditions (static condition setting rules).</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000117"><Term>rule condition</Term>
		<Definition>An expression that contains business processes and/or business functions and determines which of the following model items are included, or assigned a value in a business model.</Definition>
		<SimpleSection><List><ListIntro>The assigned value can be:</ListIntro>
				<ListItem>Business function</ListItem>
				<ListItem>Business process</ListItem>
				<ListItem>Parameter</ListItem>
				<ListItem>Static condition</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000300"><Term>running ERP component</Term>
		<Definition>The ERP component that is currently active.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000310" Version="B60adoc1"><Term>running ERP component</Term>
		<Definition>The ERP component that is currently active.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000301"><Term>running ERP component release</Term>
		<Definition>The ERP component release that is currently active.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000271"><Term>run-time optimization phase</Term>
		<Definition>The optimization phase that is used at run time. Combined with the run-time version and run-time project model, the run-time optimization phase determines which processes are displayed and how to displayed these processes in the dynamic menu browser.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000272"><Term>run-time project model</Term>
		<Definition>A project model (within a company) that is used at run-time. Combined with the run-time version and run-time optimization phase, the run-time project model determines the processes that are displayed in the dynamic menu browser.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000273"><Term>run-time version</Term>
		<Definition>The version that contains the run-time project model. Combined with the run-time project model and run-time optimization phase, the run-time version determines the processes that are displayed in the dynamic menu browser.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000161"><Term>seasonal pattern code</Term>
		<Definition>The code to identify a seasonal pattern. A seasonal pattern describesthe relative ratios for norm values for one or more periods in a year.These values can be linked to performance indicators.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000122"><Term>sequence number</Term>
		<Definition>A number that determines the sequence in which records are displayed inan overview session or list box.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000025"><Term>state</Term>
		<Definition>Part of a business process that is used internally to control the path through the business process.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000028"><Term>static condition</Term>
		<Definition>A condition that can be linked to an outgoing transition of a control activity. During the implementation of ERP, the static condition values are evaluated by static condition-setting rules and can result in activating/deactivating parts of business processes.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000032"><Term>static condition setting rule</Term>
		<Definition>An expression containing business functions and/or business processes whose presence or absence determine the values of static conditions in a business model.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000062"><Term>status</Term>
		<Definition>The stage in the development of a model item.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000309" Version="B60adoc1"><Term>subapplication</Term>
		<Definition>An application defined as accessible from a defined component application. If the component application is an ERP session, the subapplications are equivalent to ERP subsessions.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000175"><Term>sub-role</Term>
		<Definition>A regular role that is linked to another role at one level below the latter.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000128"><Term>subtype relationship</Term>
		<Definition>An entity relationship between two entity types (a subtype and asupertype) that is used to indicate that the supertype's attribute alsoapply to (are inherited by) the subtype.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000304"><Term>supervisor</Term>
		<Definition>The employee that manages one or more employee groups, as a result of which he gets distributed all business processes that belong to the employee group(s) he/she supervises.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000280"><Term>support application</Term>
		<Definition>One or more applications that can be linked to a business process or an activity to help the employee carry out the process/activity. Note that a support application can contain both applications and other support applications.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000125"><Term>table definition</Term>
		<Definition>The definition of a table and its fields/columns and so on, in the ERP datadictionary.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000282"><Term>target date</Term>
		<Definition>A date on which the process instance should have reached a specific state. If the state is not reached, the Workflow Management System initializes a predefined action. A deadline is a special target date.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000221"><Term>target date mode</Term>
		<Definition>Determines how the deadline date must be interpreted by the Workflow Management System.</Definition>
		<CrossRef>See also: <Link href="/baanerp/tg/glossary/glossary#000048" role="glossary">deadline date/time</Link>
		</CrossRef>
	</GlossaryEntry>
	<GlossaryEntry ID="000064"><Term>tools role</Term>
		<Definition></Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000031"><Term>transformation rule</Term>
		<Definition>An expression imposing a unilateral dependency of business processes in relation to business functions. By carrying out the rules, business processes are imported into the business model based on the business functions that are already present.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000131"><Term>transition</Term>
		<Definition>A directed link or connection between an activity and a state in a Petri-net. You can link a static and/or dynamic condition to a transition.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000306"><Term>trigger</Term>
		<Definition>An arrow in a business-control diagram that can be drawn between business functions, external agents, primary activities, and buffers. An incoming trigger (request loop) represents the cause/origin of a business function; the returning trigger (feedback loop) reports the confirmation/result of the action to the invoking function/agent. Note: an incoming and outgoing trigger must be present between each type of model item.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000170"><Term>unit</Term>
		<Definition>The physical quantity in which goods are managed. For example, wood canbe expressed by length in meters, or by volume in cubic meters.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000290"><Term>URL</Term>
		<Definition>Uniform Resource Locator (URL). An address for a resource on the Internet. URLs are used by Web browsers to locate Internet resources.</Definition>
		<SimpleSection><List><ListIntro>A URL specifies:</ListIntro>
				<ListItem>The protocol to be used in accessing the resource (such as http: for a World Wide Web page, or ftp: for an FTP site).</ListItem>
				<ListItem>The name of the server on which the resource resides (such as www.whitehouse.gov).</ListItem>
				<ListItem>The path to a resource (such as an HTML document or a file on that server).</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000291"><Term>user authorization</Term>
		<Definition>The level of authorization that is given to a user to work with a component activity.</Definition>
		<SimpleSection><List><ListIntro>The following levels of authorization exist:</ListIntro>
				<ListItem>Display</ListItem>
				<ListItem>Print/Display</ListItem>
				<ListItem>Modify/Print/Display</ListItem>
				<ListItem>Insert/Modify/Print/Display</ListItem>
				<ListItem>Full Authorization</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000001"><Term>version</Term>
		<Definition>A group of model items that share some characteristics, such as the customer, owner, and effective date.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000293"><Term>version tree</Term>
		<Definition>Shows the derived-from structure of versions.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000071"><Term>wizard</Term>
		<Definition>A special form of user assistance that automates a task by setting the parameter values within a business model and which directs the software to meet the specific requirements of an organization.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000146"><Term>wizard constraint</Term>
		<Definition>Determines what you must do when a wizard step is carried out. You must only apply a wizard constraint if the actions involve more than simply setting a parameter; for example, starting a nested wizard.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000154"><Term>wizard dll function</Term>
		<Definition>A DLL contains one or more functions to accomplish a certain task. Amongother things, these functions can be used in constraints to check theanswer given by the user against certain conditions, to check on thepresence of a business function in the business function model, to readparameters, or to read wizard step answers.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000167"><Term>wizard end text</Term>
		<Definition>A text that explains the result of the wizard after the ERP user has completed all wizard steps.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000150"><Term>wizard Help text</Term>
		<Definition>Text that contains background information or a detailed description of the wizard-step question.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000148"><Term>wizard hint text</Term>
		<Definition>Text that contains information for wizard-step answers based on common practice.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000158"><Term>wizard question text</Term>
		<Definition>The question that a user is asked in a wizard. The question is displayedin the wizard step dialog box.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000166"><Term>wizard start text</Term>
		<Definition>A text that explains the function of the wizard.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000144"><Term>wizard step</Term>
		<Definition>The section of a wizard that accomplishes the dialog with the ERP user.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000145"><Term>wizard-step answer</Term>
		<Definition>The answer to a wizard step which the user can select from a range ofpossible answers. Usually, ERP automatically creates answers based onthe domain linked to the parameter that can be set in the wizard.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000096"><Term>work item</Term>
		<Definition>A user related activity instance that is entered in the user'sWorklist. The Workflow Management System schedules an activity instanceto all authorized Workflow users, so that one activity instance can havemore than one work item.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000010"><Term>workflow attributes</Term>
		<Definition>A variable for use in SSA Workflow that transfers a value along activities in a business process.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000188"><Term>workflow Database</Term>
		<Definition>The data required for the Workflow Management System is stored in thisdatabase (except of data host and configuration files). All programs of Workflowcan access it. The Workflow Administration System serves thedatabase administration.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000189"><Term>workflow enabled</Term>
		<Definition>A parameter of an ERP session that indicates the session can be started through SSA Workflow.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000047"><Term>workflow engine</Term>
		<Definition>A software part of the Workflow Server. The Workflow Engine uses the Workflow API to provide data and services to the Workflow Processing Clients. The Workflow Engine consists of several workers, the Job Manager and the Operator Manager.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000045"><Term>Workflow Management System</Term>
		<Definition>A system that uses software to define, create, and manage the execution of business processes. The WMS runs on one or more Workflow Servers. The WMS can interpret process definitions, interact with Workflow users, and, if required, use IT tools and applications.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000190"><Term>workflow processing</Term>
		<Definition>Comprises all actions to realize current business processes. The processinstances are subdivided into single steps and are given to theappropriate Workflow users. Responsibilities and access rights arechecked. Workflow processing provides the right people with the righttools and the right data at the right time.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000191"><Term>Workflow Processing Client</Term>
		<Definition>A software component for the Workflow user to carry out work items (forexample the Worklist Handler). The client is connected to the server bymeans of a network.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000192"><Term>Workflow Server</Term>
		<Definition>The Workflow Engine and the Workflow Database running on the (physical)server. In case of several logical servers, this is called amultiserver.</Definition>
		<SimpleSection><Paragraph>Synonym: logical server</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000193"><Term>Workflow System Administration</Term>
		<Definition>This administration tool is a graphical user interface to the Workflow Database.Each database table has a corresponding form for searching anddata entry, and the option for report generation.</Definition>
		<SimpleSection><Paragraph>Synonym: WSA</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000194"><Term>workflow system attributes</Term>
		<Definition>Variables and constants containing workflow system data.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000195"><Term>workflow system data</Term>
		<Definition>Workflow data managed by the Workflow Management System and/or theWorkflow Engine. Such data is internal to the WMS and is usually notaccessible for applications.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000039"><Term>workflow user</Term>
		<Definition>A user of the Worklist Handler. Workflow users can be employees and system-internal users.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000063"><Term>workflow-process status</Term>
		<Definition>The development stage of a business process.</Definition>
		<SimpleSection><List><ListIntro>The stage determines whether:</ListIntro>
				<ListItem>You can modify the business process</ListItem>
				<ListItem>SSA Workflow can use it</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000014"><Term>worklist</Term>
		<Definition>A complete list of work items for a specific Workflow user in the Worklist Handler.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000196"><Term>Worklist Handler</Term>
		<Definition>A software component that manages the interaction between the Workflowuser and the Workflow Engine to carry out work items.</Definition>
	</GlossaryEntry>
</Glossary>
