<?xml version="1.0" encoding="utf-8"?>
<Glossary ID="/baanerp/td/glossary/glossary" xml:lang="en">
	<Header>
		<Title xmlns:ssa="http://www.ssaglobal.com" xmlns:HTML="http://www.w3.org/TR/REC-html40">Glossary for the TD package</Title>
	</Header>
	<GlossaryEntry ID="000328" Version="B60adoc1" ContextApps="td"><Term>acceptance rule</Term>
		<Definition>If an approval rule is based on acceptance rules, SSA ERP automatically approves a purchase order that meets a valid rule. If you define approval rules based on acceptance, you define for what combination of data elements you want SSA ERP to approve the purchase order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Accessory.td" Version="B60asy04" ContextApps="td"><Term>accessory</Term>
		<Definition>A list type that permits the definition of related inventory items or kits that are offered to business partners when they order an end item.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="376" Version="6.0a" ContextApps="td"><Term>account manager</Term>
		<Definition>The manager who is responsible for maintaining relations with accounts, or business partners.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000129" Version="B60adoc1" ContextApps="td"><Term>activity</Term>
		<Definition>A step that you must carry out for the purchase/sales order type. An activity represents the sessions or the manual action that you must carry our for the purchase/sales order type.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="ActiviSMI.td" Version="B60adoc0" ContextApps="td"><Term>activity</Term>
		<Definition>An action that must be, or is carried out for a trade relation or marketing project, for example paying for calls and registering phone calls or complaints.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000232" Version="B60asy04" ContextApps="td"><Term>activity code</Term>
		<Definition>The code that identifies an activity within SSA ERP.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="ActiviDefini.td" Version="B60asy04" ContextApps="td"><Term>activity definitions</Term>
		<Definition>The description of an activity. An activity is any action carried out in connection with a business relation or marketing project, for example paying for calls and registering phone calls or complaints. As the data to be recorded can vary from one activity to another, you can link a separate feature definition or feature set to each activity.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000131" Version="B60asy04" ContextApps="td"><Term>activity number</Term>
		<Definition>A number that expresses the sequence for each activity in the business process.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000102" Version="B60asy04" ContextApps="td"><Term>actual delivery date</Term>
		<Definition>The date on which the ordered goods are delivered.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="AdditiCosts.td" Version="B60asy04" ContextApps="td"><Term>additional costs</Term>
		<Definition>The extra cost items that can be placed on an order after the last item has been recorded.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000370" Version="B60adoc1" ContextApps="td"><Term>additional rate quantity by unit</Term>
		<Definition>A quantity by unit against which you can define freight rates. You can choose from the units defined in <GUIRef href="/baanerp/tc" role="package">Common Data</GUIRef>. Many freight rates are based on distance and weight. Additional quantities/units enable you to define rates that are based on other units, such as volume, or define rates that are based on combinations of distance, weight, and other units.</Definition>
		<SimpleSection><Paragraph>Example 1</Paragraph>
			<Paragraph><Emphasis>Freight rate by additional quantity/unit</Emphasis>:</Paragraph>
			<Paragraph><GUIRef href="/baanerp/td/pcg/tdpcg0150m000#tdpcg050.aruq" role="formfield">Additional Rate Quantity</GUIRef>: 1 pallet, <GUIRef href="/baanerp/td/pcg/tdpcg0150m000#tdpcg050.dist" role="formfield">Distance</GUIRef>: 1000 km</Paragraph>
			<Paragraph><GUIRef href="/baanerp/td/pcg/tdpcg0150m000#tdpcg050.vaad" role="formfield">Amount by Distance</GUIRef>: 10</Paragraph>
			<Paragraph></Paragraph>
			<Paragraph>Example 2</Paragraph>
			<Paragraph><Emphasis>Freight rates by combinations of units by distance/zone</Emphasis>:</Paragraph>
			<Paragraph><GUIRef href="/baanerp/td/pcg/tdpcg0150m000#tdpcg050.wght" role="formfield">Weight</GUIRef>: 10 kg</Paragraph>
			<Paragraph><GUIRef href="/baanerp/td/pcg/tdpcg0150m000#tdpcg050.aruq" role="formfield">Additional Rate Quantity</GUIRef>: 1 m³</Paragraph>
			<Paragraph><GUIRef href="/baanerp/td/pcg/tdpcg0150m000#tdpcg050.brty" role="formfield">Break Type</GUIRef>: <GUIRef href="/baanerp/td/domains/pcg.brty#min" role="enum">Minimum</GUIRef>
			</Paragraph>
			<TABLE border="1"><TBODY><TR><TD><GUIRef href="/baanerp/td/pcg/tdpcg0150m000#tdpcg050.dist" role="formfield">Distance</GUIRef>:</TD>
						<TD width="28">0</TD>
						<TD width="33">100</TD>
						<TD width="39">500</TD>
					</TR>
					<TR><TD><GUIRef href="/baanerp/td/pcg/tdpcg0150m000#tdpcg050.vaad" role="formfield">Amount by Distance</GUIRef>
						</TD>
						<TD width="28">10</TD>
						<TD width="33">15</TD>
						<TD width="39">20</TD>
					</TR>
					<TR><TD><GUIRef href="/baanerp/td/pcg/tdpcg0150m000#tdpcg050.vaaw" role="formfield">Amount by Weight</GUIRef>
						</TD>
						<TD width="28">5</TD>
						<TD width="33">5</TD>
						<TD width="39">10</TD>
					</TR>
					<TR><TD><GUIRef href="/baanerp/td/pcg/tdpcg0150m000#tdpcg050.amru" role="formfield">Amount by Additional Rate Unit</GUIRef>
						</TD>
						<TD width="28">5</TD>
						<TD width="33">5</TD>
						<TD width="39">7</TD>
					</TR>
				</TBODY>
			</TABLE>
			<Paragraph>In this example, freight rates are based on distance by weight and volume. Shipment SH0001, from Amsterdam to Rotterdam, includes the following details: Distance: 70 km, Weight: 50 kg, Volume: 7 m³</Paragraph>
			<Paragraph>The freight costs for shipment SH0001 are:</Paragraph>
			<Formula><Paragraph UserLevel="Novice" UserType="Taskuser"> 10 * 70 (distance) + 5 * 50 (weight) + 5 * 7 (volume) = 985 </Paragraph>
			</Formula>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="AgreemGroup.td" Version="B60asy04" ContextApps="td"><Term>agreement group</Term>
		<Definition>A group of relations to which the same commission/rebate agreements are linked.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000186" Version="B60asy04" ContextApps="td"><Term>alternative quantity</Term>
		<Definition>The total quantity to be budgeted for the specified year part, expressed in an alternative unit.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000123" Version="B60asy04" ContextApps="td"><Term>amount</Term>
		<Definition>The budgeted turnover amount in a specific period, expressed in the home currency.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000311" Version="B60asy04" ContextApps="td"><Term>append structure</Term>
		<Definition>Copy an existing category structure into another existing structure, combining both structures in the target category.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000138" Version="B60asy04" ContextApps="td"><Term>approval process</Term>
		<Definition>A user-defined procedure that identifies the approval loop for a document. A formal approval process is typically and usually identifies the required approval levels and the appropriate approvers.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000327" Version="B60adoc1" ContextApps="td"><Term>approval rule</Term>
		<Definition>A combination of data elements, such as buy-from business partner, buyer, planner, effective date, expiry date, and amount, based on which SSA ERP approves purchase orders. The approval rules, on their turn, are based on acceptance rules or exception rules.</Definition>
		<SimpleSection></SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000139" Version="B60adoc1" ContextApps="td"><Term>approved</Term>
		<Definition>The requisition status when an approver approves the requisition, or requisition line.</Definition>
		<SimpleSection><Paragraph>An approved requisition can be resubmitted for further approval, or it can be converted.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000112" Version="B60asy04" ContextApps="td"><Term>approved quantity</Term>
		<Definition>The number of delivered items that is approved.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000084" Version="B60adoc0" ContextApps="td"><Term>approved source list</Term>
		<Definition>A list of either buy-from business partners approved to deliver certain items, or items for which a certain buy-from business partner is approved.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000166" Version="B60asy04" ContextApps="td"><Term>attention code</Term>
		<Definition>The messages linked to trade relations, marketing projects, and so on that draw your attention to special events or circumstances.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="BackOrder.td" Version="B60adoc0" ContextApps="td"><Term>back order</Term>
		<Definition>An unfilled customer order, or partial delivery at a later date. A demand for an item whose inventory is insufficient to satisfy demand.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="BackorQuanti.td" Version="B60asy04" ContextApps="td"><Term>back order quantity</Term>
		<Definition>The number of items to be delivered at a later stage. This quantity does not need to be equal to the rejected quantity.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000133" Version="B60asy04" ContextApps="td"><Term>base price</Term>
		<Definition>The price of the goods stored in a warehouse. The base price is independent of the price factor, discounts, the order quantity, and value and is stated in the home currency and inventory unit.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000342" Version="B60adoc1" ContextApps="td"><Term>blanket warehousing order</Term>
		<Definition>A warehousing order that is generated during the creation of a push schedule and that contains:</Definition>
		<SimpleSection><List><ListItem>A position number and sequence number of zero.</ListItem>
				<ListItem>An item as defined on the purchase schedule.</ListItem>
				<ListItem>An order quantity equal to the quantity as defined on the purchase contract line.</ListItem>
				<ListItem>An empty planned delivery date and planned receipt date, but a contract date similar to the purchase contract date.</ListItem>
				<ListItem>A lot selection defined as Any.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000135" Version="B60adoc0" ContextApps="td"><Term>book price</Term>
		<Definition>The price for the item according to the standard price book, increased by an <Link href="/baanerp/tc/glossary/glossary#000450" role="glossary" Update="No">upgrade price</Link> if applicable. The default price for an item is stored in the default price book.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000371" Version="B60adoc1" ContextApps="td"><Term>break type</Term>
		<Definition>An entity used to specify how breaks between ranges of entities such as distances, amounts, or ordered quantities of items are defined. A break, in this case, is the first or the last number of a range. A break type has either of the following values:</Definition>
		<SimpleSection><Paragraph><GUIRef href="/baanerp/td/domains/pcg.brty#min" role="enum">Minimum</GUIRef> The break is the lowest number of a range.</Paragraph>
		</SimpleSection>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<TABLE border="1"><THEAD><TR><TD colspan="2" width="256">Break type minimum</TD>
					</TR>
				</THEAD>
				<TBODY><TR><TH width="133">Ordered quantity</TH>
						<TH width="119">Discount</TH>
					</TR>
					<TR><TD width="133">10</TD>
						<TD width="119">3%</TD>
					</TR>
					<TR><TD width="133">50</TD>
						<TD width="119">5%</TD>
					</TR>
				</TBODY>
			</TABLE>
			<Paragraph>In this case, the breaks are 10 and 50. Ordered quantities &gt;= 10 and &lt; 50 get a 3% discount. Ordered quantities of 50 and more get a 5% discount.</Paragraph>
		</ExampleSection>
		<SimpleSection><Paragraph><GUIRef href="/baanerp/td/domains/pcg.brty#upto" role="enum">Up To</GUIRef> The break is the highest number of a range.</Paragraph>
		</SimpleSection>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<TABLE border="1"><THEAD><TR><TD colspan="2" width="257">Break type up to</TD>
					</TR>
				</THEAD>
				<TBODY><TR><TH width="132">Distance</TH>
						<TH width="121">Freight rate</TH>
					</TR>
					<TR><TD width="132">100</TD>
						<TD width="121">10</TD>
					</TR>
					<TR><TD width="132">1000</TD>
						<TD width="121">50</TD>
					</TR>
				</TBODY>
			</TABLE>
			<Paragraph>In this case, the breaks are 100 and 1000. For distances &lt;= 100, the rate is 10. For distances &gt; 100 and &lt;= 1000, the rate is 50.</Paragraph>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="SalesBudget.td" Version="B60asy04" ContextApps="td"><Term>budget</Term>
		<Definition>A plan that includes the budgeted quantities and/or amounts by period for the sorts selected; the budgeted or expected sales or purchase figures.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000119" Version="B60asy04" ContextApps="td"><Term>business partner 2</Term>
		<Definition>The business partner, only with a different label and a different function.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000006" Version="B60asy04" ContextApps="td"><Term>business partner's contact</Term>
		<Definition>The employee or department of the business partner that is used as the contact to your own company or department in case of problems or questions.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000242" Version="B60asy04" ContextApps="td"><Term>business procedure</Term>
		<Definition>The designation of a set of logically related tasks or activities that are performed to achieve a defined business outcome. A business procedure consists of the sessions or manual activities to be carried out.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000127" Version="B60adoc0" ContextApps="td"><Term>business process</Term>
		<Definition>The activities and steps that must be carried out to get a specific result. For example, the steps of the order procedure. The steps are expressed by means of sessions or manual actions.</Definition>
		<SimpleSection><Paragraph>You can link a business process to a workflow.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000002" Version="B60asy04" ContextApps="td"><Term>business-partner order reference</Term>
		<Definition>The order number created by your business partner to represent the requirement in the business partner's system. The business partner order reference number ensures that you compare the same records.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000060" Version="B60asy04" ContextApps="td"><Term>business-partner prices/discounts</Term>
		<Definition>A business partner can be selected as parent. This means that the order discount specified for this business partner is the input for the relevant order.</Definition>
		<SimpleSection><Paragraph>If a parent business partner is defined on an order, SSA ERP first looks for the order discount defined for the parent business partner.</Paragraph>
			<Paragraph>If an order discount is not specified for the parent or if no parent is specified, SSA ERP looks for the order discount that is specified for the business partner on the order.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000061" Version="B60asy04" ContextApps="td"><Term>business-partner texts</Term>
		<Definition>A business partner can be selected as 'parent'. This means that the texts that are specified for this business partner are the input for the relevant order.</Definition>
		<SimpleSection><Paragraph>If a parent business partner is defined on an order, SSA ERP first looks for texts as defined for the parent business partner.</Paragraph>
			<Paragraph>If texts are not specified for the parent or if no parent is specified, SSA ERP looks for the texts that are specified for the business partner on the order.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="Buyer.td" Version="B60adoc0" ContextApps="td"><Term>buyer</Term>
		<Definition>The employee of your company who is the contact to the concerned buy-from business partner. The buyer is also known as the purchasing agent.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000222" Version="B60asy04" ContextApps="td"><Term>called amount</Term>
		<Definition>The actual ordered quantity multiplied by the price per unit.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000218" Version="B60asy04" ContextApps="td"><Term>called quantity</Term>
		<Definition>The number of items currently ordered.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000199" Version="B60asy04" ContextApps="td"><Term>call-off</Term>
		<Definition>To call up goods from a business partner based on a purchase schedule. Call-off involves sending a message (EDI) to notify a business partner that the scheduled items must be delivered. The message contains the item quantity and the date and time they must be delivered.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000140" Version="B60asy04" ContextApps="td"><Term>canceled</Term>
		<Definition>A requisition with the <GUIRef href="/baanerp/td/domains/pur.rqst#created" role="enum">Created</GUIRef>, <GUIRef href="/baanerp/td/domains/pur.rqst#modified" role="enum">Modified</GUIRef>, or <GUIRef href="/baanerp/td/domains/pur.rqst#rejected" role="enum">Rejected</GUIRef> status can be canceled by the requester. A canceled requisition cannot be changed.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000026" Version="B60asy04" ContextApps="td"><Term>capacity time unit</Term>
		<Definition>The time unit in which the ship-from business partner capacity is expressed.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000087" Version="B60asy04" ContextApps="td"><Term>carrier</Term>
		<Definition>The company responsible for the transportation of goods to the ship-to business partner.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000304" Version="B60asy04" ContextApps="td"><Term>catalog</Term>
		<Definition>The highest level of a category structure. A catalog contains one or more categories, which contain items or subcategories. A catalog cannot be a member of another category.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000301" Version="B60asy04" ContextApps="td"><Term>category</Term>
		<Definition>A classification or division of items. The classification can be by form, fit, or function. Categories are used in catalogs. The highest level category is referred to as a catalog.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000062" Version="B60adoc1" ContextApps="td"><Term>change order sequence number</Term>
		<Definition>An optional number that is used to assign the occurrence of changes to a purchase order or a sales order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000063" Version="B60adoc1" ContextApps="td"><Term>change reason</Term>
		<Definition>The reason that can be assigned to a changed purchase order (line) or sales order (line).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000064" Version="B60adoc1" ContextApps="td"><Term>change type</Term>
		<Definition>The indicator of the type of change of a changed purchase order (line) or sales order (line).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000089" Version="B60asy04" ContextApps="td"><Term>changed delivery date</Term>
		<Definition>The new delivery date that is used if the supplier cannot comply with the agreed delivery date and states a new delivery date. Together with the planned and/or confirmed delivery date, the changed delivery date is the basis for determining the vendor rating, and the planned inventory movements. In addition, this date is also used in the reminder procedure.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="ClaimNote.td" Version="B60asy04" ContextApps="td"><Term>claim note</Term>
		<Definition>The notes printed to notify the buy-from business partner if the actual delivered quantity is less than the quantity on the packing slip</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000343" Version="B60adoc1" ContextApps="td"><Term>clustering</Term>
		<Definition>Grouping several schedules lines to send the lines in one purchase release.</Definition>
		<SimpleSection><Paragraph>For clustering, first the next schedule issue date, according to the issue pattern, is determined. Next, the schedule lines are clustered based on the segment time unit, and the segment length, derived from the segment set.</Paragraph>
		</SimpleSection>
		<Note><SectionTitle>Note</SectionTitle>
			<Paragraph>Clustering only applies to non-referenced schedules.</Paragraph>
		</Note>
	</GlossaryEntry>
	<GlossaryEntry ID="CollecOrder.td" Version="B60adoc1" ContextApps="td"><Term>collect order</Term>
		<Definition>An order type in which goods are immediately issued from inventory upon order entry. The goods are then immediately collected by the customer. The related transactions are immediately concluded when the sales order lines are created.</Definition>
		<SimpleSection><Paragraph>If you create and save a collect sales order, SSA ERP sets the sales order status to Delivered. At the same time, SSA ERP creates a warehouse order and sets the status of the warehouse order to Shipped. The warehouse order type is the warehouse order type that is linked to the sales order type.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000320" Version="B60asy04" ContextApps="td"><Term>commingle</Term>
		<Definition>To group a number of purchase orders that originate from different sources, into a single purchase order. Commingling reduces the number of purchase orders and enables you to obtain the best available prices and discounts.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Commission.td" Version="B60asy04" ContextApps="td"><Term>commission</Term>
		<Definition>The amount of money to be paid to an employee (sales representative) or buy-from business partner (agent) for closing a sales order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="CommisAgreem.td" Version="B60adoc0" ContextApps="td"><Term>commission agreement</Term>
		<Definition>A rate agreed to be paid as commission to an employee (sales representative) or buy-from business partner (agent) for the sale of a particular item (or item group).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000125" Version="B60asy04" ContextApps="td"><Term>commission amount</Term>
		<Definition>The amount of money to be paid to an employee (sales representative) or buy-from business partner (agent) for closing a sales order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="CommisGroup.td" Version="B60asy04" ContextApps="td"><Term>commission/rebate group</Term>
		<Definition>A set of items that is grouped and then linked to an agreement.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Competitors.td" Version="B60adoc0" ContextApps="td"><Term>competitor</Term>
		<Definition>A company that competes for the same sales orders. Generally, a competitor operates in the same market segment as your company.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000174" Version="B60adoc0" ContextApps="td"><Term>configuration date</Term>
		<Definition>The date on which the bill of material is exploded.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000221" Version="B60asy04" ContextApps="td"><Term>confirmed back order</Term>
		<Definition>An order created for any order quantity that cannot immediately be delivered due to inventory shortages.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000086" Version="B60asy04" ContextApps="td"><Term>confirmed delivery date</Term>
		<Definition>The delivery date for the items, which is confirmed by the buy-from business partner.</Definition>
		<SimpleSection><List><ListIntro>This date is used for several purposes:</ListIntro>
				<ListItem>As one of the bases by which the vendor rating is determined.</ListItem>
				<ListItem>As the default value for the confirmed delivery date on the order lines.</ListItem>
				<ListItem>As the reference date for the printing of reminders.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="Contract.td" Version="B60asy04" ContextApps="td"><Term>contract</Term>
		<Definition>A SSA ERP term for the agreement between two parties to purchase or sell an unspecified quantity of material over a certain period of time. A contract may be associated with one or more purchase orders, sales orders, or schedules.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="ContraAcknow.td" Version="B60asy04" ContextApps="td"><Term>contract acknowledgments</Term>
		<Definition>An acknowledgment sent to suppliers to confirm that the contract is closed (concluded).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000204" Version="B60asy04" ContextApps="td"><Term>contract date</Term>
		<Definition>The date on which the contract is entered in the system.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="ContraLine.td" Version="B60asy04" ContextApps="td"><Term>contract line</Term>
		<Definition>An agreement of one customer with one supplier, about both commercial and logistic conditions, related to the supply of one item, during a period of time.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000136" Version="B60asy04" ContextApps="td"><Term>contract price</Term>
		<Definition>The price agreed upon in a sales contract, a purchase contract, or a request-for- quotation (RFQ).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000214" Version="B60asy04" ContextApps="td"><Term>contract quantity</Term>
		<Definition>The quantity that must be delivered according to the agreements of the contract. The contract quantity must always be greater than zero.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000170" Version="B60asy04" ContextApps="td"><Term>control state</Term>
		<Definition>The list fields that you need to fill in when you enter an order or order line.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="ConverFactor.td" Version="B60asy04" ContextApps="td"><Term>conversion factor</Term>
		<Definition>The multiplication factor used to convert an alternative unit to the base unit. The conversion factor is calculated as follows:</Definition>
		<SimpleSection><Formula><Paragraph UserLevel="Novice" UserType="Taskuser">(alternative unit/base unit)</Paragraph>
			</Formula>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000141" Version="B60asy04" ContextApps="td"><Term>converted</Term>
		<Definition>When the requisition is approved and a conversion type is linked to it, this status is assigned during the conversion process.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="CostOrder.td" Version="B60adoc0" ContextApps="td"><Term>cost order</Term>
		<Definition>A type of order that can be used to charge separate, extra costs. Extra costs are, for example, accounting expenses, clearance charges, costs of design, and freight expenses. A cost order does not contain physical items.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="CostSetsLine.td" Version="B60asy04" ContextApps="td"><Term>cost set lines</Term>
		<Definition>The lines that SSA ERP uses to determine which additional costs must be added to the sales orders for all individual customers. Examples of cost sets lines are administrative costs added to the order costs if the order amount is lower than a certain value, or freight costs added to the order if the total weight of the sold/purchased goods exceeds a certain value.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="CostSets.td" Version="B60adoc1" ContextApps="td"><Term>cost sets</Term>
		<Definition>The code under which a number of additional costs can be stored. Cost sets can be linked to customers or price lists and, via these, to orders.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000310" Version="B60asy04" ContextApps="td"><Term>create new structure</Term>
		<Definition>Copy an existing category structure into a new category to create an exact copy.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000143" Version="B60asy04" ContextApps="td"><Term>Created</Term>
		<Definition>The status assigned to the purchase requisition when the requester enters and saves the purchase requisition.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000350" Version="B60adoc1" ContextApps="td"><Term>CUM reset date</Term>
		<Definition>The date and time at which a schedule's cumulatives/ authorizations are reset.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000080" Version="B60asy04" ContextApps="td"><Term>CUMs start date</Term>
		<Definition>The date from which the cumulatives of this record are calculated.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="CumulaCUMs.td" Version="B60adoc0" ContextApps="td"><Term>cumulatives (CUMs)</Term>
		<Definition>The year-to-date totals for quantities shipped, received, required, and invoiced.</Definition>
		<SimpleSection><Paragraph>Cumulatives are used as schedule statistics to track if its status is ahead or behind schedule compared to the demand.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000240" Version="B60asy04" ContextApps="td"><Term>customer order number</Term>
		<Definition>The number that the sold-to business partner assigned to the order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="InstalSchedu.td" Version="B60asy04" ContextApps="td"><Term>default installment schedule</Term>
		<Definition>The installment schedules used for sales orders that are invoiced before or after the ordered goods are actually delivered.</Definition>
		<SimpleSection><Paragraph>After entering the desired schedule number, you can record the defaults for a number of installment lines. The time fence between the order date and the invoice date, the percentage of the total net amount, and the type of installment are defined on the installment orderline.</Paragraph>
			<Paragraph>You can define up to nine different default installment schedule sets.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000144" Version="B60adoc1" ContextApps="td"><Term>deleted</Term>
		<Definition>The requisition status when the requisition is deleted.</Definition>
		<SimpleSection><Paragraph>A requisition can be deleted if its current status is <GUIRef href="/baanerp/td/domains/pur.rqst#created" role="enum">Created</GUIRef>, <GUIRef href="/baanerp/td/domains/pur.rqst#converted" role="enum">Converted</GUIRef>, <GUIRef href="/baanerp/td/domains/pur.rqst#rejected" role="enum">Rejected</GUIRef>, <GUIRef href="/baanerp/td/domains/pur.rqst#modified" role="enum">Modified</GUIRef>, or <GUIRef href="/baanerp/td/domains/pur.rqst#canceled" role="enum">Canceled</GUIRef>.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000068" Version="B60asy04" ContextApps="td"><Term>delivered quantity</Term>
		<Definition>The quantity delivered by the supplier identified in the purchase unit.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000219" Version="B60asy04" ContextApps="td"><Term>delivered quantity</Term>
		<Definition>The quantity of goods stated on the sales order line, expressed in the sales unit, and delivered to the sold-to business partner.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000333" Version="B60adoc1" ContextApps="td"><Term>delivery contract</Term>
		<Definition>A list of time-phased delivery, derived from a contract and converted to purchase orders. A delivery contract is not a real schedule, but a schedule solution to generate purchase orders in time.</Definition>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<TABLE border="1"><TBODY><TR><TH width="105">Contract line</TH>
						<TH width="129">Delivery contract</TH>
						<TH width="139">Purchase order (PO)</TH>
					</TR>
					<TR><TD width="105">100 pieces (pcs)</TD>
						<TD width="129">01/12/2000 20 pcs</TD>
						<TD width="139">PO1 01/12/2000 20 pcs</TD>
					</TR>
					<TR><TD width="105">-</TD>
						<TD width="129">08/02/2000 25 pcs</TD>
						<TD width="139">PO2 08/02/2000 25 pcs</TD>
					</TR>
					<TR><TD width="105">-</TD>
						<TD width="129">15/12/2000 40 pcs</TD>
						<TD width="139">PO3 15/12/2000 40 pcs</TD>
					</TR>
					<TR><TD width="105">-</TD>
						<TD width="129">22/12/2000 15 pcs</TD>
						<TD width="139">PO4 22/12/2000 15 pcs</TD>
					</TR>
				</TBODY>
			</TABLE>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="DeliveDate.td" Version="B60asy04" ContextApps="td"><Term>delivery date</Term>
		<Definition>The date on which the inventory is issued from the replenishment warehouse and transported to the destination warehouse.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000014" Version="B60asy04" ContextApps="td"><Term>delivery date tolerance (-)</Term>
		<Definition>The number of days early that a supplier can make a delivery.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000015" Version="B60asy04" ContextApps="td"><Term>delivery date tolerance (+)</Term>
		<Definition>The number of days late that a supplier can make a delivery.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Device.td" Version="B60adoc0" ContextApps="td"><Term>device</Term>
		<Definition>The output device selected for the report such as a printer, a screen (device: display), an ASCII file, and so on.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="DirectDelive.td" Version="B60asy04" ContextApps="td"><Term>direct delivery</Term>
		<Definition>The process in which a seller orders the sold goods from a buy-from business partner, who must also deliver the goods directly to the sold-to business partner. By means of a purchase order that is linked to a sales order, the buy-from business partner delivers the goods directly to the sold-to business partner. The goods are not delivered from your own warehouse, so <GUIRef href="/baanerp/wh" role="package">Warehouse Management</GUIRef> is not involved.</Definition>
		<SimpleSection><List><ListIntro>A seller can decide for a direct delivery because:</ListIntro>
				<ListItem>There is a shortage of available stock.</ListItem>
				<ListItem>The ordered quantity cannot be delivered in time.</ListItem>
				<ListItem>The ordered quantity cannot be transported by your company.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="Discount.td" Version="B60adoc0" ContextApps="td"><Term>discount</Term>
		<Definition>An allowance of deduction granted by the seller to the buyer, usually when the buyer meets certain stipulated conditions that reduce the price of the goods purchased.</Definition>
		<SimpleSection><List><ListIntro>Three types of discounts exist:</ListIntro>
				<ListItem>A quantity discount: an allowance determined by the quantity or value of the purchase.</ListItem>
				<ListItem>A cash discount: an allowance extended to encourage payment of an invoice on or before a stated date.</ListItem>
				<ListItem>A trade discount: a deduction from an established price for items or services made by the seller to those engaged in a certain business.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000217" Version="B60asy04" ContextApps="td"><Term>discount amount</Term>
		<Definition>The discount given to a business partner, calculated by unit and expressed as a value. For instance, 3 euro.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000364" Version="B60adoc1" ContextApps="td"><Term>discount percentage</Term>
		<Definition>The percentage that you can subtract from the gross sales price or purchase price.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000363" Version="B60adoc1" ContextApps="td"><Term>discount schedule</Term>
		<Definition>A schedule used to calculate discounts for an item. The discounts defined in a discount schedule are expressed as a percentage or an amount and are subject to a minimum or maximum quantity or value.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="DoubtfCustom.td" Version="B60asy04" ContextApps="td"><Term>doubtful customer</Term>
		<Definition>A customer who has an inconsistent or questionable payment history.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="EffectPeriod.td" Version="B60asy04" ContextApps="td"><Term>effectivity period</Term>
		<Definition>The period of time defined by the effective date and expiry date in which an agreement is valid.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000228" Version="B60asy04" ContextApps="td"><Term>employee number</Term>
		<Definition>The number that identifies an employee.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000227" Version="B60asy04" ContextApps="td"><Term>end date</Term>
		<Definition>The date and time the activity is completed.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000329" Version="B60adoc1" ContextApps="td"><Term>exception rule</Term>
		<Definition>If an approval rule is based on exception rules, SSA ERP automatically approves a purchase order that does not meet a valid rule. If you define approval rules based on exception, you define for what combination of data elements you do not want SSA ERP to approve the purchase order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000210" Version="B60asy04" ContextApps="td"><Term>expiry date</Term>
		<Definition>The last day on which a record is valid. If you do not specify an expiry time, the validity expires at the end of the expiry date, at 24:00 hours.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Extensions.td" Version="B60asy04" ContextApps="td"><Term>extensions</Term>
		<Definition>The parts of projects for which special arrangements are have been made that concern invoicing, such as variations, provisional amounts, quantities to be settled, and fluctuation settlements. An extension can be attached to one or more budget lines.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000003" Version="B60asy04" ContextApps="td"><Term>fab authorization</Term>
		<Definition>The valid authorization for the business partner to start the production for a quantity of items required on a purchase schedule. The fab authorization is expressed as a cumulative quantity and is calculated using the fab period.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000083" Version="B60asy04" ContextApps="td"><Term>fab authorization through date</Term>
		<Definition>The date until which the fab authorization is valid.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000336" Version="B60adoc1" ContextApps="td"><Term>fab period</Term>
		<Definition>The time period during which the supplier is authorized to manufacture the goods required on a schedule, calculated from the schedule issue date on for push schedules, and from the current date on for pull forecast schedules.</Definition>
		<SimpleSection><Paragraph>The fab period is expressed in a number of days.</Paragraph>
		</SimpleSection>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<List><ListItem>CUM start quantity: 10000</ListItem>
				<ListItem>Schedule issue date/current date: 05.07.99</ListItem>
				<ListItem>Fab period: 20 days</ListItem>
			</List>
			<TABLE border="1"><TBODY><TR><TD>Issue/current date</TD>
						<TD>Quantity</TD>
					</TR>
					<TR><TD>05.07.99</TD>
						<TD>100</TD>
					</TR>
					<TR><TD>12.07.99</TD>
						<TD>100</TD>
					</TR>
					<TR><TD>19.07.99</TD>
						<TD>100</TD>
					</TR>
					<TR><TD>26.07.99</TD>
						<TD>100</TD>
					</TR>
				</TBODY>
			</TABLE>
			<Formula><Paragraph UserLevel="Novice" UserType="Taskuser">
Fab time fence   : 05.07.99 (+ 20 days) = 25.07.99.
Fab authorization: 10000 + 100 + 100 + 100 = 10300.
</Paragraph>
			</Formula>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="FeaturDefini.td" Version="B60asy04" ContextApps="td"><Term>feature definitions</Term>
		<Definition>The definitions used to record additional information about customers, prospects, contacts, marketing projects, or activities.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000171" Version="B60asy04" ContextApps="td"><Term>feature option</Term>
		<Definition>The possible values for a feature definition.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="FeaturSets.td" Version="B60asy04" ContextApps="td"><Term>feature set</Term>
		<Definition>A set of item attributes used to classify feature definitions. Feature definitions are used to record additional information on customers, prospects, contacts, marketing projects, or activities.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="FinalInvoic.td" Version="B60asy04" ContextApps="td"><Term>final invoice</Term>
		<Definition>An invoice that replaces a provisional invoice that was sent earlier. No modifications are allowed on final invoices.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000117" Version="B60asy04" ContextApps="td"><Term>financial customer group</Term>
		<Definition>A unit that consists of two or more financial business partner groups, which is used to link these business partners to ledger accounts.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000016" Version="B60asy04" ContextApps="td"><Term>firm requirement</Term>
		<Definition>A requirement that is handled as an actual order and that can be shipped.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000346" Version="B60adoc1" ContextApps="td"><Term>frozen period</Term>
		<Definition>The overlap period of the frozen zone+ and the frozen zone-. No changes to the purchase schedule line are permitted in this period.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000028" Version="B60asy04" ContextApps="td"><Term>frozen zone-</Term>
		<Definition>The number of days, calculated from the current date, for which you can no longer reduce the quantity of required items.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000027" Version="B60asy04" ContextApps="td"><Term>frozen zone+</Term>
		<Definition>The number of days, calculated from the current date, for which you can no longer increase the quantity of required items.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000302" Version="B60asy04" ContextApps="td"><Term>general category</Term>
		<Definition>A category that applies to any sold-to business partner.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000075" Version="B60asy04" ContextApps="td"><Term>generation date</Term>
		<Definition>The date the specific schedule is (re)generated.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000106" Version="B60adoc1" ContextApps="td"><Term>gross amount</Term>
		<Definition>The total amount from which taxes, rebates, discounts, and so on are deducted to reach the net amount. The gross amount is calculated by multiplying the order quantity with the book price.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="GrossMargin.td" Version="B60asy04" ContextApps="td"><Term>gross margin</Term>
		<Definition>The sales revenue minus all manufacturing costs, both fixed and variable.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000212" Version="B60asy04" ContextApps="td"><Term>gross price</Term>
		<Definition>The full price minus the order line discount and the order header discount.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="GrossProfit.td" Version="B60asy04" ContextApps="td"><Term>gross profit</Term>
		<Definition>The earnings after direct costs of the goods sold are deducted from the sales revenue for a specific period.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000008" Version="B60asy04" ContextApps="td"><Term>high fab authorization</Term>
		<Definition>The highest fab authorization ever calculated on a purchase schedule, counted from the latest CUM reset date on.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000009" Version="B60asy04" ContextApps="td"><Term>high raw authorization</Term>
		<Definition>The highest raw authorization ever calculated on a purchase schedule, counted from the latest CUM reset date on.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000183" Version="B60asy04" ContextApps="td"><Term>hold reason</Term>
		<Definition></Definition>
		<SimpleSection><List><ListIntro>A reason for blocking a sales order or a sales order line, which can be:</ListIntro>
				<ListItem>The open order balance exceeds the customer's credit limit.</ListItem>
				<ListItem>The customer has overdue invoices.</ListItem>
				<ListItem>The customer's status is doubtful.</ListItem>
				<ListItem>The sales margin of one of the order lines is exceeded.</ListItem>
				<ListItem>The gross margin of the order is exceeded.</ListItem>
				<ListItem>The sales order is received through EDI.</ListItem>
				<ListItem>The sales order has an invalid zip code.</ListItem>
				<ListItem>The sales order is entered by an inexperienced operator.</ListItem>
				<ListItem>The sales order line contains a blocked item.</ListItem>
				<ListItem>A promotion is linked to the sales order (line).</ListItem>
				<ListItem>A user-defined general reason.</ListItem>
			</List>
			<Paragraph>An order can be held for more than one reason at any point in the sales order procedure. For example, an order can be blocked due to credit checking (the order balance exceeds the customers credit limit) at the same time as being blocked due to margin control (the gross margin of the order is exceeded).</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000014" Version="B60adoc1" ContextApps="td"><Term>immediate requirement</Term>
		<Definition>All schedule lines scheduled until the next schedule issue date that must be shipped as soon as possible.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000241" Version="B60asy04" ContextApps="td"><Term>installment</Term>
		<Definition>An incremental payment method used to spread invoice payments over a period of time. Installments enable you to send invoices for a sales order before or after the ordered goods are actually delivered.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="InstalOrder.td" Version="B60asy04" ContextApps="td"><Term>installment order</Term>
		<Definition>An order that is not paid for immediately but in partial amounts or percentages of the total net amount.</Definition>
		<SimpleSection><Paragraph>You can send invoices for a percentage of the total net amount on the sales order, before or after the ordered goods are actually delivered. In this case, a number of installment lines is added to the sales order. An installment line consists of an amount and a number of additional details.</Paragraph>
			<List><ListIntro>Billed installments are settled (subtracted from the goods amount) when the goods are delivered and invoiced. Two types of settlement exist:</ListIntro>
				<ListItem>Indirect settlement: delivered goods are not invoiced until the installment order is closed. Then the invoiced amounts are subtracted from the total net amount on the invoice.</ListItem>
				<ListItem>Direct settlement.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000040" Version="B60asy04" ContextApps="td"><Term>internal processing time</Term>
		<Definition>The time required between the recognition of needs and the release of the purchase order. Internal processing time includes document preparation and sourcing.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000079" Version="B60asy04" ContextApps="td"><Term>invoice date</Term>
		<Definition>The date on which the invoice is printed.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="InvoicAmount.td" Version="B60asy04" ContextApps="td"><Term>invoiced amount</Term>
		<Definition>The amount charged to a business partner.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000007" Version="B60asy04" ContextApps="td"><Term>invoiced cumulative</Term>
		<Definition>A schedule's total invoiced cumulative quantity, calculated from the CUM reset date on up to the last transaction date, which is the invoice date. Invoiced CUMs are updated as soon as a an invoice is approved by <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000109" Version="B60asy04" ContextApps="td"><Term>invoiced quantity</Term>
		<Definition>The number of items actually billed.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000115" Version="B60asy04" ContextApps="td"><Term>item dimensions</Term>
		<Definition>The length, width, and thickness of items with a physical quantity that is set to <GUIRef href="/baanerp/tc/domains/tccu#length" role="enum">Length</GUIRef>, <GUIRef href="/baanerp/tc/domains/tccu#area" role="enum">Area (m2)</GUIRef>, or <GUIRef href="/baanerp/tc/domains/tccu#volume" role="enum">Volume</GUIRef>.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="JobTitles.td" Version="B60asy04" ContextApps="td"><Term>job titles</Term>
		<Definition>The names of functions or titles of employees in an organization, for example sales manager, financial director, or accountant.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000247" Version="B60adoc1" ContextApps="td"><Term>kit</Term>
		<Definition>A predefined list of items to be delivered together when ordered by the customer.</Definition>
		<SimpleSection><List><ListIntro>You can define kits to facilitate order entry. A kit is ordered and priced as a single item. For internal order entry and warehousing purposes, the kit item is a list of components. On the sales order line, the components are linked. The cost price of the kit is the sum of the components' cost prices. The components of a kit can be of the following types:</ListIntro>
				<ListItem>Items.</ListItem>
				<ListItem>Other kits.</ListItem>
				<ListItem>Option lists.</ListItem>
			</List>
			<Paragraph>Example: The components of a PC kit usually consist of the main cabinet, a monitor, a keyboard, and a mouse. In the Do-It-Yourself market, a toolshed kit can contain the parts for the walls and the roof, a door with hinges, a door handle, and a lock.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000081" Version="B60asy04" ContextApps="td"><Term>last receipt date</Term>
		<Definition>The most recent date on which a shipment, related to the specific schedule number and position number, is received.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="379" Version="6.0a" ContextApps="td"><Term>layout code</Term>
		<Definition>An identifying code and description of the layout properties of a report, such as paper size, font, range of data, column headings, and data.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Letters.td" Version="B60asy04" ContextApps="td"><Term>letters</Term>
		<Definition>The general memoranda mailed to relations and contacts (whether within the framework of a marketing project or not) that can be printed and composed by using variables.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="380" Version="6.0a" ContextApps="td"><Term>level attribute</Term>
		<Definition>A data field whose information is updated and set aside for statistics overviews. It can be regarded as a pre-selection of statistics information, which can be fine-tuned later by means of sorts.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000316" Version="B60asy04" ContextApps="td"><Term>line level promotion</Term>
		<Definition>A special offer on a sales order line that reduces the price of the original item by a percentage or monetary amount, or that offers premiums with the purchase of the original item.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000059" Version="B60asy04" ContextApps="td"><Term>line of business</Term>
		<Definition>A group of customers, suppliers, or employees that work in the same business sector.</Definition>
		<SimpleSection><Paragraph>Lines of business can be used as selection criteria when generating reports or inquiries of statistical and historical data.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="ListType.td" Version="B60asy04" ContextApps="td"><Term>list type</Term>
		<Definition>The way in which a list item can be defined.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000349" Version="B60adoc1" ContextApps="td"><Term>logistic agreements</Term>
		<Definition>Conditions that must be formally agreed upon between a supplier and a customer regarding logistic data, such as:</Definition>
		<SimpleSection><List><ListItem>Delivery pattern.</ListItem>
				<ListItem>Frozen periods.</ListItem>
				<ListItem>Sourcing percentage.</ListItem>
				<ListItem>Ship-from business partner.</ListItem>
				<ListItem>Inspection.</ListItem>
				<ListItem>Schedule release type.</ListItem>
				<ListItem>Carrier.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000348" Version="B60adoc1" ContextApps="td"><Term>lower bound</Term>
		<Definition>Time period during which the schedule line quantity can increase, but not decrease, and during which the deletion of schedule lines is not allowed.</Definition>
		<SimpleSection><Paragraph>Lower bound applies when the end of the frozen zone+ lies before the end of the frozen zone-.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000163" Version="B60asy04" ContextApps="td"><Term>lower limit</Term>
		<Definition>The lowest value or quantity for which you are allowed to add additional costs.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="ManufaItem.td" Version="B60asy04" ContextApps="td"><Term>manufactured item</Term>
		<Definition>The items that can be manufactured end products and subassemblies. A manufactured item is usually associated with a bill of material and a routing that describe the components used to assemble it and the manner in which it is assembled. Manufactured items are also referred to as production items and can be purchased.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Margin.td" Version="B60asy04" ContextApps="td"><Term>margin</Term>
		<Definition>The percentage that the net sales price is allowed to deviate from the target price.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="MarginContro.td" Version="B60asy04" ContextApps="td"><Term>margin control</Term>
		<Definition>The sales submodule that controls whether the sales order or quotation price of an item differs too much from the specified target price. The percentage that the net sales price is allowed to deviate from the target price is known as the allowed margin.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000178" Version="B60asy04" ContextApps="td"><Term>marketing project</Term>
		<Definition>A group of activities, executed in the same period, that relate to the same trade relation for promotion, sales, and distribution of a product or service.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="MateriReleas.td" Version="B60adoc0" ContextApps="td"><Term>material release</Term>
		<Definition>A schedule on which forecasted information is provided about shipping times, delivery times, and quantities.</Definition>
		<SimpleSection><Paragraph>In general, a material release can be considered as a planning release. For push schedules, however, the material release can also contain the actual order.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000366" Version="B60adoc1" ContextApps="td"><Term>matrix attributes</Term>
		<Definition>A list of elements used to define a price, discount, promotion, or freight rate. The group of matrix attributes is identified by a matrix definition and type.</Definition>
		<SimpleSection><List><ListIntro>For example, imagine you are a furniture vendor and you decide to maintain your sales prices based on two elements:</ListIntro>
				<ListItem>The specific item you sell.</ListItem>
				<ListItem>The way to handle payments.</ListItem>
			</List>
			<Paragraph>In this case, the matrix type is Sales Price, the matrix definition is Furni (this name is user-definable), and the matrix attributes are Item and Payment Method.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="MatrixDefini.td" Version="B60adoc1" ContextApps="td"><Term>matrix definition</Term>
		<Definition>The matrix definition code defines the group of elements (matrix attributes) that a <GUIRef href="/baanerp/td/pcg" role="module">Pricing Control</GUIRef> matrix uses to determine a price, discount, promotion, or freight rate.</Definition>
		<SimpleSection><List><ListIntro>For example, imagine you are a furniture vendor and you decide to maintain your sales prices based on two elements:</ListIntro>
				<ListItem>The specific item you sell.</ListItem>
				<ListItem>The way to handle payments.</ListItem>
			</List>
			<Paragraph>In this case, the matrix type is Sales Price, the matrix definition is Furni (this name is user-definable), and the matrix attributes are Item and Payment Method.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000373" Version="B60adoc1" ContextApps="td"><Term>matrix segments</Term>
		<Definition>A matrix segment is a table field that is used to define a matrix attribute. When a matrix definition is selected in a <GUIRef href="/baanerp/td/pcg" role="module">Pricing Control</GUIRef> matrix, the selected matrix segments are used as the matrix attributes of the matrix. In the matrix, you can enter the values for the matrix attributes. Matrix segments are table fields from the following sessions:</Definition>
		<SimpleSection><List><ListItem><GUIRef href="/baanerp/tc/com/tccom4500m000" role="session">Business Partners (tccom4500m000)</GUIRef>
				</ListItem>
				<ListItem><GUIRef href="/baanerp/td/sls/tdsls4100m000" role="session">Sales Orders (tdsls4100m000)</GUIRef>
				</ListItem>
				<ListItem><GUIRef href="/baanerp/td/pur/tdpur4100m000" role="session">Purchase Orders (tdpur4100m000)</GUIRef>
				</ListItem>
				<ListItem><GUIRef href="/baanerp/tc/ibd/tcibd0501m000" role="session">Items - General (tcibd0501m000)</GUIRef>
				</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000101" Version="B60asy04" ContextApps="td"><Term>matrix sequence</Term>
		<Definition>The order in which a matrix definition will be searched for. The matrix sequence is set by precedence in date.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="MatrixType.td" Version="B60adoc0" ContextApps="td"><Term>matrix type</Term>
		<Definition>An entity used to define the type of a <GUIRef href="/baanerp/td/pcg/tdpcg0130m000#tdpcg030.made" role="formfield">Matrix Definition</GUIRef> and to classify the matrix attributes.</Definition>
		<SimpleSection><Paragraph>The following matrix types are available in the <GUIRef href="/baanerp/td/pcg" role="module">Pricing Control</GUIRef> module:</Paragraph>
			<List><ListItem><GUIRef href="/baanerp/td/domains/pcg.maty#sobook" role="enum">Sales Price</GUIRef>.</ListItem>
				<ListItem><GUIRef href="/baanerp/td/domains/pcg.maty#soldsc" role="enum">SOL Discount</GUIRef>.</ListItem>
				<ListItem><GUIRef href="/baanerp/td/domains/pcg.maty#sodsc" role="enum">SO Total Discount</GUIRef>.</ListItem>
				<ListItem><GUIRef href="/baanerp/td/domains/pcg.maty#pobook" role="enum">Purchase Price</GUIRef>.</ListItem>
				<ListItem><GUIRef href="/baanerp/td/domains/pcg.maty#poldsc" role="enum">POL Discount</GUIRef>.</ListItem>
				<ListItem><GUIRef href="/baanerp/td/domains/pcg.maty#podsc" role="enum">PO Total Discount</GUIRef>.</ListItem>
				<ListItem><GUIRef href="/baanerp/td/domains/pcg.maty#transfer" role="enum">Transfer Price</GUIRef>.</ListItem>
				<ListItem><GUIRef href="/baanerp/td/domains/pcg.maty#lineprom" role="enum">Line Promotion</GUIRef>.</ListItem>
				<ListItem><GUIRef href="/baanerp/td/domains/pcg.maty#ordprom" role="enum">Order Promotion</GUIRef>.</ListItem>
				<ListItem><GUIRef href="/baanerp/td/domains/pcg.maty#clfrate" role="enum">Client Freight Rate</GUIRef>.</ListItem>
				<ListItem><GUIRef href="/baanerp/td/domains/pcg.maty#cafrate" role="enum">Carrier Freight Rate</GUIRef>.</ListItem>
			</List>
			<Paragraph>For each type, SSA ERP generates a selection of attributes. In a matrix type, the combination of a maximum of six attributes identifies the matrix definition.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000025" Version="B60asy04" ContextApps="td"><Term>maximum capacity tolerance</Term>
		<Definition>The maximum percentage that can exceed ship-from business partner capacity.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000211" Version="B60asy04" ContextApps="td"><Term>maximum contract quantity</Term>
		<Definition>The agreed maximum total quantity for the entire contract, expressed in the quantity unit. The maximum contract quantity must be greater than or equal to the agreed contract quantity.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="MaximuOrderQ.td" Version="B60asy04" ContextApps="td"><Term>maximum order quantity</Term>
		<Definition>The maximum quantity of items to be purchased or produced at once.</Definition>
		<SimpleSection><Paragraph>When planned orders are generated, the quantity of items to be purchased or produced at once is never more than the maximum order quantity. The maximum order quantity prevents the purchase or production of an item in quantities that are too large.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000245" Version="B60asy04" ContextApps="td"><Term>menu</Term>
		<Definition>A type of item that consists of a group of items with similar characteristics that are classified under one generic item to facilitate order entry. The items in the group can be selected separately.</Definition>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<Paragraph>A monitor, a computermouse and a CD player are defined as related items used to configure a personal computer. But, you can also select a computermouse as a separate item.</Paragraph>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000024" Version="B60asy04" ContextApps="td"><Term>minimum capacity tolerance</Term>
		<Definition>The minimum percentage that can stay below ship-from business partner capacity.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000215" Version="B60asy04" ContextApps="td"><Term>minimum contract quantity</Term>
		<Definition>The agreed minimum total quantity for the whole contract, expressed in the quantity unit. The minimum contract quantity must be greater than zero and less than or equal to the agreed contract quantity.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000149" Version="B60asy04" ContextApps="td"><Term>modified</Term>
		<Definition>After a requisition is rejected, it can be modified by changing header or line information. The modified requisition can then be resubmitted for approval.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000107" Version="B60asy04" ContextApps="td"><Term>net amount</Term>
		<Definition>The gross amount minus discounts. The net value is always stated in the transactional currency.</Definition>
		<SimpleSection><Paragraph>If multiple discount levels are used, the net amount is calculated from the gross amount minus discounts at previous levels.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000066" Version="B60asy04" ContextApps="td"><Term>net order line amount</Term>
		<Definition>The net order line amount, expressed in the transaction currency. This amount is calculated as follows:</Definition>
		<SimpleSection><Formula><Paragraph UserLevel="Novice" UserType="Taskuser">Amount = (Quantity x Price) - Order Line Discount</Paragraph>
			</Formula>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="NetPrice.td" Version="B60asy04" ContextApps="td"><Term>net price</Term>
		<Definition>The book price with all (other) discounts applied. If no discounts exist, the gross price is equal to the net price. The net price is calculated as follows:</Definition>
		<SimpleSection><Formula><Paragraph UserLevel="Novice" UserType="Taskuser">Net price = sales price - line discount - order discount</Paragraph>
			</Formula>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000338" Version="B60adoc1" ContextApps="td"><Term>non-referenced schedule</Term>
		<Definition>A schedule that contains lines without a reference number. Because no specific requirement exists for the schedule line, non-referenced schedule lines can first be clustered and then ordered, shipped, and received together.</Definition>
		<SimpleSection><Paragraph>Push schedules and pull forecast schedules are non-referenced schedules.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="NormalContra.td" Version="B60adoc0" ContextApps="td"><Term>normal contract</Term>
		<Definition>A customer-oriented contract, agreed upon by suppliers and customers, that is used to record specific agreements. A normal contract is usually valid for approximately one year.</Definition>
		<SimpleSection><Paragraph>In a specific period, you cannot define more than one normal contract for each item or price group for a business partner.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000252" Version="B60adoc1" ContextApps="td"><Term>objective criterion</Term>
		<Definition>A criterion for which the score is calculated directly from the data in the system.</Definition>
		<SimpleSection><List><ListIntro>The following objective criteria are available:</ListIntro>
				<ListItem><GUIRef href="/baanerp/td/domains/pur.ctyp#delivery" role="enum">Delivery</GUIRef>.</ListItem>
				<ListItem><GUIRef href="/baanerp/td/domains/pur.ctyp#quality" role="enum">Quality</GUIRef>.</ListItem>
				<ListItem><GUIRef href="/baanerp/td/domains/pur.ctyp#quantity" role="enum">Quantity</GUIRef>.</ListItem>
				<ListItem><GUIRef href="/baanerp/td/domains/pur.ctyp#costperf" role="enum">Cost Performance</GUIRef>.</ListItem>
				<ListItem><GUIRef href="/baanerp/td/domains/pur.ctyp#orderconf" role="enum">Order Confirmation</GUIRef>.</ListItem>
				<ListItem><GUIRef href="/baanerp/td/domains/pur.ctyp#period.rating" role="enum">Period Rating</GUIRef>.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000345" Version="B60adoc1" ContextApps="td"><Term>offsetting</Term>
		<Definition>The process of planning backwards to look for a valid delivery moment on which requirements can be delivered in time. Based on the generated delivery moments, requirements are clustered in <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>.</Definition>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<TABLE border="1"><TBODY><TR><TD>Days</TD>
						<TD width="35">1</TD>
						<TD width="35">2</TD>
						<TD width="35">3</TD>
						<TD width="35">4</TD>
						<TD width="35">5</TD>
						<TD width="35">6</TD>
						<TD width="35">7</TD>
						<TD width="35">8</TD>
						<TD width="35">9</TD>
						<TD width="35">10</TD>
						<TD width="35">11</TD>
						<TD width="35">12</TD>
						<TD width="35">13</TD>
						<TD width="35">14</TD>
						<TD width="35">15</TD>
						<TD width="35">16</TD>
						<TD width="35">17</TD>
						<TD width="35">18</TD>
						<TD width="35">19</TD>
						<TD width="35">20</TD>
					</TR>
					<TR><TD>Requirements</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">1</TD>
						<TD width="35">1</TD>
						<TD width="35">1</TD>
						<TD width="35">1</TD>
						<TD width="35">1</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">1</TD>
						<TD width="35">1</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
					</TR>
					<TR><TD>Delivery pattern</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">X</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">X</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">X</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
					</TR>
					<TR><TD>Clustered demand</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">3</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">3</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">1</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
						<TD width="35">-</TD>
					</TR>
				</TBODY>
			</TABLE>
			<Paragraph></Paragraph>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="OpenBalanc.td" Version="B60asy04" ContextApps="td"><Term>open balance</Term>
		<Definition>The balance of all unpaid invoices relating to one particular business partner.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000248" Version="B60asy04" ContextApps="td"><Term>option</Term>
		<Definition>A generic item type that differs from other similar items by one or two features. For example, a group of chairs with similar main characteristics can differ in size and color.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="OrderAcknow.td" Version="B60asy04" ContextApps="td"><Term>order acknowledgment</Term>
		<Definition>The document that confirms the sale of goods to a sold-to business partner according to the listed terms of delivery.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000182" Version="B60asy04" ContextApps="td"><Term>order confirmation date</Term>
		<Definition>The date on which the buy-from business partner confirmed the purchase order.</Definition>
		<SimpleSection><Paragraph>The order confirmation date is used for the calculation of order confirmation objective ratings in vendor rating. The buy-from business partner is given a rating according to the time interval between the order date and the order confirmation date.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000046" Version="B60adoc0" ContextApps="td"><Term>order date</Term>
		<Definition>The date on which the order is manually entered into the system or is automatically generated.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000367" Version="B60adoc1" ContextApps="td"><Term>order discount</Term>
		<Definition>A discount percentage or amount to be subtracted from the total order amount.</Definition>
		<Synonym>Synonym: total discount.</Synonym>
	</GlossaryEntry>
	<GlossaryEntry ID="000317" Version="B60asy04" ContextApps="td"><Term>order level promotion</Term>
		<Definition>A special offer on a sales order that reduces the total order price by a percentage, or that offers a premium.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000368" Version="B60adoc1" ContextApps="td"><Term>order line discount</Term>
		<Definition>A percentage or amount subtracted from the amount of an order line.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000067" Version="B60adoc0" ContextApps="td"><Term>order line discount amount</Term>
		<Definition>The discount amount resulting from the order line discount. This amount is calculated as follows:</Definition>
		<SimpleSection><Formula><Paragraph UserLevel="Novice" UserType="Taskuser">Order Line Discount Amount = Quantity x Price x Order Line Discount/100
</Paragraph>
			</Formula>
			<Paragraph>The calculation result is rounded. The order line discount amount is always expressed in the order/quotation currency.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000372" Version="B60adoc1" ContextApps="td"><Term>order origin</Term>
		<Definition>The source of the information on which an order is based, such as SSA ERP sessions, or user defined sources such as phone, mail, and so on.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="OrderPrioriS.td" Version="B60asy04" ContextApps="td"><Term>order priority simulations</Term>
		<Definition>A simulated activity that enables you to calculate the priority sequence in which inventory is allocated to orders.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="OrderType.td" Version="B60asy04" ContextApps="td"><Term>order type</Term>
		<Definition>A group of orders that are processed according to the same procedure (series of order steps = sessions). In addition, these orders share a number of other characteristics (return order y/n, collect order y/n, subcontracting order y/n, and so on).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000035" Version="B60asy04" ContextApps="td"><Term>ordered quantity</Term>
		<Definition>The quantity that must be delivered according to the terms on the order line. The quantity is expressed in the purchase unit or the sales unit of the item.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000375" Version="B60adoc1" ContextApps="td"><Term>over-delivery</Term>
		<Definition>A positive deviation from the original ordered quantity.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000250" Version="B60asy04" ContextApps="td"><Term>parent criterion</Term>
		<Definition>A subjective criterion to which one or more other subjective criteria are linked in a tree structure.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000030" Version="B60adoc1" ContextApps="td"><Term>pattern</Term>
		<Definition>A scheme on which you can define the day of the month, the day of the week, and the time of the day you want an activity, for example a release or a delivery, to be carried out.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000019" Version="B60adoc1" ContextApps="td"><Term>pattern code</Term>
		<Definition>The code used to identify the pattern for your activities. The pattern defines the date and time, for example the month or the day of the month, on which you want to carry out the activity.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="PeriodTable.td" Version="B60asy04" ContextApps="td"><Term>period table</Term>
		<Definition>A table that consists of any number of time units, for example, months or weeks.</Definition>
		<SimpleSection><Paragraph>A period is used to define the time horizon during which, for example, a schedule is valid.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000226" Version="B60asy04" ContextApps="td"><Term>phase code</Term>
		<Definition>The code by which the phase is identified within SSA ERP.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="PhasesInTheP.td" Version="B60asy04" ContextApps="td"><Term>phases in the marketing project</Term>
		<Definition>The units of time that identify a particular stage or phase in the contact with the customer. For example, first contact (prospect) or regular customer (customer).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="PhoneOffice.td" Version="B60asy04" ContextApps="td"><Term>phone (office)</Term>
		<Definition>The telephone number, including area code, at the contact's work site.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000088" Version="B60adoc1" ContextApps="td"><Term>planned delivery date</Term>
		<Definition>The planned date on which the items on the order/schedule line must be delivered. The planned delivery date cannot occur before the order date/schedule generation date.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000017" Version="B60asy04" ContextApps="td"><Term>planned requirement</Term>
		<Definition>A requirement that you want to communicate to your business partner for information and planning purposes only.</Definition>
		<SimpleSection><Paragraph>You can enter these requirement lines (manually) during schedule generation. The line can also receive this requirement type as a result of schedule regeneration.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000344" Version="B60adoc1" ContextApps="td"><Term>planned shipment date</Term>
		<Definition>The planned date on which the items on the order/schedule line must be shipped/picked up at the ship from business partner's site. The planned shipment date cannot fall before the order date.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000018" Version="B60adoc1" ContextApps="td"><Term>planner</Term>
		<Definition>The employee or department responsible for planning the production, purchase and distribution of items. The planner takes into account the inventory levels, availability of materials, and capacities of resources, and reacts on signals such as rescheduling messages that SSA ERP generates.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000207" Version="B60asy04" ContextApps="td"><Term>position number of an order line</Term>
		<Definition>The number used to identify the position of the order line on the sales or purchase order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000331" Version="B60adoc1" ContextApps="td"><Term>potential back order</Term>
		<Definition>A back order that must be manually confirmed and that can be modified by the user.</Definition>
		<SimpleSection><List><ListIntro>The following can result in a potential back order:</ListIntro>
				<ListItem>The received quantity of the purchase order line is less than the ordered quantity at the time of delivery date.</ListItem>
				<ListItem>The received quantity is partially rejected during inspection.</ListItem>
				<ListItem>The received quantity is equal to the ordered quantity, but the user changes the back order quantity from zero into a higher value.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000318" Version="B60adoc1" ContextApps="td"><Term>premium</Term>
		<Definition>A free item that is offered to the customer as part of a promotion.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="PriceAgreem.td" Version="B60asy04" ContextApps="td"><Term>price agreements</Term>
		<Definition>The agreement that concerns the prices and allowances of specific goods/services.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="PriceBook.td" Version="B60asy04" ContextApps="td"><Term>price book</Term>
		<Definition></Definition>
		<SimpleSection><List><ListIntro>The place where you can store the following:</ListIntro>
				<ListItem>The base sales price.</ListItem>
				<ListItem>The base purchase price.</ListItem>
				<ListItem>The price unit for items.</ListItem>
			</List>
			<Paragraph>Prices are defined by currency and are valid for a given period of time.</Paragraph>
			<Paragraph>A quantity or value break discount schedule can be tied to a price book.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="PriceGroup.td" Version="B60asy04" ContextApps="td"><Term>price group</Term>
		<Definition>A group of items to which the same pricing characteristics apply.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="PriceMatrixC.td" Version="B60asy04" ContextApps="td"><Term>price matrix</Term>
		<Definition>A pricing structure that offers flexible criteria to define prices and discounts. You can set up additional prices for items in a price matrix.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="PriceUnit.td" Version="B60asy04" ContextApps="td"><Term>price unit</Term>
		<Definition>The unit to which the (sales/purchase) price applies.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="PricinPCG.td" Version="B60adoc0" ContextApps="td"><Term>Pricing (PCG)</Term>
		<Definition>A module that enables you to define prices and discounts in a flexible way. A basic price is retrieved from a predefined price book.</Definition>
		<SimpleSection><Paragraph>If Pricing Control (PCG) matrices are used, depending on the matrix type and by using a matrix definition, the different elements of the item file, business partner, and sales or purchase order (line) can be combined at various levels.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000360" Version="B60adoc1" ContextApps="td"><Term>Pricing Control (PCG) matrices</Term>
		<Definition>A <GUIRef href="/baanerp/td/pcg" role="module">Pricing Control</GUIRef> matrix is an entity in which prices, discounts, freight rates, or promotions are maintained for customers, suppliers and/or items. In the <GUIRef href="/baanerp/td/pcg" role="module">Pricing Control</GUIRef> module, the following types of matrices are available:</Definition>
		<SimpleSection><List><ListItem>Price matrices.</ListItem>
				<ListItem>Discount matrices.</ListItem>
				<ListItem>Promotion matrices.</ListItem>
				<ListItem>Freight Rate matrices.</ListItem>
			</List>
			<Paragraph>Essentially, a <GUIRef href="/baanerp/td/pcg" role="module">Pricing Control</GUIRef> matrix includes the following elements:</Paragraph>
			<List><ListItem>A <GUIRef href="/baanerp/td/pcg/tdpcg0130m000#tdpcg030.maty" role="formfield">Matrix Type</GUIRef>.</ListItem>
				<ListItem>A <GUIRef href="/baanerp/td/pcg/tdpcg0130m000#tdpcg030.made" role="formfield">Matrix Definition</GUIRef>.</ListItem>
				<ListItem>A set of matrix attributes.</ListItem>
				<ListItem>Pricing information, such as price books, discount schedules, promotions, or freight rate books.</ListItem>
			</List>
			<Paragraph>The matrix type and the matrix definition determine the available matrix attributes. The pricing information is determined by the type of <GUIRef href="/baanerp/td/pcg" role="module">Pricing Control</GUIRef> matrix.</Paragraph>
			<Paragraph>Example</Paragraph>
			<Paragraph>In a price matrix, you can define a price for the following attributes and values:</Paragraph>
			<TABLE border="1"><TBODY><TR><TH width="193">Attribute</TH>
						<TH width="188">Value</TH>
					</TR>
					<TR><TD width="193">Sold-to business partner</TD>
						<TD width="188">Apex Wholesellers, Inc.</TD>
					</TR>
					<TR><TD width="193">Terms of Delivery</TD>
						<TD width="188">CoD (cash on delivery)</TD>
					</TR>
					<TR><TD width="193">Item</TD>
						<TD width="188">Can opener aw10</TD>
					</TR>
				</TBODY>
			</TABLE>
			<Paragraph>When an order is entered for Apex Wholesellers, Inc. for item Can opener aw10, and the terms of delivery are CoD, the price maintained in the price matrix is used to calculate the price for the order.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000361" Version="B60adoc1" ContextApps="td"><Term>pricing information</Term>
		<Definition>Pricing information includes prices, discounts, promotions, and freight rates. If Pricing Control (PCG) matrices are used, pricing information is maintained for sets of attributes and values. The attributes are defined in matrix definitions and the values in the relevant Pricing Control (PCG) matrix.</Definition>
		<ExampleSection><SectionTitle>Example</SectionTitle>
		</ExampleSection>
		<SimpleSection><Paragraph>You can define a price for the following attributes and values:</Paragraph>
			<TABLE border="1"><TBODY><TR><TH width="193">Attribute</TH>
						<TH width="188">Value</TH>
					</TR>
					<TR><TD width="193">Sold-to business partner</TD>
						<TD width="188">Apex Wholesellers, Inc.</TD>
					</TR>
					<TR><TD width="193">Terms of Delivery</TD>
						<TD width="188">CoD (cash on delivery)</TD>
					</TR>
					<TR><TD width="193">Item</TD>
						<TD width="188">Can opener aw10</TD>
					</TR>
				</TBODY>
			</TABLE>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="PrintiJobs.td" Version="B60asy04" ContextApps="td"><Term>printing/processing jobs</Term>
		<Definition>The fixed jobs that print or process data in batch. A job can be repeated whenever desired or used for checking purposes.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000356" Version="B60adoc1" ContextApps="td"><Term>prior required CUM</Term>
		<Definition>A schedule's total required CUM calculated from the last CUM reset date through the (next) schedule issue date.</Definition>
		<SimpleSection><Paragraph>In contrast to required CUM, prior CUM also includes the requirements of released schedule lines for which no receipts are booked yet.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000097" Version="B60asy04" ContextApps="td"><Term>priority</Term>
		<Definition>An option that enables you to add a certain rating for suppliers. If the priority is defined, the item/supplier combinations are sorted according to descending priority.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="ProforInvoic.td" Version="B60asy04" ContextApps="td"><Term>pro forma invoice</Term>
		<Definition>An invoice sent to the buyer who must pay for the goods before they are sent to that buyer.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="ProducVarian.td" Version="B60adoc1" ContextApps="td"><Term>product variant</Term>
		<Definition>A unique configuration or specification of a generic item. The specification results from the configuration process and includes information such as feature options, company, and assembly line.</Definition>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<List><ListIntro>If your generic item is a bike, you can have three product variants:</ListIntro>
				<ListItem>A red bike produced on assembly line one.</ListItem>
				<ListItem>A blue bike produced on assembly line two.</ListItem>
				<ListItem>A red bike produced on assembly line two. In this example, color and line are product-variant options.</ListItem>
			</List>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000128" Version="B60asy04" ContextApps="td"><Term>profit amount</Term>
		<Definition>The budgeted gross profit amount in a specific period, expressed in the home currency.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000230" Version="B60asy04" ContextApps="td"><Term>project code</Term>
		<Definition>The unique code of a main project, a subproject or a single project. By means of a project code, the complete production can be managed on the basis of customer orders.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000319" Version="B60asy04" ContextApps="td"><Term>promotion</Term>
		<Definition>The application of an additional discount, value off, or premium to a sales order based on predefined order levels of selected items. Two basic types of promotions exist: order level and line level.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000365" Version="B60adoc1" ContextApps="td"><Term>promotion group</Term>
		<Definition>An entity in which items, sold-to business partners, or promotions that share the same promotion attribute values are maintained.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="377" Version="6.0a" ContextApps="td"><Term>promotional contract</Term>
		<Definition>A type of special contract that applies to each sold-to business partner. As a result, the sold-to business partner is not entered in the contract.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000335" Version="B60adoc1" ContextApps="td"><Term>pull schedule</Term>
		<Definition>Two types of pull schedules exist:</Definition>
		<SimpleSection><List><ListItem><Emphasis>Pull forecast schedules</Emphasis>: a list of time-phased planned requirements, generated by <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef>, that are sent to the supplier. Pull forecast schedules are only used for forecasting purposes. To actually order the items, a pull call-off schedule must be generated.</ListItem>
				<ListItem><Emphasis>Pull call-off schedules</Emphasis>: a list of time-phased specific requirements of purchased items, triggered from <GUIRef href="/baanerp/ti/asc" role="module">Assembly Control</GUIRef>, <GUIRef href="/baanerp/ti/sfc" role="module">Shop Floor Control</GUIRef>, or <GUIRef href="/baanerp/wh" role="package">Warehouse Management</GUIRef> (KANBAN, Time-phased order point).</ListItem>
			</List>
		</SimpleSection>
		<SimpleSection><List><ListIntro>A pull schedule can use one of the following release types:</ListIntro>
				<ListItem><GUIRef href="/baanerp/tc/domains/scrd#shipping" role="enum">Shipping Schedule</GUIRef>: both material releases and shipping schedules are sent. <List><ListItem>Material releases are issued through the pull forecast schedule.</ListItem>
						<ListItem>Shipping schedules are issued through the pull call-off schedule.</ListItem>
						<ListItem>Shipping is carried out based on the <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="enum">Firm</GUIRef> requirements in the shipping schedule. The material release only sends forecasting data.</ListItem>
					</List>
				</ListItem>
				<ListItem><GUIRef href="/baanerp/tc/domains/scrd#sequence" role="enum">Sequence Shipping Schedule</GUIRef>: both material releases and sequence shipping schedules are sent. <List><ListItem>Material releases are issued through the pull forecast schedule.</ListItem>
						<ListItem>Sequence shipping schedules are issued through the pull call-off schedule.</ListItem>
						<ListItem>Shipping is performed based on the <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="enum">Firm</GUIRef> requirements in the sequence shipping schedule. The material release only sends forecasting data.</ListItem>
					</List>
				</ListItem>
				<ListItem><GUIRef href="/baanerp/tc/domains/scrd#ship.only" role="enum">Shipping Schedule Only</GUIRef>: only shipping schedules are sent. <List><ListItem>Shipping schedules are issued through the pull call-off schedule.</ListItem>
						<ListItem>Shipping is carried out based on the <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="enum">Firm</GUIRef> requirements in the shipping schedule.</ListItem>
						<ListItem>No forecasting data is sent to the supplier through a pull forecast schedule.</ListItem>
					</List>
				</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="PurchaAdvise.td" Version="B60asy04" ContextApps="td"><Term>purchase advice</Term>
		<Definition>A recommendation that can originate from various planning mechanisms and which indicates what items must be purchased and when. You can also manually create and maintain the advice.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="PurchContra.td" Version="B60asy04" ContextApps="td"><Term>purchase contract</Term>
		<Definition>Purchase contracts are used to register specific agreements with a supplier that concern the delivery of specific goods.</Definition>
		<SimpleSection><List><ListIntro>In addition to specifying an effectivity period, a user can also indicate whether the minimum quantity to be purchased is a binding agreement. The agreements mainly concern prices and discounts for an item or price group. A contract is comprised of:</ListIntro>
				<ListItem>A purchase contract header with general supplier data.</ListItem>
				<ListItem>One or more purchase contract lines with price/discount agreements and quantity information that apply to an item or price group.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="PuCoHistor.td" Version="B60asy04" ContextApps="td"><Term>purchase contract history</Term>
		<Definition>The purchase contracts that have been added, changed, copied, or deleted. Whenever a transaction is made to the purchase contract (line), SSA ERP writes a copy of the transaction to the history.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="PuCoLines.td" Version="B60asy04" ContextApps="td"><Term>purchase contract lines</Term>
		<Definition>The agreement with a supplier about a certain item. Purchase contract lines contain both commercial and logistic conditions related to the supply of one item, during a period of time.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000332" Version="B60adoc1" ContextApps="td"><Term>purchase contract price revision</Term>
		<Definition>A date-controlled agreement for price and discount elements on the purchase contract line. Price revisions enable you to have several prices over time. An active revision is valid from its effective date up to the effective date of the next revision, or the expiry date of the purchase contract line.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000325" Version="B60adoc1" ContextApps="td"><Term>purchase coordinator</Term>
		<Definition>The employee who is responsible for registering item-manufacturer information and item-supplier information for those manufacturers and suppliers that are acceptable for a specific item.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000019" Version="B60asy04" ContextApps="td"><Term>purchase currency</Term>
		<Definition>The monetary unit in which the purchase price is expressed.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="PurchaInvoic.td" Version="B60asy04" ContextApps="td"><Term>purchase invoice</Term>
		<Definition>Purchased goods that are received, inspected (if required), and posted to inventory are placed on a purchase invoice. You must pay the buy-from business partner for the quantity on the invoice.</Definition>
		<SimpleSection><Paragraph>The buy-from business partner, order, item data, prices, and discounts are printed on the invoice. You can compare the data on the invoice to the invoice you receive from the buy-from business partner.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000151" Version="B60asy04" ContextApps="td"><Term>purchase office for requisitions</Term>
		<Definition>A department, clearly identified in the company business model, that manages business partner purchase relationships. This department identifies the location from which a purchase requisition is initiated. Purchase office information is used to convert the requisition to a purchase order or request-for-quotation (RFQ).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="PurchaOrders.td" Version="B60adoc0" ContextApps="td"><Term>purchase order</Term>
		<Definition>The order that indicates which items are delivered by a buy-from business partner according to certain terms and conditions.</Definition>
		<SimpleSection><List><ListIntro>A purchase order contains:</ListIntro>
				<ListItem>A header with general order data, buy-from business partner data, terms of payment, and terms of delivery.</ListItem>
				<ListItem>One or more order lines with more detailed information about the actual items to be delivered.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000072" Version="B60adoc1" ContextApps="td"><Term>purchase order acknowledgment</Term>
		<Definition>A message that suppliers send to the purchaser to confirm the receipt of the purchase order, which usually implies the acceptance of the order by the supplier.</Definition>
		<SimpleSection><List><ListIntro>Suppliers can change the purchase order data in the order acknowledgment according to:</ListIntro>
				<ListItem>Their company's terms and conditions.</ListItem>
				<ListItem>Former agreements with the purchaser.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="PurchaOrderH.td" Version="B60asy04" ContextApps="td"><Term>purchase order header</Term>
		<Definition>The general information of a purchase order.</Definition>
		<SimpleSection><List><ListIntro>A purchase order header contains, among other things:</ListIntro>
				<ListItem>General order data.</ListItem>
				<ListItem>General buy-from business partner data.</ListItem>
				<ListItem>Terms of payment.</ListItem>
				<ListItem>Terms of delivery.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="PurOrderHist.td" Version="B60asy04" ContextApps="td"><Term>purchase order history</Term>
		<Definition>The purchase orders that have been added changed, copied, or deleted. Whenever a purchase order line is maintained the system writes a copy of it to the history. A copy is created for each transaction.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="PurchaOrderL.td" Version="B60adoc0" ContextApps="td"><Term>purchase order lines</Term>
		<Definition></Definition>
		<SimpleSection><List><ListIntro>The lines on purchase orders that record detailed information about, for example:</ListIntro>
				<ListItem>The ordered items.</ListItem>
				<ListItem>The price agreements.</ListItem>
				<ListItem>The delivery dates.</ListItem>
				<ListItem>Shipping.</ListItem>
				<ListItem>Invoicing.</ListItem>
			</List>
			<Paragraph>You can have one or more lines on a purchase order.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000056" Version="B60asy04" ContextApps="td"><Term>purchase order type</Term>
		<Definition>The order type determines which sessions are part of the order procedure and how and in which sequence this procedure is executed.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="PurchaOrderU.td" Version="B60asy04" ContextApps="td"><Term>purchase order unit of measure</Term>
		<Definition>The unit in which item dimensions are expressed on purchase orders.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000012" Version="B60asy04" ContextApps="td"><Term>purchase price</Term>
		<Definition>The price you pay for an item, expressed in the purchase currency.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="PurchaPriceU.td" Version="B60asy04" ContextApps="td"><Term>purchase price unit</Term>
		<Definition>The item unit in which an item's purchase price is expressed. This unit can differ from the item's inventory unit.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000351" Version="B60adoc1" ContextApps="td"><Term>purchase release</Term>
		<Definition>A purchase release is used to send out, under one release number, those schedules that share the following common characteristics:</Definition>
		<SimpleSection><List><ListItem>Buy-from business partner.</ListItem>
				<ListItem>Ship-from business partner.</ListItem>
				<ListItem>Ship-to address.</ListItem>
				<ListItem>Release type (material release/ shipping schedule/ sequence shipping schedule).</ListItem>
				<ListItem>Shipment based schedule/ delivery based schedule.</ListItem>
				<ListItem>Communication method.</ListItem>
				<ListItem>Warehouse.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000153" Version="B60asy04" ContextApps="td"><Term>purchase requisition</Term>
		<Definition>A request by a user to obtain authorization for the procurement of goods and services.</Definition>
		<SimpleSection><Paragraph>A purchase requisition includes both standard and nonstandard material, cost, or service requirements. Information on a purchase requisition includes name, department, location, purchase office, and approver in the header section. The requisition line detail includes item, supplier, quantity, price, and amount.</Paragraph>
			<List><ListIntro>Purchase requisitions can only be converted into:</ListIntro>
				<ListItem>Purchase orders.</ListItem>
				<ListItem>Requests-for-quotation (RFQ).</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000011" Version="B60asy04" ContextApps="td"><Term>purchase schedule</Term>
		<Definition>A timetable of planned supply of materials. Purchase schedules support long-term purchasing with frequent deliveries and are usually backed by a purchase contract. All requirements for the same item, buy-from business partner, ship-from business partner, purchase office, and warehouse are stored in one schedule.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="PurchaUnit.td" Version="B60adoc1" ContextApps="td"><Term>purchase unit</Term>
		<Definition>The unit in which you purchase an item, also referred to as the purchase quantity unit.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000150" Version="B60asy04" ContextApps="td"><Term>purchased item</Term>
		<Definition>An item that is typically procured from an outside source. A bill of material and routing can be linked to a purchased item.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000334" Version="B60adoc1" ContextApps="td"><Term>push schedule</Term>
		<Definition>A list of time-phased requirements, generated by a central planning system, such as <GUIRef href="/baanerp/cp" role="package">Enterprise Planning</GUIRef> or <GUIRef href="/baanerp/tp" role="package">Project</GUIRef>, that are sent to the supplier. Push schedules contain both a forecast for the longer term and actual orders for the short term.</Definition>
		<SimpleSection><Paragraph>A push schedule can use one of the following release types:</Paragraph>
			<List><ListItem><GUIRef href="/baanerp/tc/domains/scrd#material" role="enum">Material Release</GUIRef>: only material releases are sent. Shipping is performed based on the <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="enum">Firm</GUIRef> and <GUIRef href="/baanerp/td/domains/pur.rtyp#immediate" role="enum">Immediate</GUIRef> requirements in the material release.</ListItem>
				<ListItem><GUIRef href="/baanerp/tc/domains/scrd#shipping" role="enum">Shipping Schedule</GUIRef>: both material releases and shipping schedules are sent. Shipping is carried out based on the <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="enum">Firm</GUIRef> and <GUIRef href="/baanerp/td/domains/pur.rtyp#immediate" role="enum">Immediate</GUIRef> requirements in the shipping schedule. The material release only sends forecasting data.</ListItem>
				<ListItem><GUIRef href="/baanerp/tc/domains/scrd#ship.only" role="enum">Shipping Schedule Only</GUIRef>: only shipping schedules are sent. Shipping is carried out based on the <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="enum">Firm</GUIRef> and <GUIRef href="/baanerp/td/domains/pur.rtyp#immediate" role="enum">Immediate</GUIRef> requirements in the shipping schedule. No forecasting data is sent to the supplier.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000122" Version="B60asy04" ContextApps="td"><Term>quantity</Term>
		<Definition>The budgeted amounts of an item in a specific period expressed in the inventory unit.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000016" Version="B60asy04" ContextApps="td"><Term>quantity tolerance (-)</Term>
		<Definition>The minimum quantity that a supplier must deliver. The minimum quantity tolerance is expressed as a percentage of the ordered quantity.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000017" Version="B60asy04" ContextApps="td"><Term>quantity tolerance (+)</Term>
		<Definition>The maximum quantity that a supplier can deliver. The maximum quantity tolerance is expressed as a percentage of the ordered quantity.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Quotation.td" Version="B60asy04" ContextApps="td"><Term>quotation</Term>
		<Definition>A written proposal that offers goods or services for a certain price and terms of sale to a prospective purchaser upon request.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000213" Version="B60asy04" ContextApps="td"><Term>quotation header</Term>
		<Definition>A header that contains the general data related to the sales quotation, such as terms of payment and terms of delivery.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000202" Version="B60asy04" ContextApps="td"><Term>quotation lines</Term>
		<Definition>The lines used to record the items offered, as well as the associated price agreements and quantities. A sales quotation is comprised of one or more quotation lines.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="RateCurrenEx.td" Version="B60asy04" ContextApps="td"><Term>rate (currency exchange rate)</Term>
		<Definition>The exchange rate (purchase or sales) of currencies.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000082" Version="B60asy04" ContextApps="td"><Term>raw authorization through date</Term>
		<Definition>The date until which the raw authorization is valid.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000002" Version="B60asy04" ContextApps="td"><Term>raw authorizations</Term>
		<Definition>The valid authorization for the business partner to buy the raw materials required on a purchase schedule. The raw authorization is expressed as a cumulative quantity and is calculated using the raw period.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000337" Version="B60adoc1" ContextApps="td"><Term>raw period</Term>
		<Definition>The time period during which the supplier is authorized to procure the raw materials required on a schedule, calculated from the schedule issue date on for push schedules, and from the current date on for pull forecast schedules.</Definition>
		<SimpleSection><Paragraph>The raw period is expressed in a number of days.</Paragraph>
		</SimpleSection>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<List><ListItem>CUM start quantity: 10000</ListItem>
				<ListItem>Schedule issue date/current date: 05.07.99</ListItem>
				<ListItem>Raw period: 20 days</ListItem>
			</List>
			<TABLE border="1"><TBODY><TR><TH width="135">Issue/current date</TH>
						<TH width="135">Quantity</TH>
					</TR>
					<TR><TD width="135">05.07.99</TD>
						<TD width="135">100</TD>
					</TR>
					<TR><TD width="135">12.07.99</TD>
						<TD width="135">100</TD>
					</TR>
					<TR><TD width="135">19.07.99</TD>
						<TD width="135">100</TD>
					</TR>
					<TR><TD width="135">26.07.99</TD>
						<TD width="135">100</TD>
					</TR>
				</TBODY>
			</TABLE>
			<Formula><Paragraph UserLevel="Novice" UserType="Taskuser">
Raw time fence   : 05.07.99 (+ 20 days) = 25.07.99.
Raw authorization: 10000 + 100 + 100 + 100 = 10300.
</Paragraph>
			</Formula>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="Rebate.td" Version="B60asy04" ContextApps="td"><Term>rebate</Term>
		<Definition>The amount of money to be paid to a sold-to business partner as a kind of discount for closing a sales order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="RebateAgreem.td" Version="B60asy04" ContextApps="td"><Term>rebate agreement</Term>
		<Definition>An agreement on the bonus (discount) to be paid to a customer for the sale of a particular item (or item group).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000126" Version="B60asy04" ContextApps="td"><Term>rebate amount</Term>
		<Definition>The amount of money to be paid to a sold-to business partner as a kind of discount for closing a sales order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000006" Version="B60asy04" ContextApps="td"><Term>received cumulative</Term>
		<Definition>A schedule's total received cumulative quantity, calculated from the CUM reset date on up to the last transaction date, which is the receipt date. Received CUMs are updated as soon as receipts are made for the schedule line(s).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="378" Version="6.0asy04" ContextApps="td"><Term>reference</Term>
		<Definition>A number that, if determined by <GUIRef href="/baanerp/ti/asc" role="module">Assembly Control</GUIRef>, refers to a unique combination of line station, assembly kit, and parent serial number.</Definition>
		<SimpleSection><Paragraph>A number that, if determined by <GUIRef href="/baanerp/td/pur" role="module">Purchase Control</GUIRef>, refers to a unique purchase schedule call-off that is generated from <GUIRef href="/baanerp/wh" role="package">Warehouse Management</GUIRef>.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000048" Version="B60asy04" ContextApps="td"><Term>reference A</Term>
		<Definition>The first extra reference by which the order or (request-for-) quotation can be identified. This reference is printed on various order documents and lists.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000049" Version="B60asy04" ContextApps="td"><Term>reference B</Term>
		<Definition>The second extra reference field that you can fill with extra information. This reference is printed on the order documents and lists.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000105" Version="B60asy04" ContextApps="td"><Term>reference date</Term>
		<Definition>The date that determines which orders are printed on the reminder. All orders that are not yet delivered and have a confirmed or planned delivery date before or equal to the reference date, are printed on the reminding note.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000339" Version="B60adoc1" ContextApps="td"><Term>referenced schedule</Term>
		<Definition>A schedule that contains lines with reference numbers. When goods are shipped, received, and invoiced, the reference numbers are used to communicate with suppliers and other SSA ERP packages. Because a specific requirement exists for the schedule line, each single schedule line is ordered, shipped, and received separately.</Definition>
		<SimpleSection><Paragraph>Pull call-off schedules are referenced schedules.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000341" Version="B60adoc1" ContextApps="td"><Term>regeneration</Term>
		<Definition>The process of rearranging schedule lines and moving the lines in time.</Definition>
		<SimpleSection><Paragraph>Regeneration is only carried out for non-referenced schedules.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000154" Version="B60asy04" ContextApps="td"><Term>rejected</Term>
		<Definition>The status of the requisition when an approver does not accept a submitted requisition. A purchase requisition can be rejected if it has the status <GUIRef href="/baanerp/td/domains/pur.rqst#submitted" role="enum">Submitted</GUIRef>, or <GUIRef href="/baanerp/td/domains/pur.rqst#approved" role="enum">Approved</GUIRef>.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000113" Version="B60asy04" ContextApps="td"><Term>rejected quantity</Term>
		<Definition>The number of delivered items that is rejected.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Relation.td" Version="B60asy04" ContextApps="td"><Term>relation</Term>
		<Definition>A shortened term for trade relation. Relation is a collective term for an employee or buy-from business partner that is entitled to a commission, and a sold-to business partner entitled to a rebate. Relations can be grouped in a relation team for the purpose of assigning the same agreement structure.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="RelatiTeam.td" Version="B60asy04" ContextApps="td"><Term>relation team</Term>
		<Definition>A function used to group relations so that multiple relations can be linked to a sales order. As a result, the appropriate relations will be rewarded for the sales activities that concern a specific sales order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="RelatiType.td" Version="B60asy04" ContextApps="td"><Term>relation type</Term>
		<Definition>A classification that determines whether a commission or a rebate is involved, as well as how commissions are to be paid. The relation is a sold-to business partner to whom a rebate is granted, or a buy-from business partner (agent) or an employee (representative) to whom commission is paid.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000324" Version="B60asy04" ContextApps="td"><Term>release date</Term>
		<Definition>The planned date to release the order to <GUIRef href="/baanerp/wh" role="package">Warehouse Management</GUIRef>. The release date is calculated by subtracting the warehouse inbound lead time from the planned delivery date.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000009" Version="B60asy04" ContextApps="td"><Term>release position number</Term>
		<Definition>A number used to identify the position of a purchase schedule in a purchase release. Each release line receives a separate release position number.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000008" Version="B60asy04" ContextApps="td"><Term>release revision number</Term>
		<Definition>A number that uniquely identifies the revision of the purchase release. The release revision number indicates the updates that are sent to the business partner.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000010" Version="B60asy04" ContextApps="td"><Term>release type</Term>
		<Definition>A classification used to specify the type of the purchase release based on which EDI messages can be generated. These messages are indicated by the used schedule.</Definition>
		<SimpleSection><List><ListIntro>A release can be of the following types:</ListIntro>
				<ListItem><GUIRef href="/baanerp/td/domains/pur.reltype#matrelease" role="enum">Material Release</GUIRef>: a material release can contain push schedules or pull forecast schedules.</ListItem>
				<ListItem><GUIRef href="/baanerp/td/domains/pur.reltype#shipschedule" role="enum">Shipping Schedule</GUIRef>: a shipping schedule can contain push schedules or pull call-off schedules.</ListItem>
				<ListItem><GUIRef href="/baanerp/td/domains/pur.reltype#seqschedule" role="enum">Sequence Shipping Schedule</GUIRef>: a sequence shipping schedule can only contain pull call-of schedules.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="Reminders.td" Version="B60asy04" ContextApps="td"><Term>reminder</Term>
		<Definition>A purchase order document that urges the supplier to deliver the ordered goods under the conditions agreed upon.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000312" Version="B60asy04" ContextApps="td"><Term>replace structure</Term>
		<Definition>Copy an existing structure into another existing structure, replacing the current structure of the target category.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="RequesForQuo.td" Version="B60asy04" ContextApps="td"><Term>request-for-quotation (RFQ)</Term>
		<Definition>A purchasing document that is used as a request to suppliers to submit their terms (price, discount, delivery time, terms of payment, terms of delivery, and so on) for delivering a (quantity of a) product.</Definition>
		<SimpleSection><Paragraph>You can send the request to a number of suppliers. The supplier, in turn, can submit quotations for the specified items.</Paragraph>
			<Paragraph>You can enter the quotation results into the system. This enables you to compare the prices and discounts that are offered by different suppliers.</Paragraph>
			<Paragraph>An accepted quotation can be copied to a contract, an order, or a price book.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000239" Version="B60asy04" ContextApps="td"><Term>request-for-quotation (RFQ) line</Term>
		<Definition>The lines that contain the item details in a request-for-quotation (RFQ), such as required quantity, time to be delivered, delivery warehouse and so on.</Definition>
		<SimpleSection><Paragraph>The item lines are sent to the buy-from business partner. As a result, the buy-from business partner can quote for each item individually. The buy-from business partner can also give alternatives for the required item.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000236" Version="B60asy04" ContextApps="td"><Term>request-for-quotation date</Term>
		<Definition>The date on which the request-for-quotation is entered into the system.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000004" Version="B60asy04" ContextApps="td"><Term>required cumulative</Term>
		<Definition>A schedule's total required cumulative quantity, calculated from the CUM reset date on up to the planned requirement date, which is the planned delivery date or planned shipment date. Required CUMs are updated as soon as receipts are confirmed for the schedule line(s).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000340" Version="B60adoc1" ContextApps="td"><Term>requirement type</Term>
		<Definition>Three requirement types exist that represent a requirement in time, used for scheduling. The available requirement types are:</Definition>
		<SimpleSection><List><ListItem><GUIRef href="/baanerp/td/domains/pur.rtyp#immediate" role="enum">Immediate</GUIRef>.</ListItem>
				<ListItem><GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="enum">Firm</GUIRef>.</ListItem>
				<ListItem><GUIRef href="/baanerp/td/domains/pur.rtyp#planned" role="enum">Planned</GUIRef>.</ListItem>
			</List>
			<Paragraph>For non-referenced schedules, requirement types are linked to segments.</Paragraph>
			<Paragraph>For pull forecast schedules, the requirement type is always <GUIRef href="/baanerp/td/domains/pur.rtyp#planned" role="enum">Planned</GUIRef> or <GUIRef href="/baanerp/td/domains/pur.rtyp#immediate" role="enum">Immediate</GUIRef>. For pull call-off schedules, the requirement type is always <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="enum">Firm</GUIRef>.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000313" Version="B60asy04" ContextApps="td"><Term>retrobilling</Term>
		<Definition>To re-invoice previously shipped items using a price based on a new contract negotiation. Retrobilling can also be performed on an individual sales order that is not related to a contract.</Definition>
		<Synonym>Synonym: retroactive billing.</Synonym>
	</GlossaryEntry>
	<GlossaryEntry ID="000237" Version="B60asy04" ContextApps="td"><Term>return date</Term>
		<Definition>The last date on which the buy-from business partner can submit a quotation on the request-for-quotation.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000108" Version="B60asy04" ContextApps="td"><Term>return note</Term>
		<Definition>A note that accompanies purchased goods when they are rejected in an inspection and must be sent back to the buy-from business partner.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="ReturnOrder.td" Version="B60asy04" ContextApps="td"><Term>return order</Term>
		<Definition>A purchase or sales order on which returned shipments are reported. A return order can only contain negative amounts.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000058" Version="B60asy04" ContextApps="td"><Term>return reason</Term>
		<Definition>The reason why the delivered goods are rejected and sent back to the buy-from business partner.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000224" Version="B60asy04" ContextApps="td"><Term>RFQ criteria set</Term>
		<Definition>A list of request-for-quotation (RFQ) criterions that can be linked to an RFQ header. A quotation is valuated according to these criteria.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000238" Version="B60asy04" ContextApps="td"><Term>RFQ criterion</Term>
		<Definition>A subjective criterion used to determine which quotation is accepted. You can link RFQ criterions to RFQ criterion sets.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000374" Version="B60adoc1" ContextApps="td"><Term>rush order</Term>
		<Definition>An order that must be executed as soon as possible and that usually requires special terms of payment and delivery.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000041" Version="B60asy04" ContextApps="td"><Term>safety time</Term>
		<Definition>The time that you can add to the normal lead time to protect delivery of goods against fluctuations in the lead time so that an order can be completed before the order's real need date.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000185" Version="B60asy04" ContextApps="td"><Term>sales acknowledgment code</Term>
		<Definition>A code that represents the reasons for a change of a sales order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000121" Version="B60adoc0" ContextApps="td"><Term>sales channel</Term>
		<Definition>A structured path in distribution to sell your merchandise.</Definition>
		<Synonym>Synonym: channel</Synonym>
	</GlossaryEntry>
	<GlossaryEntry ID="000220" Version="B60asy04" ContextApps="td"><Term>sales contract</Term>
		<Definition>A long-term contract for the sale of goods. Sales contracts are used to register specific agreements with customers or their projects about the delivery of certain goods. The agreements will mainly concern prices and discounts for an item or price group.</Definition>
		<SimpleSection><List><ListIntro>A contract is comprised of:</ListIntro>
				<ListItem>A contract header with general customer data.</ListItem>
				<ListItem>One or more contract lines with price/discount agreements concerning an item or price group.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000254" Version="B60asy04" ContextApps="td"><Term>sales contract header</Term>
		<Definition>Comprises general business partner data and data to identify general terms for the contract such as effective date and type of sales contract.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000234" Version="B60asy04" ContextApps="td"><Term>sales contract history</Term>
		<Definition>A log file that contains information about all sales contracts that are created, modified, copied, or deleted. Whenever a sales contract is maintained, SSA ERP writes a copy of that contract to the history. A copy is created for each transaction.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000235" Version="B60asy04" ContextApps="td"><Term>sales contract line history</Term>
		<Definition>A log file that contains information about all sales contract lines that are created, modified, copied, or deleted.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000243" Version="B60asy04" ContextApps="td"><Term>sales currency</Term>
		<Definition>The monetary unit in which the sales price is expressed.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="SalesInv.td" Version="B60asy04" ContextApps="td"><Term>sales invoice</Term>
		<Definition>A bill that relates to the sale of goods or services. A sales invoice is a document, sent by the seller to the buyer, for each sale containing details on the goods sold.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="SalesOffice.td" Version="B60asy04" ContextApps="td"><Term>sales office</Term>
		<Definition>A department clearly identified within the company business model to manage the sales relations of the business partner. The sales office is used to identify the locations that are responsible for the sales activities within the organization.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="SalesOrder.td" Version="B60asy04" ContextApps="td"><Term>sales order</Term>
		<Definition>An agreement that is used to sell items or services to a business partner according to certain terms and conditions. A sales order consists of a header and one or more order lines.</Definition>
		<SimpleSection><Paragraph>The general order data such as business partner data, terms of payment, and terms of delivery are stored in the header. The data about the actual items to be supplied, such as price agreements and delivery dates, is entered on the order lines.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="SalesOrderHe.td" Version="B60asy04" ContextApps="td"><Term>sales order header</Term>
		<Definition>A sales order contains items that are delivered to a customer, according to certain terms and conditions. The header of a sales order contains general data.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="SlsOrderLns.td" Version="B60asy04" ContextApps="td"><Term>sales order lines</Term>
		<Definition>A sales order contains items that are delivered to a customer, according to certain terms and conditions. The lines of a sale order are used to record the items ordered, as well as the associated price agreements and delivery dates.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="SalesOrderNu.td" Version="B60asy04" ContextApps="td"><Term>sales order number</Term>
		<Definition>A unique control number assigned to each new customer order, usually during order entry. A sales order number is often used by order promising, master scheduling, cost accounting, invoicing, and so on. For some make-to-order products, a sales order number can also take the place of an end item part number by becoming the control number that is scheduled through the finishing operations.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000172" Version="B60adoc1" ContextApps="td"><Term>sales order type</Term>
		<Definition>The order type, which determines the sessions that are part of the order procedure and how and in which sequence this procedure is executed.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000193" Version="B60asy04" ContextApps="td"><Term>sales order units of measure</Term>
		<Definition>The units in which item dimensions in sales orders are expressed.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="SalesPrice.td" Version="B60asy04" ContextApps="td"><Term>sales price</Term>
		<Definition>The price for which an item is sold.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="SalesPriceLi.td" Version="B60asy04" ContextApps="td"><Term>sales price list</Term>
		<Definition>The highest level used to record prices and discounts for a group of customers and/or suppliers. The price and discount can be determined by linking a price list code to a sales order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="SalesQuotat.td" Version="B60adoc1" ContextApps="td"><Term>sales quotations</Term>
		<Definition>A statement of price, the terms of sale, and a description of goods or services offered by a supplier to a prospective purchaser; a bid. The customer data, terms of payment, and terms of delivery are contained in the header; the data about the actual items is entered on the quotation lines. When given in response to a request-for-quotation, a bid is usually considered an offer to sell.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000169" Version="B60asy04" ContextApps="td"><Term>sales release</Term>
		<Definition>Identifies, by one release number, those sales schedules that share the following common characteristics:</Definition>
		<SimpleSection><List><ListItem>Sold-to business partner.</ListItem>
				<ListItem>Ship-to business partner.</ListItem>
				<ListItem>Release type (material release / shipping schedule / sequence shipping schedule).</ListItem>
				<ListItem>Shipment based schedule / delivery based schedule.</ListItem>
				<ListItem>Ship-to address.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000160" Version="B60asy04" ContextApps="td"><Term>sales representative</Term>
		<Definition>An employee of your company who maintains contact with the sold-to business partner. The employee number of the sales representative is also used as a sorting criterion in the sales statistics.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="SalesSchedu.td" Version="B60asy04" ContextApps="td"><Term>sales schedule</Term>
		<Definition>A timetable of planned supply of materials. Sales schedules support long-term sales with frequent deliveries. All requirements for the same item, sold-to business partner, ship-to business partner, and delivery parameter are stored in the same sales schedule.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000357" Version="B60adoc1" ContextApps="td"><Term>sales schedule revision number</Term>
		<Definition>A number that uniquely identifies the revision of the sales schedule. The sales schedule revision number indicates the sales schedule updates that are sent by your business partner.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="SalesUnit.td" Version="B60asy04" ContextApps="td"><Term>sales unit</Term>
		<Definition>The unit in which an item is sold.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Salutations.td" Version="B60asy04" ContextApps="td"><Term>salutations</Term>
		<Definition>The phrase used to address the recipient of a letter. For instance: Dear Sir, Miss, or To the Board of Directors.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000355" Version="B60adoc1" ContextApps="td"><Term>schedule issue date</Term>
		<Definition>The date and time, calculated by the issue pattern, which, for non-referenced schedules, is used to define the moment at which:</Definition>
		<SimpleSection><List><ListItem>Schedule lines are clustered.</ListItem>
				<ListItem>A purchase release is sent.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000100" Version="B60asy04" ContextApps="td"><Term>schedule line</Term>
		<Definition>The location where all separate requirements of one specific item delivered by a combination of the same buy-from business partner and ship-from business partner, ordered from a single purchase office, are located.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000001" Version="B60asy04" ContextApps="td"><Term>schedule number</Term>
		<Definition>An automatically generated and unique character string that identifies the schedule. This number is used as long as the requirement or the contract exists.</Definition>
		<SimpleSection><Paragraph>If schedule regeneration takes place, the schedule lines that are affected by the regeneration are copied to a new schedule revision number.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000003" Version="B60asy04" ContextApps="td"><Term>schedule position number</Term>
		<Definition>The number of the schedule line. This number uniquely identifies each requirement of an item that a specified business partner must supply at a specific date and time.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000005" Version="B60asy04" ContextApps="td"><Term>schedule quantity</Term>
		<Definition>The quantity of the item required for the schedule line(s).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000000000000012" Version="B60asy04" ContextApps="td"><Term>schedule revision number</Term>
		<Definition>The original schedule line that starts with revision number one. After each regeneration of the schedule, changed records are inserted with a new revision number. All new lines inserted can be compared against the current revision.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000010" Version="B60asy04" ContextApps="td"><Term>schedule text</Term>
		<Definition>A specific text with for example additional reference information.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="SearchArgume.td" Version="B60asy04" ContextApps="td"><Term>search argument</Term>
		<Definition>A keyword that is used for searching. A search argument is usually linked to a description.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000255" Version="B60adoc1" ContextApps="td"><Term>search priorities</Term>
		<Definition>The commission/rebate agreement search priorities are used to find a valid agreement for the entered search combination.</Definition>
		<SimpleSection><Paragraph>If a valid agreement is found for the first priority, it will be used for calculation. If not, SSA ERP searches for a valid agreement for the second priority and so on.</Paragraph>
		</SimpleSection>
		<ExampleSection><SectionTitle>Example</SectionTitle>
			<Paragraph>Priority 1 - Relation / Item.</Paragraph>
			<Paragraph>Priority 2 - Customer / Relation / Item.</Paragraph>
		</ExampleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000094" Version="B60asy04" ContextApps="td"><Term>segment</Term>
		<Definition>A part of a schedule that defines a unit of time used for scheduling. A segment contains a requirement type, a segment time unit, and a segment length.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000020" Version="B60asy04" ContextApps="td"><Term>segment code</Term>
		<Definition>The code that identifies the schedule segment.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000095" Version="B60asy04" ContextApps="td"><Term>segment length</Term>
		<Definition>The period that is assigned to the segment. The period is expressed in the segment time unit.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000093" Version="B60adoc1" ContextApps="td"><Term>segment set</Term>
		<Definition>A set that is used to define the structure of a schedule. A segment set consists of a number of segments.</Definition>
		<SimpleSection><Paragraph>The segment set is used for schedule regeneration and for clustering schedule lines. No segment sets are used for pull call-off schedules.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000021" Version="B60asy04" ContextApps="td"><Term>segment time unit</Term>
		<Definition>The time unit in which the segment is expressed, for example days, weeks, months, and so on.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000208" Version="B60asy04" ContextApps="td"><Term>sequence number</Term>
		<Definition>The number used to identify in detail the position number of a sales order (delivery) line or a purchase order line (detail).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000034" Version="B60asy04" ContextApps="td"><Term>sequence shipping schedule</Term>
		<Definition>A supplement to the material release or the shipping schedule with precise information about the production or deliveries of the requirements. This schedule can include the production or delivery sequence, and the order, the place, and the time of unloading after shipment.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000156" Version="B60asy04" ContextApps="td"><Term>service item</Term>
		<Definition>A standard item that represents services instead of goods.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000244" Version="B60asy04" ContextApps="td"><Term>set number</Term>
		<Definition>A number used to group together one or more order lines. Order lines with the same set number are released simultaneously to, for example, warehousing or invoicing.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000099" Version="B60asy04" ContextApps="td"><Term>ship-from business partner capacity</Term>
		<Definition>The maximum number of items the ship-from business partner can ship in the specified capacity time unit. SSA ERP takes into account this value to create valid requirements.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000352" Version="B60adoc1" ContextApps="td"><Term>shipment ID</Term>
		<Definition>The code of the shipment created by <GUIRef href="/baanerp/wh" role="package">Warehouse Management</GUIRef> during the advance shipment notice (ASN) process.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000353" Version="B60adoc1" ContextApps="td"><Term>shipment sequence</Term>
		<Definition>The shipment sequence created by <GUIRef href="/baanerp/wh" role="package">Warehouse Management</GUIRef> during the advance shipment notice (ASN) process for a particular shipment ID.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000005" Version="B60asy04" ContextApps="td"><Term>shipped cumulative</Term>
		<Definition>A schedule's total shipped cumulative quantity for which an advance shipment notice is received, calculated from the CUM-reset date on up to the last transaction date, which is the shipment date. If you do not use advance shipment notices, shipped CUMs are not updated in a logistic company.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000354" Version="B60adoc1" ContextApps="td"><Term>shipped quantity</Term>
		<Definition>The quantity shipped against a particular shipment ID and shipment sequence.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000033" Version="B60asy04" ContextApps="td"><Term>shipping schedule</Term>
		<Definition>A schedule on which detailed information is given about shipping times or delivery times and quantities. A shipping schedule facilitates just-in-time (JIT) management.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="SimulaCodes.td" Version="B60asy04" ContextApps="td"><Term>simulation codes</Term>
		<Definition>The simulations that help you calculating the priority sequence in which inventory is allocated to orders.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="SmoothFactor.td" Version="B60asy04" ContextApps="td"><Term>smoothing factor</Term>
		<Definition>The factor used to calculate smoothing data.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000161" Version="B60asy04" ContextApps="td"><Term>sort code</Term>
		<Definition>An identifying code and description of a set of data fields grouped in a sequence. These data fields are used in statistics reports and displays. When a report or display is generated, the fields are filled with data from the database and displayed in the report or display according to the sequence defined in the sort code.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000165" Version="B60asy04" ContextApps="td"><Term>source</Term>
		<Definition>The places, events, or methods where or through which trade relations come in contact with your company (for example, a trade fair or an advertisement).</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000229" Version="B60asy04" ContextApps="td"><Term>source code</Term>
		<Definition>The code that identifies a source within SSA ERP.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000096" Version="B60asy04" ContextApps="td"><Term>sourcing percentage</Term>
		<Definition>A percentage used to calculate how orders are divided among suppliers.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="SourciRule.td" Version="B60asy04" ContextApps="td"><Term>sourcing rule</Term>
		<Definition>The planning system that contains the rules for allocating demand based on a combination of supplier priority and percentage allocation to specific suppliers.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="SpeciaContra.td" Version="B60asy04" ContextApps="td"><Term>special contract</Term>
		<Definition>A customer-oriented contract, agreed upon by buy-from business partners and sold-to business partners that is used to record specific agreements for specific projects. A special contract can also be a promotional contract.</Definition>
		<SimpleSection><Paragraph>For special contracts, an overlap in effectivity periods is allowed for the same item/business partner combination.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000303" Version="B60asy04" ContextApps="td"><Term>specific category</Term>
		<Definition>A category that is linked to a specific sold-to business partner.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000233" Version="B60asy04" ContextApps="td"><Term>start date</Term>
		<Definition>The date and time the activity started.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000116" Version="B60asy04" ContextApps="td"><Term>statistical year</Term>
		<Definition>The tax year.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000305" Version="B60asy04" ContextApps="td"><Term>subcategory</Term>
		<Definition>Defines lower levels (catalog pages) of a catalog structure.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="SubconItem.td" Version="B60adoc1" ContextApps="td"><Term>subcontracting item</Term>
		<Definition>The auxiliary item code for recording subcontracting operations. Items of this type also belong to the administrative items. These items are non-physical items which are used to record the subcontracting costs.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Subcontracto.td" Version="B60asy04" ContextApps="td"><Term>subcontractor</Term>
		<Definition>A business partner that is hired to perform certain services, such as the execution of a part of a project or production order. The services are delivered via a purchase order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000249" Version="B60adoc1" ContextApps="td"><Term>subjective criterion</Term>
		<Definition>A criterion whose rating is based on user judgements that are entered in a questionnaire.</Definition>
		<SimpleSection><Paragraph>You can classify subjective criteria in a tree structure.</Paragraph>
			<Paragraph>Subjective criteria are taken into account in vendor rating.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000251" Version="B60asy04" ContextApps="td"><Term>subjective value</Term>
		<Definition>Subjective values are used to provide the user with an easy to use rating scale on a vendor rating questionnaire and the ranking of quotations. The method of using subjective values prevents the user from rating criteria on percentage scale. You can assign actual values to the subjective values. The actual values are expressed in percentages.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000158" Version="B60asy04" ContextApps="td"><Term>submitted</Term>
		<Definition>The requisition status when the requester submits a created requisition to a valid approver.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000256" Version="B60asy04" ContextApps="td"><Term>success percentage</Term>
		<Definition>A percentage associated with a quotation that represents the probability of the business partner accepting the quotation. Acceptance results in the conversion of the quotation into a sales order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="SuggesRetail.td" Version="B60asy04" ContextApps="td"><Term>suggested retail price</Term>
		<Definition>The sales price that suppliers recommend and that resellers charge their customers.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000029" Version="B60asy04" ContextApps="td"><Term>supplier capacity</Term>
		<Definition>The maximum capacity of a business partner for a given period.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000057" Version="B60asy04" ContextApps="td"><Term>supplier order number</Term>
		<Definition>The number the buy-from business partner assigned to the order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000330" Version="B60adoc1" ContextApps="td"><Term>supplier price book</Term>
		<Definition></Definition>
		<SimpleSection><List><ListIntro>A standard purchase price book that is used to store:</ListIntro>
				<ListItem>The default purchase price of an item by buy-from business partner, ship-from business partner, or both.</ListItem>
				<ListItem>The prices copied from supplier quotations.</ListItem>
				<ListItem>The default prices of items.</ListItem>
			</List>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="SupplyChain.td" Version="B60adoc0" ContextApps="td"><Term>supply chain</Term>
		<Definition>The physical entities, people, and processes that lead from acquiring raw materials from suppliers to providing finished products to meet customer requirements.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000011" Version="B60adoc1" ContextApps="td"><Term>supply time</Term>
		<Definition>The total time required to obtain a purchased item. This time includes order document preparation, sourcing, and supplier lead time.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Surname.td" Version="B60asy04" ContextApps="td"><Term>surname</Term>
		<Definition>A person's last name in personnel data.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000173" Version="B60asy04" ContextApps="td"><Term>system date</Term>
		<Definition>The current date that is generated by the system.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="TableFieldsT.td" Version="B60asy04" ContextApps="td"><Term>table fields in SMI</Term>
		<Definition>The table fields from the SSA ERP database that have been linked to the <GUIRef href="/baanerp/td/smi" role="module">Relation Management</GUIRef> module and can be used in selection expressions and letter and report layouts.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000209" Version="B60asy04" ContextApps="td"><Term>target price</Term>
		<Definition>The price that forms the basis for margin control calculations.</Definition>
		<SimpleSection><List><ListIntro>A target price can be one of the following prices:</ListIntro>
				<ListItem>The sales price.</ListItem>
				<ListItem>The recommended retail price.</ListItem>
				<ListItem>The cost price of the item.</ListItem>
				<ListItem>The selling price found after a search in the pricing module.</ListItem>
			</List>
			<Paragraph>The target price and the sales price are evaluated in relation to the margin limits registered in the item file.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="TerminLetter.td" Version="B60asy04" ContextApps="td"><Term>termination letter</Term>
		<Definition>A letter sent from the customer to the supplier that states that a contract has been ended.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000358" Version="B60adoc1" ContextApps="td"><Term>thank-you-for-bidding-letter</Term>
		<Definition>A letter sent to buy-from business partners who are involved in the bidding process to thank the buy-from business partners who did not receive the order.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000103" Version="B60asy04" ContextApps="td"><Term>total approved quantity</Term>
		<Definition>The total quantity of approved items expressed in the purchase unit.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000216" Version="B60asy04" ContextApps="td"><Term>total contract amount</Term>
		<Definition>The total value of the goods recorded on the contract.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000203" Version="B60adoc1" ContextApps="td"><Term>transaction date/time</Term>
		<Definition>The date and time when the order/schedule/contract (line) is changed and/or written to the history file.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="Turnover.td" Version="B60asy04" ContextApps="td"><Term>turnover</Term>
		<Definition>The annual sales volume.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000134" Version="B60asy04" ContextApps="td"><Term>unit price</Term>
		<Definition>The default unit price calculated by multiplying the price factor by the base price from the most current price book of the price matrix.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000347" Version="B60adoc1" ContextApps="td"><Term>upper bound</Term>
		<Definition>Time period during which the schedule line quantity can decrease, but not increase, and during which the creation of new schedule lines is not allowed.</Definition>
		<SimpleSection><Paragraph>Upper bound applies when the end of the frozen zone- lies before the end of the frozen zone+.</Paragraph>
		</SimpleSection>
	</GlossaryEntry>
	<GlossaryEntry ID="000164" Version="B60asy04" ContextApps="td"><Term>upper limit</Term>
		<Definition>The highest value or quantity for which you are allowed to add additional costs.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="User.td" Version="B60asy04" ContextApps="td"><Term>user</Term>
		<Definition>The person that works with an application software package.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="UserDefaulSa.td" Version="B60asy04" ContextApps="td"><Term>user defaults (sales)</Term>
		<Definition>The default data recorded by the user that substantially affects the creation of sales quotations and sales orders. This data determines the method of order entry, the default values during order input, the degree of acceptance after order entry, and so on.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="000168" Version="B60asy04" ContextApps="td"><Term>user profile (sales)</Term>
		<Definition>The default data that is recorded by the user and influences the creation of sales quotations, sales contracts, sales orders, and sales schedules. This data determines the method of order entry, default values during order input, and so on.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="UserDefaulPu.td" Version="B60asy04" ContextApps="td"><Term>user profiles (purchase)</Term>
		<Definition>The default data that is recorded by the user and influences the creation of purchase requisitions, requests-for-quotations, purchase contracts, purchase orders, purchase schedules, purchase releases, call-offs, and approval rules. This data determines the method of order entry, default values during order input, and so on.</Definition>
	</GlossaryEntry>
	<GlossaryEntry ID="VendorRating.td" Version="B60asy04" ContextApps="td"><Term>vendor rating</Term>
		<Definition>A classification of a supplier based on certain criteria. These criteria can be based on deliveries (on time, sufficient quality, and so on) as well as other factors.</Definition>
	</GlossaryEntry>
</Glossary>
