<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/performance/cp/P000009_scenario_start_and_finish" xml:lang="en">
   <Header>
      <Title>Scenario start and finish date</Title>
      <Keyword type="header" order="d1e1088047">
         <Level1>Valid for LN FP0, FP1, FP2, FP3, FP4, FP5, FP6, 10, 10.2</Level1>
         <Level2>scenario start and finish date</Level2>
      </Keyword>
      <Keyword type="header" order="d1e1088052">
         <Level1>scenario start and finish date</Level1>
      </Keyword>
      <Keyword type="header" order="d1e1088055">
         <Level1>Effect on CPU</Level1>
         <Level2>scenario start and finish date</Level2>
      </Keyword>
   </Header>
   <GeneralSection>
      <Paragraph>To define the <Link href="/baanerp/cp/glossary/glossary#000007" role="glossary">scenario</Link> 's start date and finish date, use the <GUIRef href="/baanerp/cp/rpd/cprpd4100m000#cprpd400.plsd" role="manual">Scenario Start Date</GUIRef> and <GUIRef href="/baanerp/cp/rpd/cprpd4100m000#cprpd400.plfd" role="manual">Scenario Finish Date</GUIRef> fields in the <GUIRef href="/baanerp/cp/rpd/cprpd4100m000" role="session">Scenarios (cprpd4100m000)</GUIRef> session.</Paragraph>
      <Paragraph>The length of time between a scenario's start date and finish
		date affects the system performance if you <Link href="/baanerp/cp/glossary/glossary#000006" role="glossary">roll</Link> the scenario. The rolling process recalculates all <Link href="/baanerp/cp/glossary/glossary#000019" role="glossary">master-plan</Link> data from <Link href="/baanerp/cp/glossary/glossary#000109" role="glossary">plan periods</Link> to separate days; then, the rolling process
		recalculates the data from days to plan periods.</Paragraph>
      <Paragraph>The recalculation process also includes open orders with a start
		date before the start date of the scenario. The orders between the start date
		and the current date form the history of the <Link href="/baanerp/cp/glossary/glossary#000019" role="glossary">master plan</Link>. To check what has happened in the previous
		periods, use this historic data. However, a longer history reduces the system
		performance of the planning process.</Paragraph>
      <Paragraph>The <Link href="/baanerp/cp/glossary/glossary#000044" role="glossary">goods flow</Link> before the scenario's start date is aggregated
		to one transaction at the scenario start date. Before the scenario's start
		date, no <Link href="/baanerp/cp/glossary/glossary#000452" role="glossary">pegging information</Link> is available, because all
		transactions before the scenario's start date are anonymous.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <List>
         <ListIntro>Recommendations:</ListIntro>
         <ListItem>Do not make the period between the scenario's start date and
		  finish date too long.</ListItem>
         <ListItem>Do not set the scenario's start date too far before the current
		  date.</ListItem>
      </List>
   </GeneralSection>
   <GeneralSection>
      <GeneralSection>
         <SectionTitle>Performance aspects</SectionTitle>
         <List>
            <ListItem>Effect on CPU: Yes</ListItem>
            <ListItem>Effect on database growth: Not applicable</ListItem>
         </List>
      </GeneralSection>
   </GeneralSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/cp/onlinemanual/000044" role="manual">Scenarios in Enterprise Planning</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/cp/onlinemanual/000150" role="manual">To use a rolling scenario</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>