<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/dm/chm/dmchm0101m000" xml:lang="en">
   <Header>
      <Title>Change Request (dmchm0101m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to list change request. The
		  session also enables you to create and process the change requests. To create a
		  new <Link href="/baanerp/dm/glossary/glossary#000004" role="glossary">change request</Link>, click <GUIRef href="" role="manual">New</GUIRef> on the <GUIRef href="" role="manual">File</GUIRef> menu.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>In this session, you
		  can categorize the change request raisers as either internal or external. You
		  can also maintain the reason to raise the <Link href="/baanerp/dm/glossary/glossary#000004" role="glossary">change request</Link> and the description of the problem that
		  might arise, due to non-compliance of the change, along with a suggested
		  solution.</Paragraph>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>A change request is
			 created and linked to a <Link href="/baanerp/dm/glossary/glossary#000003" role="glossary">change</Link>. A change request which is linked to a change can
			 no longer be rejected.</Paragraph>
         </Note>
         <Paragraph>Depending on the
		  user's authorization, the change request can be created, linked to change, or
		  rejected. At a given instance, a user may or may not have authorizations to
		  perform all the functions.</Paragraph>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/dm/onlinemanual/000012" role="manual">Change Request</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/dm/onlinemanual/000013" role="manual">Change</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="dmchm001.crid">
         <Header>
            <Title>Change Request</Title>
         </Header>
         <FuncDesc>The change request ID is a unique code assigned to the change
		  request. If a mask is defined and is active for the change request, the mask
		  generates this code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm001.desc">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description for the change request.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>The user can only enter up to 30 characters.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="dmchm001.prio">
         <Header>
            <Title>Priority</Title>
         </Header>
         <FuncDesc>Indicates a priority level. Use the browse arrow to select the
		  priority code from the Change Priority (dmchm0103m000) session. You must select
		  the priority.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm001.role">
         <Header>
            <Title>Reviewer</Title>
         </Header>
         <FuncDesc>The individual with highest authorization role to review the
		  change request. Use the browse arrow to select the role title, such as
		  Designer, Engineer, Administrator, and so on, from the <GUIRef href="/baanerp/tc/ppl/tcppl0160m000" role="session">Roles (tcppl0160m000)</GUIRef> session. The roles are defined in LN <GUIRef href="" role="manual">People</GUIRef> and the defined roles are used in the <Link href="/baanerp/dm/glossary/glossary#000107" role="glossary">Change Management</Link> module.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/dm/onlinemanual/dmchm" role="manual">Change Management (CHM)</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="dmchm001.stcr">
         <Header>
            <Title>Request Raiser</Title>
         </Header>
         <FuncDesc>Select the request raiser to indicate the source of the change.
		  A request can be raised by an internal or an external source. The internal
		  source can be other departments in the company, and the external option refers
		  to a customer or business partner.</FuncDesc>
         <SimpleSection>
            <Paragraph>Sources of change
			 can be either internal or external.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="dmchm001.sscr">
         <Header>
            <Title>Source</Title>
         </Header>
         <FuncDesc>Additional details on the request raiser. For an internal
		  request raiser, you must enter the department and the contact number from which
		  the request originates. For an external request raiser, you must enter the full
		  address.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>The user cannot enter more than 255 characters.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="dmchm001.rscd">
         <Header>
            <Title>Request Reason</Title>
         </Header>
         <FuncDesc>The reason code for the change request. Use the browse arrow to
		  select a reason code from the <Link href="/baanerp/dm/com/dmcom0150m000" role="session">Reasons (dmcom0150m000)</Link> session. The request reason codes
		  defined are used to define all the change requests.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm001.prob">
         <Header>
            <Title>Problem Description</Title>
         </Header>
         <FuncDesc>The detail description of the problem. This parameter is a
		  multiline text field in which you can describe a change request in detail.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm001.desg">
         <Header>
            <Title>Suggested Solution</Title>
         </Header>
         <FuncDesc>The suggested solution for the change request. This parameter
		  is a multiline text field in which you can provide sufficient space to describe
		  a solution for the change request.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm001.rfdc">
         <Header>
            <Title>Reference Document</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/dm/glossary/glossary#000018" role="glossary">reference document</Link> code upon which the suggested solution
		  is based. Use the browse arrow to select a document from the <Link href="/baanerp/dm/doc/dmdoc1510m000" role="session">Documents (dmdoc1510m000)</Link> session, where the reference
		  document codes are defined. The document can be any of the document types
		  supported by the <Link href="/baanerp/dm/glossary/glossary#000107" role="glossary">Change Management</Link> module, such as a drawing.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm001.crst">
         <Header>
            <Title>Change Request Status</Title>
         </Header>
         <FuncDesc>The status of the change request. The allowed values are:</FuncDesc>
         <SimpleSection>
            <List>
               <ListItem>Created</ListItem>
               <ListItem>Linked to Change</ListItem>
               <ListItem>Rejected</ListItem>
            </List>
         </SimpleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>You cannot modify a rejected change request.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="dmchm001.cpid">
         <Header>
            <Title>Change</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/dm/glossary/glossary#000003" role="glossary">change</Link> ID, which appears if the change is linked to a
		  change request. You can link more than one change request to a change header.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ch_status">
         <Header>
            <Title>Change Header Status</Title>
         </Header>
         <FuncDesc>The status of the change request header.</FuncDesc>
         <SimpleSection>
            <Paragraph>The change request header can have the following
			 statuses:</Paragraph>
            <List>
               <ListItem>Create</ListItem>
               <ListItem>Freeze</ListItem>
               <ListItem>Unfreeze</ListItem>
               <ListItem>Approval Ready</ListItem>
               <ListItem>Cancel</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="dmsys020.dsca">
         <Header>
            <Title>Secondary Status</Title>
         </Header>
         <FuncDesc>The user-defined status.</FuncDesc>
         <SimpleSection>
            <Paragraph>You can define the
			 secondary status in the <Link href="/baanerp/dm/sys/dmsys0520m000" role="session">Object Statuses by Object (dmsys0520m000)</Link> session. Use the browse arrow to
			 select the status from the session. Status enables you to identify a record
			 with a particular entity.</Paragraph>
            <Paragraph>For example, a
			 change request with the status Created can have the secondary status <GUIRef href="" role="manual">Created by Employee</GUIRef>, <GUIRef href="" role="manual">Created by Customer</GUIRef>, and
			 so on. This is an optional step in the change process.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="dmchm001.crby">
         <Header>
            <Title>Created By</Title>
         </Header>
         <FuncDesc>The login ID of the user who creates the <Link href="/baanerp/dm/glossary/glossary#000004" role="glossary">change request</Link>. The user must have the authorization to
		  create a new change request.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm001.dtcr">
         <Header>
            <Title>Creation Date</Title>
         </Header>
         <FuncDesc>The date and time at which the user creates the change request.
		  The UTC date and time format is used.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm001.rcom">
         <Header>
            <Title>Comments</Title>
         </Header>
         <FuncDesc>Enter the reviewer comments for the change request. The user
		  can enter up to 255 characters.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm001.stdt">
         <Header>
            <Title>Modification Date</Title>
         </Header>
         <FuncDesc>The date and time when the change request is modified. This
		  parameter is a display field and cannot be modified by the user. LN updates this field
		  each time the record is modified.</FuncDesc>
         <SimpleSection>
            <Paragraph>This field is
			 enabled only if the action is set to Modify.</Paragraph>
         </SimpleSection>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="exec.user.0">
         <Header>
            <Title>Link to Change</Title>
         </Header>
         <FuncDesc>Links a change request to a change.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="exec.user.1">
         <Header>
            <Title>Reject</Title>
         </Header>
         <FuncDesc>Rejects a change request with a specific reason code.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="exec.user.3">
         <Header>
            <Title>Show Changes</Title>
         </Header>
         <FuncDesc>Starts the <GUIRef href="/baanerp/dm/chm/dmchm0111m000" role="session">Change Header (dmchm0111m000)</GUIRef> session. This option is available only if a change is
		  linked to the request.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="exec.user.7">
         <Header>
            <Title>Browse</Title>
         </Header>
         <FuncDesc>Starts the browser to view the properties of the change and
		  proposals.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="exec.user.10">
         <Header>
            <Title>Query Filter</Title>
         </Header>
         <FuncDesc>Sets the filtering mechanism, wherein the queries are used as a
		  filter.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="exec.user.11">
         <Header>
            <Title>Undo Query Filter</Title>
         </Header>
         <FuncDesc>Disables the filtering mechanism.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>