<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/cp/onlinemanual/000023" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Horizons and time fences</Title>
		<Keyword><Level1>Horizons and time fences</Level1>
			<Level2>Enterprise Planning</Level2>
		</Keyword>
		<Keyword><Level1>Time fences</Level1>
			<Level2>Enterprise Planning</Level2>
		</Keyword>
	</Header>
	<GeneralSection><Paragraph>You can influence the planning procedure in Enterprise Planning by means of horizons and time fences.</Paragraph>
		<GeneralSection><SectionTitle>Horizons</SectionTitle>
			<Paragraph>Generally, a horizon is a time period during which a particular function or planning concept is available. A horizon can either start at the current date, or start at a future date. A horizon in Enterprise Planning is defined by a figure that indicates a number of <Link href="/baanerp/cp/glossary/glossary#000064" role="glossary">workdays</Link>. This figure represents either the start or the end of the horizon.</Paragraph>
		</GeneralSection>
		<GeneralSection><SectionTitle>Time fences</SectionTitle>
			<Paragraph>Generally, a <Link href="/baanerp/cp/glossary/glossary#000063" role="glossary">time fence</Link> is a point in time before which a certain restriction applies. A time fence in Enterprise Planning is defined by a figure that indicates a number of workdays.</Paragraph>
		</GeneralSection>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>In Enterprise Planning, horizons and time fences are rounded to the end of a plan period, except the <Link href="/baanerp/cp/glossary/glossary#000071" role="glossary">signal horizon</Link>. For that reason, you must always define plan periods for a scenario, even if you only use <Link href="/baanerp/cp/glossary/glossary#000060" role="glossary">order planning</Link>.</Paragraph>
		</Note>
		<GeneralSection><SectionTitle>Major horizons and time fences</SectionTitle>
			<Paragraph>The most general horizon in Enterprise Planning is the <Link href="/baanerp/cp/glossary/glossary#000066" role="glossary">planning horizon</Link>. The planning horizon represents the period during which requirements are generated and supply is planned.</Paragraph>
			<List><ListIntro>The planning horizon consists of an <Link href="/baanerp/cp/glossary/glossary#000065" role="glossary">order horizon</Link> and/or a <Link href="/baanerp/cp/glossary/glossary#000303" role="glossary">master-planning horizon</Link>. This yields three possible planning situations:</ListIntro>
				<ListItem>Order horizon only.</ListItem>
				<ListItem>Order horizon (for shorter-term planning) and master-planning horizon (for longer-term planning).</ListItem>
				<ListItem>Master-planning horizon only.</ListItem>
			</List>
			<Paragraph>For the first part of the planning horizon, you can set a time fence to prevent Enterprise Planning from making changes in your near-future supply planning.</Paragraph>
			<List><ListIntro>Order horizons and planning horizons must comply with a number of rules. SSA ERP can check these horizons according to the following types of rules:</ListIntro>
				<ListItem>Length rules that are based on cumulative order lead times</ListItem>
				<ListItem>A synchronization rule between order horizons at various BOM levels</ListItem>
			</List>
		</GeneralSection>
		<GeneralSection><SectionTitle>Other horizons and time fences</SectionTitle>
			<List><ListIntro>The following horizons and time fences are available for all plan items:</ListIntro>
				<ListItem>The <Link href="/baanerp/cp/glossary/glossary#415" role="glossary">ATP/CTP horizon</Link>, which determines for which period ATP or CTP must be checked.</ListItem>
				<ListItem>The <Link href="/baanerp/cp/glossary/glossary#000058" role="glossary">fixed lead-time horizon</Link>, which is used in <Link href="/baanerp/cp/glossary/glossary#000060" role="glossary">order planning</Link> to determine whether Enterprise Planning must use a fixed order lead time or detailed routing data to plan production orders.</ListItem>
			</List>
			<List><ListIntro>When you maintain an <Link href="/baanerp/cp/glossary/glossary#000019" role="glossary">item master plan</Link> for an item, you can use the following additional horizons and time fences:</ListIntro>
				<ListItem><Link href="/baanerp/cp/glossary/glossary#000067" role="glossary">Forecast time fence</Link> (ignore the forecast in near-future planning)</ListItem>
				<ListItem><Link href="/baanerp/cp/glossary/glossary#000068" role="glossary">Forecast horizon</Link> (used for forecast-based inventory planning)</ListItem>
				<ListItem><Link href="/baanerp/cp/glossary/glossary#000033" role="glossary">Family CTP horizon</Link> (optionally redirect ATP/CTP checks to a higher product-family level)</ListItem>
			</List>
			<Paragraph>You can use the <Link href="/baanerp/cp/glossary/glossary#000071" role="glossary">signal horizon</Link> to indicate for which period you want Enterprise Planning to generate a particular planning signal.</Paragraph>
		</GeneralSection>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>You can define most horizons and time fences in the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000" role="session">Items - Planning (cprpd1100m000)</GUIRef> session. Signal horizons are defined in the <GUIRef href="/baanerp/cp/rao/cprao1110m000" role="session">Signal Types - by Planner (cprao1110m000)</GUIRef> session.</Paragraph>
		</Note>
		<GeneralSection><SectionTitle>Diagram of horizons and time fences</SectionTitle>
			<Figure><HTML:IMG SRC="../images/tr_graph_000023.gif" height="360" width="540" xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40"/></Figure>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>Most of these horizons and time fences can be set independently from each other. However, the following rules apply:</Paragraph>
			</Note>
			<List><ListItem>The planning horizon must be greater than zero.</ListItem>
				<ListItem>The order horizon, time fence, forecast time fence, and CTP horizon must fall within the planning horizon.</ListItem>
				<ListItem>The end of the fixed lead-time horizon coincides with the end of the order horizon.</ListItem>
				<ListItem>The end of the family CTP horizon coincides with the ATP/CTP horizon.</ListItem>
			</List>
		</GeneralSection>
	</GeneralSection>
	<RelatedTopics><SectionTitle>Related topics</SectionTitle>
		<RelTopic><Link href="/baanerp/cp/onlinemanual/000316" role="manual">Lead times and horizons</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/cp/onlinemanual/000411" role="manual">Time fences in order planning and in master planning</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/cp/onlinemanual/000024" role="manual">Time fence calculation</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/cp/onlinemanual/000044" role="manual">Scenarios in Enterprise Planning</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/cp/onlinemanual/000087" role="manual">Workdays and calendar days in Enterprise Planning</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/cp/onlinemanual/000302" role="manual">Plan periods in Enterprise Planning</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/cp/onlinemanual/000303" role="manual">Master planning versus order planning</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
