<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/cp/onlinemanual/000078" xml:lang="en">
   <Header>
      <Title>Purchase schedules and Enterprise Planning</Title>
      <Keyword type="header" order="d1e164604">
         <Level1>Purchase schedules</Level1>
      </Keyword>
      <Keyword type="header" order="d1e164607">
         <Level1>JIT items</Level1>
      </Keyword>
   </Header>
   <GeneralSection>
      <Paragraph>In ERP Enterprise, the purchase of <Link href="/baanerp/tc/glossary/glossary#000073" role="glossary">JIT items</Link> is handled through <Link href="/baanerp/td/glossary/glossary#000000000000011" role="glossary">purchase schedules</Link>. This
		topic describes how <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> handles the purchase planning of these items.</Paragraph>
      <List>
         <ListIntro>During an order simulation in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>,
		  purchase volumes are usually planned as <Link href="/baanerp/cp/glossary/glossary#000048" role="glossary">planned purchase orders</Link>.
		  However, ERP Enterprise can also
		  transfer purchase orders to a purchase schedule in the <GUIRef href="/baanerp/td/pur" role="module">Purchase Control</GUIRef> module
		  of <GUIRef href="/baanerp/procurement" role="package">Procurement</GUIRef>. ERP Enterprise does so, if:</ListIntro>
         <ListItem>The order simulation is
		  run for the <Link href="/baanerp/cp/glossary/glossary#000093" role="glossary">actual scenario</Link>.</ListItem>
         <ListItem>You selected the <GUIRef href="/baanerp/tc/ibd/tcibd0101s000#tcibd001.psiu" role="manual">Purchase Schedule in Use</GUIRef> check box in the <GUIRef href="/baanerp/tc/ibd/tcibd0101s000" role="session">Item - General (tcibd0101s000)</GUIRef> session for the item involved.</ListItem>
      </List>
   </GeneralSection>
   <GeneralSection>
      <Paragraph>If you run the <GUIRef href="/baanerp/cp/rrp/cprrp1210m000" role="session">Generate Order Planning (cprrp1210m000)</GUIRef> session, ERP Enterprise determines whether a
		shortage exists for a particular item for the simulated time period, and takes
		into account the demand, the firm supply, and for what exact moments possible
		shortages exist. If a shortage occurs, ERP Enterprise generates
		supply.</Paragraph>
      <Paragraph>If ERP Enterprise uses a <Link href="/baanerp/td/glossary/glossary#000000000000011" role="glossary">purchase schedule</Link> to plan supply for an
		item, ERP Enterprise does not
		generate <Link href="/baanerp/cp/glossary/glossary#000048" role="glossary">planned purchase orders</Link>, but stores a purchase volume in
		an internal memory. When ERP Enterprise generated all the required purchase volumes
		for the item, ERP Enterprise groups
		the ordered purchase volumes in between two delivery moments in one
		purchase-schedule line, and lot sizes the purchase volumes according to the
		lot-size rules.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>General constraints</SectionTitle>
      <Paragraph>During an order-based planning run, ERP Enterprise checks if shortages
		exist for the purchase schedule items. If so, ERP Enterprise records the supply of
		these items in <Link href="/baanerp/td/glossary/glossary#000100" role="glossary">schedule lines</Link> that it set on the delivery moments that
		you generated in the <GUIRef href="/baanerp/td/ipu/tdipu0225m000" role="session">Generate Planned Delivery Moments (tdipu0225m000)</GUIRef> session for the supplier involved in
		the purchase schedule. If the purchase schedule is shipment-based ERP Enterprise lists these planned
		delivery moments in the <GUIRef href="/baanerp/td/ipu/tdipu0125m000" role="session">Planned Delivery Moments (Shipment Based) (tdipu0125m000)</GUIRef> session; if the purchase
		schedule is delivery based, ERP Enterprise lists the planned delivery moments in the <GUIRef href="/baanerp/td/ipu/tdipu0126m000" role="session">Planned Delivery Moments (Delivery Based) (tdipu0126m000)</GUIRef> session.</Paragraph>
      <Paragraph>In the order-based planning process, ERP Enterprise carries out a
		rescheduling step to match supply with demand. The way in which this
		rescheduling mechanism works for purchase scheduled items differs slightly from
		the way ERP Enterprise applies this
		mechanism for items that are not planned through purchase schedules.</Paragraph>
      <List>
         <ListIntro>The following constraints apply for purchase schedule items:</ListIntro>
         <ListItem>ERP Enterprise always
		  disables the <GUIRef href="/baanerp/cp/rpd/cprpd0100m000#cprpd000.rsio" role="manual">Only Reschedule Total Order Quantity</GUIRef> check box in the <GUIRef href="/baanerp/cp/rpd/cprpd0100m000" role="session">Planning Parameters (cprpd0100m000)</GUIRef> session for purchase schedule items.</ListItem>
         <ListItem>Purchase schedule lines always behave as if the <GUIRef href="/baanerp/cp/rpd/cprpd0100m000#cprpd000.fipl" role="manual">Planned Order before Firm/Actual</GUIRef> check box in the <GUIRef href="/baanerp/cp/rpd/cprpd0100m000" role="session">Planning Parameters (cprpd0100m000)</GUIRef> session where selected.</ListItem>
         <ListItem>ERP Enterprise can
		  only reschedule schedule line quantities to delivery moments.</ListItem>
      </List>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Horizons and Frozen Zones</SectionTitle>
      <Paragraph>ERP Enterprise uses a
		specific horizon and a frozen zone to plan purchase schedule items. The horizon
		end date of a purchase schedule is the date until which ERP Enterprise displays delivery
		moments in the <GUIRef href="/baanerp/td/ipu/tdipu0125m000" role="session">Planned Delivery Moments (Shipment Based) (tdipu0125m000)</GUIRef> session or the <GUIRef href="/baanerp/td/ipu/tdipu0126m000" role="session">Planned Delivery Moments (Delivery Based) (tdipu0126m000)</GUIRef> session.</Paragraph>
      <Paragraph>ERP Enterprise groups
		all the requirements between two delivery moments into one purchase schedule. ERP Enterprise groups purchase
		volumes that fall between the last defined delivery moment and the horizon end
		date to a <Link href="/baanerp/td/glossary/glossary#000100" role="glossary">schedule line</Link> for the last delivery moment.</Paragraph>
      <Paragraph>Beyond the horizon end date, where no predefined delivery
		moments exist, ERP Enterprise inserts
		required purchase volumes into the purchase schedule, but does not lotsize, nor
		group the purchase volumes to a delivery moment.</Paragraph>
      <Paragraph>After the contract related to the purchase schedule expires, ERP Enterprise translates the
		required purchase volumes to <Link href="/baanerp/cp/glossary/glossary#000048" role="glossary">planned purchase orders</Link> for an empty supplier and
		generates a <Link href="/baanerp/cp/glossary/glossary#000371" role="glossary">signal</Link> to inform the planner.</Paragraph>
      <Paragraph>Beyond the horizon end date, where no predefined delivery
		moments exist, ERP Enterprise translates required purchase volumes into planned purchase orders for an empty
		supplier and generates a <Link href="/baanerp/cp/glossary/glossary#000371" role="glossary">exception message</Link> to warn the planner.</Paragraph>
      <Paragraph>For plan items, ERP Enterprise uses a time fence as a period during which ERP Enterprise cannot modify the
		supply plan and the planned orders. However, for the firm part of purchase
		schedule items, ERP Enterprise uses
		a:</Paragraph>
      <List>
         <ListItem>Frozen Period: the time period during which <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> cannot
		  generate or update purchase schedule lines.</ListItem>
         <ListItem>Frozen Zone - : the time period calculated from the current
		  date and during which ERP Enterprise takes into account a lowerbound, which means that the schedule line quantities
		  can increase, but not decrease. Enterprise Planning can create new schedule
		  lines for new demand, but cannot delete existing schedule lines in this period.</ListItem>
         <ListItem>Frozen Zone + : the time period calculated from the current
		  date and during which ERP Enterprise takes into account an upperbound, which means that the schedule line quantities
		  can decrease, but not increase. Enterprise Planning cannot generate new
		  schedule lines in this period, but the quantities of the existing lines can be
		  lowered.</ListItem>
      </List>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Purchase schedule items and time fences</SectionTitle>
      <Paragraph>In addition to the <Link href="/baanerp/td/glossary/glossary#000028" role="glossary">frozen zone-</Link>, the <Link href="/baanerp/td/glossary/glossary#000027" role="glossary">frozen zone+</Link>, and the <Link href="/baanerp/td/glossary/glossary#000346" role="glossary">frozen period</Link>, you can set a <Link href="/baanerp/cp/glossary/glossary#000063" role="glossary">time fence</Link> in the <GUIRef href="/baanerp/cp/rpd/cprpd1100m000" role="session">Items - Planning (cprpd1100m000)</GUIRef> session for items for which the <GUIRef href="/baanerp/tc/ibd/tcibd0101s000#tcibd001.psiu" role="manual">Purchase Schedule in Use</GUIRef> check box in the <GUIRef href="/baanerp/tc/ibd/tcibd0501m000" role="session">Items - General (tcibd0501m000)</GUIRef> session is selected.</Paragraph>
      <Paragraph>Although the use of a time fence for purchase schedule items
		leads to complex and unclear results, the reason for this functionality is that
		you can have multiple sources for a plan item. You can have several clusters
		for an item - each with a different cluster. Possibly, only one of these items
		has a purchase schedule, while the other items are distributed or manufactured
		items. Therefore, you can enter a time fence for plan items with a purchase
		schedule. However, if you do enter a time fence, ERP Enterprise displays a warning.</Paragraph>
   </GeneralSection>
   <Note>
      <SectionTitle>Note</SectionTitle>
      <Paragraph>You cannot use purchase schedules for <Link href="/baanerp/ti/glossary/glossary#000098" role="glossary">project items</Link>, or for distribution items (items with the
		cluster segment filled).</Paragraph>
   </Note>
   <Note>
      <SectionTitle>Note</SectionTitle>
      <Paragraph>You cannot set capacity constraints in Enterprise Planning for
		purchase schedule items, because purchase schedules already contain capacity.
		Therefore, the capacity constraints fields in the <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Items - Purchase Business Partner (tdipu0110m000)</GUIRef> session are disabled for purchase
		schedule items.</Paragraph>
   </Note>
   <Note>
      <SectionTitle>Note</SectionTitle>
      <Paragraph>You can use a <Link href="/baanerp/cp/glossary/glossary#000104" role="glossary">sourcing strategy</Link> and/or a <Link href="/baanerp/cp/glossary/glossary#000105" role="glossary">supply strategy</Link> for purchase schedule items. If you use a
		supplying strategy, supply can entirely or partly be planned based on purchase
		schedules.</Paragraph>
   </Note>
   <ExampleSection>
      <SectionTitle>Example frozen zone and horizon</SectionTitle>
      <Figure space-and-orientation="indented-estimated">
         <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="684" width="576"
                   SRC="../images/tr_graph_000078a.gif"
                   alt="[...]"/>
         <FigLegend>
            <LegendEntry>
               <Symbol>X</Symbol>
               <Desc>delivery moment</Desc>
            </LegendEntry>
            <LegendEntry>
               <Symbol>S</Symbol>
               <Desc>schedule line</Desc>
            </LegendEntry>
            <LegendEntry>
               <Symbol>R</Symbol>
               <Desc>Requirement</Desc>
            </LegendEntry>
         </FigLegend>
      </Figure>
      <Paragraph>In Figure 1-1, the time span of the purchase schedule is divided
		in four periods. The figures show how both <GUIRef href="/baanerp/procurement" role="package">Procurement</GUIRef>, and <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> model
		the existing situation, and how ERP Enterprise handles requirements that occur in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>:</Paragraph>
      <List>
         <ListItem>Period 1 is the <Link href="/baanerp/td/glossary/glossary#000346" role="glossary">frozen period</Link>. ERP Enterprise cannot touch the volumes recorded in the
		  schedule lines in this period. <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> cannot plan supply in this period.
		  To avoid supply from being originated by requirements that result from an
		  order-planning or master-planning run end up in this period, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> generates a <Link href="/baanerp/ti/glossary/glossary#RescheMessag_ti" role="glossary">rescheduling message</Link> which advises you to
		  plan the supply to another delivery moment on a date outside period 1.</ListItem>
         <ListItem>In period 2, the <Link href="/baanerp/td/glossary/glossary#000027" role="glossary">frozen zone+</Link>, ERP Enterprise cannot add new schedule lines, but only
		  decrease the quantities of the schedule lines in this period. To avoid that
		  requirements resulting from an order-planning or a master-planning run end up
		  in this part of the purchase schedule, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> can
		  generate rescheduling messages.</ListItem>
         <ListItem>In period 3, the purchase schedule can be regenerated, and
		  subsequently the schedule lines (delivery moments) are not yet defined. <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> groups
		  all the requirements that it generated during a planning run to the delivery
		  moments, and then sends these requirements to the <GUIRef href="/baanerp/td/pur" role="module">Purchase Control</GUIRef> module of <GUIRef href="/baanerp/procurement" role="package">Procurement</GUIRef> where the requirements are used to update
		  the corresponding schedule line.</ListItem>
         <ListItem>In period 4, Figure 1-1 shows that no more delivery moment are
		  available. As a result, <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> considers every date as a potential delivery moment, and does
		  not group the requirements anymore, but sends them directly to <GUIRef href="/baanerp/td/pur" role="module">Purchase Control</GUIRef>.</ListItem>
      </List>
   </ExampleSection>
   <ExampleSection>
      <SectionTitle>Example planning and rescheduling</SectionTitle>
      <Paragraph>Figure 1-2 shows the existing demand for a purchase schedule
		item. All the time moments are in the <Link href="/baanerp/td/glossary/glossary#000028" role="glossary">frozen zone-</Link>, and t1 falls after the <Link href="/baanerp/td/glossary/glossary#000027" role="glossary">frozen zone+</Link>. In addition the following is
		true:</Paragraph>
      <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
         <TBODY noTR="6">
            <TR no="1" isLast="false">
               <TD rowspan="1" colspan="1">Min. Lot
				Size</TD>
               <TD rowspan="1" colspan="1">8</TD>
            </TR>
            <TR no="2" isLast="false">
               <TD rowspan="1" colspan="1">Demand on t2</TD>
               <TD rowspan="1" colspan="1">5
				pcs</TD>
            </TR>
            <TR no="3" isLast="false">
               <TD rowspan="1" colspan="1">Demand on t3</TD>
               <TD rowspan="1" colspan="1">10 pcs</TD>
            </TR>
            <TR no="4" isLast="false">
               <TD rowspan="1" colspan="1">Demand on
				t5</TD>
               <TD rowspan="1" colspan="1">5 pcs</TD>
            </TR>
            <TR no="5" isLast="false">
               <TD rowspan="1" colspan="1">Pattern moment 1</TD>
               <TD rowspan="1" colspan="1">on
				t1</TD>
            </TR>
            <TR no="6" isLast="true">
               <TD rowspan="1" colspan="1">Pattern moment 2</TD>
               <TD rowspan="1" colspan="1">on t4</TD>
            </TR>
         </TBODY>
      </TABLE>
      <Figure space-and-orientation="indented-estimated">
         <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="216" width="504"
                   SRC="../images/tr_graph_000078c.gif"
                   alt="[...]"/>
         <FigCaption>1-2 Planning and rescheduling purchase schedule
		  items</FigCaption>
         <FigLegend>
            <LegendEntry>
               <Symbol>X</Symbol>
               <Desc>planned delivery moment</Desc>
            </LegendEntry>
            <LegendEntry>
               <Symbol>FZ+</Symbol>
               <Desc>frozen zone +</Desc>
            </LegendEntry>
            <LegendEntry>
               <Symbol>FZ-</Symbol>
               <Desc>frozen zone -</Desc>
            </LegendEntry>
         </FigLegend>
      </Figure>
      <Paragraph>ERP Enterprise must
		fill the demand placed on t2 and t3 in time, which is why ERP Enterprise generates supply of 15
		pieces on t1, that is, the closest planned delivery moment
		available.</Paragraph>
      <Paragraph>ERP Enterprise must
		fill the second demand of 5 pieces, placed on t5, with a supply of 8 pcs
		(minimum lot size) on planned delivery moment t4 (see Figure 1-3).</Paragraph>
      <Figure space-and-orientation="indented-estimated">
         <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="216" width="504"
                   SRC="../images/tr_graph_000078d.gif"
                   alt="[...]"/>
         <FigCaption>1-3 Planning supply for a purchase schedule item</FigCaption>
         <FigLegend>
            <LegendEntry>
               <Symbol>S1</Symbol>
               <Desc>schedule line 1</Desc>
            </LegendEntry>
            <LegendEntry>
               <Symbol>S2</Symbol>
               <Desc>schedule line 2</Desc>
            </LegendEntry>
         </FigLegend>
      </Figure>
      <Paragraph>Figure 1-4 shows how ERP Enterprise reacts if the demand placed on t3 increases
		with 5 pieces.</Paragraph>
      <Figure space-and-orientation="indented-estimated">
         <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="216" width="504"
                   SRC="../images/tr_graph_000078e.gif"
                   alt="[...]"/>
         <FigCaption>1-4 Rescheduling supply for a purchase schedule
		  item</FigCaption>
      </Figure>
      <Paragraph> ERP Enterprise carries out the following steps during an order-based planning run, if the
		demand placed on t3 increases by five pieces (see Figure 1-3):</Paragraph>
      <ProcedureList>
         <ListItem>The schedule lines S1 and S2 are recognized as firm planned
		  because these lines are in the <Link href="/baanerp/td/glossary/glossary#000028" role="glossary">frozen zone-</Link>. However, the lines are firm planned in the
		  sense that ERP Enterprise can still
		  increase the ordered quantity, not decrease it.</ListItem>
         <ListItem>Generate a rescheduling message <GUIRef href="/baanerp/cp/messages/raosign.29" role="message">Reschedule into %1$u001 %2$U001.</GUIRef>. In other words, ERP Enterprise advices you to
		  reschedule five pieces of schedule line 2 into schedule line 1.</ListItem>
         <ListItem>ERP Enterprise adds 2
		  pieces to schedule line 2 to be able to fill the demand placed on t5.</ListItem>
      </ProcedureList>
      <Paragraph>Figure 1-5 shows the way in which ERP Enterprise reacts if the demand
		placed on t3 increases by ten pieces.</Paragraph>
      <Figure space-and-orientation="indented-estimated">
         <HTML:IMG xmlns:HTML="http://www.w3.org/TR/REC-html40" height="216" width="504"
                   SRC="../images/tr_graph_000078f.gif"
                   alt="[...]"/>
         <FigCaption>1-5 Rescheduling supply for a purchase schedule
		  item</FigCaption>
      </Figure>
      <Paragraph>ERP Enterprise carries
		out the folowing steps during an order-based planning run, if the demand placed
		on t3 increases with 10 pieces (see Figure 1-5):</Paragraph>
      <ProcedureList>
         <ListItem>The schedule line are recognized as firm planned in the sense
		  that ERP Enterprise can still
		  increase the ordered quantity, but not decrease it.</ListItem>
         <ListItem>Generate a rescheduling message <GUIRef href="/baanerp/cp/messages/raosign.29" role="message">Reschedule into %1$u001 %2$U001.</GUIRef>. In other words, ERP Enterprise advices you to
		  reschedule eight pieces of schedule line 2 into schedule line 1.</ListItem>
         <ListItem>ERP Enterprise adds 5
		  pieces to schedule line 2 to be able to fill the demand placed on t5.</ListItem>
      </ProcedureList>
   </ExampleSection>
   <Note>
      <SectionTitle>Note</SectionTitle>
      <Paragraph>If Enterprise Planning cannot update the purchase schedule, it
		generates a <Link href="/baanerp/cp/glossary/glossary#000048" role="glossary">planned purchase order</Link> for the same supplier. Note that
		Enterprise Planning blocks planned purchase orders for purchase schedule items
		at the moment of transferring planned orders to the execution
		level.</Paragraph>
   </Note>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/cp/onlinemanual/000017" role="manual">Plan items in Enterprise Planning</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/cp/onlinemanual/000354" role="manual">Sales schedules in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>
         </Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>