<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/td/pur/tdpur3211m000" xml:lang="en">
   <Header>
      <Title>Regenerate Schedules (tdpur3211m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to <Link href="/baanerp/td/glossary/glossary#000341" role="glossary">regenerate</Link> 
            <Link href="/baanerp/td/glossary/glossary#000338" role="glossary">non-referenced schedules</Link>.</Paragraph>
      </AimSection>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>ERP Enterprise only
		  regenerates the schedule lines that have the <GUIRef href="/baanerp/td/domains/pur.stat#approved" role="option">Approved</GUIRef> status.</Paragraph>
      </Note>
      <GeneralSection>
         <Paragraph>For <Link href="/baanerp/td/glossary/glossary#000334" role="glossary">push schedules</Link>, the process of schedule line regeneration
		  serves the following purposes:</Paragraph>
         <List>
            <ListItem>To determine the applicable <Link href="/baanerp/td/glossary/glossary#000093" role="glossary">segment set</Link> and <Link href="/baanerp/td/glossary/glossary#000000000000019" role="glossary">pattern code</Link> as retrieved from the <GUIRef href="/baanerp/td/pur/tdpur3102m000" role="session">Purchase Contract Line Logistic Data (tdpur3102m000)</GUIRef> session and/or the <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Items - Purchase Business Partner (tdipu0110m000)</GUIRef> session, and to update the <Link href="/baanerp/td/glossary/glossary#Buyer_td" role="glossary">buyer</Link>.</ListItem>
            <ListItem>To calculate the schedule line's new <Link href="/baanerp/td/glossary/glossary#000340" role="glossary">requirement type</Link> based on the applicable segment set and
			 issue <Link href="/baanerp/td/glossary/glossary#000030" role="glossary">pattern</Link>. As a result, the schedule line is moved in time.</ListItem>
         </List>
         <Paragraph>For pull-forecast schedules, regeneration is only performed to
		  retrieve the correct segment set, pattern code, and buyer for the purchase
		  schedule.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>To shift segments due to regeneration</SectionTitle>
         <Paragraph>Regeneration is performed based on a schedule's applicable
		  segment set and issue pattern, as stored in the <GUIRef href="/baanerp/td/pur/tdpur3102m000" role="session">Purchase Contract Line Logistic Data (tdpur3102m000)</GUIRef> session and/or the <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Items - Purchase Business Partner (tdipu0110m000)</GUIRef> session. Every time the regeneration
		  process is repeated, the next schedule issue date is determined based on the
		  schedule's linked issue pattern. After this, ERP Enterprise determines in which
		  segment the schedule lines fall. If the segments are shifted, the changed
		  requirement types are stored on the schedule lines.</Paragraph>
         <List>
            <ListIntro>For the following release types, the following segment set
			 and issue pattern are used for regeneration:</ListIntro>
            <ListItemHead>
               <GUIRef href="/baanerp/td/domains/pur.reltype#matrelease" role="option">Material Release</GUIRef>
            </ListItemHead>
            <ListItem>Only a material release is sent to the supplier. The issue
			 pattern and segment set for material release are taken as starting point for
			 the regeneration. All requirements that fall after the horizon of the material
			 release's segment set, receive the <GUIRef href="/baanerp/td/domains/pur.rtyp#planned" role="option">Planned</GUIRef> requirement type.</ListItem>
            <ListItemHead>
               <GUIRef href="/baanerp/tc/domains/scrd#ship.only" role="option">Shipping Schedule Only</GUIRef>
            </ListItemHead>
            <ListItem>Only a shipping schedule is sent to the supplier. The issue
			 pattern and segment set for shipping schedule are taken as a starting point for
			 the regeneration. All requirements that fall after the horizon of the shipping
			 schedule's segment set, receive the <GUIRef href="/baanerp/td/domains/pur.rtyp#planned" role="option">Planned</GUIRef> requirement type.</ListItem>
            <ListItemHead>
               <GUIRef href="/baanerp/td/domains/pur.reltype#shipschedule" role="option">Shipping Schedule</GUIRef>
            </ListItemHead>
            <ListItem>A material release and a shipping schedule are sent to the
			 supplier. The issue pattern and segment set for shipping schedule are taken as
			 a starting point for the regeneration. All requirements that fall after the
			 horizon of the shipping schedule's segment set, receive the <GUIRef href="/baanerp/td/domains/pur.rtyp#planned" role="option">Planned</GUIRef> requirement type.</ListItem>
         </List>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>As a general rule, you can assume that in the regeneration
			 process, only the <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="option">Firm</GUIRef> requirement types are calculated. All schedule lines
			 that fall outside the period of the <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="option">Firm</GUIRef> requirement type, receive the <GUIRef href="/baanerp/td/domains/pur.rtyp#planned" role="option">Planned</GUIRef> requirement type. Whether or not the lines with
			 the <GUIRef href="/baanerp/td/domains/pur.rtyp#planned" role="option">Planned</GUIRef> requirement type are sent in a <Link href="/baanerp/td/glossary/glossary#000351" role="glossary">purchase release</Link> depends on the purchase schedule's
			 release type. However, if a period is undefined between two segments, the
			 schedule lines that fall in this time gap automatically receive the requirement
			 type of the segment with the highest sequence number.</Paragraph>
         </Note>
      </GeneralSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <List>
            <ListItem>Release type: <GUIRef href="/baanerp/td/domains/pur.reltype#matrelease" role="option">Material Release</GUIRef>.</ListItem>
            <ListItem>The Segment Set for Material Release SS1 contains the
			 following segments:</ListItem>
         </List>
         <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="5">
               <TR no="1" isLast="false">
                  <TD rowspan="1" colspan="1">Segment Code</TD>
                  <TD rowspan="1" colspan="1">Requirement
				  Type</TD>
                  <TD rowspan="1" colspan="1">Time Unit</TD>
                  <TD rowspan="1" colspan="1">Segment
				  Length</TD>
               </TR>
               <TR no="2" isLast="false">
                  <TD rowspan="1" colspan="1">001</TD>
                  <TD rowspan="1" colspan="1">Immediate</TD>
                  <TD rowspan="1" colspan="1">hours</TD>
                  <TD rowspan="1" colspan="1">0</TD>
               </TR>
               <TR no="3" isLast="false">
                  <TD rowspan="1" colspan="1">003</TD>
                  <TD rowspan="1" colspan="1">Firm</TD>
                  <TD rowspan="1" colspan="1">weeks</TD>
                  <TD rowspan="1" colspan="1">2
				  (weeks)</TD>
               </TR>
               <TR no="4" isLast="false">
                  <TD rowspan="1" colspan="1">004</TD>
                  <TD rowspan="1" colspan="1">Planned</TD>
                  <TD rowspan="1" colspan="1">weeks</TD>
                  <TD rowspan="1" colspan="1">2
				  (weeks)</TD>
               </TR>
               <TR no="5" isLast="true">
                  <TD rowspan="1" colspan="1">005</TD>
                  <TD rowspan="1" colspan="1">Planned</TD>
                  <TD rowspan="1" colspan="1">four weeks</TD>
                  <TD rowspan="1" colspan="1">2 (four
				  weeks)</TD>
               </TR>
            </TBODY>
         </TABLE>
         <Paragraph/>
         <List>
            <ListIntro>If the next <Link href="/baanerp/td/glossary/glossary#000355" role="glossary">schedule issue date</Link>, according to the issue pattern for
			 material release, is Monday, 23 April 2001, the following applies:</ListIntro>
            <ListItem>All schedule lines whose planned delivery dates/planned
			 shipment dates fall within two weeks from the schedule issue date on (segment
			 003), receive the status <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="option">Firm</GUIRef>.
			 These requirements are the schedule requirements that fall between 23 April
			 2001 and 6 May 2001.</ListItem>
            <ListItem>All schedule lines whose planned delivery dates/planned
			 shipment dates fall within the next two weeks (segment 004), receive the status <GUIRef href="/baanerp/td/domains/pur.rtyp#planned" role="option">Planned</GUIRef>. These are the schedule requirements that fall
			 between 7 May 2001 and 20 May 2001.</ListItem>
            <ListItem>All schedule lines whose planned delivery dates/planned
			 shipment dates fall within the next eight weeks (segment 005) also receive the
			 status <GUIRef href="/baanerp/td/domains/pur.rtyp#planned" role="option">Planned</GUIRef>. These are the schedule requirements that fall
			 between 21 May 2001 and 15 July 2001. However, if schedule requirements fall
			 after the horizon of the segment set, after 15 July 2001, these schedule lines
			 also receive the status <GUIRef href="/baanerp/td/domains/pur.rtyp#planned" role="option">Planned</GUIRef>.</ListItem>
         </List>
         <Paragraph>If you take the same example, but the next schedule issue date
		  is Tuesday, 24 April 2001, requirement types are calculated from 30 April 2001
		  on. The reason for this is that the weekly <Link href="/baanerp/td/glossary/glossary#000021" role="glossary">segment time unit</Link> always takes Monday as a starting point. As a result, the schedule
		  lines that fall between 24 April 2001 and 29 April 2001 are excluded from the
		  regeneration process.</Paragraph>
      </ExampleSection>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>If schedule lines are moved in time through regeneration,
		  transactions are logged for the schedule line based on the value of the <GUIRef href="/baanerp/td/pur/tdpur3102m000#tdpur302.fprm" role="manual">Transaction Time Fence</GUIRef> field of the <GUIRef href="/baanerp/td/pur/tdpur3102m000" role="session">Purchase Contract Line Logistic Data (tdpur3102m000)</GUIRef> session and/or the <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Items - Purchase Business Partner (tdipu0110m000)</GUIRef> session.</Paragraph>
      </Note>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000346" role="manual">Purchase schedule release types</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000006" role="manual">Using segment sets</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000010" role="manual">Overview of purchase schedule handling</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000347" role="manual">Push schedules</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000067" role="manual">Purchase contracts</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="err.rep">
         <Header>
            <Title>Error Report</Title>
         </Header>
         <FuncDesc>If this check box is selected, if errors occur during
		  regeneration, an error report is generated.</FuncDesc>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="exec.cont.process">
         <Header>
            <Title>Regenerate</Title>
         </Header>
         <FuncDesc>
            <Link href="/baanerp/td/glossary/glossary#000341" role="glossary">Regenerates</Link> the purchase
		  schedule.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>