<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ti/pcs/tipcs4110m000" xml:lang="en">
   <Header>
      <Title>Activity Relationships (tipcs4110m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to maintain the
		  relationships between a project's activities, thus enabling a network planning
		  for the project to be carried out.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>This session enables
		  you to determine the sequence of activities and the start and finish time of an
		  activity compared with the preceding or next activity.</Paragraph>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListItem>Relations between
				activities are recorded by manual input or by running the <GUIRef href="/baanerp/ti/pcs/tipcs2210m000" role="session">Copy Project (tipcs2210m000)</GUIRef> session.</ListItem>
               <ListItem>Relations between
				activities are used in the time planning and the rough capacity planning in
				Network planning.</ListItem>
            </List>
         </Note>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/ti/onlinemanual/000178" role="manual">Network planning</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tipcs410.cprj">
         <Header>
            <Title>Project</Title>
         </Header>
         <FuncDesc>A collection of manufacturing and purchasing actions that are
		performed especially for a particular customer order. A project is initiated by
		a customer order for items having a <GUIRef href="/baanerp/tc/domains/opol#on.order" role="option">To Order</GUIRef> order policy. The purpose of a project is to plan and coordinate the production
		of these items.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>For a standard-to-order production, the project is only
			 used to link the item with the customer order. Otherwise, a project can
			 include:</ListIntro>
               <ListItem>Customized item data (BOMs and routings)</ListItem>
               <ListItem>Project planning (activity planning)</ListItem>
            </List>
            <Paragraph>A budget is a special type of project. A budget is used to
		  plan and estimate, not to carry out production.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000175" role="manual">Project types</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tipcs030.psts">
         <Header>
            <Title>Status</Title>
         </Header>
         <FuncDesc>The status of the project.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs410.sern">
         <Header>
            <Title>Sequence</Title>
         </Header>
         <FuncDesc>The number that identifies a data record or a step in a
		sequence of activities. Sequence numbers are used in many contexts. Usually LN generates the
		sequence number for the next item or step. Depending on the context, you can
		overwrite this number. You can sometimes influence the numbering by setting the
		corresponding parameters.</FuncDesc>
         <SimpleSection>
            <Paragraph>By default, LN shows numbers in the
			 sequence of 10, 20, 30, and so on. Numbering is free. However, you are
			 recommended to adopt these default values, because the intervening numbers are
			 necessary to insert any activity relationships.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tipcs410.pact">
         <Header>
            <Title>Preceding Activity</Title>
         </Header>
         <FuncDesc>The code of the activity for which you want to create a
		  relationship with another activity.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs410.sact">
         <Header>
            <Title>Next Activity</Title>
         </Header>
         <FuncDesc>Enter the code of the activity which has a relationship with a
		  preceding activity.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tipcs410.korl">
         <Header>
            <Title>Relation Type</Title>
         </Header>
         <FuncDesc>The relation type indicates the relationship between the
		  preceding and the next activity.</FuncDesc>
         <AllowedValues>
            <SectionTitle>Allowed values</SectionTitle>
            <Paragraph>
               <Link href="/baanerp/tc/domains/korl" role="domain">Relation Type</Link>
            </Paragraph>
         </AllowedValues>
      </FieldHelp>
      <FieldHelp ID="tipcs410.arfl">
         <Header>
            <Title>Float Time (Day)</Title>
         </Header>
         <FuncDesc>Enter the absolute relationship float-time in days.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>A positive
			 float-time always means a positive shift of the next activity with respect to
			 the preceding activity.</Paragraph>
         </Note>
         <SimpleSection>
            <Paragraph>Example: Two
			 activities have an end-start relationship. If these activities directly link up
			 with each other, the absolute float-time is zero. If the next activity is to
			 start four days before the end of the preceding one, you can enter an absolute
			 float-time of minus four. If the next activity is to start five days after the
			 end of the preceding activity, the absolute float-time is five.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000150" role="manual">Float times</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tipcs410.rrfl">
         <Header>
            <Title>Float Time (in Perc)</Title>
         </Header>
         <FuncDesc>Enter the relative relationship float-time as a percentage of
		  the duration of the preceding activity.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>A positive
			 float-time always means a positive shift of the next activity with respect to
			 the preceding activity.</Paragraph>
         </Note>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000150" role="manual">Float times</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
   </Fields>
</Session>