<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ti/apl/tiapl4500m000" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Segment Schedules (tiapl4500m000)</Title>
	</Header>
	<HelpTopic><AimSection><Paragraph>Use this session to calculate and display <Link href="/baanerp/ti/glossary/glossary#000408" role="glossary" Update="No">segment schedules</Link>.</Paragraph>
		</AimSection>
		<GeneralSection><Paragraph>Segment schedules are schedules that indicate when the <Link href="/baanerp/ti/glossary/glossary#000073" role="glossary" Update="No">assembly parts</Link> that are required for the work in a particular <Link href="/baanerp/ti/glossary/glossary#000019" role="glossary">line segment</Link> must be delivered to the shop floor warehouse. For each segment on a line, a range of offline periods is defined. And for each period a date is scheduled on which the assembly parts are required. Therefore, every <Link href="/baanerp/td/glossary/glossary#ProducVarian.td" role="glossary">product variant</Link> whose requested offline date falls in one of these periods requires its assembly parts for the segment in question on that date.</Paragraph>
			<ProcedureList><ListIntro>The advantage of these schedules is that the assembly part requirements can be determined right from the schedule, if only the requested offline date of the product variant and the segment of the assembly parts is known. Compare this to the following procedure, which you must use if no segment schedules are used:</ListIntro>
				<ListItem>Determine in which segment a part is required.</ListItem>
				<ListItem>Offset that line segment: calculate the time between the start of the segment and the end of the <Link href="/baanerp/ti/glossary/glossary#000350" role="glossary">roll-off line</Link>.</ListItem>
				<ListItem>Calculate the date on which the assembly part is required.</ListItem>
				<ListItem>Determine the plan period in which this date falls.</ListItem>
				<ListItem>Determine the delivery date of the part, which is the start date of the plan period.</ListItem>
			</ProcedureList>
			<Paragraph>Segment schedules are used for a rough planning of assembly part requirements, especially in the more distant future, that is, the period after the allocation <Link href="/baanerp/ti/glossary/glossary#000407" role="glossary">time fence</Link>, but before the demand time fence. However, the schedules cover the whole period in the demand time fence, including the allocation time fence.</Paragraph>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>To prevent that no date can be scheduled for product variants whose requested offline date falls before the first period of a segment, the <GUIRef href="/baanerp/ti/apl/tiapl4500m000#tiapl400.podf" role="formfield">Planned Offline Date From</GUIRef> field of the first period of a segment is empty. As a result, the date scheduled of that period applies for all dates before the <GUIRef href="/baanerp/ti/apl/tiapl4500m000#tiapl400.podt" role="formfield">Planned Offline Date To</GUIRef>.</Paragraph>
			</Note>
			<List><ListIntro>The fields in the current session must be read as follows:</ListIntro>
				<ListItem>The <GUIRef href="/baanerp/ti/apl/tiapl4500m000#tiapl400.podt" role="formfield">Planned Offline Date To</GUIRef> and the <GUIRef href="/baanerp/ti/apl/tiapl4500m000#tiapl400.podf" role="formfield">Planned Offline Date From</GUIRef> display the periods that are defined for the segments displayed in the <GUIRef href="/baanerp/ti/apl/tiapl4500m000#tiapl400.segm" role="formfield">Line Segment</GUIRef> field.</ListItem>
				<ListItem>A product variant whose requested offline date falls in this period requires its assembly parts for the segment concerned on the <GUIRef href="/baanerp/ti/apl/tiapl4500m000#tiapl400.dsch" role="formfield">Date Scheduled</GUIRef>.</ListItem>
				<ListItem>These segments occur on the displayed <GUIRef href="/baanerp/ti/apl/tiapl4500m000#tiapl400.asln" role="formfield">Assembly Line</GUIRef>. This assembly line is a feeding line to the displayed <GUIRef href="/baanerp/ti/apl/tiapl4500m000#tiapl400.roln" role="formfield">Roll-off Line</GUIRef> if the codes of these lines differ. If the codes are equal, the <GUIRef href="/baanerp/ti/apl/tiapl4500m000#tiapl400.asln" role="formfield">Assembly Line</GUIRef> is itself the <GUIRef href="/baanerp/ti/apl/tiapl4500m000#tiapl400.roln" role="formfield">Roll-off Line</GUIRef>.</ListItem>
			</List>
			<Important><SectionTitle>Important!</SectionTitle>
				<Paragraph>The <GUIRef href="/baanerp/ti/apl/tiapl2221m000" role="session">Calculate Assembly Part Requirements (tiapl2221m000)</GUIRef> session must use the most up-to-date schedule. Therefore, that session automatically updates the segments if a change is detected that affects the schedules. However, not all changes can be detected automatically. In some cases, the schedule must be updated manually, either through the <GUIRef href="/baanerp/ti/apl/tiapl4500m000#update.schedules" role="formcommand">Update</GUIRef> command on the <GUIRef href="" role="menu">Specific</GUIRef> menu of the current session, or by selecting the <GUIRef href="/baanerp/ti/apl/tiapl2221m000#segment.schedules" role="formfield">Update Segment Schedules</GUIRef> check box in the <GUIRef href="/baanerp/ti/apl/tiapl2221m000" role="session">Calculate Assembly Part Requirements (tiapl2221m000)</GUIRef> session.</Paragraph>
				<List><ListIntro>The schedules must be updated manually when:</ListIntro>
					<ListItem>The line structure is changed.</ListItem>
					<ListItem>The plan period definition of the current scenario is changed, while the reference date is not changed.</ListItem>
				</List>
			</Important>
		</GeneralSection>
		<RelatedTopics><SectionTitle>Related topics</SectionTitle>
			<RelTopic><Link href="/baanerp/ti/onlinemanual/000402" role="manual">Assembly planning overview</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/ti/onlinemanual/000401" role="manual">Segment schedules</Link>
			</RelTopic>
		</RelatedTopics>
	</HelpTopic>
	<Fields><FieldHelp ID="tiapl400.roln"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Roll-off Line</Title>
			</Header>
			<FuncDesc>The code of the <Link href="/baanerp/ti/glossary/glossary#000350" role="glossary">roll-off line</Link> where the end product comes off.</FuncDesc>
			<SimpleSection><Paragraph>The roll-offline is used to offset the line segments, which means that the time between the start of a line segment and the end of the roll-off line is calculated.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tiapl400.asln"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Assembly Line</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/ti/glossary/glossary#000000000000055" role="glossary">assembly line</Link> whose assembly part requirements are calculated, based on the segment schedule displayed in this session.</FuncDesc>
			<SimpleSection><Paragraph>The line segment displayed in the <GUIRef href="/baanerp/ti/apl/tiapl4500m000#tiapl400.segm" role="formfield">Line Segment</GUIRef> field is a segment of this line.</Paragraph>
				<Paragraph>If the code of this line differs from the code that appears in the <GUIRef href="/baanerp/ti/apl/tiapl4500m000#tiapl400.roln" role="formfield">Roll-off Line</GUIRef> field, the line is a supply line.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tiapl400.segm"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Line Segment</Title>
			</Header>
			<FuncDesc>The <Link href="/baanerp/ti/glossary/glossary#000019" role="glossary">line segment</Link> for which the assembly part requirements are calculated, based on the segment schedule displayed in this session.</FuncDesc>
			<SimpleSection><Paragraph>The segment is a segment of the assembly line that appears in the <GUIRef href="/baanerp/ti/apl/tiapl4500m000#tiapl400.asln" role="formfield">Assembly Line</GUIRef> field.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tiapl400.podf"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Planned Offline Date From</Title>
			</Header>
			<FuncDesc>The start date of the date range for the displayed line segment.</FuncDesc>
			<SimpleSection><Paragraph>A product variant whose requested offline date falls in this range requires its assembly parts for the displayed line segment on the date that appears in the <GUIRef href="/baanerp/ti/apl/tiapl4500m000#tiapl400.dsch" role="formfield">Date Scheduled</GUIRef> field.</Paragraph>
			</SimpleSection>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>The first period of a segment has no start date. In that case the current field is empty. As a result, the <GUIRef href="/baanerp/ti/apl/tiapl4500m000#tiapl400.dsch" role="formfield">Date Scheduled</GUIRef> of the record applies for all assembly part requirements up to the <GUIRef href="/baanerp/ti/apl/tiapl4500m000#tiapl400.podt" role="formfield">Planned Offline Date To</GUIRef>.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="tiapl400.podt"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Planned Offline Date To</Title>
			</Header>
			<FuncDesc>The end date of the date range for the displayed line segment.</FuncDesc>
			<SimpleSection><Paragraph>A product variant whose requested offline date falls in this range requires its assembly parts for the displayed line segment on the date that appears in the <GUIRef href="/baanerp/ti/apl/tiapl4500m000#tiapl400.dsch" role="formfield">Date Scheduled</GUIRef> field.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tiapl400.dsch"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Date Scheduled</Title>
			</Header>
			<FuncDesc>The date on which the assembly parts for the displayed line segment are required, if the requested offline date of the product variant falls between the <GUIRef href="/baanerp/ti/apl/tiapl4500m000#tiapl400.podt" role="formfield">Planned Offline Date To</GUIRef> and the <GUIRef href="/baanerp/ti/apl/tiapl4500m000#tiapl400.podf" role="formfield">Planned Offline Date From</GUIRef>.</FuncDesc>
		</FieldHelp>
	</Fields>
	<FormCommands><CommandHelp ID="update.schedules"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Update</Title>
			</Header>
			<FuncDesc>Updates the segment schedules.</FuncDesc>
			<SimpleSection><Paragraph>Because the <GUIRef href="/baanerp/ti/apl/tiapl2221m000" role="session">Calculate Assembly Part Requirements (tiapl2221m000)</GUIRef> session must use the most up-to-date schedule, that session automatically updates the segments if a change is detected that affects the schedules. However, not all changes can be detected automatically. In some cases, the schedule must be updated manually, either through this <GUIRef href="/baanerp/ti/apl/tiapl4500m000#update.schedules" role="formcommand">Update</GUIRef> command, or by selecting the <GUIRef href="/baanerp/ti/apl/tiapl2221m000#segment.schedules" role="formfield">Update Segment Schedules</GUIRef> check box in the <GUIRef href="/baanerp/ti/apl/tiapl2221m000" role="session">Calculate Assembly Part Requirements (tiapl2221m000)</GUIRef> session.</Paragraph>
				<List><ListIntro>The schedules must be updated manually when:</ListIntro>
					<ListItem>The line structure is changed.</ListItem>
					<ListItem>The plan period definition of the current scenario is changed, while the reference date is not changed.</ListItem>
				</List>
			</SimpleSection>
		</CommandHelp>
	</FormCommands>
</Session>
