<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/td/onlinemanual/000349" xml:lang="en">
   <Header>
      <Title>Pull call-off schedules</Title>
      <Keyword type="header" order="d1e1292270">
         <Level1>Purchase schedule</Level1>
         <Level2>pull call-off schedules</Level2>
      </Keyword>
      <Keyword type="header" order="d1e1292275">
         <Level1>Pull call-off schedule</Level1>
      </Keyword>
      <Keyword type="header" order="d1e1292278">
         <Level1>Referenced schedule</Level1>
      </Keyword>
   </Header>
   <AimSection>
      <Paragraph>A <Link href="/baanerp/td/glossary/glossary#000335" role="glossary">pull schedule</Link> of the type call-off is a <Link href="/baanerp/td/glossary/glossary#000339" role="glossary">referenced schedule</Link> that is generated from <GUIRef href="/baanerp/ti/asc" role="module">Assembly Control</GUIRef> or from <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef> ( <Link href="/baanerp/wh/glossary/glossary#000400" role="glossary">Kanban</Link>, <Link href="/baanerp/wh/glossary/glossary#000424" role="glossary">time-phased order point</Link>).</Paragraph>
   </AimSection>
   <ProcedureSection>
      <ProcIntro>
         <Paragraph>The following steps are automatically performed based on the
		  parameters and triggers:</Paragraph>
      </ProcIntro>
      <Steps>
         <Step>
            <StepTitle>Generating a schedule header</StepTitle>
            <Paragraph>A purchase schedule (header) is generated in the <Link href="/baanerp/td/pur/tdpur3110m000" role="session">Purchase Schedules (tdpur3110m000)</Link> session. If the pull call-off schedule is preceded by a
			 pull forecast schedule, LN searches for the corresponding pull forecast schedule in the <GUIRef href="/baanerp/td/pur/tdpur3110m000" role="session">Purchase Schedules (tdpur3110m000)</GUIRef> session. Once found, LN creates a pull
			 call-off schedule with the same schedule number as the pull forecast schedule.
			 In this way, forecasting data and ordering data are separated. However, if in
			 the <GUIRef href="/baanerp/td/pur/tdpur3102m000" role="session">Purchase Contract Line Logistic Data (tdpur3102m000)</GUIRef> session the <Link href="/baanerp/td/sls/tdsls3102m000#tdsls302.shus" role="formfield">Use Shipping Schedule</Link> or <Link href="/baanerp/td/sls/tdsls3102m000#tdsls302.squs" role="formfield">Use Sequence Shipping Schedule</Link> check boxes are selected, no
			 forecasting data is generated. In this case, the generated pull call-off
			 schedule has no corresponding pull forecast schedule.</Paragraph>
            <Paragraph>You cannot manually update pull call-off schedules. You can
			 update these schedules only from the origin that generated the pull call-off
			 schedule.</Paragraph>
         </Step>
         <Step>
            <StepTitle>Generating schedule lines</StepTitle>
            <Paragraph>Schedule lines are generated in the <Link href="/baanerp/td/pur/tdpur3111m000" role="session">Purchase Schedule - Lines (tdpur3111m000)</Link> session.</Paragraph>
            <Paragraph>If the pull call-off schedule is triggered from <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>, the
			 schedule lines in the <GUIRef href="/baanerp/td/pur/tdpur3111m000" role="session">Purchase Schedule - Lines (tdpur3111m000)</GUIRef> session are generated from the <GUIRef href="/baanerp/wh/inh/whinh2200m000" role="session">Generate Orders (KANBAN) (whinh2200m000)</GUIRef>, or <GUIRef href="/baanerp/wh/inh/whinh2201m000" role="session">Generate Orders (TPOP) (whinh2201m000)</GUIRef> sessions.</Paragraph>
            <Paragraph>If the pull call-off schedule is triggered from <GUIRef href="/baanerp/ti/asc" role="module">Assembly Control</GUIRef> and the schedule release type is <GUIRef href="/baanerp/tc/domains/scrd#sequence" role="option">Sequence Shipping Schedule</GUIRef>, the number of lines for each schedule can be enormous.
			 Therefore, for each item, a schedule line per call-off is generated in the <GUIRef href="/baanerp/td/pur/tdpur3111m000" role="session">Purchase Schedule - Lines (tdpur3111m000)</GUIRef> session, but sequence details, such as VIN
			 number and line station, are stored in the <Link href="/baanerp/td/pur/tdpur3517m000" role="session">Sequence Shipping data (tdpur3517m000)</Link> session. To start this session, click <GUIRef href="/baanerp/td/pur/tdpur3111m000#tdpur3517m000" role="command">Sequence Shipping data</GUIRef> on the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu of the <GUIRef href="/baanerp/td/pur/tdpur3111m000" role="session">Purchase Schedule - Lines (tdpur3111m000)</GUIRef> session.</Paragraph>
            <Paragraph>For more information, refer to <Link href="/baanerp/td/onlinemanual/000357" role="manual">Sequence shipping schedules</Link>.</Paragraph>
         </Step>
         <Step>
            <StepTitle>Generating a purchase release</StepTitle>
            <Paragraph>A <Link href="/baanerp/td/glossary/glossary#000351" role="glossary">purchase release</Link> is generated with the <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="option">Scheduled</GUIRef> status in the <Link href="/baanerp/td/pur/tdpur3120m000" role="session">Purchase Releases (tdpur3120m000)</Link> session. With each generation of a schedule line, LN generates a release
			 line detail record in the <Link href="/baanerp/td/pur/tdpur3522m000" role="session">Purchase Release Line - Details (tdpur3522m000)</Link> session. This record has a one-to-one
			 relationship with the schedule line and has the <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="option">Scheduled</GUIRef> status.</Paragraph>
            <List>
               <ListIntro>If the schedule is a <Link href="/baanerp/td/glossary/glossary#000034" role="glossary">sequence shipping schedule</Link>, however, the following applies:</ListIntro>
               <ListItem>Only a purchase release header is created. No purchase
				release lines and purchase release line detail records are created. Items in a
				sequence shipping schedule are required for a combination of vehicle number
				(VIN), line station, and assembly kit. Therefore, a link exists between the
				release header in the <GUIRef href="/baanerp/td/pur/tdpur3120m000" role="session">Purchase Releases (tdpur3120m000)</GUIRef> session and the release lines in the <Link href="/baanerp/td/pur/tdpur3523m000" role="session">Purchase Release Lines - Sequence Shipping Data (tdpur3523m000)</Link> session.</ListItem>
               <ListItem>The <Link href="/baanerp/td/pur/tdpur3120m000#tdpur320.mesv" role="formfield">Generate Release per Vehicle</Link> or <Link href="/baanerp/td/pur/tdpur3120m000#tdpur320.grpi" role="formfield">Generate Release per Item</Link> check boxes in the <GUIRef href="/baanerp/td/pur/tdpur3120m000" role="session">Purchase Releases (tdpur3120m000)</GUIRef> session determine how the release is created: per
				vehicle, per item, or per business partner.</ListItem>
            </List>
            <Paragraph>For more information, refer to <Link href="/baanerp/td/onlinemanual/000350" role="manual">Purchase releases</Link>.</Paragraph>
         </Step>
         <Step>
            <StepTitle>Printing the purchase release</StepTitle>
            <Paragraph>The purchase release is printed in the <Link href="/baanerp/td/pur/tdpur3422m000" role="session">Print Purchase Releases (tdpur3422m000)</Link> session.</Paragraph>
            <Paragraph>If the <GUIRef href="/baanerp/td/pur/tdpur3102m000#tdpur302.wcom" role="field">Communication Channel</GUIRef> field is <GUIRef href="/baanerp/td/domains/wcom#edi" role="option">EDI</GUIRef> in the <GUIRef href="/baanerp/td/pur/tdpur3102m000" role="session">Purchase Contract Line Logistic Data (tdpur3102m000)</GUIRef> and <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Items - Purchase Business Partner (tdipu0110m000)</GUIRef> sessions and the <Link href="/baanerp/td/pur/tdpur3102m000#tdpur302.demr" role="formfield">Release EDI Message Directly</Link> check box is also selected in these sessions, you
			 need not print the purchase release in the <GUIRef href="/baanerp/td/pur/tdpur3422m000" role="session">Print Purchase Releases (tdpur3422m000)</GUIRef> session. LN automatically prints
			 the purchase release.</Paragraph>
         </Step>
         <Step>
            <StepTitle>Inserting receipt details</StepTitle>
            <Paragraph>Receipt details are inserted in the <Link href="/baanerp/td/pur/tdpur3115m200" role="session">Purchase Schedule - Receipts (tdpur3115m200)</Link> session.</Paragraph>
            <Paragraph>After receipts are confirmed in <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef>,
			 scheduled items can also be inspected. For more information, refer to <Link href="/baanerp/td/onlinemanual/000356" role="manual">To inspect scheduled items</Link>.</Paragraph>
         </Step>
         <Step>
            <StepTitle>Inserting cumulatives</StepTitle>
            <List>
               <ListIntro>
                  <Link href="/baanerp/td/glossary/glossary#CumulaCUMs_td" role="glossary">Cumulatives</Link> (CUMS) are inserted in these sessions:</ListIntro>
               <ListItem>
                  <Link href="/baanerp/td/pur/tdpur3131m000" role="session">Shipped Cumulatives (tdpur3131m000)</Link>
               </ListItem>
               <ListItem>
                  <Link href="/baanerp/td/pur/tdpur3132m000" role="session">Received Cumulatives (tdpur3132m000)</Link>
               </ListItem>
               <ListItem>
                  <Link href="/baanerp/td/pur/tdpur3130m000" role="session">Required Cumulatives (tdpur3130m000)</Link>
               </ListItem>
               <ListItem>
                  <Link href="/baanerp/td/pur/tdpur3133m000" role="session">Invoiced Cumulatives (tdpur3133m000)</Link>
               </ListItem>
            </List>
            <Paragraph>For pull call-off schedules, cumulatives are filled for
			 information purposes only. Pull call-off schedules do not use cumulatives. Pull
			 forecast schedules, however, which usually have the same schedule number as a
			 particular pull call-off schedule, use the <Link href="/baanerp/td/glossary/glossary#000004" role="glossary">required cumulatives</Link> from the pull call-off schedule to calculate <Link href="/baanerp/td/glossary/glossary#000003" role="glossary">fab authorizations</Link> and <Link href="/baanerp/td/glossary/glossary#000002" role="glossary">raw authorizations</Link>.</Paragraph>
            <List>
               <ListIntro>For more information, refer to:</ListIntro>
               <ListItem>
                  <Link href="/baanerp/td/onlinemanual/000353" role="manual">Purchase schedule cumulatives</Link>
               </ListItem>
               <ListItem> 
                  <Link href="/baanerp/td/onlinemanual/000001" role="manual">Authorizations</Link>
               </ListItem>
            </List>
         </Step>
         <Step>
            <StepTitle>Resetting the cumulatives and authorizations</StepTitle>
            <Paragraph>The cumulatives and authorizations are reset in the <Link href="/baanerp/td/pur/tdpur3230m000" role="session">Reset Cumulatives (tdpur3230m000)</Link> session.</Paragraph>
            <Paragraph>For more information, refer to <Link href="/baanerp/td/onlinemanual/000355" role="manual">To reset purchase schedule cumulatives</Link> and <Link href="/baanerp/td/onlinemanual/000342" role="manual">To reset authorizations</Link>.</Paragraph>
         </Step>
         <Step>
            <StepTitle>Updating history and turnover data</StepTitle>
            <Paragraph>Purchase schedule history and turnover data is updated in
			 the <Link href="/baanerp/td/pur/tdpur3223m000" role="session">Process Delivered Purchase Schedules (tdpur3223m000)</Link> session. As a result, the status of the
			 schedule line is changed to <GUIRef href="/baanerp/td/domains/pur.stat#processed" role="option">Processed</GUIRef>.</Paragraph>
            <Paragraph>In the <GUIRef href="/baanerp/td/pur/tdpur3224m000" role="session">Delete Purchase Schedules (tdpur3224m000)</GUIRef> session, you can delete the processed
			 purchase schedule.</Paragraph>
         </Step>
      </Steps>
   </ProcedureSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000357" role="manual">Sequence shipping schedules</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000310" role="manual">Configured items on purchase schedules</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000350" role="manual">Purchase releases</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000356" role="manual">To inspect scheduled items</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000353" role="manual">Purchase schedule cumulatives</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000001" role="manual">Authorizations</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000355" role="manual">To reset purchase schedule cumulatives</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000342" role="manual">To reset authorizations</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000348" role="manual">Pull forecast schedules</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000010" role="manual">Overview of purchase schedule handling</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>