<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/td/ipu/tdipu0114m000" xml:lang="en">
   <Header>
      <Title>Segment Set - Segments (tdipu0114m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to maintain <Link href="/baanerp/td/glossary/glossary#000094" role="glossary">segments</Link> by <Link href="/baanerp/td/glossary/glossary#000093" role="glossary">segment set</Link>.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>You can define <Link href="/baanerp/td/glossary/glossary#000020" role="glossary">segment codes</Link> in the <GUIRef href="/baanerp/td/ipu/tdipu0115m000" role="session">Schedule Segments (tdipu0115m000)</GUIRef> session.</Paragraph>
         <Paragraph>You can define segment sets in the <GUIRef href="/baanerp/td/ipu/tdipu0113m000" role="session">Schedule Segment Sets (tdipu0113m000)</GUIRef> session.</Paragraph>
         <List>
            <ListIntro>If you use <Link href="/baanerp/td/glossary/glossary#000338" role="glossary">non-referenced schedules</Link>, segment sets are used to:</ListIntro>
            <ListItem>
               <Link href="/baanerp/td/glossary/glossary#000341" role="glossary">Regenerate</Link> schedule lines, which you can perform in the <GUIRef href="/baanerp/td/pur/tdpur3211m000" role="session">Regenerate Schedules (tdpur3211m000)</GUIRef> session.</ListItem>
            <ListItem>
               <Link href="/baanerp/td/glossary/glossary#000343" role="glossary">Cluster</Link> schedule lines to generate release lines with
			 the status <GUIRef href="/baanerp/tc/domains/edi.stat#preview" role="option">Preview</GUIRef>, which you can perform in the <GUIRef href="/baanerp/td/pur/tdpur3222m000" role="session">Generate Release Lines (tdpur3222m000)</GUIRef> session.</ListItem>
         </List>
         <Paragraph>If you use <Link href="/baanerp/td/glossary/glossary#000339" role="glossary">referenced schedules</Link>, no segment sets are used because
		  these schedules are immediately put into a purchase release with the status <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="option">Scheduled</GUIRef>. Consequently, the requirement type is always <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="option">Firm</GUIRef>.</Paragraph>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000006" role="manual">Using segment sets</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000346" role="manual">Purchase schedule release types</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000010" role="manual">Overview of purchase schedule handling</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000347" role="manual">Push schedules</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000348" role="manual">Pull forecast schedules</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000349" role="manual">Pull call-off schedules</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tdipu014.segs">
         <Header>
            <Title>Segment Set</Title>
         </Header>
         <FuncDesc>A set that is used to define the structure of a schedule. A
		segment set consists of a number of segments.</FuncDesc>
         <SimpleSection>
            <Paragraph>The segment set is used for schedule regeneration and for
		  clustering schedule lines. No segment sets are used for pull call-off
		  schedules.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/td/onlinemanual/000006" role="manual">Using segment sets</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tdipu014.segc">
         <Header>
            <Title>Segment</Title>
         </Header>
         <FuncDesc>
            <Link href="/baanerp/td/glossary/glossary#000020" role="glossary">segment code</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdipu015.dsca">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>The description or name of the code.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdipu015.rtype">
         <Header>
            <Title>Requirement Type</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/td/glossary/glossary#000340" role="glossary">requirement type</Link> linked to the segment (code).</FuncDesc>
         <AllowedValues>
            <SectionTitle>Allowed values</SectionTitle>
            <Paragraph>
               <Link href="/baanerp/td/domains/pur.rtyp" role="domain">Requirement Type</Link>
            </Paragraph>
         </AllowedValues>
      </FieldHelp>
      <FieldHelp ID="tdipu015.setu">
         <Header>
            <Title>Segment Time Unit</Title>
         </Header>
         <FuncDesc>The time unit in which the segment is expressed, for example
		days, weeks, months, and so on.</FuncDesc>
         <AllowedValues>
            <SectionTitle>Allowed values</SectionTitle>
            <Paragraph>
               <Link href="/baanerp/td/domains/ipu.time" role="domain">Time Unit</Link>
            </Paragraph>
         </AllowedValues>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/td/onlinemanual/000006" role="manual">Using segment sets</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tdipu015.segl">
         <Header>
            <Title>Segment Length</Title>
         </Header>
         <FuncDesc>The period that is assigned to the segment. The period is
		expressed in the segment time unit.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdipu014.seqn">
         <Header>
            <Title>Sequence Number</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 ERP Enterprise 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>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>This number is automatically assigned by ERP Enterprise, based on the
			 following procedure:</Paragraph>
            <ProcedureList>
               <ListItem>ERP Enterprise assigns the sequence numbers according to the defined <Link href="/baanerp/td/glossary/glossary#000340" role="glossary">requirement type</Link> in the following sequence: <GUIRef href="/baanerp/td/domains/pur.rtyp#immediate" role="option">Immediate</GUIRef>, <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="option">Firm</GUIRef>, or <GUIRef href="/baanerp/td/domains/pur.rtyp#planned" role="option">Planned</GUIRef>.</ListItem>
               <ListItem>If the requirement types of segments are the same, ERP Enterprise assigns the sequence
				numbers according to the <Link href="/baanerp/td/glossary/glossary#000021" role="glossary">segment time unit</Link>. The
				segment with the shortest time unit appears first.</ListItem>
               <ListItem>If both the requirement type and the segment time unit are
				the same, ERP Enterprise assigns the
				sequence number according to the <Link href="/baanerp/td/glossary/glossary#000095" role="glossary">segment length</Link>. The segment
				with the shortest segment length appears first.</ListItem>
               <ListItem>If the requirement type, segment time unit, and segment
				length are the same, ERP Enterprise arranges the segments alphabetically.</ListItem>
            </ProcedureList>
         </Note>
      </FieldHelp>
   </Fields>
</Session>