<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tc/mcs/tcmcs2103m000" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Purchase Type Exceptions (tcmcs2103m000)</Title>
	</Header>
	<HelpTopic><AimSection><Paragraph>Use this session to <Link href="/baanerp/tf/glossary/glossary#000433" role="glossary">purchase type</Link> exceptions. Purchase type exceptions link purchase types (and through the purchase type, a control account) to transactions that involve specific details for an invoice-from business partner and order origin.</Paragraph>
		</AimSection>
		<GeneralSection><Paragraph>Transactions for which you do not define a purchase type exception are posted to the control account linked to the default purchase type for the business partner group.</Paragraph>
			<List><ListIntro>You can define exceptions for various logistic order origins, such as Purchase, Project, and Freight. You can define exceptions for the following types of order details:</ListIntro>
				<ListItem>Item groups.</ListItem>
				<ListItem>Items.</ListItem>
				<ListItem>Project categories.</ListItem>
				<ListItem>Projects.</ListItem>
			</List>
			<Paragraph>If the order origin is <GUIRef href="" role="manual">Purchase</GUIRef>, you can indicate whether the exception is valid for direct delivery orders.</Paragraph>
			<Paragraph>You can specify exceptions that apply to a specific business partner and you can specify exceptions that apply generally to all the transactions. To define general exceptions, leave the <GUIRef href="/baanerp/tc/mcs/tcmcs2103m000#tcmcs203.ifbp" role="formfield">Invoice-from BP</GUIRef> field empty.</Paragraph>
			<Paragraph>For each exception, you can indicate the priority. If more than one exception is found, SSA ERP uses the details of the exception with the highest priority. For example, if the exception for an item has a higher priority than the exception for a specific project, transactions concerning both the item and the project are posted to the control account linked to the purchase type specified for the item.</Paragraph>
			<Paragraph>Each combination of order origin, item, item group, project category, project, direct delivery indicator, and purchase type that you define as an exception, must be unique.</Paragraph>
		</GeneralSection>
		<RelatedTopics><SectionTitle>Related topics</SectionTitle>
			<RelTopic><Link href="/baanerp/tf/onlinemanual/000400" role="manual">Control accounts</Link>
			</RelTopic>
			<RelTopic><Link href="/baanerp/tf/onlinemanual/000401" role="manual">To set up control accounts</Link>
			</RelTopic>
		</RelatedTopics>
	</HelpTopic>
	<Fields><FieldHelp ID="tcmcs203.ifbp"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Invoice-from BP</Title>
			</Header>
			<FuncDesc>The invoice-from business partner to whom the exceptions apply.</FuncDesc>
			<SimpleSection><Paragraph>To define exceptions that apply to all purchase invoices independent of the invoice-from business partner, leave this field empty.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tcmcs203.orig"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Order Origin</Title>
			</Header>
			<FuncDesc>The logistic origin of the order.</FuncDesc>
			<SimpleSection><List><ListIntro>The order origin can be:</ListIntro>
					<ListItem>Purchase.</ListItem>
					<ListItem>Internal invoice.</ListItem>
					<ListItem>Freight.</ListItem>
					<ListItem>Project.</ListItem>
					<ListItem>All origins.</ListItem>
				</List>
			</SimpleSection>
			<Note><SectionTitle>Note</SectionTitle>
				<Paragraph>For internal invoices, you cannot define exceptions. Internal invoices are always posted to the control account linked to the default purchase type of the business partner group.</Paragraph>
			</Note>
		</FieldHelp>
		<FieldHelp ID="tcmcs203.prio"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Priority</Title>
			</Header>
			<FuncDesc>The priority of the exception. A low value indicates a high priority. The value 1 indicates the highest priority.</FuncDesc>
			<SimpleSection><Paragraph>For example, if the exception for an item has priority 1 and the exception for a specific project has priority 2, the purchase type defined for the item is the default purchase type for the order lines with both the item and the project.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tcmcs203.citg"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Item Group</Title>
			</Header>
			<FuncDesc>Subject to the priority rules, the purchase type for this item group is the default purchase type for the order line.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="tcmcs203.item"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Item</Title>
			</Header>
			<FuncDesc>Subject to the priority rules, the purchase type for this item is the default purchase type for the order line.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="tcmcs203.catg"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Project Category</Title>
			</Header>
			<FuncDesc>Subject to the priority rules, the purchase type for this project is the default purchase type for the order line.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="tcmcs203.cprj"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Project</Title>
			</Header>
			<FuncDesc>Subject to the priority rules, the purchase type for this project is the default purchase type for the order line.</FuncDesc>
		</FieldHelp>
		<FieldHelp ID="tcmcs203.ddel"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Direct Delivery</Title>
			</Header>
			<FuncDesc>If this check box is selected, subject to the priority rules, the purchase type is the default purchase type for order lines with direct delivery.</FuncDesc>
			<SimpleSection><Paragraph>If this check box is cleared, subject to the priority rules the purchase is the default purchase type for the order lines for all orders.</Paragraph>
			</SimpleSection>
		</FieldHelp>
		<FieldHelp ID="tcmcs203.ptyp"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Purchase Type</Title>
			</Header>
			<FuncDesc>The purchase type that SSA ERP uses to determine the control account to be used for the invoice transactions.</FuncDesc>
			<SimpleSection><Paragraph>The transactions are posted to the control account that you linked to the purchase type in the <GUIRef href="/baanerp/tf/acp/tfacp0515m000" role="session">Control Accounts by BP Group (tfacp0515m000)</GUIRef> session.</Paragraph>
			</SimpleSection>
		</FieldHelp>
	</Fields>
	<FormCommands><CommandHelp ID="increment.prio.as.fr.mark"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Increment Priority</Title>
			</Header>
			<FuncDesc>Increases each priority number by one, starting at the selected line. For example, you can use this to insert a line between two existing lines with consecutive priorities.</FuncDesc>
		</CommandHelp>
		<CommandHelp ID="renumber"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Renumber</Title>
			</Header>
			<FuncDesc>Renumbers the priorities to remove any gaps in the numbers. For example, if you define exceptions with the priorities 1, 4, 6, 7, then after renumbering the priorities will be 1, 2, 3, 4.</FuncDesc>
		</CommandHelp>
		<CommandHelp ID="tcmcs2203m000"><Header>
				<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Copy Purchase Type Exceptions</Title>
			</Header>
			<FuncDesc>Starts the <GUIRef href="/baanerp/tc/mcs/tcmcs2203m000" role="session">Copy Purchase Type Exceptions (tcmcs2203m000)</GUIRef> session, which you can use to copy the purchase type exceptions that you defined for the invoice-from business partner and order origin, to a different order origin of the same business partner or to an order origin for a different invoice-from business partner.</FuncDesc>
		</CommandHelp>
	</FormCommands>
</Session>
