A command which enables the user to perform specific operations on an Data Management 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.

The status to indicate that the respective object is approved for implementation.

The directory recognized by the Document Management module to store the registered files.

A (physical) file attached to a document revision.

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.

The list of objects defined in Data Management are used in Change Management. Some of the change affected objects that can be used in the lifecycle process of a change in Data Management are Item, BOM, routing operations, and so on.

A module in LN Data Management 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.

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.

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.

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.

The change proposal can have the following status:

• Created: The initial status for a new proposal.
• Under Review: The proposal is submitted for review.
• Approved or Rejected: The proposal is approved/ rejected
• Tasks are Done: All the tasks that are linked to a proposal are run. The tasks can have the following statuses: Freeze, Unfreeze, Cancel, and Completed

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.

A change request can have the following status:

• Created
• Linked to Change
• Rejected

Change requests with the Linked to Change status cannot be rejected and a rejected change request cannot be modified.

A change order that is linked to a parent change order and inherits the parent change order date automatically.

The initial status of the change request or change itself.

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 document, the document is a purely logical entity, generally used for grouping documents.

A module in Data Management, 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.

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.

The document revision has the following status through the document lifecycle:

• Created
• Submitted
• Approved
• Released
• Rejected
• Expired and
• Withdrawn.

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.

An object related to an object family. The object family can have objects as members.

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.

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.

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.

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.

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.

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.

The status assigned to a new document revision.

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.

The physical substance of the hard copy to store, for example, data, such as paper, mylar, disk, CD-ROM, aperture cards, and so on.

A procedure that defines the way, a remote work area can be accessed from the local host.

A nonphysical entity that is defined in Data Management 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 Data Management objects and LN objects. Data Management objects are related to Data Management, for example, libraries, documents, changes, folders, queries, and so on. The non- LN objects are item, BOM, sales order, purchase order, and so on.

The object explorer that enables the user to view the object's links in the form of a horizontal tree-like structure.

A family with one or more objects as family members, which are linked to the family owner.

An independent package in LN that provides effective data management solutions in a product development scenario with truly embedded data management functionality. Data Management ensures that the product data is handled properly and that the most stringent product lifecycle management processes are applied. Data Management provides fully integrated document management, change management and folder management facilities for LN users. Data Management is accessed directly from LN, which enables users to attach documents to LN objects, and view corresponding files attached to documents.

The family owner is the source object of a link that belongs to the family.

A department in your organization that is responsible for buying the materials and services required by your organization. You assign number groups to the purchase office.

A generic mechanism to filter a set of records based on the provided conditions.

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.

A list of codes and descriptions that provide a reason for the change. The codes and descriptions are defined by the system administrator.

A document that describes the details of the change request that is stored in Data Management for reference purpose.

A status that indicates that the object has been rejected and requires no further review.

A status that indicates that a document has got a formal approval and is ready for distribution.

The person responsible for the review of the change proposal or document revision.

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.

Role specifies the employee's position and the authorizations the employee must perform specific actions and processes or to access specific data.

Statuses that an administrator assigns to Data Management objects based on the system defined status. Also referred to as user-defined status.

The main object to which a secondary object is linked, for example, the family owner.

The object that is linked to the source object.

The actual change to be implemented at a prescribed date. You can link tasks directly to a change proposal if the proposal is in Created status.

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.

Denotes various positions in the execution of a task life cycle. The statuses are Created, In-Work, Done, and Skipped.

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.

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 Data Management during certain operations and also enables you to register and access the files in the case of mounted area.

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.

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 Data Management.