<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/cp/onlinemanual/000085" xml:lang="en">
   <Header>
      <Title>Channel ATP periods</Title>
      <Keyword type="header" order="d1e175242">
         <Level1>Channel ATP periods</Level1>
      </Keyword>
   </Header>
   <GeneralSection>
      <Paragraph>You can enter the <Link href="/baanerp/cp/glossary/glossary#000025" role="glossary">allowed demand</Link> per <Link href="/baanerp/cp/glossary/glossary#000109" role="glossary">plan period</Link> for an item in
		the <GUIRef href="/baanerp/cp/dsp/cpdsp5130m000" role="session">Channel Master Plan (cpdsp5130m000)</GUIRef> session, but LN checks the <Link href="/baanerp/cp/glossary/glossary#000037" role="glossary">channel ATP</Link> per channel ATP
		period.</Paragraph>
      <Paragraph>You can define the
		channel ATP periods in the <GUIRef href="/baanerp/cp/dsp/cpdsp5100m000" role="session">Plan Item - Channels (cpdsp5100m000)</GUIRef> session.</Paragraph>
      <GeneralSection>
         <SectionTitle>Channel ATP period length</SectionTitle>
         <Paragraph>Enter the
		  channel-ATP-period length in the <GUIRef href="/baanerp/cp/dsp/cpdsp5100m000#cpdsp500.perl" role="manual">ATP Period Length</GUIRef> field of the <GUIRef href="/baanerp/cp/dsp/cpdsp5100m000" role="session">Plan Item - Channels (cpdsp5100m000)</GUIRef> session. A channel ATP period is defined in
		  calendar days. The channel ATP periods have a fixed length over the total
		  planning horizon.</Paragraph>
         <Paragraph>As a rule, a channel
		  ATP period comprises several plan periods.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Reference date</SectionTitle>
         <Paragraph>You can specify a
		  reference date in the <GUIRef href="/baanerp/cp/dsp/cpdsp5100m000#cpdsp500.rfdt" role="manual">Reference Date</GUIRef> field of the <GUIRef href="/baanerp/cp/dsp/cpdsp5100m000" role="session">Plan Item - Channels (cpdsp5100m000)</GUIRef> session. This reference date indicates when
		  the first channel ATP period must start.</Paragraph>
         <Paragraph>If the reference date lies before the scenario start date, LN adds a multiple of
		  the value of the <GUIRef href="/baanerp/cp/dsp/cpdsp5100m000#cpdsp500.perl" role="manual">ATP Period Length</GUIRef> field to the reference date. The first channel ATP
		  period starts at the first possible date after the start date of the scenario.</Paragraph>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>The reference date
			 is a fixed date. Rolling the scenario does not change the reference date.</Paragraph>
         </Note>
      </GeneralSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <List>
            <ListIntro>You use the following settings:</ListIntro>
            <ListItem>Reference date: Jan. 1</ListItem>
            <ListItem>Channel ATP period
			 length: 28 days. As a result, the first ATP period is: Jan. 1 - Jan. 28.</ListItem>
         </List>
      </ExampleSection>
      <GeneralSection>
         <SectionTitle>Channel ATP</SectionTitle>
         <Paragraph>LN accumulates the allowed demand of all plan
		  periods with a start date in the same channel ATP period. Customer orders can
		  be accepted for a channel, until all of the channel ATP in a channel ATP period
		  has been used up.</Paragraph>
      </GeneralSection>
   </GeneralSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/cp/onlinemanual/000080" role="manual">Channels in Enterprise Planning</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/cp/onlinemanual/000125" role="manual">Channel ATP</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>