<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/dm/chm/dmchm0530m000" xml:lang="en">
   <Header>
      <Title>Change Affected Objects (dmchm0530m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to link an <Link href="/baanerp/dm/glossary/glossary#000063" role="glossary">object</Link> to a <Link href="/baanerp/dm/glossary/glossary#000005" role="glossary">change proposal</Link>.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>You cannot start this
		  session directly from the Menu Browser. In the <Link href="/baanerp/dm/chm/dmchm0120m000" role="session">Change Proposal (dmchm0120m000)</Link> session, click <GUIRef href="/baanerp/dm/chm/dmchm0120m000#exec.user.2" role="command">Link Affected Objects</GUIRef> on the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu.
		  This action starts the <Link href="/baanerp/dm/sys/dmsys9113m000" role="session">Families Members with Amounts (dmsys9113m000)</Link> session.
		  Select the appropriate object type and double-click the record or click <GUIRef href="" role="manual">Object Attachments</GUIRef> on the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu. The <Link href="/baanerp/dm/chm/dmchm0530m000" role="session">Change Affected Objects (dmchm0530m000)</Link> session starts. On the <GUIRef href="" role="manual">File</GUIRef> menu, click <GUIRef href="" role="manual">New</GUIRef> to link an object to the
		  change proposal.</Paragraph>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>In this session, the
			 change proposal is the source object, and the attached object is the target
			 object. The object attached to the change proposal appears the next time you
			 run the <GUIRef href="/baanerp/dm/chm/dmchm0530m000" role="session">ERP Affected Objects linked to Change Proposal (dmchm0530m000)</GUIRef> session.</Paragraph>
            <Paragraph> 
               <GUIRef href="" role="manual">Relative Change Order:</GUIRef> The Relative Change Order (RCO) enables the user to set
			 relative timing for a change order that has been linked to a change proposal.
			 If you link an ERP object to a change proposal, the change proposal must have a
			 change order with some specified date. To set timing for the next entity linked
			 by Relative Change Order, the date must be the current change order date and
			 the duration must be specified. To do this, you can use base change order and
			 the duration. The Relative Change Order date depends on the base change order
			 and the duration. The Relative Change Order must be part of the current change
			 proposal and it can be linked to various objects. The Relative Change Order
			 date must not fall before the current date.</Paragraph>
         </Note>
      </GeneralSection>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="dmchm030.cpid">
         <Header>
            <Title>Change</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/dm/glossary/glossary#000003" role="glossary">change</Link> ID. This field is a display field.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm011.desc">
         <Header>
            <Title>Change Status</Title>
         </Header>
         <FuncDesc>The status of the change. This field is a display field.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm030.vers">
         <Header>
            <Title>Proposal</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/dm/glossary/glossary#000005" role="glossary">change proposal</Link> for the change. This field is a
		  display-only field and cannot be edited.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm030.obid">
         <Header>
            <Title>Object</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/dm/glossary/glossary#000063" role="glossary">object</Link> linked to the change and proposal. This can be any
		  ERP entity, for example: Engineering Item, Routing Operation, Labor Rates, and
		  so on.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm030.lnum">
         <Header>
            <Title>Sequence</Title>
         </Header>
         <FuncDesc>The sequence number of the linked entities.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="child.value.old">
         <Header>
            <Title>Old Object</Title>
         </Header>
         <FuncDesc>The selected old entity of the <Link href="/baanerp/dm/glossary/glossary#000104" role="glossary">change affected objects</Link>. The change affected object can
		  be any ERP entity, such as Engineering Item - Revisions. After the proposal is
		  approved, the old entity is set to expired. The expiry date is the change order
		  date linked to this change affected object. This field is a generic field.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="child.value.new">
         <Header>
            <Title>New Object</Title>
         </Header>
         <FuncDesc>The selected new entity of Change Affected Object. The change
		  affected object can be any ERP entity, such as Engineering Item - Revisions.
		  The new entity becomes effective after the proposal is approved. The effective
		  date is the change order date linked to this change affected object. This field
		  is a generic field.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="child.old.desc">
         <Header>
            <Title>Description of Old Object</Title>
         </Header>
         <FuncDesc>The description of the old entity.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="child.new.desc">
         <Header>
            <Title>Description of new Object</Title>
         </Header>
         <FuncDesc>The description of the new entity.</FuncDesc>
      </FieldHelp>
      <FieldHelp>
         <Header>
            <Title>Change Order</Title>
         </Header>
         <FuncDesc>The change order identifier. Change order provides a generic
		  mechanism for any controlled ERP linked entity. A change order date is
		  specified in the change order to make the linked entity effective or expire.
		  The UTC date and time format is used.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm050.prdt">
         <Header>
            <Title>Change Order Dates</Title>
         </Header>
         <FuncDesc>The change order dates. Each proposal has a list of proposed
		  effective dates and they are recorded as change orders dates. The UTC date and
		  time format is used. No past date is permitted when you create a new change
		  order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm030.lact">
         <Header>
            <Title>Link Active</Title>
         </Header>
         <FuncDesc>The field displays the status of the link between the change
		  management and the ERP entity. If this check box is selected, the change affected object is linked to a proposal. After
		  the change is approved, the link becomes inactive and the check box is cleared.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm030.user">
         <Header>
            <Title>Updated By</Title>
         </Header>
         <FuncDesc>The name of the person who updates the record. The LN user logon code
		  appears.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm030.date">
         <Header>
            <Title>Last Update</Title>
         </Header>
         <FuncDesc>The date and time when the user modifies the record.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm030.reco">
         <Header>
            <Title>Relative Change Order</Title>
         </Header>
         <FuncDesc>The option is used to provide a future date based on the
		  change order date, which is incremented with the duration value. This relative
		  change order becomes the base change order for some other entity which has to
		  be set to expired or made effective.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm030.dura">
         <Header>
            <Title>Duration</Title>
         </Header>
         <FuncDesc>The time duration of the change order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="relco.date">
         <Header>
            <Title>Effective From</Title>
         </Header>
         <FuncDesc>The date from when an entity is made effective. The UTC date
		  and time format is used, which is a sum of the current date and the duration.</FuncDesc>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="zoom2old">
         <Header>
            <Title>Old Objects</Title>
         </Header>
         <FuncDesc>Displays the list of old objects. This option is enabled if an
		  affected object is linked to an old object.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="zoom2new">
         <Header>
            <Title>New Objects</Title>
         </Header>
         <FuncDesc>Displays the list of new objects. This option is enabled if an
		  affected object is linked to a new object.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="dmchm0430m000">
         <Header>
            <Title>Print Change Affected Objects</Title>
         </Header>
         <FuncDesc>Prints a list of all the change affected objects.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>