<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/td/onlinemanual/000133" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">To determine the planned receipt date</Title>
		<Keyword><Level1>planned receipt date</Level1>
		</Keyword>
		<Keyword><Level1>lead time calculation</Level1>
		</Keyword>
		<Keyword><Level1>lead time</Level1>
		</Keyword>
	</Header>
	<GeneralSection><Paragraph>If you (manually) enter a purchase order line in the <GUIRef href="/baanerp/td/pur/tdpur4101s000" role="session">Purchase Order - Line (tdpur4101s000)</GUIRef> session, or a purchase schedule line in the <GUIRef href="/baanerp/td/pur/tdpur3111m000" role="session">Purchase Schedule - Lines (tdpur3111m000)</GUIRef> session, you must also specify a planned receipt date. Based on the order date/ generation date, you can let SSA ERP calculate the planned receipt date, on the basis of the lead times. To calculate the planned receipt date, choose <GUIRef href="" role="manual">Calc.</GUIRef> in the <GUIRef href="/baanerp/td/pur/tdpur4101s000" role="session">Purchase Order - Line (tdpur4101s000)</GUIRef> session/ <GUIRef href="/baanerp/td/pur/tdpur3111m000" role="session">Purchase Schedule - Lines (tdpur3111m000)</GUIRef> session. SSA ERP then stores the planned receipt date in the <GUIRef href="/baanerp/td/pur/tdpur3111m000#tdpur311.ddta" role="formfield">Planned Receipt Date</GUIRef> field of these sessions.</Paragraph>
		<Paragraph>If data is specified for an item in the <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Item - Purchase Business Partner (tdipu0110m000)</GUIRef> session, or the <GUIRef href="/baanerp/td/pur/tdpur3102m000" role="session">Purchase Contract Line Logistic Data (tdpur3102m000)</GUIRef>, SSA ERP determines the planned receipt date using the lead time components that are specified in these sessions.</Paragraph>
		<Paragraph>SSA ERP has two possibilities of determining the planned receipt date. Which possibility is used, depends on the following value of the <Link href="/baanerp/td/ipu/tdipu0110m000#tdipu010.oltf" role="formfield">Lead Time Horizon (Days)</Link> field in the <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Item - Purchase Business Partner (tdipu0110m000)</GUIRef>/ <GUIRef href="/baanerp/td/pur/tdpur3102m000" role="session">Purchase Contract Line Logistic Data (tdpur3102m000)</GUIRef> session.</Paragraph>
		<Note><SectionTitle>Note</SectionTitle>
			<List><ListIntro>If the lead time component is expressed in:</ListIntro>
				<ListItem>Hours, SSA ERP takes into account all the time that is available on a day according to the calendar.</ListItem>
				<ListItem>Days, SSA ERP considers a day as a whole day if some time is available on that day according to the calendar.</ListItem>
			</List>
		</Note>
		<GeneralSection><SectionTitle>Determination of horizon</SectionTitle>
			<List><ListIntro>By adding the lead time horizon to the current date and time, SSA ERP determines the horizon. When determining the horizon, SSA ERP takes into account the company calendar to which the <GUIRef href="/baanerp/td/pur" role="module">Purchase Control</GUIRef> availability type is linked. SSA ERP compares the order/generation date with the horizon, which results in one of the following possibilities, which results in a different determination of the planned receipt date:</ListIntro>
				<ListItem>The order/generation date lies beyond the horizon.</ListItem>
				<ListItem>The order/generation date lies within or before the horizon.</ListItem>
			</List>
		</GeneralSection>
		<Note><SectionTitle>Note</SectionTitle>
			<List><ListItem>The lead time horizon is always expressed in days.</ListItem>
				<ListItem>The company calendar is the calendar that is linked to the company in the <GUIRef href="/baanerp/tc/emm/tcemm1170m000" role="session">Companies (tcemm1170m000)</GUIRef> session.</ListItem>
			</List>
		</Note>
		<ExampleSection><SectionTitle>Example horizon determination</SectionTitle>
			<TABLE border="1"><TBODY><TR><TD>Current date/time: Wednesday, March 10/15:00:00</TD>
					</TR>
					<TR><TD>The company calendar for the <GUIRef href="/baanerp/td/pur" role="module">Purchase Control</GUIRef> availability type has an 8:00:00 start time and a 16:00:00 end time and is available from Monday through Friday each week</TD>
					</TR>
					<TR><TD>Lead time horizon (in days): 10</TD>
					</TR>
				</TBODY>
			</TABLE>
			<Paragraph>Because on Wednesday one hour is available, Wednesday counts for a whole day. So, during the first week three days are available. During the next week five days are available. So, two days are left for the third week. Because SSA ERP finds time available on Tuesday, March 23, this day counts for a whole day and SSA ERP takes the last available time as the horizon time. So, the horizon is Tuesday, March 23/16:00:00.</Paragraph>
		</ExampleSection>
		<GeneralSection><SectionTitle>Order/generation date beyond horizon</SectionTitle>
			<Paragraph>If the order date lies beyond the horizon, SSA ERP considers the purchase order/schedule as a forecast demand for which no accurate determination of the planned receipt date is yet required.</Paragraph>
			<Paragraph>SSA ERP determines the planned receipt date as follows, taking into account the company calendar:</Paragraph>
			<Formula><Paragraph UserLevel="Novice" UserType="Taskuser">
Planned delivery date = order date + calculated lead time
</Paragraph>
			</Formula>
			<Paragraph>SSA ERP retrieves the calculated lead time from the <GUIRef href="/baanerp/td/ipu/tdipu0110m000#tdipu010.cldt" role="formfield">Calculated Lead Time (Days)</GUIRef> field of the <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Item - Purchase Business Partner (tdipu0110m000)</GUIRef> session/ <GUIRef href="/baanerp/td/pur/tdpur3102m000" role="session">Purchase Contract Line Logistic Data (tdpur3102m000)</GUIRef> session. See also: <Link href="/baanerp/td/onlinemanual/000324" role="manual">To calculate purchase item lead time</Link>.</Paragraph>
		</GeneralSection>
		<Note><SectionTitle>Note</SectionTitle>
			<List><ListItem>The calculated lead time is always expressed in days.</ListItem>
				<ListItem>If no availability type is specified, SSA ERP searches for the company calendar without availability type.</ListItem>
				<ListItem>If no company calendar is specified at all, SSA ERP takes into account the <Link href="/baanerp/tc/glossary/glossary#StandaCalend.tc" role="glossary">standard calendar template</Link> that is specified in the <GUIRef href="/baanerp/tc/ccp/tcccp0140m000" role="session">Standard Calendar (tcccp0140m000)</GUIRef> session.</ListItem>
			</List>
		</Note>
		<ExampleSection><SectionTitle>Example order/generation date beyond horizon</SectionTitle>
			<TABLE border="1"><TBODY><TR><TD>Order/generation date: Thursday, March 25/17:00:00</TD>
					</TR>
					<TR><TD>Calculated lead time (in days): 5</TD>
					</TR>
					<TR><TD>The company calendar for the <GUIRef href="/baanerp/td/pur" role="module">Purchase Control</GUIRef> availability type has an 8:00:00 start time and a 16:00:00 end time and is available from Monday through Friday each week.</TD>
					</TR>
				</TBODY>
			</TABLE>
			<Paragraph>Because Thursday, March 25/17:00:00, is not an available date/time according to the calendar, SSA ERP searches for the first available date/time to which the calculated lead time must be added, which is Friday, 26/8:00:00. So, four days are left for the next week. Because SSA ERP finds time available on the fourth day, Thursday, April 1, this day counts for a whole day and SSA ERP takes the last available time as the planned receipt date. So, the planned receipt date is Thursday, April 1/16:00:00.</Paragraph>
		</ExampleSection>
		<GeneralSection><SectionTitle>Order/generation date within or before horizon</SectionTitle>
			<Paragraph>If the order/generation date lies within or before the horizon, SSA ERP considers the purchase order/schedule as an immediate demand for which an accurate determination of the planned receipt date is required. Therefore, SSA ERP determines the planned receipt date by adding up the lead time components, taking into account the related <Link href="/baanerp/tc/glossary/glossary#Calendar.tc" role="glossary">calendars</Link> for each component.</Paragraph>
			<Paragraph>SSA ERP determines the planned receipt date as follows:</Paragraph>
			<Formula><Paragraph UserLevel="Novice" UserType="Taskuser">Planned receipt date = order/generation date + 
internal processing time + supply time + transportation time + 
safety time.
</Paragraph>
			</Formula>
			<List><ListIntro>SSA ERP retrieves the order/generation date and the lead time components that it uses to determine the planned receipt date as follows:</ListIntro>
				<ListItem><Link href="/baanerp/td/glossary/glossary#000046" role="glossary">Order date</Link> from the <GUIRef href="/baanerp/td/pur/tdpur4101s000#tdpur401.odat" role="formfield">Order Date</GUIRef> field of the <GUIRef href="/baanerp/td/pur/tdpur4101s000" role="session">Purchase Order - Line (tdpur4101s000)</GUIRef> session.</ListItem>
				<ListItem><Link href="/baanerp/td/glossary/glossary#000075" role="glossary">Generation date</Link> from the <GUIRef href="/baanerp/td/pur/tdpur3110m000#tdpur310.gdat" role="field">Generation Date</GUIRef> field of the <GUIRef href="/baanerp/td/pur/tdpur3110m000" role="session">Purchase Schedules (tdpur3110m000)</GUIRef> session.</ListItem>
				<ListItem><Link href="/baanerp/td/glossary/glossary#000040" role="glossary">Internal processing time</Link> from the <GUIRef href="/baanerp/td/ipu/tdipu0110m000#tdipu010.ipti" role="formfield">Internal Processing Time</GUIRef> field of the <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Item - Purchase Business Partner (tdipu0110m000)</GUIRef> session/ <GUIRef href="/baanerp/td/pur/tdpur3102m000" role="session">Purchase Contract Line Logistic Data (tdpur3102m000)</GUIRef> session.</ListItem>
				<ListItem><Link href="/baanerp/td/glossary/glossary#000041" role="glossary">Safety time</Link> from the <GUIRef href="/baanerp/td/ipu/tdipu0110m000#tdipu010.sfti" role="formfield">Safety Time</GUIRef> field of the <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Item - Purchase Business Partner (tdipu0110m000)</GUIRef> session/ <GUIRef href="/baanerp/td/pur/tdpur3102m000" role="session">Purchase Contract Line Logistic Data (tdpur3102m000)</GUIRef> session.</ListItem>
				<ListItem><Link href="/baanerp/td/glossary/glossary#000011" role="glossary">Supply time</Link> from the <GUIRef href="/baanerp/td/ipu/tdipu0110m000#tdipu010.suti" role="formfield">Supply Time</GUIRef> field of the <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Item - Purchase Business Partner (tdipu0110m000)</GUIRef> session/ <GUIRef href="/baanerp/td/pur/tdpur3102m000" role="session">Purchase Contract Line Logistic Data (tdpur3102m000)</GUIRef> session.</ListItem>
				<ListItem>Transportation time from the <Link href="/baanerp/td/ipu/tdipu0110m000#transit.time" role="fieldhelp">Transportation Time (Days)</Link> field of the <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Item - Purchase Business Partner (tdipu0110m000)</GUIRef> session/ <GUIRef href="/baanerp/td/pur/tdpur3102m000" role="session">Purchase Contract Line Logistic Data (tdpur3102m000)</GUIRef> session.</ListItem>
			</List>
			<Paragraph>When determining the planned receipt date, SSA ERP also takes into account the calendars that are related to the lead time components. SSA ERP searches for the calendars that are related to the lead time components as follows:</Paragraph>
			<ProcedureList><ListItemHead>Internal processing time:</ListItemHead>
				<ListItem>If a purchase office is specified for the item and buy-from business partner combination and a calendar is specified for the purchase office, SSA ERP takes into account the purchase office's calendar. You can specify the purchase office's calendar in the <GUIRef href="/baanerp/tc/mcs/tcmcs0565m000" role="session">Departments (tcmcs0565m000)</GUIRef> session.</ListItem>
				<ListItem>If no calendar is specified for the purchase office or if no purchase office is specified, SSA ERP takes into account the company calendar.</ListItem>
			</ProcedureList>
			<ProcedureList><ListItemHead>Supply time:</ListItemHead>
				<ListItem>If a ship-from business partner is specified and the ship-from business partner's calendar is specified, SSA ERP takes into account the ship-from business partner's calendar.</ListItem>
				<ListItem>If no ship-from business partner calendar is available, SSA ERP takes into account the buy-from business partner's calendar.</ListItem>
				<ListItem>If no buy-from business partner calendar is available, SSA ERP takes into account the company calendar.</ListItem>
			</ProcedureList>
			<ProcedureList><ListItemHead>Transportation time:</ListItemHead>
				<ListItem>If a carrier is specified and a buy-from business partner is linked to the carrier and the buy-from business partner's calendar is known, SSA ERP takes into account the buy-from business partner's calendar.</ListItem>
				<ListItem>If a carrier is specified, and a buy-from business partner is linked to the carrier, but the buy-from business partner's calendar is not specified, SSA ERP takes into account the company calendar.</ListItem>
				<ListItem>If a carrier is specified, but no buy-from business partner is linked to the carrier, SSA ERP takes into account the company calendar.</ListItem>
				<ListItem>If no carrier is specified, SSA ERP takes into account the company calendar.</ListItem>
			</ProcedureList>
			<ProcedureList><ListItemHead>Safety time:</ListItemHead>
				<ListItem>If a ship-from business partner is specified and the ship-from business partner's calendar is specified, SSA ERP takes into account the ship-from business partner's calendar.</ListItem>
				<ListItem>If no ship-from business partner calendar is available, SSA ERP takes into account the buy-from business partner's calendar.</ListItem>
				<ListItem>If no buy-from business partner calendar is available, SSA ERP takes into account the company calendar .</ListItem>
			</ProcedureList>
			<List><ListIntro>SSA ERP searches for the actual calendars based on:</ListIntro>
				<ListItem>The calendar that is related to the lead time component.</ListItem>
				<ListItem>The <GUIRef href="/baanerp/td/pur" role="module">Purchase Control</GUIRef> availability type.</ListItem>
				<ListItem>The <GUIRef href="/baanerp/tc/com/tccom0000s000#tccom999.ract" role="formfield">Avail. Type for Carrying Goods</GUIRef>.</ListItem>
				<ListItem>The calendar's start date and end date.</ListItem>
			</List>
		</GeneralSection>
		<Note><SectionTitle>Note</SectionTitle>
			<List><ListItem>You can express the lead time components in hours and in days.</ListItem>
				<ListItem>You can specify the <GUIRef href="/baanerp/td/pur" role="module">Purchase Control</GUIRef> availability type in the <GUIRef href="/baanerp/td/pur/tdpur0100m000" role="session">Purchase Parameters (tdpur0100m000)</GUIRef> session.</ListItem>
				<ListItem>You can specify the <GUIRef href="/baanerp/tc/com/tccom0000s000#tccom999.ract" role="formfield">Avail. Type for Carrying Goods</GUIRef> in the <GUIRef href="/baanerp/tc/com/tccom0000s000" role="session">COM Parameters (tccom0000s000)</GUIRef> session.</ListItem>
				<ListItem>If no availability type is specified, SSA ERP searches for a calendar without availability type.</ListItem>
				<ListItem>If no calendar is specified at all, SSA ERP takes into account the <Link href="/baanerp/tc/glossary/glossary#StandaCalend.tc" role="glossary">standard calendar template</Link> that is specified in the <GUIRef href="/baanerp/tc/ccp/tcccp0140m000" role="session">Standard Calendar (tcccp0140m000)</GUIRef> session.</ListItem>
			</List>
		</Note>
		<ExampleSection><SectionTitle>Example order/generation date within or before horizon</SectionTitle>
			<TABLE border="1"><TBODY><TR><TD>Order/generation date:</TD>
						<TD>Friday, March 12/7:00:00</TD>
					</TR>
					<TR><TD>Internal processing time (in hours):</TD>
						<TD>6</TD>
					</TR>
					<TR><TD>Supply time (in days):</TD>
						<TD>1</TD>
					</TR>
					<TR><TD>Transportation time (in days):</TD>
						<TD>2</TD>
					</TR>
					<TR><TD>Safety time (in hours):</TD>
						<TD>4</TD>
					</TR>
				</TBODY>
			</TABLE>
			<Paragraph>The company calendar for the <GUIRef href="/baanerp/td/pur" role="module">Purchase Control</GUIRef> availability type and for the <GUIRef href="/baanerp/tc/com/tccom0000s000#tccom999.ract" role="formfield">Avail. Type for Carrying Goods</GUIRef> has an 8:00:00 start time and a 16:00:00 end time and is available from Monday through Friday each week. The buy-from business partner's calendar for the <GUIRef href="/baanerp/td/pur" role="module">Purchase Control</GUIRef> availability type and for the <GUIRef href="/baanerp/tc/com/tccom0000s000#tccom999.ract" role="formfield">Avail. Type for Carrying Goods</GUIRef> has an 8:30:00 start time and a 16:30:00 end time and is available from Monday through Friday each week. The ship-from business partner's calendar for the <GUIRef href="/baanerp/td/pur" role="module">Purchase Control</GUIRef> availability type has a 9:00:00 start time and a 17:00:00 end time and is available from Monday through Friday each week.</Paragraph>
		</ExampleSection>
		<ProcedureList><ListIntro>SSA ERP determines the planned receipt date as follows:</ListIntro>
			<ListItem>SSA ERP adds the internal processing time to the order/generation date, taking into account the company calendar. Because Friday, March 12/7:00:00, is not an available date/time according to the company calendar, SSA ERP searches for the first available date/time to which the internal processing time must be added, which is Friday, March 12/8:00:00.</ListItem>
			<ListItem>SSA ERP adds the internal processing time to Friday, March 12/8:00:00. The resulting date/time is Friday, March 12/14:00:00.</ListItem>
			<ListItem>SSA ERP adds the supply time to Friday, March 12/14:00:00, taking into account the company calendar. According to the company calendar on Friday, March 12, two hours are left. Because the supply time is expressed in days, SSA ERP considers Friday, March 12, as a whole day. So, the resulting date/time is Friday, March 12/16:00:00.</ListItem>
			<ListItem>SSA ERP adds the transportation time to Friday, March 12/16:00:00, taking into account the buy-from business partner's calendar. According to the buy-from business partner's calendar on Friday, March 12, half an hour is left. Because the transportation time is expressed in days, SSA ERP considers Friday, March 12, as a whole day. The second transportation day is the first available day after Friday, March 12, which is Monday, March 15. So, the resulting date/time is Monday, March 15/16:30:00.</ListItem>
			<ListItem>SSA ERP adds the safety time to Monday, March 15/16:30:00, taking into account the ship-from business partner's calendar. According to the ship-from business partner's calendar, on Monday, March 15, half an hour is left. The remaining 3,5 hours is added to Tuesday, March 16, starting at 9:00:00. So, the resulting date/time is Tuesday, March 16/12:30:00, which is the planned receipt date.</ListItem>
		</ProcedureList>
	</GeneralSection>
	<RelatedTopics><SectionTitle>Related topics</SectionTitle>
		<RelTopic><Link href="/baanerp/cp/onlinemanual/000335" role="manual">Purchase lead time calculation</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/cp/onlinemanual/000061" role="manual">Distribution lead time based on the supply calendar</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/td/onlinemanual/000133" role="manual">To determine the planned receipt date</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/tc/onlinemanual/000135" role="manual">Calendar input for lead time</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
