<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/td/onlinemanual/000346" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Purchase schedule release types</Title>
		<Keyword><Level1>release type</Level1>
		</Keyword>
		<Keyword><Level1>purchase schedule</Level1>
		</Keyword>
	</Header>
	<AimSection><Paragraph>If <Link href="/baanerp/td/glossary/glossary#000000000000011" role="glossary">purchase schedules</Link> are used, schedule <Link href="/baanerp/td/glossary/glossary#000000000000010" role="glossary">release types</Link> must be defined, based on which a <Link href="/baanerp/td/glossary/glossary#000351" role="glossary">purchase release</Link> is sent.</Paragraph>
	</AimSection>
	<GeneralSection><Paragraph>In the <GUIRef href="/baanerp/td/pur/tdpur3102m000#tdpur302.scrd" role="field">Schedule Release Detail</GUIRef> field of the <GUIRef href="/baanerp/td/pur/tdpur3102m000" role="session">Purchase Contract Line Logistic Data (tdpur3102m000)</GUIRef> session and the <GUIRef href="/baanerp/td/ipu/tdipu0110m000" role="session">Item - Purchase Business Partner (tdipu0110m000)</GUIRef> session, you must choose one of the following release types:</Paragraph>
		<List><ListItem><GUIRef href="/baanerp/tc/domains/scrd#material" role="enum">Material Release</GUIRef>: only a <Link href="/baanerp/td/glossary/glossary#MateriReleas.td" role="glossary">material release</Link> is sent.</ListItem>
			<ListItem><GUIRef href="/baanerp/tc/domains/scrd#shipping" role="enum">Shipping Schedule</GUIRef>: both a material release and a <Link href="/baanerp/td/glossary/glossary#000033" role="glossary">shipping schedule</Link> are sent.</ListItem>
			<ListItem><GUIRef href="/baanerp/tc/domains/scrd#sequence" role="enum">Sequence Shipping Schedule</GUIRef>: both a material release and a <Link href="/baanerp/td/glossary/glossary#000034" role="glossary">sequence shipping schedule</Link> are sent.</ListItem>
			<ListItem><GUIRef href="/baanerp/tc/domains/scrd#ship.only" role="enum">Shipping Schedule Only</GUIRef>: only a shipping schedule is sent.</ListItem>
		</List>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>You can only choose the <GUIRef href="/baanerp/tc/domains/scrd#material" role="enum">Material Release</GUIRef> type for <Link href="/baanerp/td/glossary/glossary#000334" role="glossary">push schedules</Link> and the <GUIRef href="/baanerp/tc/domains/scrd#sequence" role="enum">Sequence Shipping Schedule</GUIRef> type for <Link href="/baanerp/td/glossary/glossary#000335" role="glossary">pull schedules</Link>.</Paragraph>
		</Note>
		<Paragraph>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">Item - Purchase Business Partner (tdipu0110m000)</GUIRef> session, you must also enter <Link href="/baanerp/td/glossary/glossary#000093" role="glossary">segment set(s)</Link>. Which segment set(s) can be entered depends on the chosen release type. A segment set consists of several <Link href="/baanerp/td/glossary/glossary#000094" role="glossary">segments</Link>, which in turn, are linked to <Link href="/baanerp/td/glossary/glossary#000340" role="glossary">requirement types</Link>. Dependent on the release type and the applicable requirement type, specific EDI messages can be generated in time when sending the purchase release to the supplier.</Paragraph>
		<Note><SectionTitle>Note</SectionTitle>
			<List><ListItem>Because pull call-off schedule lines are not clustered and are automatically converted to purchase release line details with the status Scheduled, no segment sets are used. As a result, the requirement type is always <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="enum">Firm</GUIRef>.</ListItem>
				<ListItem>For push schedules lines, requirement types in the <GUIRef href="/baanerp/td/pur/tdpur3111m000" role="session">Purchase Schedule - Lines (tdpur3111m000)</GUIRef> session are calculated during the <Link href="/baanerp/td/glossary/glossary#000341" role="glossary">regeneration</Link> process, which you can perform in the <GUIRef href="/baanerp/td/pur/tdpur3211m000" role="session">Regenerate Schedules (tdpur3211m000)</GUIRef> session. The requirement types in the <GUIRef href="/baanerp/td/pur/tdpur3522m000" role="session">Purchase Release Line - Details (tdpur3522m000)</GUIRef> session are directly calculated from the schedule's applicable segment set and issue <Link href="/baanerp/td/glossary/glossary#000030" role="glossary">pattern</Link>, 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">Item - Purchase Business Partner (tdipu0110m000)</GUIRef> session. As a result, if you do not regenerate the schedule line, the value of the <GUIRef href="/baanerp/td/pur/tdpur3111m000#tdpur311.rqtp" role="field">Requirement Type</GUIRef> field in the <GUIRef href="/baanerp/td/pur/tdpur3111m000" role="session">Purchase Schedule - Lines (tdpur3111m000)</GUIRef> session is necessarily the same as the value of the <GUIRef href="/baanerp/td/pur/tdpur3522m000#tdpur322.rqtp" role="field">Req. Type</GUIRef> field in the <GUIRef href="/baanerp/td/pur/tdpur3522m000" role="session">Purchase Release Line - Details (tdpur3522m000)</GUIRef> session. Which schedule lines are included when you generate release lines in the <GUIRef href="/baanerp/td/pur/tdpur3222m000" role="session">Generate Release Lines (tdpur3222m000)</GUIRef> session, depends on the push schedule's release type. For example, if the release type is defined as <GUIRef href="/baanerp/tc/domains/scrd#ship.only" role="enum">Shipping Schedule Only</GUIRef>, no material release is created, so the purchase release does not contain <GUIRef href="/baanerp/td/domains/pur.rtyp#planned" role="enum">Planned</GUIRef> release lines.</ListItem>
			</List>
		</Note>
		<GeneralSection><SectionTitle>Relation between release type, requirement type, and EDI message when you generate/send a purchase release for push schedules</SectionTitle>
			<TABLE border="1"><TBODY><TR><TD colspan="2">
							<Emphasis>Release type</Emphasis>
						</TD>
						<TD><Emphasis>Linked requirement types</Emphasis>
						</TD>
						<TD><Emphasis>Linked EDI messages (BEMIS example)</Emphasis>
						</TD>
					</TR>
					<TR><TD colspan="2">Material Release:</TD>
						<TD>Planned</TD>
						<TD>BEM MRL001</TD>
					</TR>
					<TR><TD colspan="2">-</TD>
						<TD>Firm</TD>
						<TD>BEM MRL001</TD>
					</TR>
					<TR><TD colspan="2">-</TD>
						<TD>Immediate</TD>
						<TD>BEM MRL001</TD>
					</TR>
					<TR><TD colspan="2">Shipping Schedule:</TD>
						<TD>-</TD>
						<TD>-</TD>
					</TR>
					<TR><TD>*</TD>
						<TD>Material Release</TD>
						<TD>Planned</TD>
						<TD>BEM MRL001</TD>
					</TR>
					<TR><TD colspan="2">-</TD>
						<TD>Immediate</TD>
						<TD>BEM MRL001</TD>
					</TR>
					<TR><TD>*</TD>
						<TD>Shipping Schedule</TD>
						<TD>Firm</TD>
						<TD>BEM SHP001</TD>
					</TR>
					<TR><TD colspan="2">-</TD>
						<TD>Immediate</TD>
						<TD>BEM SHP001</TD>
					</TR>
					<TR><TD colspan="2">Shipping Schedule Only:</TD>
						<TD>Firm</TD>
						<TD>BEM SHP001</TD>
					</TR>
					<TR><TD colspan="2">-</TD>
						<TD>Immediate</TD>
						<TD>BEM SHP001</TD>
					</TR>
				</TBODY>
			</TABLE>
		</GeneralSection>
		<GeneralSection><SectionTitle>Relation between release type, requirement type, and EDI message when generating/sending a purchase release for pull schedules</SectionTitle>
			<TABLE border="1"><TBODY><TR><TD colspan="2">
							<Emphasis>Release type</Emphasis>
						</TD>
						<TD><Emphasis>Linked requirement types</Emphasis>
						</TD>
						<TD><Emphasis>Linked EDI messages (BEMIS example)</Emphasis>
						</TD>
					</TR>
					<TR><TD colspan="2">Shipping Schedule:</TD>
						<TD>-</TD>
						<TD>-</TD>
					</TR>
					<TR><TD>*</TD>
						<TD>Material Release</TD>
						<TD>Planned</TD>
						<TD>BEM MRL001</TD>
					</TR>
					<TR><TD colspan="2">-</TD>
						<TD>Immediate</TD>
						<TD>BEM MRL001</TD>
					</TR>
					<TR><TD>*</TD>
						<TD>Shipping Schedule</TD>
						<TD>Firm</TD>
						<TD>BEM SHP001</TD>
					</TR>
					<TR><TD colspan="2">Sequence Shipping Schedule:</TD>
						<TD>-</TD>
						<TD>-</TD>
					</TR>
					<TR><TD>*</TD>
						<TD>Material Release</TD>
						<TD>Planned</TD>
						<TD>BEM MRL001</TD>
					</TR>
					<TR><TD colspan="2">-</TD>
						<TD>Immediate</TD>
						<TD>BEM MRL001</TD>
					</TR>
					<TR><TD>*</TD>
						<TD>Sequence Shipping Schedule</TD>
						<TD>Firm</TD>
						<TD>BEM SEQ001</TD>
					</TR>
					<TR><TD colspan="2">Shipping Schedule Only:</TD>
						<TD>Firm</TD>
						<TD>BEM SHP001</TD>
					</TR>
				</TBODY>
			</TABLE>
		</GeneralSection>
		<GeneralSection><SectionTitle>Explanation for each release type</SectionTitle>
			<Paragraph><Emphasis><GUIRef href="/baanerp/tc/domains/scrd#material" role="enum">Material Release</GUIRef>
				</Emphasis>:</Paragraph>
			<Paragraph>This release type is only used by push schedules and only generates the EDI message BEM MRL001. As a result, shipping is performed based on the EDI message BEM MRL001, but only for those schedule lines whose requirement type is <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="enum">Firm</GUIRef> or <GUIRef href="/baanerp/td/domains/pur.rtyp#immediate" role="enum">Immediate</GUIRef>.</Paragraph>
			<Paragraph><Emphasis><GUIRef href="/baanerp/tc/domains/scrd#shipping" role="enum">Shipping Schedule</GUIRef>
				</Emphasis>:</Paragraph>
			<List><ListItem>Push schedules: this release type generates both material releases (EDI messages BEM MRL001) and shipping schedules (EDI message BEM SHP001). The schedule lines in a material release are released for planning purposes only. The shipping schedule only releases those schedule lines whose requirement type is <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="enum">Firm</GUIRef> or <GUIRef href="/baanerp/td/domains/pur.rtyp#immediate" role="enum">Immediate</GUIRef>, as calculated by the segment set. Planned schedule lines are not included in the release. Shipping is performed based on the EDI message BEM SHP001.</ListItem>
				<ListItem>Pull schedules: a pull forecast schedule only generates material releases (EDI message BEM MRL001) that contain <GUIRef href="/baanerp/td/domains/pur.rtyp#planned" role="enum">Planned</GUIRef> lines. EDI message BEM MRL001 is released for planning purposes only. However, the pull forecast schedule's material release can also contain <GUIRef href="/baanerp/td/domains/pur.rtyp#immediate" role="enum">Immediate</GUIRef> lines if requirements from the past are not delivered yet. The pull call-off schedule generates the shipping schedule, releasing all the schedule lines whose requirement type is <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="enum">Firm</GUIRef>. Shipping is performed based on the EDI message BEM SHP001.</ListItem>
			</List>
			<Paragraph><Emphasis><GUIRef href="/baanerp/tc/domains/scrd#sequence" role="enum">Sequence Shipping Schedule</GUIRef>
				</Emphasis>:</Paragraph>
			<Paragraph>This release type is only used by pull schedules and generates the EDI messages BEM MRL001 and BEM SEQ001. A pull forecast schedule only generates material releases (EDI message BEM MRL001) that contain <GUIRef href="/baanerp/td/domains/pur.rtyp#planned" role="enum">Planned</GUIRef> lines. EDI message BEM MRL001 is released for planning purposes, only. However, the pull forecast schedule's material release can also contain <GUIRef href="/baanerp/td/domains/pur.rtyp#immediate" role="enum">Immediate</GUIRef> lines if requirements from the past are not yet delivered. The pull call-off schedule only generates sequence shipping schedules and releases all the schedule lines whith the <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="enum">Firm</GUIRef> requirement type. Shipping is performed based on the EDI message BEM SEQ001.</Paragraph>
			<Paragraph><Emphasis><GUIRef href="/baanerp/tc/domains/scrd#ship.only" role="enum">Shipping Schedule Only</GUIRef>
				</Emphasis>:</Paragraph>
			<List><ListItem>Push schedules: this release type only generates shipping schedules. No planning data is released to the supplier. The shipping schedule only releases those schedule lines whose requirement type is <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="enum">Firm</GUIRef> or <GUIRef href="/baanerp/td/domains/pur.rtyp#immediate" role="enum">Immediate</GUIRef>, as calculated by the segment set. Schedule lines with the <GUIRef href="/baanerp/td/domains/pur.rtyp#planned" role="enum">Planned</GUIRef> requirement type are not included in the release. Shipping is carried out based on the EDI message BEM SHP001.</ListItem>
				<ListItem>Pull schedules: the pull call-off schedule generates the shipping schedule, releasing all the schedule lines, which are always <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="enum">Firm</GUIRef>. No planning data is released to the supplier. Shipping is performed based on the EDI message BEM SHP001.</ListItem>
			</List>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>EDI messages are only generated if the value of the <GUIRef href="/baanerp/td/pur/tdpur3102m000#tdpur302.wcom" role="field">Communication Channel</GUIRef> field 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">Item - Purchase Business Partner (tdipu0110m000)</GUIRef> session is set to EDI.</Paragraph>
			</Note>
		</GeneralSection>
	</GeneralSection>
	<RelatedTopics><SectionTitle>Related topics</SectionTitle>
		<RelTopic><Link href="/baanerp/td/onlinemanual/000006" role="manual">Segment sets</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/td/onlinemanual/000010" role="manual">Purchase schedules, basic data</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/000349" role="manual">Pull call-off schedules</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/td/onlinemanual/000350" role="manual">Purchase releases</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
