<?xml version="1.0" encoding="utf-8"?>
<Glossary ID="/baanerp/dm/glossary/glossary" xml:lang="en">
   <Header>
      <Title>Glossary for ODM</Title>
   </Header>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000038">
      <Term>action</Term>
      <Definition>A command which enables the user to perform specific operations
		on an <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef> object and
		is assigned a particular role. For example, a Create Change Request action
		(CR_NEW) is associated with the Change Request object. Several actions can be
		associated with every object. Similarly, actions can be common to several
		objects.</Definition>
      <Keyword type="glentry" order="d1e270679">
         <Level1>action</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="app_data_locks">
      <Term>Application Data Locks</Term>
      <Definition>Functionality to clear the application data is locked by the
		system due to a life cycle problem or network problems.</Definition>
      <Keyword type="glentry" order="d1e271182">
         <Level1>Application Data Locks</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000040">
      <Term>Approved</Term>
      <Definition>The status to indicate that the respective object is approved
		for implementation.</Definition>
      <Keyword type="glentry" order="d1e270692">
         <Level1>Approved</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000025">
      <Term>Area</Term>
      <Definition>The directory recognized by the Document Management module to
		store the registered files.</Definition>
      <Keyword type="glentry" order="d1e270607">
         <Level1>Area</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000026">
      <Term>Area Assignment</Term>
      <Definition>An area located on a host to define the designated storage of
		files, such as work area.</Definition>
      <Keyword type="glentry" order="d1e270612">
         <Level1>Area Assignment</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="area_types">
      <Term>Area Types</Term>
      <Definition>The classification of areas, such as the work area and the
		vault area to register/work with and vault the files,
		respectively.</Definition>
      <Keyword type="glentry" order="d1e271108">
         <Level1>Area Types</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000041">
      <Term>Attached File</Term>
      <Definition>A (physical) file attached to a document revision.</Definition>
      <Keyword type="glentry" order="d1e270697">
         <Level1>Attached File</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000042">
      <Term>Attached Hard Copy</Term>
      <Definition>The hard copy (information) attached to a document revision.</Definition>
      <Keyword type="glentry" order="d1e270702">
         <Level1>Attached Hard Copy</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="att">
      <Term>Attribute</Term>
      <Definition>The attribute is the field in a session for which you must
		generate a mask.</Definition>
      <Keyword type="glentry" order="d1e271203">
         <Level1>Attribute</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="browse_option">
      <Term>Browse Option</Term>
      <Definition>The <GUIRef href="" role="manual">Browse</GUIRef> option displays the object explorer
		for the selected object. This option displays the members, owner families and
		member families for the selected object.</Definition>
      <Keyword type="glentry" order="d1e271174">
         <Level1>Browse Option</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000003">
      <Term>Change</Term>
      <Definition>A unique identifier for any specific changes. A change header
		is a change which consists of similar change requests that can be grouped and
		submitted to a single change header. This identifier is a database entity that
		represents the change.</Definition>
      <Keyword type="glentry" order="d1e270503">
         <Level1>Change</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000104">
      <Term>Change Affected Objects</Term>
      <Definition>The list of objects defined in <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef> are used in Change
		Management. Some of the change affected objects that can be used in the
		lifecycle process of a change in <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef> are Item, BOM,
		routing operations, and so on.</Definition>
      <Keyword type="glentry" order="d1e271039">
         <Level1>Change Affected Objects</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000062">
      <Term>Change Classification</Term>
      <Definition>A list of codes with descriptions defined by the system
		administrator to classify the optional changes.</Definition>
      <Keyword type="glentry" order="d1e270845">
         <Level1>Change Classification</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="change_comm">
      <Term>Change Committee</Term>
      <Definition>The committee of a chairperson and reviewers who implement a
		change using change management. Only authorized users can create a change
		committee.</Definition>
      <Keyword type="glentry" order="d1e271128">
         <Level1>Change Committee</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000107">
      <Term>Change Management</Term>
      <Definition>A module in LN <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef> that
		controls the processes of product changes in the life cycle. Change Management
		ensures that the product changes are implemented in a visible, controlled, and
		orderly fashion. The Change Management module provides the flexibility of
		creating a change process to optimize an organization’s Enterprise Resource
		Planning (ERP) system.</Definition>
      <Keyword type="glentry" order="d1e271060">
         <Level1>Change Management</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000006">
      <Term>Change Order</Term>
      <Definition>A generic mechanism to change a change controlled LN linked entity. A
		change order date is specified to set the linked entity to effective or expired
		on that specified date.</Definition>
      <Keyword type="glentry" order="d1e270518">
         <Level1>Change Order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000044">
      <Term>Change Order Date</Term>
      <Definition>The date on which the change is implemented for the linked LN entity. The change
		order date is specified in the change order to make the linked LN entity effective or
		expire on the specified date.</Definition>
      <Keyword type="glentry" order="d1e270728">
         <Level1>Change Order Date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000012">
      <Term>Change Priority</Term>
      <Definition>A list of codes and descriptions that are defined according to
		organizational requirements to rate the priority level of the change.</Definition>
      <Keyword type="glentry" order="d1e270552">
         <Level1>Change Priority</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000007">
      <Term>Change Process</Term>
      <Definition>The process to create, review, approve or reject and complete
		the change.</Definition>
      <Keyword type="glentry" order="d1e270523">
         <Level1>Change Process</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000005">
      <Term>Change Proposal</Term>
      <Definition>The description of the proposal for a change. All affected LN entities, reviewer
		lists, business partner links, tasks and task groups, change orders are
		included in this proposal. A default new change proposal is created
		automatically when a change is created.</Definition>
      <Keyword type="glentry" order="d1e270513">
         <Level1>Change Proposal</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000103">
      <Term>Change Proposal Status</Term>
      <Definition>The change proposal can have the following status:</Definition>
      <SimpleSection>
         <List>
            <ListItem>
               <GUIRef href="" role="manual">Created</GUIRef>: The initial status for a new
			 proposal.</ListItem>
            <ListItem>
               <GUIRef href="" role="manual">Under Review</GUIRef>: The proposal is submitted for
			 review.</ListItem>
            <ListItem>
               <GUIRef href="" role="manual">Approved or Rejected</GUIRef>: The proposal is
			 approved/ rejected</ListItem>
            <ListItem>
               <GUIRef href="" role="manual">Tasks are Done</GUIRef>: All the tasks that are
			 linked to a proposal are run. The tasks can have the following statuses:
			 Freeze, Unfreeze, Cancel, and Completed</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e271016">
         <Level1>Change Proposal Status</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000004">
      <Term>Change Request</Term>
      <Definition>Change request initiates the change process. Change requests
		are recorded from a variety of request sources, such as demands in the
		marketplace, product reviews, and customer response for making product
		innovations and upgrades. Information stored in each change request form
		enables you to track various changes as requested by various sources.</Definition>
      <Keyword type="glentry" order="d1e270508">
         <Level1>Change Request</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000046">
      <Term>Change Request Status</Term>
      <Definition>A change request can have the following status:</Definition>
      <SimpleSection>
         <List>
            <ListItem>Created</ListItem>
            <ListItem>Linked to Change</ListItem>
            <ListItem>Rejected</ListItem>
         </List>
         <Paragraph>Change requests with the <GUIRef href="" role="manual">Linked to Change</GUIRef> status cannot be rejected and a rejected change request cannot be
		  modified.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e270738">
         <Level1>Change Request Status</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000043">
      <Term>Change Status</Term>
      <Definition>The status of the change through the life cycle. Change can
		have the following statuses:</Definition>
      <SimpleSection>
         <List>
            <ListItem>Created</ListItem>
            <ListItem>Cancelled</ListItem>
            <ListItem>Freeze/Unfreeze</ListItem>
            <ListItem>Under Review</ListItem>
            <ListItem>Approved</ListItem>
            <ListItem>Rejected</ListItem>
            <ListItem>Completed:</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e270707">
         <Level1>Change Status</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000110">
      <Term>Check In</Term>
      <Definition>A status of the files present in the vault area. Files in <GUIRef href="" role="manual">Check In</GUIRef> status cannot be edited but can only be viewed.</Definition>
      <Keyword type="glentry" order="d1e271082">
         <Level1>Check In</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="check_out">
      <Term>Check Out</Term>
      <Definition>A status of the files present in the work area. Files in <GUIRef href="" role="manual">Check Out</GUIRef> status can be edited.</Definition>
      <Keyword type="glentry" order="d1e271090">
         <Level1>Check Out</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000045">
      <Term>Child Change Order</Term>
      <Definition>A change order that is linked to a parent change order and
		inherits the parent change order date automatically.</Definition>
      <Keyword type="glentry" order="d1e270733">
         <Level1>Child Change Order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="comm_odm_par">
      <Term>Common ODM Parameter</Term>
      <Definition>Common <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef> Parameters are used to set the default values for
		the parameters in <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e271213">
         <Level1>Common ODM Parameter</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000047">
      <Term>Completed</Term>
      <Definition>The status indicates that the change has been implemented.</Definition>
      <Keyword type="glentry" order="d1e270757">
         <Level1>Completed</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000048">
      <Term>Created</Term>
      <Definition>The initial status of the change request or change itself.</Definition>
      <Keyword type="glentry" order="d1e270762">
         <Level1>Created</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="default_work_areas">
      <Term>Default Work Areas</Term>
      <Definition>The work area assigned to a user by default, to register files.
		When no work area is defined for a user, work area is generated automatically
		by the system and the default work area is assigned. Only one work area can be
		assigned as the default work area for a user. The system administrator can
		assign default work areas for all users. Individual users can assign their own
		default work area.</Definition>
      <Keyword type="glentry" order="d1e271118">
         <Level1>Default Work Areas</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000019">
      <Term>Document</Term>
      <Definition>Displays identification, document type, title, creator, role
		responsibility, and revision information. You can store the document
		information in electronic computer files (physical files) or on a
		non-electronic medium, such as paper (hard copies). Access to this information
		is always from the document, which is the unit of control for the user. If no
		file or hard copy is attached to a a document, the document is a purely logical
		entity, generally used for grouping documents.</Definition>
      <Keyword type="glentry" order="d1e270570">
         <Level1>Document</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="document_lib">
      <Term>Document Libraries</Term>
      <Definition>The logical libraries created for documents to organize data in
		a hierarchical structure. Document libraries are used to catalog documents. The
		objects contained in document libraries can be: sub-libraries, documents, and
		vault areas.</Definition>
      <Keyword type="glentry" order="d1e271123">
         <Level1>Document Libraries</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="doc_lifc">
      <Term>Document Lifecycle</Term>
      <Definition>The lifecycle of a document from concept stage to completion
		stage. The document lifecycle involves various phases, such as In Design,
		Submitted, Approved, Released, Withdrawn, Expired, and Rejected.</Definition>
      <Keyword type="glentry" order="d1e271154">
         <Level1>Document Lifecycle</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000108">
      <Term>Document Management</Term>
      <Definition>A module in <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef>, that provides general document management
		facilities such as controlled access to the documents, secure storage of the
		document contents, document life cycle support, and management of the
		relationships between documents and other objects in the LN system. Document
		Management ensures the efficient and secure use of consistent and reliable
		document information.</Definition>
      <Keyword type="glentry" order="d1e271069">
         <Level1>Document Management</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="docmancomm">
      <Term>Document Management Committee</Term>
      <Definition>The committee of a chairperson and reviewers who approve or
		reject a document using document management. Only authorized users can create a
		document management committee.</Definition>
      <Keyword type="glentry" order="d1e271134">
         <Level1>Document Management Committee</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="doc_masks">
      <Term>Document Masks</Term>
      <Definition>A generic system to generate a unique identification number for
		a document. In the Document Management module, masks can be defined for the
		document ID, the document revision value, the hard copy ID, and the file ID.
		The document ID mask and document revision mask depend on the document type.</Definition>
      <Keyword type="glentry" order="d1e271144">
         <Level1>Document Masks</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000020">
      <Term>Document Revision</Term>
      <Definition>Document revisions track changes to their attached files and
		hard copies. When a document is created, the document revision is created by
		default. Most of the work with documents is actually performed by means of the
		document revisions. Document revisions are assigned a status that indicates the
		revisions' position in the lifecycle. The operations that you can perform on a
		document revision depend on the revision's status.</Definition>
      <Keyword type="glentry" order="d1e270575">
         <Level1>Document Revision</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000022">
      <Term>Document Revision Link - Parent/Child</Term>
      <Definition>A parent/child link between two document revisions. The child
		document is logically an element of the parent document.</Definition>
      <Keyword type="glentry" order="d1e270585">
         <Level1>Document Revision Link - Parent/Child</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000021">
      <Term>Document Revision Links - Reference</Term>
      <Definition>Unidirectional or two way link between two document revisions.
		If the link is unidirectional, the document revision is linked in one
		direction, in other words, document revision 2 is linked to document revision
		1, and if the document revision 1 is also linked to document revision 2, the
		link is called a two way link.</Definition>
      <Keyword type="glentry" order="d1e270580">
         <Level1>Document Revision Links - Reference</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000049">
      <Term>Document Revision Status</Term>
      <Definition>The document revision has the following status through the
		document lifecycle:</Definition>
      <SimpleSection>
         <List>
            <ListItem>Created</ListItem>
            <ListItem>Submitted</ListItem>
            <ListItem>Approved</ListItem>
            <ListItem>Released</ListItem>
            <ListItem>Rejected</ListItem>
            <ListItem>Expired and</ListItem>
            <ListItem>Withdrawn.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e270767">
         <Level1>Document Revision Status</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000023">
      <Term>Document Type</Term>
      <Definition>Assigned to every document. Each document type is assigned a
		revision mode that is applicable to all documents of that document type. The
		document mask and document revision mask can be dependent upon the document
		type. The document types determine whether the hard copies and files attached
		to document revisions must be assigned revisions. Examples of the type of
		documents a company keeps can be, safety regulations, assembly documents,
		wiring diagram, maintenance instructions, drawing documents and standard
		documents.</Definition>
      <Keyword type="glentry" order="d1e270590">
         <Level1>Document Type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="doc_type_att">
      <Term>Document Type Attachments</Term>
      <Definition>Attachment of a document or file to a document type in the form
		of templates.</Definition>
      <Keyword type="glentry" order="d1e271149">
         <Level1>Document Type Attachments</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000051">
      <Term>Done</Term>
      <Definition>The status to indicate the completion of task execution.</Definition>
      <Keyword type="glentry" order="d1e270793">
         <Level1>Done</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="dynamic_host">
      <Term>Dynamic Host</Term>
      <Definition>Enables users to obtain the local host name dynamically when
		users from the local host connect to the LN server.</Definition>
      <Keyword type="glentry" order="d1e271113">
         <Level1>Dynamic Host</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000052">
      <Term>Exclusive Revision</Term>
      <Definition>An option that limits the revise process of document revision
		and exclusively to a single individual. Multiple document revisions of the
		document cannot be revised at the same time when this option is in use for the
		respective document.</Definition>
      <Keyword type="glentry" order="d1e270798">
         <Level1>Exclusive Revision</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="exp_and_imp">
      <Term>Export and Import</Term>
      <Definition>
         <GUIRef href="" role="manual">Export</GUIRef>: A process in data management module
		that selects data from System Table List of <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef> and transfers the <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef> system data to a
		storage directory. <GUIRef href="" role="manual">Import</GUIRef>: A process in data management module
		that imports the data from the dump files in a specified directory, to the
		system tables of <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e271232">
         <Level1>Export and Import</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000055">
      <Term>Families Owned by Type</Term>
      <Definition>All the object families that have a particular object as the
		owner.</Definition>
      <Keyword type="glentry" order="d1e270819">
         <Level1>Families Owned by Type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000054">
      <Term>Family Member</Term>
      <Definition>An object related to an object family. The object family can
		have objects as members.</Definition>
      <Keyword type="glentry" order="d1e270814">
         <Level1>Family Member</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000056">
      <Term>Family Object is Member In</Term>
      <Definition>The object is a member in the specified object family.</Definition>
      <Keyword type="glentry" order="d1e270824">
         <Level1>Family Object is Member In</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000032">
      <Term>File</Term>
      <Definition>The object that points to a physical file. All the files are
		assigned versions by LN,
		automatically. When a file is first attached to a document revision, it is
		assigned the first version. This version is retained until the file is checked
		out of the vault area. To edit a file in the vault area, the user must checkout
		the file into a work area. The checked out file is registered in the database
		as a new version of the file.</Definition>
      <Keyword type="glentry" order="d1e270642">
         <Level1>File</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000031">
      <Term>File Type</Term>
      <Definition>Upon registration, a file is assigned a file type. Each file
		type is associated with one or more file extensions. If a file type is
		specified for a particular document type, files of the specified file type only
		can be attached to a document of that document type. The system administrator
		can constrain the set of file types that can be attached to a document revision
		of a particular document type. For example, word processing files have
		three-letter extension that indicates the file's type, such as .txt or .doc.
		Similarly, graphic files have various extensions, such as .jpg, .bmp, and so
		on.</Definition>
      <Keyword type="glentry" order="d1e270637">
         <Level1>File Type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000013">
      <Term>Folder</Term>
      <Definition>A data item container that stores the group of related objects.
		Every folder has a life cycle mechanism. Folders provide a flexible solution
		for defining the relationships, links and dependencies between different
		aspects of product data in the form of objects. Folder can be personal or
		shared.</Definition>
      <Keyword type="glentry" order="d1e270557">
         <Level1>Folder</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000109">
      <Term>Folder Management</Term>
      <Definition>A module that maintains folder and simplifies the management of
		product information. The Folder Management module provides a generic flexible
		solution to address the problem of links and dependencies. Linking a folder to
		an LN object creates a
		simple and efficient method to extend the object’s data domain, and to
		facilitate the fast retrieval of any type of information related to the
		object.</Definition>
      <Keyword type="glentry" order="d1e271077">
         <Level1>Folder Management</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000059">
      <Term>Freeze</Term>
      <Definition>The status in the change lifecycle that indicates that the
		change entity has been rendered inactive or delayed for some reason.</Definition>
      <Keyword type="glentry" order="d1e270829">
         <Level1>Freeze</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000027">
      <Term>Hard Copy</Term>
      <Definition>An object that represents the physical nature, for example,
		hard copies of documents. The contents of hard copy documents are printed on
		paper. storage media, such as casette and film, are considered hard copies.</Definition>
      <Keyword type="glentry" order="d1e270617">
         <Level1>Hard Copy</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000035">
      <Term>Host</Term>
      <Definition>A host is the network node that is recognized in the network.
		All network nodes that can be accessed by the document file server or the vault
		server component can be defined as hosts.</Definition>
      <Keyword type="glentry" order="d1e270660">
         <Level1>Host</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000061">
      <Term>In-Design</Term>
      <Definition>The status assigned to a new document revision.</Definition>
      <Keyword type="glentry" order="d1e270840">
         <Level1>In-Design</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000060">
      <Term>In-Work</Term>
      <Definition>The status of a task while in progress. This status is assigned
		when an executed task is revised by using the redo action.</Definition>
      <Keyword type="glentry" order="d1e270835">
         <Level1>In-Work</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000001">
      <Term>Library</Term>
      <Definition>A logical place to save data in a hierarchy. Libraries enable
		you to define a collection of related objects and classification of documents.
		These objects can themselves be libraries. A library can have vault areas
		linked to it.</Definition>
      <Keyword type="glentry" order="d1e270493">
         <Level1>Library</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000024">
      <Term>Linked LN Entity</Term>
      <Definition>A predefined entity linked to LN objects in <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef>. Objects are
		predefined in <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef> and
		are allowed to link to document revision/change proposal/folders depending on
		their status.</Definition>
      <Keyword type="glentry" order="d1e270595">
         <Level1>Linked LN Entity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000028">
      <Term>Location</Term>
      <Definition>The place where hard copies, for example, documents, are
		stored.</Definition>
      <Keyword type="glentry" order="d1e270622">
         <Level1>Location</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="main_files">
      <Term>Main Files</Term>
      <Definition>If multiple files are attached to a document revision, the
		system checks for the main file and runs the file operations (View/Print/Edit)
		accordingly.</Definition>
      <Keyword type="glentry" order="d1e271098">
         <Level1>Main Files</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="mask_code">
      <Term>Mask Code</Term>
      <Definition>The code defined for the attribute of the object. You can
		maintain unique mask codes for the attribute of an object.</Definition>
      <Keyword type="glentry" order="d1e271198">
         <Level1>Mask Code</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="mask_conf">
      <Term>Mask Configuration</Term>
      <Definition>The detailed configuration of masks to generate IDs in the
		format used by the organization. To configure masks, you must configure the
		mask code associated with the attribute.</Definition>
      <Keyword type="glentry" order="d1e271193">
         <Level1>Mask Configuration</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000029">
      <Term>Medium</Term>
      <Definition>The physical substance of the hard copy to store, for example,
		data, such as paper, mylar, disk, CD-ROM, aperture cards, and so on.</Definition>
      <Keyword type="glentry" order="d1e270627">
         <Level1>Medium</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000034">
      <Term>Mounted Area</Term>
      <Definition>A procedure that defines the way, a remote work area can be
		accessed from the local host.</Definition>
      <Keyword type="glentry" order="d1e270655">
         <Level1>Mounted Area</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000101">
      <Term>Multi Main Table (MMT)</Term>
      <Definition>The concept of writing and editing multiple tables in a single
		session. MMT is intended to improve the ease of use of the LN applications by
		displaying the related sessions of the header as satellites in the MMT session
		itself.</Definition>
      <Keyword type="glentry" order="d1e271006">
         <Level1>Multi Main Table (MMT)</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000063">
      <Term>Object</Term>
      <Definition>A nonphysical entity that is defined in <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef> to manage the life
		cycle of the product in a simple way. For example, an LN main table is
		considered an object. Objects are classified as <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef> objects and LN objects. <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef> objects are
		related to <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef>, for
		example, libraries, documents, changes, folders, queries, and so on. The
		non- LN objects are
		item, BOM, sales order, purchase order, and so on.</Definition>
      <Keyword type="glentry" order="d1e270850">
         <Level1>Object</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000102">
      <Term>Object Browsing</Term>
      <Definition>The object explorer that enables the user to view the object's
		links in the form of a horizontal tree-like structure.</Definition>
      <Keyword type="glentry" order="d1e271011">
         <Level1>Object Browsing</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000065">
      <Term>Object Family</Term>
      <Definition>A family with one or more objects as family members, which are
		linked to the family owner.</Definition>
      <Keyword type="glentry" order="d1e270872">
         <Level1>Object Family</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000064">
      <Term>Object History</Term>
      <Definition>The history of revisions made to an object.</Definition>
      <Keyword type="glentry" order="d1e270867">
         <Level1>Object History</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000002">
      <Term>Object Linked to a folder</Term>
      <Definition>Any LN entity that can be linked to a folder. For example, an engineering folder,
		sales proposal, or employee file.</Definition>
      <Keyword type="glentry" order="d1e270498">
         <Level1>Object Linked to a folder</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="object_mask">
      <Term>Object Mask</Term>
      <Definition>A mechanism that generates a unique identification number to
		the attribute of the object represented by an unique mask code. The actual
		number generated depends upon the mask configuration defined by the user for
		the mask code. If no mask configuration is defined for an object mask, the
		default value of the object mask is taken into consideration to generate the
		number. Active object mask is used to generate the number for the attribute of
		an object.</Definition>
      <Keyword type="glentry" order="d1e271187">
         <Level1>Object Mask</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="object_stat">
      <Term>Object Statistics</Term>
      <Definition>A feature that displays statistical details, such as the number
		of hard copies and files linked to a document revision and the total size of
		the files linked to the revision.</Definition>
      <Keyword type="glentry" order="d1e271103">
         <Level1>Object Statistics</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000089">
      <Term>Object Status by Object</Term>
      <Definition>The secondary status of an object that is dependent on status
		of another system defined object in a life cycle of document or change.</Definition>
      <Keyword type="glentry" order="d1e270929">
         <Level1>Object Status by Object</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000100">
      <Term>ODM</Term>
      <Definition>An independent package in LN that provides
		effective data management solutions in a product development scenario with
		truly embedded data management functionality. <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef> ensures that the
		product data is handled properly and that the most stringent product lifecycle
		management processes are applied. <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef> provides fully
		integrated document management, change management and folder management
		facilities for LN users. <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef> is accessed
		directly from LN, which
		enables users to attach documents to LN objects, and view corresponding files attached to
		documents.</Definition>
      <Keyword type="glentry" order="d1e270992">
         <Level1>ODM</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000068">
      <Term>Owner</Term>
      <Definition>The family owner is the source object of a link that belongs
		to the family.</Definition>
      <Keyword type="glentry" order="d1e270877">
         <Level1>Owner</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000039">
      <Term>Query</Term>
      <Definition>A generic mechanism to filter a set of records based on the
		provided conditions.</Definition>
      <Keyword type="glentry" order="d1e270687">
         <Level1>Query</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000050">
      <Term>Query Condition</Term>
      <Definition>The condition provided by a user, based on the respective
		object attribute values, to set up a query. A query can be based on one or more
		conditions. For example, you can set up conditions to retrieve all documents of
		a particular type.</Definition>
      <Keyword type="glentry" order="d1e270788">
         <Level1>Query Condition</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000011">
      <Term>Reason Code</Term>
      <Definition>A list of codes and descriptions that provide a reason for the
		change. The codes and descriptions are defined by the system administrator.</Definition>
      <Keyword type="glentry" order="d1e270547">
         <Level1>Reason Code</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000053">
      <Term>Redesign</Term>
      <Definition>An action that enables the user to redesign the rejected
		document revision. The document revision status changes from <GUIRef href="" role="manual">Rejected</GUIRef> to <GUIRef href="" role="manual">In Design</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e270803">
         <Level1>Redesign</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000018">
      <Term>Reference Document</Term>
      <Definition>A document that describes the details of the change request
		that is stored in <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef> for reference purpose.</Definition>
      <Keyword type="glentry" order="d1e270562">
         <Level1>Reference Document</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000074">
      <Term>Rejected</Term>
      <Definition>A status that indicates that the object has been rejected and
		requires no further review.</Definition>
      <Keyword type="glentry" order="d1e270882">
         <Level1>Rejected</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000075">
      <Term>Relations</Term>
      <Definition>Group of actions for a specific object.</Definition>
      <Keyword type="glentry" order="d1e270887">
         <Level1>Relations</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000106">
      <Term>Relative Change Orders (RCO)</Term>
      <Definition>The Relative Change Order (RCO) governs the date effectivity
		for the linked LN entity which will trigger depending on the duration with respect to the base
		change order date.</Definition>
      <Keyword type="glentry" order="d1e271055">
         <Level1>Relative Change Orders (RCO)</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000076">
      <Term>Released</Term>
      <Definition>A status that indicates that a document has got a formal
		approval and is ready for distribution.</Definition>
      <Keyword type="glentry" order="d1e270892">
         <Level1>Released</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="rep_par">
      <Term>Report Parameters</Term>
      <Definition>The parameters used to specify the criteria for data selection
		and to be displayed for an existing report.</Definition>
      <Keyword type="glentry" order="d1e271169">
         <Level1>Report Parameters</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="reports">
      <Term>Reports</Term>
      <Definition>A basic format to represent information in a structured way.</Definition>
      <Keyword type="glentry" order="d1e271159">
         <Level1>Reports</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000010">
      <Term>Reviewer</Term>
      <Definition>The person responsible for the review of the change proposal or
		document revision.</Definition>
      <Keyword type="glentry" order="d1e270542">
         <Level1>Reviewer</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000079">
      <Term>Reviewer</Term>
      <Definition>The individual assigned to a change or document management
		committee to review the change proposal or document revision accordingly and
		give appropriate recommendations.</Definition>
      <Keyword type="glentry" order="d1e270897">
         <Level1>Reviewer</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000105">
      <Term>Reviewers Mechanism</Term>
      <Definition>The mechanism adopted by the reviewers of the change or
		document management committee. The mechanism enables controlled execution of
		the process by the reviewers of the committee.</Definition>
      <Keyword type="glentry" order="d1e271050">
         <Level1>Reviewers Mechanism</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000037">
      <Term>Revise</Term>
      <Definition>Revise enables the user to create a new revision from the
		existing approved (Change/Folder) or released (Document Revision) state, for
		example, new revision in case of document revision and new proposal in case of
		change proposal.</Definition>
      <Keyword type="glentry" order="d1e270674">
         <Level1>Revise</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="rev_modes">
      <Term>Revision Modes</Term>
      <Definition>Each document type is assigned a revision mode, which is
		applied to all documents of that document type. The revision mode specified can
		be alphanumeric revision, such as rev 01 or A1. The revision mode can also be
		set automatically to the release date of the revision, for example, 1998-05-12.</Definition>
      <Keyword type="glentry" order="d1e271139">
         <Level1>Revision Modes</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000000">
      <Term>Role</Term>
      <Definition>Role specifies the employee's position and the authorizations
		the employee must perform specific actions and processes or to access specific
		data.</Definition>
      <Keyword type="glentry" order="d1e270488">
         <Level1>Role</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000081">
      <Term>Role Assignment</Term>
      <Definition>Assignment of proper actions to a particular role according to
		the need, to perform the respective actions in <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef>, for example,
		designer, engineer, programmer, and administrator.</Definition>
      <Keyword type="glentry" order="d1e270903">
         <Level1>Role Assignment</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="role">
      <Term>Roles by Employees</Term>
      <Definition>Roles that are defined in <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef> are assigned to
		the employee as part of the authorizations that are stipulated in an
		organization.</Definition>
      <Keyword type="glentry" order="d1e271224">
         <Level1>Roles by Employees</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="rule">
      <Term>Rule</Term>
      <Definition>A principle or condition that can be used as a one-point
		provision to trigger dependent events/entities.</Definition>
      <Keyword type="glentry" order="d1e271208">
         <Level1>Rule</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000082">
      <Term>Secondary Status</Term>
      <Definition>Statuses that an administrator assigns to <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef> objects based on
		the system defined status. Also referred to as user-defined status.</Definition>
      <Keyword type="glentry" order="d1e270911">
         <Level1>Secondary Status</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000030">
      <Term>Size</Term>
      <Definition>The dimension of the hard copy, such as A2 and A4 paper size.</Definition>
      <Keyword type="glentry" order="d1e270632">
         <Level1>Size</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000087">
      <Term>Source Object</Term>
      <Definition>The main object to which a secondary object is linked, for
		example, the family owner.</Definition>
      <Keyword type="glentry" order="d1e270924">
         <Level1>Source Object</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="std_rep_lay">
      <Term>Standard Report Layout</Term>
      <Definition>A readable arrangement of reports in a standard way. The report
		layout includes the following fields: Company Number, Company Name, Date/Time,
		User, Page Number and Report Header description.</Definition>
      <Keyword type="glentry" order="d1e271164">
         <Level1>Standard Report Layout</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000086">
      <Term>Submitted for Review</Term>
      <Definition>A status that indicates that a document or a change is
		submitted for approval or rejection.</Definition>
      <Keyword type="glentry" order="d1e270919">
         <Level1>Submitted for Review</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000090">
      <Term>System Actions</Term>
      <Definition>The fundamental actions applicable to all the operations in <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef>. All the actions
		that are related to <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef> objects are systems actions, by default, which
		cannot be deleted or modified. Users cannot create system actions.</Definition>
      <Keyword type="glentry" order="d1e270934">
         <Level1>System Actions</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000091">
      <Term>System Table</Term>
      <Definition>Table that lists all objects related to <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef> configuration by
		sequence number, package, and module for exporting information.</Definition>
      <Keyword type="glentry" order="d1e270945">
         <Level1>System Table</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000092">
      <Term>Target Object</Term>
      <Definition>The object that is linked to the source object.</Definition>
      <Keyword type="glentry" order="d1e270953">
         <Level1>Target Object</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000008">
      <Term>Task</Term>
      <Definition>The actual change to be implemented at a prescribed date. You
		can link tasks directly to a change proposal if the proposal is in <GUIRef href="" role="manual">Created</GUIRef> status.</Definition>
      <Keyword type="glentry" order="d1e270528">
         <Level1>Task</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000009">
      <Term>Task Group</Term>
      <Definition>Although task groups are optional, Infor recommends
		strongly that you use task groups. The task group business function maintains
		the task group and the group's tasks. The objective of the tasks, the task's
		results, and how and when the task is implemented can be maintained in the task
		group. Task groups are optional. However, for an organization that has hundreds
		of tasks, task groups are essential in the successful implementation of a group
		of related tasks.</Definition>
      <Keyword type="glentry" order="d1e270536">
         <Level1>Task Group</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000093">
      <Term>Task Status</Term>
      <Definition>Denotes various positions in the execution of a task life
		cycle. The statuses are Created, In-Work, Done, and Skipped.</Definition>
      <Keyword type="glentry" order="d1e270958">
         <Level1>Task Status</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000094">
      <Term>Under Review</Term>
      <Definition>The status indicates that the created change is submitted for
		review.</Definition>
      <Keyword type="glentry" order="d1e270963">
         <Level1>Under Review</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B52adoc1" ContextApps="dm" ID="000095">
      <Term>Unfreeze</Term>
      <Definition>The change status, which indicates that an inactive change
		entity (frozen change) is activated and is currently in the change
		implementation process.</Definition>
      <Keyword type="glentry" order="d1e270968">
         <Level1>Unfreeze</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000096">
      <Term>User Authorization</Term>
      <Definition>The authorization level assigned to a user to determine the
		various actions that can be performed in <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef>, for example,
		creation, deletion, edit, and viewing of a document</Definition>
      <Keyword type="glentry" order="d1e270974">
         <Level1>User Authorization</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000098">
      <Term>Vault Area</Term>
      <Definition>One of the classified areas where checked-in files are stored
		when a document is submitted for review or released in case of quick approval
		document. Users have read-only access to this area.</Definition>
      <Keyword type="glentry" order="d1e270982">
         <Level1>Vault Area</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000036">
      <Term>Vault Server</Term>
      <Definition>A software program that is installed on the client or server
		systems, depending on the requirement. Running the vault server program enables
		the transfer of the files between the areas that are designated in <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef> during certain
		operations and also enables you to register and access the files in the case of
		mounted area.</Definition>
      <Keyword type="glentry" order="d1e270666">
         <Level1>Vault Server</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000099">
      <Term>Withdrawn</Term>
      <Definition>The document revision status, which indicates that the document
		revision has been withdrawn after release. The revision is no longer in use
		after a document is withdrawn.</Definition>
      <Keyword type="glentry" order="d1e270987">
         <Level1>Withdrawn</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry Version="B60asy04" ContextApps="dm" ID="000033">
      <Term>Work Area</Term>
      <Definition>An uncontrolled area where all the files are created and stored
		before a user views and and edits them. This area contains one version of each
		file. Users can edit files which are assigned as work areas. One or more work
		areas may be assigned to the same user, and more than one user can be assigned
		to the same work area. Each user who works with files is assigned a default
		work area. When the user checks the files out of the vault, the files are
		copied to this work area. The default work area is also used in other
		circumstances, such as when the files are registered in <GUIRef href="/baanerp/dm/short" role="package">ODM</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e270647">
         <Level1>Work Area</Level1>
      </Keyword>
   </GlossaryEntry>
</Glossary>