<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/cp/onlinemanual/000044" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Scenarios in Enterprise Planning</Title>
		<Keyword><Level1>Scenarios in Enterprise Planning</Level1>
		</Keyword>
		<Keyword><Level1>Scenarios</Level1>
		</Keyword>
	</Header>
	<GeneralSection><Paragraph>A <Link href="/baanerp/cp/glossary/glossary#000007" role="glossary">scenario</Link> represents one out of several (possible) overall planning situations.</Paragraph>
		<Paragraph>In <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>, planning is carried out within the context of a particular scenario, and depending on the settings in that scenario. You can set up several scenarios to compare possible planning solutions.</Paragraph>
		<GeneralSection><SectionTitle>Actual scenario</SectionTitle>
			<Paragraph>One of the scenarios is the <Link href="/baanerp/cp/glossary/glossary#000093" role="glossary">actual scenario</Link>; the other scenarios serve for what-if analyses. The planned orders (and production plans) of the actual scenario can be confirmed and transferred to the <Link href="/baanerp/cp/glossary/glossary#000027" role="glossary">execution level</Link>, where they become actual orders.</Paragraph>
		</GeneralSection>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>The actual scenario is specified in the <GUIRef href="/baanerp/cp/rpd/cprpd0100m000" role="session">EP Parameters (cprpd0100m000)</GUIRef> session.</Paragraph>
		</Note>
		<GeneralSection><SectionTitle>How to define a scenario</SectionTitle>
			<Paragraph>Use the <GUIRef href="/baanerp/cp/rpd/cprpd4100m000" role="session">Scenarios (cprpd4100m000)</GUIRef> session to define a new scenario.</Paragraph>
			<Paragraph>If you want to keep using the scenario for a prolonged period of time, you can choose to define the scenario as a <Link href="/baanerp/cp/glossary/glossary#000006" role="glossary">rolling scenario</Link>.</Paragraph>
			<Paragraph>If you want to use the scenario for central <Link href="/baanerp/tf/glossary/glossary#Multisite.tf" role="glossary">multisite</Link> planning, you must designate the scenario as a central multisite scenario.</Paragraph>
		</GeneralSection>
		<GeneralSection><SectionTitle>Plan periods</SectionTitle>
			<Paragraph>A scenario is subdivided into <Link href="/baanerp/cp/glossary/glossary#000109" role="glossary">plan periods</Link>. Plan periods are used as time buckets for <Link href="/baanerp/cp/glossary/glossary#000059" role="glossary">master planning</Link>. Horizons and time fences are always rounded to the end of a plan period.</Paragraph>
		</GeneralSection>
		<GeneralSection><SectionTitle>Scenario-dependent data</SectionTitle>
			<List><ListIntro>Many basic entities in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> are not dependent upon a particular scenario, but can be used in all scenarios:</ListIntro>
				<ListItem>Plan items.</ListItem>
				<ListItem>Resources.</ListItem>
				<ListItem>Channels.</ListItem>
				<ListItem>Clusters.</ListItem>
				<ListItem>Plan units.</ListItem>
			</List>
			<List><ListIntro>Several types of planning data, however, are defined within the context of a scenario, and therefore can differ between scenarios:</ListIntro>
				<ListItem>Master plans.</ListItem>
				<ListItem>Planned orders.</ListItem>
				<ListItem>Sourcing strategies.</ListItem>
				<ListItem>Supply strategies.</ListItem>
			</List>
			<Paragraph>You can copy the data from one scenario to another scenario. In the <GUIRef href="/baanerp/cp/rpd/cprpd4201m000" role="session">Copy Scenario (cprpd4201m000)</GUIRef> session several options are available to copy all, or only specific scenario data from the source scenario to the target scenario. The <GUIRef href="/baanerp/cp/rpd/cprpd4201m000#overwr" role="formfield">Overwrite</GUIRef> check box determines whether Enterprise Planning must add the data of the source scenario to those of the target scenario, or whether Enterprise Planning must overwrite the data of the target scenario. You can even select a range of plan items for which you want to copy specific data from one scenario to another.</Paragraph>
		</GeneralSection>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>Calendars are not scenario dependent. However, the way that calendars are used does vary by scenario, because a different <Link href="/baanerp/tc/glossary/glossary#ResoActiType.tc" role="glossary">availability type</Link> can be used for each scenario.</Paragraph>
		</Note>
	</GeneralSection>
	<RelatedTopics><SectionTitle>Related topics</SectionTitle>
		<RelTopic><Link href="/baanerp/cp/onlinemanual/000300" role="manual">Enterprise Planning, an Overview</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/cp/onlinemanual/000302" role="manual">Plan periods in Enterprise Planning</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/cp/onlinemanual/000023" role="manual">Horizons and time fences</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/cp/onlinemanual/000150" role="manual">To use a rolling scenario</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/cp/onlinemanual/000148" role="manual">Multisite planning</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/cp/onlinemanual/000034" role="manual">The use of calendars in Enterprise Planning</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
