<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/td/onlinemanual/000350" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Purchase releases</Title>
		<Keyword><Level1>purchase schedule</Level1>
		</Keyword>
		<Keyword><Level1>purchase release</Level1>
		</Keyword>
	</Header>
	<AimSection><SectionTitle>Purchase release header statuses</SectionTitle>
		<Paragraph>In the <GUIRef href="/baanerp/td/pur/tdpur3120m000" role="session">Purchase Releases (tdpur3120m000)</GUIRef> session, <Link href="/baanerp/td/glossary/glossary#000351" role="glossary">purchase release</Link> headers are displayed. The headers all contain a release status that indicates which steps in the release procedure have already been carried out and what the next step must be. Naturally, the type of step to be taken also depends on the schedule type (push schedule, pull forecast schedule, or pull call-off schedule). A purchase release can have three statuses:</Paragraph>
		<List><ListItem><GUIRef href="/baanerp/tc/domains/edi.stat#preview" role="enum">Preview</GUIRef>: the purchase release contains lines which all have the release status <GUIRef href="/baanerp/tc/domains/edi.stat#preview" role="enum">Preview</GUIRef>, or lines of which some have the status <GUIRef href="/baanerp/tc/domains/edi.stat#preview" role="enum">Preview</GUIRef> and some have the status <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="enum">Scheduled</GUIRef>.</ListItem>
			<ListItem><GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="enum">Scheduled</GUIRef>: the purchase release is approved and contains lines which all have the release status <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="enum">Scheduled</GUIRef>.</ListItem>
			<ListItem><GUIRef href="/baanerp/tc/domains/edi.stat#send" role="enum">Sent</GUIRef>: the purchase release is printed/EDI messages are sent and contains lines which all have the release status <GUIRef href="/baanerp/tc/domains/edi.stat#send" role="enum">Sent</GUIRef>.</ListItem>
		</List>
	</AimSection>
	<GeneralSection><SectionTitle>Purchase release line (detail) statuses</SectionTitle>
		<Paragraph>In the <GUIRef href="/baanerp/td/pur/tdpur3121m000" role="session">Purchase Release - Lines (tdpur3121m000)</GUIRef> session and the <GUIRef href="/baanerp/td/pur/tdpur3522m000" role="session">Purchase Release Line - Details (tdpur3522m000)</GUIRef> session, these statuses represent the following:</Paragraph>
		<List><ListItem><GUIRef href="/baanerp/tc/domains/edi.stat#preview" role="enum">Preview</GUIRef>: the purchase release line in the <GUIRef href="/baanerp/td/pur/tdpur3121m000" role="session">Purchase Release - Lines (tdpur3121m000)</GUIRef> session and the linked release line detail(s) in the <GUIRef href="/baanerp/td/pur/tdpur3522m000" role="session">Purchase Release Line - Details (tdpur3522m000)</GUIRef> session, which can contain <Link href="/baanerp/td/glossary/glossary#000343" role="glossary">clustered</Link> schedule lines, are not approved.</ListItem>
		</List>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>For <Link href="/baanerp/td/glossary/glossary#000338" role="glossary">non-referenced schedules</Link> you can cluster schedule lines in the <GUIRef href="/baanerp/td/pur/tdpur3222m000" role="session">Generate Release Lines (tdpur3222m000)</GUIRef> session.</Paragraph>
		</Note>
		<List><ListItem><GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="enum">Scheduled</GUIRef>: the purchase release line and the linked release line detail(s) are approved.</ListItem>
		</List>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>For non-referenced schedules, you can approve the purchase release line, and consequently the linked release line detail(s), in the <GUIRef href="/baanerp/td/pur/tdpur3222m100" role="session">Approve Release Lines (tdpur3222m100)</GUIRef> session. For <Link href="/baanerp/td/glossary/glossary#000339" role="glossary">referenced schedules</Link>, SSA ERP automatically converts the schedule lines into a purchase release line and a release line-detail with the status Scheduled. The schedule lines are not clustered.</Paragraph>
		</Note>
		<List><ListItem><GUIRef href="/baanerp/tc/domains/edi.stat#send" role="enum">Sent</GUIRef>: the purchase release line with the status <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="enum">Scheduled</GUIRef> and the linked release line detail(s), are 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="field">Final Report</Link> check box selected, or EDI messages are prepared and sent by <GUIRef href="/baanerp/ec" role="package">Electronic Commerce</GUIRef>.</ListItem>
		</List>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>EDI messages are automatically prepared if a purchase release receives the status <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="enum">Scheduled</GUIRef> and you have selected the <Link href="/baanerp/td/pur/tdpur3102m000#tdpur302.demr" role="field">Release EDI Message Directly</Link> check box 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.</Paragraph>
		</Note>
	</GeneralSection>
	<GeneralSection><SectionTitle>Relation between purchase release header and generating releases</SectionTitle>
		<ProcedureList><ListIntro>When running the <GUIRef href="/baanerp/td/pur/tdpur3222m000" role="session">Generate Release Lines (tdpur3222m000)</GUIRef> session for non-referenced schedules, or when generating schedule lines for referenced schedules, SSA ERP first checks whether a purchase release exists in the <GUIRef href="/baanerp/td/pur/tdpur3120m000" role="session">Purchase Releases (tdpur3120m000)</GUIRef> session for the combination of buy-from business partner, ship-from business partner, release type, shipment based/ delivery based schedule, and communication method. If no purchase release exists, SSA ERP takes the following steps:</ListIntro>
			<ListItem>A new purchase release is created in the <GUIRef href="/baanerp/td/pur/tdpur3120m000" role="session">Purchase Releases (tdpur3120m000)</GUIRef> session with a <Link href="/baanerp/td/glossary/glossary#000000000000008" role="glossary">release revision number</Link> of zero and a release status of <GUIRef href="/baanerp/tc/domains/edi.stat#preview" role="enum">Preview</GUIRef>, for non-referenced schedules, or <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="enum">Scheduled</GUIRef>, for referenced schedules.</ListItem>
			<ListItem>A purchase release line is created in the <GUIRef href="/baanerp/td/pur/tdpur3121m000" role="session">Purchase Release - Lines (tdpur3121m000)</GUIRef> session with the release status <GUIRef href="/baanerp/tc/domains/edi.stat#preview" role="enum">Preview</GUIRef> (non-referenced), or <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="enum">Scheduled</GUIRef> (referenced).</ListItem>
			<ListItem>(A) purchase release line detail record(s) is/are inserted 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="enum">Preview</GUIRef> or <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="enum">Scheduled</GUIRef>. If the schedule is a non-referenced schedule, the records in the <GUIRef href="/baanerp/td/pur/tdpur3522m000" role="session">Purchase Release Line - Details (tdpur3522m000)</GUIRef> session can be clustered schedule lines.</ListItem>
		</ProcedureList>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>If the referenced schedule is a <Link href="/baanerp/td/glossary/glossary#000034" role="glossary">sequence shipping schedule</Link>, only a purchase release header is created. No purchase release lines and purchase release line detail records are created. The reason for this is that, usually, a release is sent by item. Items in a sequence shipping schedules, however, are required for a combination of vehicle number (VIN), line station, and assembly kit. For this reason, 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 <GUIRef href="/baanerp/td/pur/tdpur3523m000" role="session">Production Synchronous Calls (tdpur3523m000)</GUIRef> session. See also: <Link href="/baanerp/td/onlinemanual/000357" role="manual">To create and update sequence shipping schedule lines</Link>.</Paragraph>
		</Note>
		<List><ListIntro>If a purchase release already exists, dependent on the purchase release's status, when running the <GUIRef href="/baanerp/td/pur/tdpur3222m000" role="session">Generate Release Lines (tdpur3222m000)</GUIRef> session for non-referenced schedules, or when generating schedule lines for referenced schedules, SSA ERP takes the following steps:</ListIntro>
			<ListItem>If the purchase release's highest revision in the <GUIRef href="/baanerp/td/pur/tdpur3120m000" role="session">Purchase Releases (tdpur3120m000)</GUIRef> session has the status <GUIRef href="/baanerp/tc/domains/edi.stat#preview" role="enum">Preview</GUIRef>, the release lines in the <GUIRef href="/baanerp/td/pur/tdpur3121m000" role="session">Purchase Release - Lines (tdpur3121m000)</GUIRef> session, which can have the status <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="enum">Scheduled</GUIRef> and/or <GUIRef href="/baanerp/tc/domains/edi.stat#preview" role="enum">Preview</GUIRef>, and the release line details in the <GUIRef href="/baanerp/td/pur/tdpur3522m000" role="session">Purchase Release Line - Details (tdpur3522m000)</GUIRef> session, are simply updated.</ListItem>
			<ListItem>If the purchase release's highest revision has the status <GUIRef href="/baanerp/tc/domains/edi.stat#send" role="enum">Sent</GUIRef>, a new release revision is created with status Preview or Scheduled.</ListItem>
			<ListItem>If the purchase release's highest revision has the status <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="enum">Scheduled</GUIRef>, you must either send the purchase release or run the <GUIRef href="/baanerp/td/pur/tdpur3222m100" role="session">Approve Release Lines (tdpur3222m100)</GUIRef> session with the <GUIRef href="/baanerp/td/pur/tdpur3222m100#reb.int.view" role="field">Rebuild Release</GUIRef> check box selected. If you choose the last option, the release lines are generated again for the specific purchase release. The purchase release keeps the same release revison number as the previous one and receives the status <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="enum">Scheduled</GUIRef>.</ListItem>
		</List>
		<Note><SectionTitle>Note</SectionTitle>
			<List><ListItem>Rebuilding the release in the <GUIRef href="/baanerp/td/pur/tdpur3222m100" role="session">Approve Release Lines (tdpur3222m100)</GUIRef> session is only applicable to non-referenced schedules.</ListItem>
				<ListItem>The way in which SSA ERP handles schedule lines in a purchase release also depends on the value of the <Link href="/baanerp/td/pur/tdpur0100m300#tdpur000.tprl" role="field">Tax Purchase Release Line</Link> check box in the <GUIRef href="/baanerp/td/pur/tdpur0100m300" role="session">Purchase Contract Parameters (tdpur0100m300)</GUIRef> session.</ListItem>
			</List>
		</Note>
		<Paragraph>Even if the status of the purchase release's highest revision is not <GUIRef href="/baanerp/tc/domains/edi.stat#send" role="enum">Sent</GUIRef>, when generating release lines, SSA ERP can still generate new revision numbers. This occurs when schedules with various <Link href="/baanerp/td/glossary/glossary#000355" role="glossary">schedule issue dates</Link> are stored under one purchase release. Any schedule with a schedule issue date different from the issue date of the last release, receives a new revision number.</Paragraph>
		<Paragraph>If, after sending a release, the released requirements of the non-referenced schedule are deleted, you can run the <GUIRef href="/baanerp/td/pur/tdpur3222m000" role="session">Generate Release Lines (tdpur3222m000)</GUIRef> session to create a release with no requirements. Because no lines are available for clustering, SSA ERP creates a release line for the item with a quantity of zero in the <GUIRef href="/baanerp/td/pur/tdpur3522m000" role="session">Purchase Release Line - Details (tdpur3522m000)</GUIRef> session. In this way, the supplier is informed about the cancelation of the previously communicated requirements. For referenced schedules, SSA ERP automatically communicates the cancelation to the supplier. See also: <Link href="/baanerp/td/onlinemanual/000372" role="manual">Zero required quantity for sales schedule lines</Link>.</Paragraph>
		<Paragraph>Pull call-off schedules, for which no schedule issue dates are defined, are automatically stored under the last purchase release revision with the status <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="enum">Scheduled</GUIRef>. Because call-off schedules are not released based on schedule issue date, it is better to select the <GUIRef href="/baanerp/td/pur/tdpur3102m000#tdpur302.demr" role="field">Release EDI Message Directly</GUIRef> check box 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. If you select the <GUIRef href="/baanerp/td/pur/tdpur3102m000#tdpur302.demr" role="field">Release EDI Message Directly</GUIRef> check box, SSA ERP automatically generates EDI messages for <GUIRef href="/baanerp/tc/domains/edi.stat#scheduled" role="enum">Scheduled</GUIRef> purchase release lines, which <GUIRef href="/baanerp/ec" role="package">Electronic Commerce</GUIRef> sends to the supplier.</Paragraph>
		<Paragraph>For non-referenced schedules that must be sent in a purchase release, SSA ERP retrieves a purchase schedule's warehouse from the <GUIRef href="/baanerp/td/pur/tdpur3110m000" role="session">Purchase Schedules (tdpur3110m000)</GUIRef> session. For referenced schedules, however, SSA ERP retrieves the purchase schedule's warehouse from the <GUIRef href="/baanerp/td/pur/tdpur3111m000" role="session">Purchase Schedule - Lines (tdpur3111m000)</GUIRef> session, which can differ from line to line. As a result, the schedule lines of the same pull call-off schedule can be stored under different purchase releases.</Paragraph>
	</GeneralSection>
	<Note><SectionTitle>Note</SectionTitle>
		<List><ListItem>You can print the differences between two release revisions of a purchase release in the <Link href="/baanerp/td/pur/tdpur3422m100" role="session">Print Purchase Release Variance Reports (tdpur3422m100)</Link> session.</ListItem>
			<ListItem>You can delete purchase release revisions in the <GUIRef href="/baanerp/td/pur/tdpur3222m200" role="session">Delete Purchase Revisions (tdpur3222m200)</GUIRef> session.</ListItem>
		</List>
	</Note>
	<RelatedTopics><SectionTitle>Related topics</SectionTitle>
		<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/000346" role="manual">Purchase schedule release types</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/td/onlinemanual/000006" role="manual">Segment sets</Link>
		</RelTopic>
		<RelTopic><Link href="/baanerp/td/onlinemanual/000351" role="manual">Clustering purchase schedule lines</Link>
		</RelTopic>
	</RelatedTopics>
</ManualTopic>
