<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/td/onlinemanual/000006" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Segment sets</Title>
		<Keyword><Level1>segment</Level1>
		</Keyword>
		<Keyword><Level1>segment set</Level1>
		</Keyword>
	</Header>
	<GeneralSection><SectionTitle>Segment set</SectionTitle>
		<Paragraph>To set up a <Link href="/baanerp/td/glossary/glossary#000093" role="glossary">segment set</Link>, take the following steps:</Paragraph>
		<ProcedureList><ListItem>Create segments in the <Link href="/baanerp/td/ipu/tdipu0115m000" role="session">Schedule Segments (tdipu0115m000)</Link> session.</ListItem>
			<ListItem>Create a segment set in the <Link href="/baanerp/td/ipu/tdipu0113m000" role="session">Schedule Segment Sets (tdipu0113m000)</Link> session.</ListItem>
			<ListItem>Add the segments to the segment set in the <Link href="/baanerp/td/ipu/tdipu0114m000" role="session">Segment Set - Segments (tdipu0114m000)</Link> session.</ListItem>
		</ProcedureList>
		<GeneralSection><SectionTitle>Segments</SectionTitle>
			<Paragraph><Link href="/baanerp/td/glossary/glossary#000094" role="glossary">Segments</Link> have a specific <Link href="/baanerp/td/glossary/glossary#000095" role="glossary">segment length</Link>, are expressed in the <Link href="/baanerp/td/glossary/glossary#000021" role="glossary">segment time unit</Link> (weeks, months, four weeks, and so on), and are linked to <Link href="/baanerp/td/glossary/glossary#000340" role="glossary">requirement types</Link>.</Paragraph>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>In the <GUIRef href="/baanerp/td/ipu/tdipu0115m000" role="session">Schedule Segments (tdipu0115m000)</GUIRef> session, you cannot define a segment time unit and a segment length for a segment with the <GUIRef href="/baanerp/td/domains/pur.rtyp#immediate" role="enum">Immediate</GUIRef> requirement type, because this requirement type involves undelivered requirements from the past that must be shipped as soon as possible.</Paragraph>
			</Note>
			<Paragraph>Each segment in the segment set has a unique number. The schedule horizon is built according to the sequence number that is assigned by SSA ERP in the <GUIRef href="/baanerp/td/ipu/tdipu0114m000#tdipu014.seqn" role="field">Sequence Number</GUIRef> field of the <GUIRef href="/baanerp/td/ipu/tdipu0114m000" role="session">Segment Set - Segments (tdipu0114m000)</GUIRef> session.</Paragraph>
		</GeneralSection>
		<GeneralSection><SectionTitle>Purchase schedules</SectionTitle>
			<Paragraph>If you use <Link href="/baanerp/td/glossary/glossary#000334" role="glossary">push schedules</Link> or pull forecast schedules, the segment set stored in the <GUIRef href="/baanerp/td/pur/tdpur3102m000" role="session">Purchase Contract Line Logistic Data (tdpur3102m000)</GUIRef> session and/or the <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Item - Purchase Business Partner (tdipu0110m000)</GUIRef> session is used to:</Paragraph>
			<List><ListItem><Link href="/baanerp/td/glossary/glossary#000341" role="glossary">Regenerate</Link> schedule lines 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 line details with the status Preview, which you can perform in the <GUIRef href="/baanerp/td/pur/tdpur3222m000" role="session">Generate Release Lines (tdpur3222m000)</GUIRef> session.</ListItem>
			</List>
			<Paragraph>For pull call-off schedules, no segment sets are used because these schedules lines are not regenerated, or clustered and are immediately converted to a release line detail with the status <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="enum">Scheduled</GUIRef>. As a result, the requirement type is always <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="enum">Firm</GUIRef>.</Paragraph>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>If you link segments to the segment set in the <GUIRef href="/baanerp/td/ipu/tdipu0114m000" role="session">Segment Set - Segments (tdipu0114m000)</GUIRef> session, you must make sure that you use the correct segment time units. Make sure that:</Paragraph>
				<List><ListItem>You correctly define the first segment time unit of the first segment in a segment set. For example, if you set the first segment time unit to Week or Four Weeks, and if the calculated <Link href="/baanerp/td/glossary/glossary#000355" role="glossary">schedule issue date</Link> does not fall on a Monday, some days can be excluded from the clustering or regeneration process. Note that these segment time units always have Monday as a starting point for their activities. As a result, for a segment time unit defined as Week or Four Weeks, SSA ERP only starts clustering or regenerating schedule lines from a Monday on and therefore starts to cluster or regenerate schedule lines from the first Monday that follows the previously calculated schedule issue date. For a segment time unit defined as Month, SSA ERP does not start to cluster or regenerate schedule lines on the first available Monday, but on the first available Monday of the following month.</ListItem>
					<ListItem>The various segments connect. For example, if you combine the weekly time unit, which runs from Monday through Sunday, with the monthly time unit, which runs from the first Monday of the month through the day before the first Monday of the following month, when you regenerate or cluster schedule lines, a period of time can be undefined.</ListItem>
				</List>
			</Note>
			<ExampleSection><SectionTitle>Example</SectionTitle>
				<Paragraph>Next schedule issue date: 19/07/99</Paragraph>
				<Paragraph>Segments in the segment set:</Paragraph>
				<TABLE border="1"><TBODY><TR><TD>Segment Code</TD>
							<TD>Requirement Type</TD>
							<TD>Time Unit</TD>
							<TD>Segment Length</TD>
						</TR>
						<TR><TD>1</TD>
							<TD>Firm</TD>
							<TD>Weeks</TD>
							<TD>1</TD>
						</TR>
						<TR><TD>2</TD>
							<TD>Planned</TD>
							<TD>Months</TD>
							<TD>1</TD>
						</TR>
						<TR><TD>3</TD>
							<TD>Planned</TD>
							<TD>Months</TD>
							<TD>1</TD>
						</TR>
					</TBODY>
				</TABLE>
				<Paragraph>Segment time calculation, based on schedule issue date:</Paragraph>
				<TABLE border="1"><TBODY><TR><TD>Segment Code</TD>
							<TD>Start Date</TD>
							<TD>End Date</TD>
							<TD>Requirement Type</TD>
						</TR>
						<TR><TD>1</TD>
							<TD>19/07/99</TD>
							<TD>25/07/99</TD>
							<TD>Firm</TD>
						</TR>
						<TR><TD>2</TD>
							<TD>02/08/99</TD>
							<TD>05/09/99</TD>
							<TD>Planned</TD>
						</TR>
						<TR><TD>3</TD>
							<TD>06/09/99</TD>
							<TD>03/10/99</TD>
							<TD>Planned</TD>
						</TR>
					</TBODY>
				</TABLE>
				<Paragraph>In the previous example, a time gap of one week exists between 26 July 1999 and 2 August 1999. Although SSA ERP automatically fills this time gap, to avoid time gaps in a segment set, use the four weeks time unit in combination with the weekly time unit.</Paragraph>
			</ExampleSection>
			<Note><SectionTitle>Note</SectionTitle>
				<List><ListItem>When SSA ERP regenerates schedule lines, if a period is undefined between two segments, the schedule lines that fall in this time gap automatically receive the requirement type of the segment with the highest sequence number. For example, if a time gap exists between a segment that calculates the <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="enum">Firm</GUIRef> requirement type and a segment that calculates the <GUIRef href="/baanerp/td/domains/pur.rtyp#planned" role="enum">Planned</GUIRef> requirement type, the schedule lines that fall in this time gap automatically receive the <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="enum">Firm</GUIRef> requirement type. As a result, the time gap from the previous example that runs from 26 July 1999 through 2 August 1999, automatically receives the <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="enum">Firm</GUIRef> requirement type.</ListItem>
					<ListItem>When SSA ERP clusters schedule lines, if a period is undefined between two segments, SSA ERP automatically adds another segment that fills this time gap so that the schedule lines that fall in this time gap are also included in the clustering process. All the schedule lines that fall within the time period of that newly generated segment, are clustered into one release line detail.</ListItem>
					<ListItem>All schedule lines in a purchase release that fall after the period calculated by the last segment in a segment set, automatically receive the <GUIRef href="/baanerp/td/domains/pur.rtyp#planned" role="enum">Planned</GUIRef> requirement type.</ListItem>
				</List>
			</Note>
		</GeneralSection>
	</GeneralSection>
	<RelatedTopics><SectionTitle>Related topics</SectionTitle>
		<RelTopic><Link href="/baanerp/td/onlinemanual/000010" role="manual">Purchase schedules, basic data</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/td/onlinemanual/000346" role="manual">Purchase schedule release types</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/td/onlinemanual/000351" role="manual">Clustering purchase schedule lines</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/td/pur/tdpur3211m000" role="session">Regenerate Schedules (tdpur3211m000)</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
