<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/td/onlinemanual/000351" xml:lang="en">
   <Header>
      <Title>To cluster purchase schedule lines</Title>
      <Keyword type="header" order="d1e1292587">
         <Level1>Purchase schedule line</Level1>
         <Level2>clustering</Level2>
      </Keyword>
      <Keyword type="header" order="d1e1292592">
         <Level1>Clustering</Level1>
      </Keyword>
   </Header>
   <GeneralSection>
      <List>
         <ListIntro>
            <Link href="/baanerp/td/glossary/glossary#000343" role="glossary">Clustering</Link> serves to:</ListIntro>
         <ListItem>Reduce the number of schedule lines that must be processed.
		  Especially those lines for which no accurate planning is required yet, can be
		  grouped.</ListItem>
         <ListItem>Provide the supplier a clear view of the schedule lines without
		  having to bother about schedule origin.</ListItem>
      </List>
      <GeneralSection>
         <SectionTitle>Conditions for clustering</SectionTitle>
         <Paragraph>For one purchase schedule, several schedule lines can be
		  generated with the same characteristics (common buy-from business partner,
		  ship-from business partner, release type, shipment based schedule/ delivery
		  based schedule, communication method), which differ only in their origin. These
		  schedule lines, which are stored under one <Link href="/baanerp/td/glossary/glossary#000351" role="glossary">purchase release</Link>, can have different planned receipt dates (or planned shipment
		  dates) that fall in one specific period. The schedule lines that fall in that
		  specific period, determined by the applicable <Link href="/baanerp/td/glossary/glossary#000094" role="glossary">segment</Link>, which is derived from the schedule's applicable <Link href="/baanerp/td/glossary/glossary#000093" role="glossary">segment set</Link>, can be clustered and put together in the <GUIRef href="/baanerp/td/pur/tdpur3522m000" role="session">Purchase Release Line - Details (tdpur3522m000)</GUIRef> session.</Paragraph>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListIntro>In the <GUIRef href="/baanerp/td/pur/tdpur3522m000" role="session">Purchase Release Line - Details (tdpur3522m000)</GUIRef> session, schedule lines are only
				clustered in the same purchase release line detail if the following fields on
				the schedule lines are the same:</ListIntro>
               <ListItem>
                  <GUIRef href="/baanerp/td/pur/tdpur3111m000#tdpur311.cuqp" role="field" Update="No">Purchase Unit</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="" role="manual" Update="No">Purchase Price Unit</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/pur/tdpur3111m000#f.price" role="manual">Price</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/pur/tdpur3111m000#tdpur311.cwar" role="field">Warehouse</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/pur/tdpur3111m000#tdpur311.cadr" role="field">Address</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/pur/tdpur3111m000#tcibd420.olid" role="manual">Option List ID</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/pur/tdpur3111m000#tdpur311.exmt" role="manual">Exempt</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/pur/tdpur3111m000#tdpur311.ccty" role="manual">Tax Country</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/pur/tdpur3111m000#tdpur311.cvat" role="manual">Tax Code</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/pur/tdpur3111m000#tax.id" role="manual">Own Tax Number</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/pur/tdpur3111m000#tdpur311.bptc" role="manual">BP Tax Country</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/pur/tdpur3111m000#bp.tax.id" role="manual">BP Tax Number</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/pur/tdpur3111m000#tdpur311.rcod" role="manual">Exempt Reason</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/pur/tdpur3111m000#tdpur311.ceno" role="manual">Exempt Certificate</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/pur/tdpur3111m000#tdpur311.mpnr" role="manual">Preferred Manufacturer Part Number</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/pur/tdpur3111m000#tdpur311.cmnf" role="manual">Manufacturer</GUIRef>
               </ListItem>
               <ListItem>The contents of the <Link href="/baanerp/td/glossary/glossary#000377" role="glossary" Update="No">MPN sets</Link> that are linked to the purchase
				schedule lines.</ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/pur/tdpur3111m000#tdpur311.revi" role="manual">Item Revision</GUIRef>
               </ListItem>
            </List>
            <List>
               <ListIntro>The following fields, which are derived from the <GUIRef href="/baanerp/td/pur/tdpur3111m000#tdpur311.cuqp" role="field">Schedule Quantity</GUIRef>, but are defined in <GUIRef href="/baanerp/tc" role="package">Common</GUIRef>, must also match
				to cluster several schedule lines into one release line detail:</ListIntro>
               <ListItem>
                  <GUIRef href="" role="manual">Conversion Factor Purchase to Inventory Unit</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="" role="manual">Conversion Factor Price to Inventory Unit</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/pur/tdpur3522m000#tdpur322.leng" role="manual">Length</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/pur/tdpur3522m000#tdpur322.widt" role="manual">Width</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/pur/tdpur3522m000#tdpur322.thic" role="manual">Height</GUIRef>
               </ListItem>
            </List>
         </Note>
         <Paragraph>The way in which <Emphasis>tax</Emphasis> fields are used in a
		  purchase release, depends on the value of the <Link href="/baanerp/td/pur/tdpur0100m300#tdpur000.tprl" role="formfield">Tax on Purchase Release Line level</Link> field in the <GUIRef href="/baanerp/td/pur/tdpur0100m300" role="session">Purchase Contract Parameters (tdpur0100m300)</GUIRef> session.</Paragraph>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>Use of segment sets for clustering</SectionTitle>
         <Paragraph>To cluster schedule lines, first the next <Link href="/baanerp/td/glossary/glossary#000355" role="glossary">schedule issue date</Link> must be determined. This date is derived from the schedule's
		  applicable issue pattern, which is defaulted from the <GUIRef href="/baanerp/td/pur/tdpur3102m000" role="session">Purchase Contract Line Logistic Data (tdpur3102m000)</GUIRef> session or the <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Items - Purchase Business Partner (tdipu0110m000)</GUIRef> session.</Paragraph>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListItem>You can define patterns in the <Link href="/baanerp/tc/ccp/tcccp0690m000" role="session">Patterns (tcccp0690m000)</Link> session.</ListItem>
               <ListItem>On the schedule issue date, schedule lines are always
				clustered from 00:00 hours on and not from the time that is indicated by the
				issue date.</ListItem>
            </List>
         </Note>
         <ExampleSection>
            <SectionTitle>Example</SectionTitle>
            <List>
               <ListItem>Release type: material release.</ListItem>
               <ListItem>Next schedule issue date: 26/07/99 10:00 hrs.</ListItem>
            </List>
            <Paragraph>
               <Emphasis>Segments in the segment set for material
			 release:</Emphasis>
            </Paragraph>
            <TABLE border="1" width="90%" space-and-orientation="indented-custom"
                   borderstyle="default">
               <TBODY noTR="4">
                  <TR no="1" isLast="false">
                     <TH width="30%" rowspan="1" colspan="1">Segment</TH>
                     <TH width="40%" rowspan="1" colspan="1">Segment time unit</TH>
                     <TH width="30%" rowspan="1" colspan="1">Segment length</TH>
                  </TR>
                  <TR no="2" isLast="false">
                     <TD width="30%" rowspan="1" colspan="1">1</TD>
                     <TD width="40%" rowspan="1" colspan="1">Week</TD>
                     <TD width="30%" rowspan="1" colspan="1">1</TD>
                  </TR>
                  <TR no="3" isLast="false">
                     <TD width="30%" rowspan="1" colspan="1">2</TD>
                     <TD width="40%" rowspan="1" colspan="1">Four Weeks</TD>
                     <TD width="30%" rowspan="1" colspan="1">1</TD>
                  </TR>
                  <TR no="4" isLast="true">
                     <TD width="30%" rowspan="1" colspan="1">3</TD>
                     <TD width="40%" rowspan="1" colspan="1">Four Weeks</TD>
                     <TD width="30%" rowspan="1" colspan="1">1</TD>
                  </TR>
               </TBODY>
            </TABLE>
            <Paragraph>
               <Emphasis>Schedule (SCH001) requirements in schedule
			 lines:</Emphasis>
            </Paragraph>
            <TABLE border="1" width="100%" space-and-orientation="indented-custom"
                   borderstyle="default">
               <TBODY noTR="8">
                  <TR no="1" isLast="false">
                     <TH width="25%" rowspan="1" colspan="1">Position
					 number</TH>
                     <TH width="25%" rowspan="1" colspan="1">Origin</TH>
                     <TH width="25%" rowspan="1" colspan="1">Planned receipt
					 date</TH>
                     <TH width="25%" rowspan="1" colspan="1">Quantity</TH>
                  </TR>
                  <TR no="2" isLast="false">
                     <TD width="20%" rowspan="1" colspan="1">10</TD>
                     <TD width="15%" rowspan="1" colspan="1">EP</TD>
                     <TD width="25%" rowspan="1" colspan="1">23/07/99</TD>
                     <TD width="10%" rowspan="1" colspan="1">15</TD>
                  </TR>
                  <TR no="3" isLast="false">
                     <TD width="20%" rowspan="1" colspan="1">20</TD>
                     <TD width="15%" rowspan="1" colspan="1">EP</TD>
                     <TD width="25%" rowspan="1" colspan="1">26/07/99</TD>
                     <TD width="10%" rowspan="1" colspan="1">10</TD>
                  </TR>
                  <TR no="4" isLast="false">
                     <TD width="20%" rowspan="1" colspan="1">30</TD>
                     <TD width="15%" rowspan="1" colspan="1">Manual</TD>
                     <TD width="25%" rowspan="1" colspan="1">28/07/99</TD>
                     <TD width="10%" rowspan="1" colspan="1">10</TD>
                  </TR>
                  <TR no="5" isLast="false">
                     <TD width="20%" rowspan="1" colspan="1">40</TD>
                     <TD width="15%" rowspan="1" colspan="1">EP</TD>
                     <TD width="25%" rowspan="1" colspan="1">03/08/99</TD>
                     <TD width="10%" rowspan="1" colspan="1">15</TD>
                  </TR>
                  <TR no="6" isLast="false">
                     <TD width="20%" rowspan="1" colspan="1">50</TD>
                     <TD width="15%" rowspan="1" colspan="1">Manual</TD>
                     <TD width="25%" rowspan="1" colspan="1">10/08/99</TD>
                     <TD width="10%" rowspan="1" colspan="1">15</TD>
                  </TR>
                  <TR no="7" isLast="false">
                     <TD width="20%" rowspan="1" colspan="1">60</TD>
                     <TD width="15%" rowspan="1" colspan="1">EP</TD>
                     <TD width="25%" rowspan="1" colspan="1">24/08/99</TD>
                     <TD width="10%" rowspan="1" colspan="1">20</TD>
                  </TR>
                  <TR no="8" isLast="true">
                     <TD width="20%" rowspan="1" colspan="1">70</TD>
                     <TD width="15%" rowspan="1" colspan="1">EP</TD>
                     <TD width="25%" rowspan="1" colspan="1">31/08/99</TD>
                     <TD width="10%" rowspan="1" colspan="1">20</TD>
                  </TR>
               </TBODY>
            </TABLE>
            <Paragraph>
               <Emphasis>Creation of clustered
			 lines:</Emphasis>
            </Paragraph>
            <TABLE border="1" space-and-orientation="portrait-max" width="100%"
                   borderstyle="default">
               <TBODY noTR="4">
                  <TR no="1" isLast="false">
                     <TH width="14%" rowspan="1" colspan="1">Release number</TH>
                     <TH width="14%" rowspan="1" colspan="1">Release revision</TH>
                     <TH width="14%" rowspan="1" colspan="1">Schedule number</TH>
                     <TH width="14%" rowspan="1" colspan="1">Release position</TH>
                     <TH width="15%" rowspan="1" colspan="1">Start date</TH>
                     <TH width="15%" rowspan="1" colspan="1">End date</TH>
                     <TH width="14%" rowspan="1" colspan="1">Quantity</TH>
                  </TR>
                  <TR no="2" isLast="false">
                     <TD rowspan="1" colspan="1">REL001</TD>
                     <TD rowspan="1" colspan="1">0</TD>
                     <TD rowspan="1" colspan="1">SCH001</TD>
                     <TD rowspan="1" colspan="1">1</TD>
                     <TD rowspan="1" colspan="1">26/07/99</TD>
                     <TD rowspan="1" colspan="1">01/08/99</TD>
                     <TD rowspan="1" colspan="1">20</TD>
                  </TR>
                  <TR no="3" isLast="false">
                     <TD rowspan="1" colspan="1">REL001</TD>
                     <TD rowspan="1" colspan="1">0</TD>
                     <TD rowspan="1" colspan="1">SCH001</TD>
                     <TD rowspan="1" colspan="1">2</TD>
                     <TD rowspan="1" colspan="1">02/08/99</TD>
                     <TD rowspan="1" colspan="1">29/08/99</TD>
                     <TD rowspan="1" colspan="1">50</TD>
                  </TR>
                  <TR no="4" isLast="true">
                     <TD rowspan="1" colspan="1">REL001</TD>
                     <TD rowspan="1" colspan="1">0</TD>
                     <TD rowspan="1" colspan="1">SCH001</TD>
                     <TD rowspan="1" colspan="1">3</TD>
                     <TD rowspan="1" colspan="1">30/08/99</TD>
                     <TD rowspan="1" colspan="1">26/09/99</TD>
                     <TD rowspan="1" colspan="1">20</TD>
                  </TR>
               </TBODY>
            </TABLE>
            <Paragraph>All scheduline lines that fall within one week, calculated
			 from the next schedule issue date on, are clustered in one release line detail
			 (segment 1). After this period, all schedule lines that fall within the next
			 four weeks are clustered in another release line detail (segment 2). Finally,
			 the schedule lines that fall within the next four weeks are clustered in the
			 last release line detail.</Paragraph>
         </ExampleSection>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListItem>If schedule lines exist with planned receipt/shipment dates
				that fall before the next schedule issue date, these lines are inserted as <Link href="/baanerp/td/glossary/glossary#000000000000014" role="glossary">immediate requirements</Link> in the <GUIRef href="/baanerp/td/pur/tdpur3522m000" role="session">Purchase Release Line - Details (tdpur3522m000)</GUIRef> session for receipt based schedules.</ListItem>
               <ListItem>If a period is undefined between two segments, LN automatically adds
				another segment that fills this time gap, so the schedule lines that fall in
				this time gap are also included in the clustering process. All the schedule
				lines that fall within the time period of that newly generated segmen,t are
				clustered into one release line detail. For more information, refer to <Link href="/baanerp/td/onlinemanual/000006" role="manual">Using segment sets</Link>.</ListItem>
               <ListItem>If the first segment time unit of the first segment in a
				segment set is set to <GUIRef href="/baanerp/td/domains/ipu.time#week" role="option">Week</GUIRef>, <GUIRef href="/baanerp/td/domains/ipu.time#four.week" role="option">Four Weeks</GUIRef>, or <GUIRef href="/baanerp/td/domains/ipu.time#month" role="option">Month</GUIRef>,
				which are all segment time units that have Monday as a starting point for their
				activities, and if the calculated schedule issue date does not fall on a
				Monday, some days can be excluded from the clustering process. For more information, refer to <Link href="/baanerp/td/onlinemanual/000006" role="manual">Using segment sets</Link>.</ListItem>
            </List>
         </Note>
      </GeneralSection>
   </GeneralSection>
   <GeneralSection>
      <GeneralSection>
         <SectionTitle>Overall process for clustering schedule
		  lines</SectionTitle>
         <ProcedureList>
            <ListItem>To cluster schedule lines, you can run the <GUIRef href="/baanerp/td/pur/tdpur3222m000" role="session">Generate Release Lines (tdpur3222m000)</GUIRef> session. The clustered schedule lines are stored
			 in the <GUIRef href="/baanerp/td/pur/tdpur3522m000" role="session">Purchase Release Line - Details (tdpur3522m000)</GUIRef> session with the status <GUIRef href="/baanerp/tc/domains/edi.stat#preview" role="option">Preview</GUIRef>. The linked release line in the <GUIRef href="/baanerp/td/pur/tdpur3121m000" role="session">Purchase Release - Lines (tdpur3121m000)</GUIRef> session, also has the status <GUIRef href="/baanerp/tc/domains/edi.stat#preview" role="option">Preview</GUIRef>.</ListItem>
            <ListItem>If you agree to the release line detail with the status <GUIRef href="/baanerp/tc/domains/edi.stat#preview" role="option">Preview</GUIRef> and you do not want to change the release line
			 detail, you can approve the line (detail) in the <GUIRef href="/baanerp/td/pur/tdpur3222m100" role="session">Approve Release Lines (tdpur3222m100)</GUIRef> session. The clustered lines in the <GUIRef href="/baanerp/td/pur/tdpur3522m000" role="session">Purchase Release Line - Details (tdpur3522m000)</GUIRef> session and the release line in
			 the <GUIRef href="/baanerp/td/pur/tdpur3121m000" role="session">Purchase Release - Lines (tdpur3121m000)</GUIRef> session receive the status <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="option">Scheduled</GUIRef>.</ListItem>
            <ListItem>As soon as the release line with the status <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="option">Scheduled</GUIRef> is printed in the <GUIRef href="/baanerp/td/pur/tdpur3422m000" role="session">Print Purchase Releases (tdpur3422m000)</GUIRef> session with the <Link href="/baanerp/td/pur/tdpur3422m000#final.report" role="formfield">Final Report</Link> check box selected, or when EDI messages are automatically
			 generated and sent, the clustered lines in the <GUIRef href="/baanerp/td/pur/tdpur3522m000" role="session">Purchase Release Line - Details (tdpur3522m000)</GUIRef> session and the release line in the <GUIRef href="/baanerp/td/pur/tdpur3121m000" role="session">Purchase Release - Lines (tdpur3121m000)</GUIRef> session receive the status <GUIRef href="/baanerp/tc/domains/edi.stat#send" role="option">Sent</GUIRef>.</ListItem>
         </ProcedureList>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>To update clustered schedule lines</SectionTitle>
         <ProcedureList>
            <ListIntro>If you check the clustered schedule lines with the status <GUIRef href="/baanerp/tc/domains/edi.stat#preview" role="option">Preview</GUIRef> in the <GUIRef href="/baanerp/td/pur/tdpur3522m000" role="session">Purchase Release Line - Details (tdpur3522m000)</GUIRef> session, and you do not want these
			 lines to be approved in this format, or if you check the clustered schedule
			 lines with the status <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="option">Scheduled</GUIRef> and you do not want the lines to be sent to the
			 supplier in this format, you can update the lines. To update the release line
			 (detail) of a non-referenced schedule, take the following steps:</ListIntro>
            <ListItem>In the <GUIRef href="/baanerp/td/pur/tdpur3522m000" role="session">Purchase Release Line - Details (tdpur3522m000)</GUIRef> session, select a record.</ListItem>
            <ListItem>On the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu of the <GUIRef href="/baanerp/td/pur/tdpur3522m000" role="session">Purchase Release Line - Details (tdpur3522m000)</GUIRef> session, click <GUIRef href="/baanerp/td/pur/tdpur3522m000#tdpur3111m000" role="command">Purchase Schedule - Lines</GUIRef>, which will start the <GUIRef href="/baanerp/td/pur/tdpur3111m000" role="session">Purchase Schedule - Lines (tdpur3111m000)</GUIRef> session.</ListItem>
            <ListItem>Double-click the schedule line that you want to update and
			 make the change.</ListItem>
            <ListItem>On the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu of the <GUIRef href="/baanerp/td/pur/tdpur3522m000" role="session">Purchase Release Line - Details (tdpur3522m000)</GUIRef> session, click <GUIRef href="/baanerp/td/pur/tdpur3522m000#update.release" role="command">Update Release</GUIRef>. The release is now updated with
			 the changes you made on the schedule line(s).</ListItem>
         </ProcedureList>
      </GeneralSection>
      <GeneralSection>
         <SectionTitle>To receive clustered schedule lines</SectionTitle>
         <Paragraph>If a supplier sends the goods based on the clustered lines,
		  and goods are received in <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef> against a <Link href="/baanerp/td/glossary/glossary#000342" role="glossary">blanket warehouse order</Link>, the received quantity is distributed over the <Link href="/baanerp/td/glossary/glossary#000334" role="glossary">push schedule</Link> lines, based on the following rule:</Paragraph>
         <Paragraph>Received quantity is booked in the <GUIRef href="/baanerp/td/pur/tdpur3111m000#tdpur311.qidl" role="field">Received Quantity</GUIRef> field of the <GUIRef href="/baanerp/td/pur/tdpur3111m000" role="session">Purchase Schedule - Lines (tdpur3111m000)</GUIRef> session for the purchase schedule line that has
		  the oldest unfulfilled requirement of the type <Link href="/baanerp/td/glossary/glossary#000000000000014" role="glossary">immediate</Link> or <Link href="/baanerp/td/glossary/glossary#000000000000016" role="glossary">firm</Link>. For more information, refer to <Link href="/baanerp/wh/onlinemanual/000332" role="manual">Blanket warehousing orders</Link>.</Paragraph>
         <List>
            <ListIntro>A purchase schedule line is unfulfilled if:</ListIntro>
            <ListItem>The delivered quantity is less than the ordered quantity.</ListItem>
            <ListItem>The ordered quantity is equal to the delivered quantity, but
			 the sum of the approved quantity and the rejected quantity is less than the
			 delivered quantity.</ListItem>
         </List>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListItem>No receipts can be made on schedule lines with the <Link href="/baanerp/td/glossary/glossary#000000000000017" role="glossary">planned</Link> requirement type.</ListItem>
               <ListItem>If no unfulfilled purchase schedule lines can be found,
				goods cannot be received on a purchase schedule.</ListItem>
            </List>
         </Note>
      </GeneralSection>
   </GeneralSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000006" role="manual">Using segment sets</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/wh/onlinemanual/000332" role="manual">Blanket warehousing orders</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000346" role="manual">Purchase schedule release types</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000350" role="manual">Purchase releases</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000347" role="manual">Push schedules</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000348" role="manual">Pull forecast schedules</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000353" role="manual">Purchase schedule cumulatives</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>