<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/dm/chm/dmchm0150m004" xml:lang="en">
   <Header>
      <Title>Bill of Change Orders (dmchm0150m004)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to establish parent/child links between change orders.</Paragraph>
         <Paragraph>On the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu, click <GUIRef href="" role="manual">Add Child CO</GUIRef> to add a new <Link href="/baanerp/dm/glossary/glossary#000045" role="glossary">child change order</Link> to the parent change order. This
		  option is available only if you run this session directly from the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu.</Paragraph>
         <Paragraph>On the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu, click the <GUIRef href="" role="manual">Remove BOCO Link</GUIRef> option to remove the link between child
		  change order and the parent change order.</Paragraph>
         <Paragraph>On the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu, click the <GUIRef href="" role="manual">Change Orders Children</GUIRef> option to open another instance of the
		  session. You can maintain the children of a selected child change order, that
		  is, the second-level children of the parent change orders. You can construct a
		  bill of change orders.</Paragraph>
         <Paragraph>When you create a new <Link href="/baanerp/dm/glossary/glossary#000006" role="glossary">change order</Link>, the dates of the parent change order are
		  applicable to the children.</Paragraph>
      </AimSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/dm/onlinemanual/000015" role="manual">Change Order</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="dmchm050.prsq">
         <Header>
            <Title>Parent</Title>
         </Header>
         <FuncDesc>The parent change order ID. A parent change order is
		  independent, and free of change and proposal. A maximum of two levels is
		  permitted in the bill of change order.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="prdt">
         <Header>
            <Title>Parent Date</Title>
         </Header>
         <FuncDesc>The parent change order date. The parent change order date is
		  called the parent date. This date is applicable to the child change orders.</FuncDesc>
         <SimpleSection>
            <Paragraph> 
               <GUIRef href="" role="manual">Note</GUIRef> The parent change
			 order must not be postdated.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="dmchm050.sqnm">
         <Header>
            <Title>Change Order</Title>
         </Header>
         <FuncDesc>The child change order. The change order provides a generic
		  mechanism for any ERP controlled link entity. The change order date is
		  specified to put the linked entity into effect or to set the entity to expired.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm050.prdt">
         <Header>
            <Title>Change Order Date</Title>
         </Header>
         <FuncDesc>The change order date and time for a specific change order.
		  Each proposal has a list of proposed effective and expiry dates, specified in
		  UTC date and time format. The dates are recorded as change orders dates. When a
		  new change order is created, the date can be specified in this field. The date
		  specified is applicable to the linked entity. If the approval date is later
		  than the change order date, the date specified is applicable to the linked
		  entity. A change order must not be postdated.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="dmchm050.desc">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="exec.user.3">
         <Header>
            <Title>Add Child CO</Title>
         </Header>
         <FuncDesc>Adds a child change order.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="exec.user.4">
         <Header>
            <Title>Remove BOCO Link</Title>
         </Header>
         <FuncDesc>Removes the Bill of Change Order link.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>