<?xml version="1.0" encoding="utf-8"?>
<Glossary ID="/baanerp/td/glossary/glossary" xml:lang="en">
   <Header>
      <Title>Glossary for CRM, Sales, and Procurement</Title>
   </Header>
   <GlossaryEntry ID="000328" Version="B60adoc1" ContextApps="td">
      <Term>acceptance rule</Term>
      <Definition>If an approval rule is based on acceptance rules, ERP Enterprise 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 ERP Enterprise to approve the
		purchase order.</Definition>
      <Keyword type="glentry" order="d1e1588696">
         <Level1>acceptance rule</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1588701">
         <Level1>accessory</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1588706">
         <Level1>account manager</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1588711">
         <Level1>activity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ActiviSMI_td" Version="B60adoc0" ContextApps="td">
      <Term>activity</Term>
      <Definition>An appointment, call, task, mailing, or e-mail that is
		registered in ERP Enterprise and
		that can be linked to, for example, a contact, a business partner, or an
		opportunity. Optionally, tasks, appointments, and calls can be synchronized
		with desktop applications.</Definition>
      <Keyword type="glentry" order="d1e1588716">
         <Level1>activity</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1588721">
         <Level1>activity number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000404" Version="B60adoc1" ContextApps="td">
      <Term>activity template</Term>
      <Definition>The definition of a standard activity. As the data to be
		recorded can vary from one activity to another, you can link a separate
		attribute set to each activity template. An activity template can be used as a
		basis for creating tasks and mailings.</Definition>
      <Keyword type="glentry" order="d1e1588726">
         <Level1>activity template</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000102" Version="B60asy04" ContextApps="td">
      <Term>actual delivery date</Term>
      <Definition>The date on which the sold goods are delivered.</Definition>
      <Keyword type="glentry" order="d1e1588731">
         <Level1>actual delivery date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000104" Version="B60asy04" ContextApps="td">
      <Term>actual receipt date</Term>
      <Definition>The date on which the ordered goods are received.</Definition>
      <Keyword type="glentry" order="d1e1588736">
         <Level1>actual receipt date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="CostSetsLine_td" Version="B60asy04" ContextApps="td">
      <Term>additional cost line</Term>
      <Definition>Includes a cost item that can be linked as additional costs to
		a sales order or shipment. Examples of additional cost 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>
      <Keyword type="glentry" order="d1e1588763">
         <Level1>additional cost line</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="AdditiCosts_td" Version="B60asy04" ContextApps="td">
      <Term>additional costs</Term>
      <Definition>The cost items that can be placed on a sales order or shipment
		to charge extra costs for an order or shipment.</Definition>
      <Keyword type="glentry" order="d1e1588741">
         <Level1>additional costs</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000110" Version="B60asy04" ContextApps="td">
      <Term>additional cost scenario</Term>
      <Definition>A set of search attributes used to determine an order's or
		shipment's <Link href="/baanerp/td/glossary/glossary#AdditiCosts_td" role="glossary">additional costs</Link>. Each scenario is linked to a <Link href="/baanerp/td/glossary/glossary#CostSets_td" role="glossary">cost set</Link>.</Definition>
      <Keyword type="glentry" order="d1e1588747">
         <Level1>additional cost scenario</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="CostSets_td" Version="B60adoc1" ContextApps="td">
      <Term>additional cost set</Term>
      <Definition>The code under which a number of additional cost lines and
		scenarios can be stored. Cost sets can be linked to items, business partners or
		price lists and, via these, to orders and shipments.</Definition>
      <Keyword type="glentry" order="d1e1588758">
         <Level1>additional cost set</Level1>
      </Keyword>
   </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</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="manual">Additional Rate Quantity</GUIRef>: 1 pallet, <GUIRef href="/baanerp/td/pcg/tdpcg0150m000#tdpcg050.dist" role="manual">Distance</GUIRef>: 1000 km</Paragraph>
         <Paragraph>
            <GUIRef href="/baanerp/td/pcg/tdpcg0150m000#tdpcg050.vaad" role="manual">Amount by Distance</GUIRef>:
		  10</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="manual">Weight</GUIRef>: 10 kg</Paragraph>
         <Paragraph>
            <GUIRef href="/baanerp/td/pcg/tdpcg0150m000#tdpcg050.aruq" role="manual">Additional Rate Quantity</GUIRef>: 1 m³</Paragraph>
         <Paragraph>
            <GUIRef href="/baanerp/td/pcg/tdpcg0150m000#tdpcg050.brty" role="manual">Break Type</GUIRef>: <GUIRef href="/baanerp/td/domains/pcg.brty#min" role="option">Minimum</GUIRef>
         </Paragraph>
         <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="4">
               <TR no="1" isLast="false">
                  <TD rowspan="1" colspan="1">
                     <GUIRef href="/baanerp/td/pcg/tdpcg0150m000#tdpcg050.dist" role="manual">Distance</GUIRef>:</TD>
                  <TD width="28" rowspan="1" colspan="1">0</TD>
                  <TD width="33" rowspan="1" colspan="1">100</TD>
                  <TD width="39" rowspan="1" colspan="1">500</TD>
               </TR>
               <TR no="2" isLast="false">
                  <TD rowspan="1" colspan="1">
                     <GUIRef href="/baanerp/td/pcg/tdpcg0150m000#tdpcg050.vaad" role="manual">Amount by Distance</GUIRef>
                  </TD>
                  <TD width="28" rowspan="1" colspan="1">10</TD>
                  <TD width="33" rowspan="1" colspan="1">15</TD>
                  <TD width="39" rowspan="1" colspan="1">20</TD>
               </TR>
               <TR no="3" isLast="false">
                  <TD rowspan="1" colspan="1">
                     <GUIRef href="/baanerp/td/pcg/tdpcg0150m000#tdpcg050.vaaw" role="manual">Amount by Weight</GUIRef>
                  </TD>
                  <TD width="28" rowspan="1" colspan="1">5</TD>
                  <TD width="33" rowspan="1" colspan="1">5</TD>
                  <TD width="39" rowspan="1" colspan="1">10</TD>
               </TR>
               <TR no="4" isLast="true">
                  <TD rowspan="1" colspan="1">
                     <GUIRef href="/baanerp/td/pcg/tdpcg0150m000#tdpcg050.amru" role="manual">Amount by Additional Rate Unit</GUIRef>
                  </TD>
                  <TD width="28" rowspan="1" colspan="1">5</TD>
                  <TD width="33" rowspan="1" colspan="1">5</TD>
                  <TD width="39" rowspan="1" colspan="1">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 space-and-orientation="indented-estimated">
            <Paragraph> 10 * 70 (distance) + 5 * 50 (weight) + 5 * 7 (volume) = 985 </Paragraph>
         </Formula>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1588768">
         <Level1>additional rate quantity by unit</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1588869">
         <Level1>agreement group</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1588874">
         <Level1>alternative quantity</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1588879">
         <Level1>amount</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1588884">
         <Level1>append structure</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000401" Version="B60adoc0" ContextApps="td">
      <Term>appointment</Term>
      <Definition>An activity type that specifies an appointment scheduled for a
		contact, business partner, opportunity, or activity that you want to track
		through completion. An appointment has invited atttendees.</Definition>
      <Keyword type="glentry" order="d1e1588889">
         <Level1>appointment</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1588894">
         <Level1>approval process</Level1>
      </Keyword>
   </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 ERP Enterprise approves
		purchase orders. The approval rules, on their turn, are based on acceptance
		rules or exception rules.</Definition>
      <SimpleSection/>
      <Keyword type="glentry" order="d1e1588899">
         <Level1>approval rule</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000139" Version="B60adoc1" ContextApps="td">
      <Term>approved</Term>
      <Definition>The status assigned to a purchase requisition when all relevant
		approvers have approved a requisition with the <GUIRef href="/baanerp/td/domains/pur.rqst#submitted" role="option">Pending Approval</GUIRef> status.</Definition>
      <Keyword type="glentry" order="d1e1588906">
         <Level1>approved</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000112" Version="B60asy04" ContextApps="td">
      <Term>approved quantity</Term>
      <Definition>The number of delivered items that is approved.</Definition>
      <Keyword type="glentry" order="d1e1588914">
         <Level1>approved quantity</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1588919">
         <Level1>approved source list</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000166" Version="B60asy04" ContextApps="td">
      <Term>attention code</Term>
      <Definition>The messages linked to business partners, opportunities, and so
		on that draw your attention to special events or circumstances.</Definition>
      <Keyword type="glentry" order="d1e1588924">
         <Level1>attention code</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="FeaturDefini_td" Version="B60asy04" ContextApps="td">
      <Term>attribute</Term>
      <Definition>Used to record distinctive information on (potential) business
		partners, contacts, opportunities, or activities and to segment data when
		specifying a batch selection for generating activities, mail merge (letters),
		or flexible reports.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="9">
               <TR no="1" isLast="false">
                  <TH rowspan="1" colspan="1">Attribute</TH>
                  <TH rowspan="1" colspan="1">Description</TH>
                  <TH rowspan="1" colspan="1">Type</TH>
                  <TH rowspan="1" colspan="1">Details</TH>
               </TR>
               <TR no="2" isLast="false">
                  <TD rowspan="1" colspan="1">sf</TD>
                  <TD rowspan="1" colspan="1">Is
				  the person a soccer fan?</TD>
                  <TD rowspan="1" colspan="1">Option</TD>
                  <TD rowspan="1" colspan="1">Options are Yes and No;
				  default is No</TD>
               </TR>
               <TR no="3" isLast="false">
                  <TD rowspan="1" colspan="1">fc</TD>
                  <TD rowspan="1" colspan="1">Favorite soccer club</TD>
                  <TD rowspan="1" colspan="1">Alphanumeric</TD>
                  <TD rowspan="1" colspan="1">Default is &lt;blank&gt;</TD>
               </TR>
               <TR no="4" isLast="false">
                  <TD rowspan="1" colspan="1">conv</TD>
                  <TD rowspan="1" colspan="1">How did you value this
				  conversation?</TD>
                  <TD rowspan="1" colspan="1">Alphanumeric</TD>
                  <TD rowspan="1" colspan="1">No defaults</TD>
               </TR>
               <TR no="5" isLast="false">
                  <TD rowspan="1" colspan="1">ccb</TD>
                  <TD rowspan="1" colspan="1">Can I call you back next week?</TD>
                  <TD rowspan="1" colspan="1">Option</TD>
                  <TD rowspan="1" colspan="1">Options are Yes and No; default is No</TD>
               </TR>
               <TR no="6" isLast="false">
                  <TD rowspan="1" colspan="1">lunch</TD>
                  <TD rowspan="1" colspan="1">Should bring own lunch</TD>
                  <TD rowspan="1" colspan="1">Option</TD>
                  <TD rowspan="1" colspan="1">Options are Yes and No; default is No</TD>
               </TR>
               <TR no="7" isLast="false">
                  <TD rowspan="1" colspan="1">dressc</TD>
                  <TD rowspan="1" colspan="1">What is the dress code?</TD>
                  <TD rowspan="1" colspan="1">Option</TD>
                  <TD rowspan="1" colspan="1">Options are formal and casual (default)</TD>
               </TR>
               <TR no="8" isLast="false">
                  <TD rowspan="1" colspan="1">comp</TD>
                  <TD rowspan="1" colspan="1">Main competitor</TD>
                  <TD rowspan="1" colspan="1">Alphanumeric</TD>
                  <TD rowspan="1" colspan="1">No defaults</TD>
               </TR>
               <TR no="9" isLast="true">
                  <TD rowspan="1" colspan="1">terr</TD>
                  <TD rowspan="1" colspan="1">Territory</TD>
                  <TD rowspan="1" colspan="1">Option</TD>
                  <TD rowspan="1" colspan="1">Options are East and West</TD>
               </TR>
            </TBODY>
         </TABLE>
         <Paragraph/>
         <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="6">
               <TR no="1" isLast="false">
                  <TH rowspan="1" colspan="1">Attribute set</TH>
                  <TH rowspan="1" colspan="1">Description</TH>
                  <TH rowspan="1" colspan="1">Attributes</TH>
               </TR>
               <TR no="2" isLast="false">
                  <TD rowspan="1" colspan="1">CON</TD>
                  <TD rowspan="1" colspan="1">Default
				  attribute set for contacts</TD>
                  <TD rowspan="1" colspan="1">sf, fc</TD>
               </TR>
               <TR no="3" isLast="false">
                  <TD rowspan="1" colspan="1">BP</TD>
                  <TD rowspan="1" colspan="1">Default
				  attribute set for business partners</TD>
                  <TD rowspan="1" colspan="1">sf,
				  fc</TD>
               </TR>
               <TR no="4" isLast="false">
                  <TD rowspan="1" colspan="1">CALL</TD>
                  <TD rowspan="1" colspan="1">Default attribute set for calls</TD>
                  <TD rowspan="1" colspan="1">conv,
				  ccb</TD>
               </TR>
               <TR no="5" isLast="false">
                  <TD rowspan="1" colspan="1">APP</TD>
                  <TD rowspan="1" colspan="1">Default attribute set for appointments</TD>
                  <TD rowspan="1" colspan="1">lunch, dressc</TD>
               </TR>
               <TR no="6" isLast="true">
                  <TD rowspan="1" colspan="1">OPP</TD>
                  <TD rowspan="1" colspan="1">Default attribute set for
				  opportunities</TD>
                  <TD rowspan="1" colspan="1">comp, terr</TD>
               </TR>
            </TBODY>
         </TABLE>
      </ExampleSection>
      <Keyword type="glentry" order="d1e1588929">
         <Level1>attribute</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000171" Version="B60asy04" ContextApps="td">
      <Term>attribute option</Term>
      <Definition>A possible value of an attribute of the option type.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="9">
               <TR no="1" isLast="false">
                  <TH rowspan="1" colspan="1">Attribute</TH>
                  <TH rowspan="1" colspan="1">Description</TH>
                  <TH rowspan="1" colspan="1">Type</TH>
                  <TH rowspan="1" colspan="1">Details</TH>
               </TR>
               <TR no="2" isLast="false">
                  <TD rowspan="1" colspan="1">sf</TD>
                  <TD rowspan="1" colspan="1">Is
				  the person a soccer fan?</TD>
                  <TD rowspan="1" colspan="1">Option</TD>
                  <TD rowspan="1" colspan="1">Options are Yes and No;
				  default is No</TD>
               </TR>
               <TR no="3" isLast="false">
                  <TD rowspan="1" colspan="1">fc</TD>
                  <TD rowspan="1" colspan="1">Favorite soccer club</TD>
                  <TD rowspan="1" colspan="1">Alphanumeric</TD>
                  <TD rowspan="1" colspan="1">Default is &lt;blank&gt;</TD>
               </TR>
               <TR no="4" isLast="false">
                  <TD rowspan="1" colspan="1">conv</TD>
                  <TD rowspan="1" colspan="1">How did you value this
				  conversation?</TD>
                  <TD rowspan="1" colspan="1">Alphanumeric</TD>
                  <TD rowspan="1" colspan="1">No defaults</TD>
               </TR>
               <TR no="5" isLast="false">
                  <TD rowspan="1" colspan="1">ccb</TD>
                  <TD rowspan="1" colspan="1">Can I call you back next week?</TD>
                  <TD rowspan="1" colspan="1">Option</TD>
                  <TD rowspan="1" colspan="1">Options are Yes and No; default is No</TD>
               </TR>
               <TR no="6" isLast="false">
                  <TD rowspan="1" colspan="1">lunch</TD>
                  <TD rowspan="1" colspan="1">Should bring own lunch</TD>
                  <TD rowspan="1" colspan="1">Option</TD>
                  <TD rowspan="1" colspan="1">Options are Yes and No; default is No</TD>
               </TR>
               <TR no="7" isLast="false">
                  <TD rowspan="1" colspan="1">dressc</TD>
                  <TD rowspan="1" colspan="1">What is the dress code?</TD>
                  <TD rowspan="1" colspan="1">Option</TD>
                  <TD rowspan="1" colspan="1">Options are formal and casual (default)</TD>
               </TR>
               <TR no="8" isLast="false">
                  <TD rowspan="1" colspan="1">comp</TD>
                  <TD rowspan="1" colspan="1">Main competitor</TD>
                  <TD rowspan="1" colspan="1">Alphanumeric</TD>
                  <TD rowspan="1" colspan="1">No defaults</TD>
               </TR>
               <TR no="9" isLast="true">
                  <TD rowspan="1" colspan="1">terr</TD>
                  <TD rowspan="1" colspan="1">Territory</TD>
                  <TD rowspan="1" colspan="1">Option</TD>
                  <TD rowspan="1" colspan="1">Options are East and West</TD>
               </TR>
            </TBODY>
         </TABLE>
         <Paragraph/>
         <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="6">
               <TR no="1" isLast="false">
                  <TH rowspan="1" colspan="1">Attribute set</TH>
                  <TH rowspan="1" colspan="1">Description</TH>
                  <TH rowspan="1" colspan="1">Attributes</TH>
               </TR>
               <TR no="2" isLast="false">
                  <TD rowspan="1" colspan="1">CON</TD>
                  <TD rowspan="1" colspan="1">Default
				  attribute set for contacts</TD>
                  <TD rowspan="1" colspan="1">sf, fc</TD>
               </TR>
               <TR no="3" isLast="false">
                  <TD rowspan="1" colspan="1">BP</TD>
                  <TD rowspan="1" colspan="1">Default
				  attribute set for business partners</TD>
                  <TD rowspan="1" colspan="1">sf,
				  fc</TD>
               </TR>
               <TR no="4" isLast="false">
                  <TD rowspan="1" colspan="1">CALL</TD>
                  <TD rowspan="1" colspan="1">Default attribute set for calls</TD>
                  <TD rowspan="1" colspan="1">conv,
				  ccb</TD>
               </TR>
               <TR no="5" isLast="false">
                  <TD rowspan="1" colspan="1">APP</TD>
                  <TD rowspan="1" colspan="1">Default attribute set for appointments</TD>
                  <TD rowspan="1" colspan="1">lunch, dressc</TD>
               </TR>
               <TR no="6" isLast="true">
                  <TD rowspan="1" colspan="1">OPP</TD>
                  <TD rowspan="1" colspan="1">Default attribute set for
				  opportunities</TD>
                  <TD rowspan="1" colspan="1">comp, terr</TD>
               </TR>
            </TBODY>
         </TABLE>
      </ExampleSection>
      <Keyword type="glentry" order="d1e1589065">
         <Level1>attribute option</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="FeaturSets_td" Version="B60asy04" ContextApps="td">
      <Term>attribute set</Term>
      <Definition>A set used to group related attributes.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="9">
               <TR no="1" isLast="false">
                  <TH rowspan="1" colspan="1">Attribute</TH>
                  <TH rowspan="1" colspan="1">Description</TH>
                  <TH rowspan="1" colspan="1">Type</TH>
                  <TH rowspan="1" colspan="1">Details</TH>
               </TR>
               <TR no="2" isLast="false">
                  <TD rowspan="1" colspan="1">sf</TD>
                  <TD rowspan="1" colspan="1">Is
				  the person a soccer fan?</TD>
                  <TD rowspan="1" colspan="1">Option</TD>
                  <TD rowspan="1" colspan="1">Options are Yes and No;
				  default is No</TD>
               </TR>
               <TR no="3" isLast="false">
                  <TD rowspan="1" colspan="1">fc</TD>
                  <TD rowspan="1" colspan="1">Favorite soccer club</TD>
                  <TD rowspan="1" colspan="1">Alphanumeric</TD>
                  <TD rowspan="1" colspan="1">Default is &lt;blank&gt;</TD>
               </TR>
               <TR no="4" isLast="false">
                  <TD rowspan="1" colspan="1">conv</TD>
                  <TD rowspan="1" colspan="1">How did you value this
				  conversation?</TD>
                  <TD rowspan="1" colspan="1">Alphanumeric</TD>
                  <TD rowspan="1" colspan="1">No defaults</TD>
               </TR>
               <TR no="5" isLast="false">
                  <TD rowspan="1" colspan="1">ccb</TD>
                  <TD rowspan="1" colspan="1">Can I call you back next week?</TD>
                  <TD rowspan="1" colspan="1">Option</TD>
                  <TD rowspan="1" colspan="1">Options are Yes and No; default is No</TD>
               </TR>
               <TR no="6" isLast="false">
                  <TD rowspan="1" colspan="1">lunch</TD>
                  <TD rowspan="1" colspan="1">Should bring own lunch</TD>
                  <TD rowspan="1" colspan="1">Option</TD>
                  <TD rowspan="1" colspan="1">Options are Yes and No; default is No</TD>
               </TR>
               <TR no="7" isLast="false">
                  <TD rowspan="1" colspan="1">dressc</TD>
                  <TD rowspan="1" colspan="1">What is the dress code?</TD>
                  <TD rowspan="1" colspan="1">Option</TD>
                  <TD rowspan="1" colspan="1">Options are formal and casual (default)</TD>
               </TR>
               <TR no="8" isLast="false">
                  <TD rowspan="1" colspan="1">comp</TD>
                  <TD rowspan="1" colspan="1">Main competitor</TD>
                  <TD rowspan="1" colspan="1">Alphanumeric</TD>
                  <TD rowspan="1" colspan="1">No defaults</TD>
               </TR>
               <TR no="9" isLast="true">
                  <TD rowspan="1" colspan="1">terr</TD>
                  <TD rowspan="1" colspan="1">Territory</TD>
                  <TD rowspan="1" colspan="1">Option</TD>
                  <TD rowspan="1" colspan="1">Options are East and West</TD>
               </TR>
            </TBODY>
         </TABLE>
         <Paragraph/>
         <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="6">
               <TR no="1" isLast="false">
                  <TH rowspan="1" colspan="1">Attribute set</TH>
                  <TH rowspan="1" colspan="1">Description</TH>
                  <TH rowspan="1" colspan="1">Attributes</TH>
               </TR>
               <TR no="2" isLast="false">
                  <TD rowspan="1" colspan="1">CON</TD>
                  <TD rowspan="1" colspan="1">Default
				  attribute set for contacts</TD>
                  <TD rowspan="1" colspan="1">sf, fc</TD>
               </TR>
               <TR no="3" isLast="false">
                  <TD rowspan="1" colspan="1">BP</TD>
                  <TD rowspan="1" colspan="1">Default
				  attribute set for business partners</TD>
                  <TD rowspan="1" colspan="1">sf,
				  fc</TD>
               </TR>
               <TR no="4" isLast="false">
                  <TD rowspan="1" colspan="1">CALL</TD>
                  <TD rowspan="1" colspan="1">Default attribute set for calls</TD>
                  <TD rowspan="1" colspan="1">conv,
				  ccb</TD>
               </TR>
               <TR no="5" isLast="false">
                  <TD rowspan="1" colspan="1">APP</TD>
                  <TD rowspan="1" colspan="1">Default attribute set for appointments</TD>
                  <TD rowspan="1" colspan="1">lunch, dressc</TD>
               </TR>
               <TR no="6" isLast="true">
                  <TD rowspan="1" colspan="1">OPP</TD>
                  <TD rowspan="1" colspan="1">Default attribute set for
				  opportunities</TD>
                  <TD rowspan="1" colspan="1">comp, terr</TD>
               </TR>
            </TBODY>
         </TABLE>
      </ExampleSection>
      <Keyword type="glentry" order="d1e1589201">
         <Level1>attribute set</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589337">
         <Level1>back order</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589342">
         <Level1>back order quantity</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589347">
         <Level1>base price</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589352">
         <Level1>blanket warehousing order</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589370">
         <Level1>book price</Level1>
      </Keyword>
   </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="option">Minimum</GUIRef> The break is the
		  lowest number of a range.</Paragraph>
      </SimpleSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
            <THEAD noTR="1">
               <TR no="1" isLast="true">
                  <TD colspan="2" width="256" rowspan="1">Break type minimum</TD>
               </TR>
            </THEAD>
            <TBODY noTR="3">
               <TR no="1" isLast="false">
                  <TH width="133" rowspan="1" colspan="1">Ordered quantity</TH>
                  <TH width="119" rowspan="1" colspan="1">Discount</TH>
               </TR>
               <TR no="2" isLast="false">
                  <TD width="133" rowspan="1" colspan="1">10</TD>
                  <TD width="119" rowspan="1" colspan="1">3%</TD>
               </TR>
               <TR no="3" isLast="true">
                  <TD width="133" rowspan="1" colspan="1">50</TD>
                  <TD width="119" rowspan="1" colspan="1">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="option">Up To</GUIRef> The break is the
		  highest number of a range.</Paragraph>
      </SimpleSection>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
            <THEAD noTR="1">
               <TR no="1" isLast="true">
                  <TD colspan="2" width="257" rowspan="1">Break type up to</TD>
               </TR>
            </THEAD>
            <TBODY noTR="3">
               <TR no="1" isLast="false">
                  <TH width="132" rowspan="1" colspan="1">Distance</TH>
                  <TH width="121" rowspan="1" colspan="1">Freight rate</TH>
               </TR>
               <TR no="2" isLast="false">
                  <TD width="132" rowspan="1" colspan="1">100</TD>
                  <TD width="121" rowspan="1" colspan="1">10</TD>
               </TR>
               <TR no="3" isLast="true">
                  <TD width="132" rowspan="1" colspan="1">1000</TD>
                  <TD width="121" rowspan="1" colspan="1">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>
      <Keyword type="glentry" order="d1e1589378">
         <Level1>break type</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589446">
         <Level1>budget</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589456">
         <Level1>business partner's contact</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589451">
         <Level1>business partner 2</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589474">
         <Level1>business-partner order reference</Level1>
      </Keyword>
   </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, ERP Enterprise first searches 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, ERP Enterprise searches for the order discount that is specified for the business partner on
		  the order.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1589479">
         <Level1>business-partner prices/discounts</Level1>
      </Keyword>
   </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, ERP Enterprise first searches 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, ERP Enterprise searches
		  for the texts that are specified for the business partner on the order.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1589489">
         <Level1>business-partner texts</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589461">
         <Level1>business procedure</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589466">
         <Level1>business process</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589499">
         <Level1>buyer</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000402" Version="B60adoc0" ContextApps="td">
      <Term>call</Term>
      <Definition>An activity type that specifies a call scheduled for a contact,
		business partner, opportunity, or activity that you want to track through
		completion. A call has invited attendees.</Definition>
      <Keyword type="glentry" order="d1e1589505">
         <Level1>call</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000222" Version="B60asy04" ContextApps="td">
      <Term>called amount</Term>
      <Definition>The actual ordered quantity multiplied by the price per unit.</Definition>
      <Keyword type="glentry" order="d1e1589510">
         <Level1>called amount</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000218" Version="B60asy04" ContextApps="td">
      <Term>called quantity</Term>
      <Definition>The number of items currently ordered.</Definition>
      <Keyword type="glentry" order="d1e1589515">
         <Level1>called quantity</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589520">
         <Level1>call-off</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000140" Version="B60asy04" ContextApps="td">
      <Term>canceled</Term>
      <Definition>The status assigned to a purchase requisition when the
		requester cancels a requisition with the <GUIRef href="/baanerp/td/domains/pur.rqst#created" role="option">Created</GUIRef>, <GUIRef href="/baanerp/td/domains/pur.rqst#modified" role="option">Modified</GUIRef>, or <GUIRef href="/baanerp/td/domains/pur.rqst#rejected" role="option">Rejected</GUIRef> status. A canceled requisition cannot be changed.</Definition>
      <Keyword type="glentry" order="d1e1589525">
         <Level1>canceled</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589539">
         <Level1>capacity time unit</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589544">
         <Level1>carrier</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589549">
         <Level1>catalog</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589554">
         <Level1>category</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000390" Version="B60asy04" ContextApps="td">
      <Term>central contract</Term>
      <Definition>A contract to which no specific contract office is linked.</Definition>
      <Keyword type="glentry" order="d1e1589559">
         <Level1>central contract</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000089" Version="B60asy04" ContextApps="td">
      <Term>changed receipt date</Term>
      <Definition>The new receipt date that is used if the supplier cannot comply
		with the agreed receipt date and states a new receipt date. Together with the
		planned and/or confirmed receipt date, the changed receipt 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>
      <Keyword type="glentry" order="d1e1589575">
         <Level1>changed receipt date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000062" Version="B60adoc1" ContextApps="td">
      <Term>change order sequence number</Term>
      <Definition>A number that is used to assign the occurrence of changes to a
		purchase order or a sales order.</Definition>
      <Keyword type="glentry" order="d1e1589564">
         <Level1>change order sequence number</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589570">
         <Level1>change reason</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589580">
         <Level1>change type</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589585">
         <Level1>claim note</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589590">
         <Level1>clustering</Level1>
      </Keyword>
   </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. When the sales order lines are created, the related transactions are
		automatically concluded.</Definition>
      <SimpleSection>
         <Paragraph>When you create and save a collect sales order, ERP Enterprise sets the sales order
		  status to <GUIRef href="/baanerp/td/domains/sls.hdst#closed" role="option">Closed</GUIRef>. At the same time, ERP Enterprise creates a warehouse
		  order and sets the status of the warehouse order to <GUIRef href="/baanerp/wh/domains/inh.hsta#shipped" role="option">Shipped</GUIRef>. The warehouse order type is the warehouse order
		  type that is linked to the sales order type.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1589603">
         <Level1>collect order</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589617">
         <Level1>commingle</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589622">
         <Level1>commission</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589637">
         <Level1>commission/rebate group</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589627">
         <Level1>commission agreement</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589632">
         <Level1>commission amount</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589643">
         <Level1>competitor</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000392">
      <Term>component</Term>
      <Definition>An item that is sold, and invoiced in combination with other
		items as part of a kit.</Definition>
      <Keyword type="glentry" order="d1e1589648">
         <Level1>component</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000174" Version="B60adoc0" ContextApps="td">
      <Term>configuration date</Term>
      <Definition>The date on which the bill of material is exploded.</Definition>
      <Keyword type="glentry" order="d1e1589653">
         <Level1>configuration date</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589658">
         <Level1>confirmed back order</Level1>
      </Keyword>
   </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
		sales representative and communicated to the buyer. The buyer then uses this
		date to enter the confirmed receipt date on the purchase order.</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>
      <Keyword type="glentry" order="d1e1589663">
         <Level1>confirmed delivery date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000091" Version="B60asy04" ContextApps="td">
      <Term>confirmed receipt date</Term>
      <Definition>The receipt date for the items, which is confirmed by the
		buy-from business partner or confirmed to the sold-to 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 receipt date on the
			 order lines.</ListItem>
            <ListItem>As the reference date for the printing of reminders.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1589678">
         <Level1>confirmed receipt date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Contract_td" Version="B60asy04" ContextApps="td">
      <Term>contract</Term>
      <Definition>An agreement between two parties to purchase or sell an
		unspecified quantity of material over a certain period of time. A contract can
		be linked to one or more orders or schedules.</Definition>
      <Keyword type="glentry" order="d1e1589693">
         <Level1>contract</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589698">
         <Level1>contract acknowledgments</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589703">
         <Level1>contract date</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589708">
         <Level1>contract line</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000136" Version="B60asy04" ContextApps="td">
      <Term>contract price</Term>
      <Definition>The agreed upon price in a sales contract, purchase contract,
		or request-for- quotation (RFQ).</Definition>
      <Keyword type="glentry" order="d1e1589713">
         <Level1>contract price</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000332" Version="B60adoc1" ContextApps="td">
      <Term>contract price revision</Term>
      <Definition>A date-controlled agreement for price and discount elements on
		the 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 contract line.</Definition>
      <Keyword type="glentry" order="d1e1589719">
         <Level1>contract price revision</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000214" Version="B60asy04" ContextApps="td">
      <Term>contract quantity</Term>
      <Definition>The quantity that must be delivered according to the contract
		agreements. The contract quantity must always be greater than zero.</Definition>
      <Keyword type="glentry" order="d1e1589724">
         <Level1>contract quantity</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589729">
         <Level1>control state</Level1>
      </Keyword>
   </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: (alternative
		unit/base unit)</Definition>
      <Keyword type="glentry" order="d1e1589734">
         <Level1>conversion factor</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000141" Version="B60asy04" ContextApps="td">
      <Term>converted</Term>
      <Definition>The status assigned to a purchase requisition when the buyer
		converts a requisition with the <GUIRef href="/baanerp/td/domains/pur.rqst#approved" role="option">Approved</GUIRef> status to a request-for-quotation (RFQ) or a
		purchase order.</Definition>
      <Keyword type="glentry" order="d1e1589739">
         <Level1>converted</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="381" Version="6.0a" ContextApps="td">
      <Term>copy exception</Term>
      <Definition>A field that is not automatically copied from the source order
		to the target order and for which you must define a copy action.</Definition>
      <Keyword type="glentry" order="d1e1589747">
         <Level1>copy exception</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="382" Version="6.0a" ContextApps="td">
      <Term>copy template</Term>
      <Definition>A standard set of <Link href="/baanerp/td/glossary/glossary#381" role="glossary">copy exceptions</Link> based on which existing orders are copied
		to target orders.</Definition>
      <Keyword type="glentry" order="d1e1589752">
         <Level1>copy template</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589760">
         <Level1>cost order</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000143" Version="B60asy04" ContextApps="td">
      <Term>created</Term>
      <Definition>The status assigned to a purchase requisition when the
		requester enters and saves a purchase requisition.</Definition>
      <Keyword type="glentry" order="d1e1589770">
         <Level1>created</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589765">
         <Level1>create new structure</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589775">
         <Level1>CUM reset date</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589781">
         <Level1>CUMs start date</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589786">
         <Level1>cumulatives (CUMs)</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000240" Version="B60asy04" ContextApps="td">
      <Term>customer order number</Term>
      <Definition>The number the sold-to business partner assigned to the order.
		In the automotive industry, it can represent the sold-to business partner's
		purchase contract number.</Definition>
      <Keyword type="glentry" order="d1e1589794">
         <Level1>customer order number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000391" Version="B60asy04" ContextApps="td">
      <Term>decentral contract</Term>
      <Definition>A contract that is linked to a specific contract office.</Definition>
      <Keyword type="glentry" order="d1e1589799">
         <Level1>decentral contract</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="InstalSchedu_td" Version="B60asy04" ContextApps="td">
      <Term>default installment schedule</Term>
      <Definition>A schedule set with installment defaults used to generate
		installments on sales orders or project contracts.</Definition>
      <SimpleSection>
         <Paragraph>After entering the desired schedule number, you can specify
		  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 specified on the installment line.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1589804">
         <Level1>default installment schedule</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000144" Version="B60adoc1" ContextApps="td">
      <Term>deleted</Term>
      <Definition>The status assigned to a purchase requisition when a
		requisition with the <GUIRef href="/baanerp/td/domains/pur.rqst#converted" role="option">Converted</GUIRef> or <GUIRef href="/baanerp/td/domains/pur.rqst#canceled" role="option">Canceled</GUIRef> status is deleted.</Definition>
      <Keyword type="glentry" order="d1e1589812">
         <Level1>deleted</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000219" Version="B60asy04" ContextApps="td">
      <Term>delivered quantity</Term>
      <Definition>The quantity of goods expressed in the sales unit or the
		inventory unit, which is delivered to the sold-to business partner.</Definition>
      <Keyword type="glentry" order="d1e1589823">
         <Level1>delivered quantity</Level1>
      </Keyword>
   </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" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="5">
               <TR no="1" isLast="false">
                  <TH width="105" rowspan="1" colspan="1">Contract line</TH>
                  <TH width="129" rowspan="1" colspan="1">Delivery contract</TH>
                  <TH width="139" rowspan="1" colspan="1">Purchase order
				  (PO)</TH>
               </TR>
               <TR no="2" isLast="false">
                  <TD width="105" rowspan="1" colspan="1">100 pieces (pcs)</TD>
                  <TD width="129" rowspan="1" colspan="1">2000/12/01 20 pcs</TD>
                  <TD width="139" rowspan="1" colspan="1">PO1 2000/12/01 20 pcs</TD>
               </TR>
               <TR no="3" isLast="false">
                  <TD width="105" rowspan="1" colspan="1">-</TD>
                  <TD width="129" rowspan="1" colspan="1">2000/02/08 25 pcs</TD>
                  <TD width="139" rowspan="1" colspan="1">PO2 2000/02/08 25 pcs</TD>
               </TR>
               <TR no="4" isLast="false">
                  <TD width="105" rowspan="1" colspan="1">-</TD>
                  <TD width="129" rowspan="1" colspan="1">2000/12/15 40 pcs</TD>
                  <TD width="139" rowspan="1" colspan="1">PO3
				  2000/12/15 40 pcs</TD>
               </TR>
               <TR no="5" isLast="true">
                  <TD width="105" rowspan="1" colspan="1">-</TD>
                  <TD width="129" rowspan="1" colspan="1">2000/12/22 15 pcs</TD>
                  <TD width="139" rowspan="1" colspan="1">PO4 2000/12/22 15
				  pcs</TD>
               </TR>
            </TBODY>
         </TABLE>
      </ExampleSection>
      <Keyword type="glentry" order="d1e1589828">
         <Level1>delivery contract</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589873">
         <Level1>delivery date</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589878">
         <Level1>delivery date tolerance (-)</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589883">
         <Level1>delivery date tolerance (+)</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589889">
         <Level1>device</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="DirectDelive_td" Version="B60asy04" ContextApps="td">
      <Term>direct delivery</Term>
      <Definition>The process in which a seller orders 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
		or a service 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">Warehousing</GUIRef> is not involved.</Definition>
      <SimpleSection>
         <Paragraph>In a Vendor Managed Inventory (VMI) setup, a direct delivery
		  is achieved by creating a purchase order for the customer warehouse.</Paragraph>
      </SimpleSection>
      <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>
            <ListItem>Costs and time are saved.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1589894">
         <Level1>direct delivery</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589917">
         <Level1>discount</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589932">
         <Level1>discount amount</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589937">
         <Level1>discount percentage</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589942">
         <Level1>discount schedule</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589947">
         <Level1>doubtful customer</Level1>
      </Keyword>
   </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 a record is valid.</Definition>
      <Keyword type="glentry" order="d1e1589952">
         <Level1>effectivity period</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000408" Version="B60adoc0" ContextApps="td">
      <Term>e-mail</Term>
      <Definition>An activity type that specifies an e-mail created for a
		contact, business partner, opportunity, or activity that you want to record in ERP Enterprise. E-mails can be
		created to send them, but also to manually register received e-mails. An e-mail
		has selected recipients.</Definition>
      <Keyword type="glentry" order="d1e1589957">
         <Level1>e-mail</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000228" Version="B60asy04" ContextApps="td">
      <Term>employee number</Term>
      <Definition>The number that identifies an employee.</Definition>
      <Keyword type="glentry" order="d1e1589962">
         <Level1>employee number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000227" Version="B60asy04" ContextApps="td">
      <Term>end date</Term>
      <Definition>The date and time the activity is completed.</Definition>
      <Keyword type="glentry" order="d1e1589967">
         <Level1>end date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000329" Version="B60adoc1" ContextApps="td">
      <Term>exception rule</Term>
      <Definition>If an approval rule is based on exception rules, ERP Enterprise 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 ERP Enterprise to approve the purchase order.</Definition>
      <Keyword type="glentry" order="d1e1589973">
         <Level1>exception rule</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589978">
         <Level1>expiry date</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589983">
         <Level1>extensions</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589993">
         <Level1>fab authorization</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1589988">
         <Level1>fab authorization through date</Level1>
      </Keyword>
   </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" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="5">
               <TR no="1" isLast="false">
                  <TD rowspan="1" colspan="1">Issue/current date</TD>
                  <TD rowspan="1" colspan="1">Quantity</TD>
               </TR>
               <TR no="2" isLast="false">
                  <TD rowspan="1" colspan="1">05.07.99</TD>
                  <TD rowspan="1" colspan="1">100</TD>
               </TR>
               <TR no="3" isLast="false">
                  <TD rowspan="1" colspan="1">12.07.99</TD>
                  <TD rowspan="1" colspan="1">100</TD>
               </TR>
               <TR no="4" isLast="false">
                  <TD rowspan="1" colspan="1">19.07.99</TD>
                  <TD rowspan="1" colspan="1">100</TD>
               </TR>
               <TR no="5" isLast="true">
                  <TD rowspan="1" colspan="1">26.07.99</TD>
                  <TD rowspan="1" colspan="1">100</TD>
               </TR>
            </TBODY>
         </TABLE>
         <Formula space-and-orientation="indented-estimated">
            <Paragraph>
Fab time fence   : 05.07.99 (+ 20 days) = 25.07.99.
Fab authorization: 10000 + 100 + 100 + 100 = 10300.
</Paragraph>
         </Formula>
      </ExampleSection>
      <Keyword type="glentry" order="d1e1589998">
         <Level1>fab period</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590046">
         <Level1>final invoice</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590051">
         <Level1>financial customer group</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590056">
         <Level1>firm requirement</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590061">
         <Level1>frozen period</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590066">
         <Level1>frozen zone-</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590072">
         <Level1>frozen zone+</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000013" Version="B60adoc1" ContextApps="td">
      <Term>full supply time</Term>
      <Definition>The total time required to obtain an item that is not
		forecasted. This time is used to calculate the full cumulative order lead time
		for an item, which includes the cumulative lead time of purchased
		parts.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>For item A, the supplier communicated a <Emphasis>supply
		  time</Emphasis> of 50 days. This is in fact a reduced lead time and is only
		  possible because a three year forecast is sent to the supplier for this item.
		  If additional quantities are needed, which are not included in the forecast,
		  the supplier needs the <Emphasis>full supply time</Emphasis>, which is 300
		  days.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e1590077">
         <Level1>full supply time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000302" Version="B60asy04" ContextApps="td">
      <Term>general category</Term>
      <Definition>A category that applies to any sold-to business partner.</Definition>
      <Keyword type="glentry" order="d1e1590093">
         <Level1>general category</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000075" Version="B60asy04" ContextApps="td">
      <Term>generation date</Term>
      <Definition>The date the specific schedule is (re)generated.</Definition>
      <Keyword type="glentry" order="d1e1590098">
         <Level1>generation date</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590103">
         <Level1>gross amount</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590108">
         <Level1>gross margin</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590113">
         <Level1>gross price</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590118">
         <Level1>gross profit</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590123">
         <Level1>high fab authorization</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590128">
         <Level1>high raw authorization</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000183" Version="B60asy04" ContextApps="td">
      <Term>hold reason</Term>
      <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>
      <Keyword type="glentry" order="d1e1590133">
         <Level1>hold reason</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000000000000014" Version="B60adoc1" ContextApps="td">
      <Term>immediate requirement</Term>
      <Definition>A requirement that must be shipped as soon as possible.</Definition>
      <Keyword type="glentry" order="d1e1590167">
         <Level1>immediate requirement</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590172">
         <Level1>installment</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590187">
         <Level1>internal processing time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="InvoicAmount_td" Version="B60asy04" ContextApps="td">
      <Term>invoiced amount</Term>
      <Definition>The amount charged to a business partner.</Definition>
      <Keyword type="glentry" order="d1e1590197">
         <Level1>invoiced amount</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000079" Version="B60asy04" ContextApps="td">
      <Term>invoice date</Term>
      <Definition>The date on which the invoice is printed.</Definition>
      <Keyword type="glentry" order="d1e1590192">
         <Level1>invoice date</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590202">
         <Level1>invoiced cumulative</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000109" Version="B60asy04" ContextApps="td">
      <Term>invoiced quantity</Term>
      <Definition>The number of items actually billed.</Definition>
      <Keyword type="glentry" order="d1e1590210">
         <Level1>invoiced quantity</Level1>
      </Keyword>
   </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="option">Length</GUIRef>, <GUIRef href="/baanerp/tc/domains/tccu#area" role="option">Area (m2)</GUIRef>, or <GUIRef href="/baanerp/tc/domains/tccu#volume" role="option">Volume</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e1590215">
         <Level1>item dimensions</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590229">
         <Level1>job titles</Level1>
      </Keyword>
   </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>
         <Paragraph>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.</Paragraph>
         <List>
            <ListIntro>The components of a kit can be of the following types:</ListIntro>
            <ListItem>Purchased items</ListItem>
            <ListItem>Manufactured items</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>
      <Keyword type="glentry" order="d1e1590234">
         <Level1>kit</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590252">
         <Level1>last receipt date</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590257">
         <Level1>layout code</Level1>
      </Keyword>
   </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 an opportunity or not) that can be printed and composed
		by using variables.</Definition>
      <Keyword type="glentry" order="d1e1590262">
         <Level1>letters</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590267">
         <Level1>level attribute</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590280">
         <Level1>line level promotion</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590272">
         <Level1>line of business</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590285">
         <Level1>list type</Level1>
      </Keyword>
   </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 schedule messages, frozen
		periods, authorizations, delivery patterns, carrier, and so on.</Definition>
      <Keyword type="glentry" order="d1e1590290">
         <Level1>logistic agreements</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590295">
         <Level1>lower bound</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590303">
         <Level1>lower limit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000406" Version="B60adoc0" ContextApps="td">
      <Term>mailing</Term>
      <Definition>An activity type that specifies a standard letter printed for a
		contact, business partner, opportunity, or activity with specific business
		object information merged in. A mailing is always generated from an activity
		template.</Definition>
      <Keyword type="glentry" order="d1e1590308">
         <Level1>mailing</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590314">
         <Level1>manufactured item</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000376" Version="B60asy04" ContextApps="td">
      <Term>manufacturer part number (MPN)</Term>
      <Definition>The unique identification of a manufacturer's item code, which
		is used in the item ordering and identification process.</Definition>
      <Keyword type="glentry" order="d1e1590319">
         <Level1>manufacturer part number (MPN)</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590324">
         <Level1>margin</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590329">
         <Level1>margin control</Level1>
      </Keyword>
   </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. However, the material release can also contain the actual order.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1590334">
         <Level1>material release</Level1>
      </Keyword>
   </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>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 <GUIRef href="/baanerp/td/domains/pcg.maty#sobook" role="option">Sales Price</GUIRef>, the matrix definition is Furni (this name is user-definable),
		  and the matrix attributes are <GUIRef href="/baanerp/td/domains/pcg.attr#item" role="option">Item</GUIRef> and <GUIRef href="/baanerp/td/domains/pcg.attr#pame" role="option">Payment Method</GUIRef>.</Paragraph>
         <Paragraph>In the <GUIRef href="/baanerp/td/pcg" role="module">Pricing</GUIRef> matrix, you specify the values for the matrix
		  attributes.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1590342">
         <Level1>matrix attributes</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000362" Version="B60asy04" ContextApps="tc">
      <Term>matrix attribute set</Term>
      <Definition>A set that groups matrix attributes of the same matrix type for
		use on matrix definitions.</Definition>
      <SimpleSection>
         <Paragraph>The matrix attributes that you can specify in a matrix
		  definition are determined by the attribute set that is selected in the pricing
		  parameters for the matrix type.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1590371">
         <Level1>matrix attribute set</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="MatrixDefini_td" Version="B60adoc1" ContextApps="td">
      <Term>matrix definition</Term>
      <Definition>Defines the group of elements (matrix attributes) that a <GUIRef href="/baanerp/td/pcg" role="module">Pricing</GUIRef> matrix uses to
		determine a price, discount, promotion, or freight rate.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>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 <GUIRef href="/baanerp/td/domains/pcg.maty#sobook" role="option">Sales Price</GUIRef>, the matrix definition is Furni (this name is user-definable),
		  and the matrix attributes are <GUIRef href="/baanerp/td/domains/pcg.attr#item" role="option">Item</GUIRef> and <GUIRef href="/baanerp/td/domains/pcg.attr#pame" role="option">Payment Method</GUIRef>.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1590379">
         <Level1>matrix definition</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000101" Version="B60asy04" ContextApps="td">
      <Term>matrix priority</Term>
      <Definition>For a matrix type, the order in which matrix definitions are
		searched for.</Definition>
      <Keyword type="glentry" order="d1e1590406">
         <Level1>matrix priority</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="MatrixType_td" Version="B60adoc0" ContextApps="td">
      <Term>matrix type</Term>
      <Definition>Defines the type of a matrix definition and is linked to a set
		of matrix attributes.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>The following matrix types are available in <GUIRef href="/baanerp/td/pcg" role="module">Pricing</GUIRef>:</ListIntro>
            <ListItem> 
               <GUIRef href="/baanerp/td/domains/pcg.maty#sobook" role="option">Sales Price</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/td/domains/pcg.maty#soldsc" role="option">Sales Line Discount</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/td/domains/pcg.maty#sodsc" role="option">Sales Total Discount</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/td/domains/pcg.maty#pobook" role="option">Purchase Price</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/td/domains/pcg.maty#poldsc" role="option">Purchase Line Discount</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/td/domains/pcg.maty#podsc" role="option">Purchase Total Discount</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/td/domains/pcg.maty#transfer" role="option">Transfer Price</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/td/domains/pcg.maty#lineprom" role="option">Line Promotions</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/td/domains/pcg.maty#ordprom" role="option">Order Promotions</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/td/domains/pcg.maty#clfrate" role="option">Client Freight Rate</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/td/domains/pcg.maty#cafrate" role="option">Carrier Freight Rate</GUIRef>
            </ListItem>
         </List>
         <Paragraph>Each type has its own a selection of attributes. For a matrix
		  type, the combination of a maximum of six attributes identifies the matrix
		  definition.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1590411">
         <Level1>matrix type</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590470">
         <Level1>maximum capacity tolerance</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590476">
         <Level1>maximum contract quantity</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590481">
         <Level1>maximum order quantity</Level1>
      </Keyword>
   </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 computer mouse and a CD player are defined as
		  related items used to configure a personal computer. But, you can also select a
		  computer mouse as a separate item.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e1590489">
         <Level1>menu</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590499">
         <Level1>minimum capacity tolerance</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590504">
         <Level1>minimum contract quantity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000149" Version="B60asy04" ContextApps="td">
      <Term>modified</Term>
      <Definition>The status assigned to a purchase requisition when the
		requester changes a requisition header or line for a requisition with the <GUIRef href="/baanerp/td/domains/pur.rqst#rejected" role="option">Rejected</GUIRef> status. The modified requisition can be
		resubmitted for approval.</Definition>
      <Keyword type="glentry" order="d1e1590509">
         <Level1>modified</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000377" Version="B60asy04" ContextApps="td">
      <Term>MPN set</Term>
      <Definition>A set of manufacturer part numbers (MPNs) that belongs to a
		purchase order line or a purchase schedule line.</Definition>
      <Keyword type="glentry" order="d1e1590517">
         <Level1>MPN set</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590522">
         <Level1>net amount</Level1>
      </Keyword>
   </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 space-and-orientation="indented-estimated">
            <Paragraph>Amount = (Quantity * Price) - Order Line Discount</Paragraph>
         </Formula>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1590530">
         <Level1>net order line amount</Level1>
      </Keyword>
   </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 space-and-orientation="indented-estimated">
            <Paragraph>Net price = book price - line discount - order discount</Paragraph>
         </Formula>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1590539">
         <Level1>net price</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590548">
         <Level1>non-referenced schedule</Level1>
      </Keyword>
   </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>A normal contract cannot be activated if another active
		  contract exists for the same business partner in a specific period.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1590554">
         <Level1>normal contract</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000407" Version="B60adoc1" ContextApps="td">
      <Term>note</Term>
      <Definition>A text comment with log information, which can be linked to an
		object.</Definition>
      <SimpleSection>
         <Paragraph>Multiple notes can be linked to an object.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1590562">
         <Level1>note</Level1>
      </Keyword>
   </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="option">Delivery</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/td/domains/pur.ctyp#quality" role="option">Quality</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/td/domains/pur.ctyp#quantity" role="option">Quantity</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/td/domains/pur.ctyp#costperf" role="option">Cost Performance</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/td/domains/pur.ctyp#orderconf" role="option">Order Confirmation</GUIRef>
            </ListItem>
            <ListItem> 
               <GUIRef href="/baanerp/td/domains/pur.ctyp#period.rating" role="option">Period Rating</GUIRef>
            </ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1590570">
         <Level1>objective criterion</Level1>
      </Keyword>
   </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" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="4">
               <TR no="1" isLast="false">
                  <TD rowspan="1" colspan="1">Days</TD>
                  <TD width="35" rowspan="1" colspan="1">1</TD>
                  <TD width="35" rowspan="1" colspan="1">2</TD>
                  <TD width="35" rowspan="1" colspan="1">3</TD>
                  <TD width="35" rowspan="1" colspan="1">4</TD>
                  <TD width="35" rowspan="1" colspan="1">5</TD>
                  <TD width="35" rowspan="1" colspan="1">6</TD>
                  <TD width="35" rowspan="1" colspan="1">7</TD>
                  <TD width="35" rowspan="1" colspan="1">8</TD>
                  <TD width="35" rowspan="1" colspan="1">9</TD>
                  <TD width="35" rowspan="1" colspan="1">10</TD>
                  <TD width="35" rowspan="1" colspan="1">11</TD>
                  <TD width="35" rowspan="1" colspan="1">12</TD>
                  <TD width="35" rowspan="1" colspan="1">13</TD>
                  <TD width="35" rowspan="1" colspan="1">14</TD>
                  <TD width="35" rowspan="1" colspan="1">15</TD>
                  <TD width="35" rowspan="1" colspan="1">16</TD>
                  <TD width="35" rowspan="1" colspan="1">17</TD>
                  <TD width="35" rowspan="1" colspan="1">18</TD>
                  <TD width="35" rowspan="1" colspan="1">19</TD>
                  <TD width="35" rowspan="1" colspan="1">20</TD>
               </TR>
               <TR no="2" isLast="false">
                  <TD rowspan="1" colspan="1">Requirements</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">1</TD>
                  <TD width="35" rowspan="1" colspan="1">1</TD>
                  <TD width="35" rowspan="1" colspan="1">1</TD>
                  <TD width="35" rowspan="1" colspan="1">1</TD>
                  <TD width="35" rowspan="1" colspan="1">1</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">1</TD>
                  <TD width="35" rowspan="1" colspan="1">1</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
               </TR>
               <TR no="3" isLast="false">
                  <TD rowspan="1" colspan="1">Delivery pattern</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">X</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">X</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">X</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
               </TR>
               <TR no="4" isLast="true">
                  <TD rowspan="1" colspan="1">Clustered demand</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">3</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">3</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">1</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
                  <TD width="35" rowspan="1" colspan="1">-</TD>
               </TR>
            </TBODY>
         </TABLE>
      </ExampleSection>
      <Keyword type="glentry" order="d1e1590603">
         <Level1>offsetting</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590792">
         <Level1>open balance</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000178" Version="B60asy04" ContextApps="td">
      <Term>opportunity</Term>
      <Definition>Used by a sales person to record and monitor sales information
		related to a business partner with the purpose of selling, promoting, or
		distributing a product or service to this business partner.</Definition>
      <Keyword type="glentry" order="d1e1590797">
         <Level1>opportunity</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000177" Version="B60asy04" ContextApps="td">
      <Term>opportunity type</Term>
      <Definition>A way to classify opportunities with similar characteristics
		for sorting and selecting purposes.</Definition>
      <Keyword type="glentry" order="d1e1590802">
         <Level1>opportunity type</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590807">
         <Level1>option</Level1>
      </Keyword>
   </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 delivery terms.</Definition>
      <Keyword type="glentry" order="d1e1590812">
         <Level1>order acknowledgment</Level1>
      </Keyword>
   </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, or the date on which the sales order is confirmed to the
		sold-to business partner.</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>
      <Keyword type="glentry" order="d1e1590817">
         <Level1>order confirmation date</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590825">
         <Level1>order date</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590831">
         <Level1>order discount</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e1590831">
         <Level1>Synonym: total discount.</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590869">
         <Level1>ordered quantity</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590874">
         <Level1>order level promotion</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590838">
         <Level1>order line discount</Level1>
      </Keyword>
   </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 space-and-orientation="indented-estimated">
            <Paragraph>Order Line Discount Amount = Quantity * Price * 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>
      <Keyword type="glentry" order="d1e1590843">
         <Level1>order line discount amount</Level1>
      </Keyword>
   </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 ERP Enterprise sessions, or user
		defined sources such as phone, mail, and so on.</Definition>
      <Keyword type="glentry" order="d1e1590854">
         <Level1>order origin</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590859">
         <Level1>order priority simulations</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590864">
         <Level1>order type</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000375" Version="B60adoc1" ContextApps="td">
      <Term>over-delivery</Term>
      <Definition>A positive deviation from the original ordered quantity.</Definition>
      <Keyword type="glentry" order="d1e1590879">
         <Level1>over-delivery</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590884">
         <Level1>parent criterion</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000030" Version="B60adoc1" ContextApps="td">
      <Term>pattern</Term>
      <Definition>A scheme on which you can define the day of the week, day of
		the month, or day of the year, and the time of the day you want an activity,
		such as a release or a delivery, to be carried out.</Definition>
      <Keyword type="glentry" order="d1e1590889">
         <Level1>pattern</Level1>
      </Keyword>
   </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, such as the month or the day of the month,
		on which you want to carry out the activity.</Definition>
      <Keyword type="glentry" order="d1e1590895">
         <Level1>pattern code</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000158" Version="B60asy04" ContextApps="td">
      <Term>pending approval</Term>
      <Definition>The status assigned to a purchase requisition when the
		requester submits a requisition with the <GUIRef href="/baanerp/td/domains/pur.rqst#created" role="option">Created</GUIRef> or <GUIRef href="/baanerp/td/domains/pur.rqst#modified" role="option">Modified</GUIRef> status for approval.</Definition>
      <Keyword type="glentry" order="d1e1590900">
         <Level1>pending approval</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590911">
         <Level1>period table</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="PhasesInTheP_td" Version="B60asy04" ContextApps="td">
      <Term>phase</Term>
      <Definition>The identification of a stage or phase in the sales process.
		For example, analysis, proposal, negotiation, and so on.</Definition>
      <Keyword type="glentry" order="d1e1590919">
         <Level1>phase</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590924">
         <Level1>phone (office)</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000130" Version="B60asy04" ContextApps="td">
      <Term>pick-up sheet</Term>
      <Definition>A list of items to be picked-up at the supplier’s site by a
		specific carrier for transport to the customer on a specific day.</Definition>
      <Keyword type="glentry" order="d1e1590929">
         <Level1>pick-up sheet</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590934">
         <Level1>planned delivery date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000090" Version="B60adoc1" ContextApps="td">
      <Term>planned receipt date</Term>
      <Definition>The planned date on which the items on the order/schedule line
		are planned to be received. The planned receipt date cannot occur before the
		order date/schedule generation date.</Definition>
      <Keyword type="glentry" order="d1e1590939">
         <Level1>planned receipt date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000000000000017" Version="B60asy04" ContextApps="td">
      <Term>planned requirement</Term>
      <Definition>A requirement that is communicated to a business partner for
		information and planning purposes only.</Definition>
      <Keyword type="glentry" order="d1e1590944">
         <Level1>planned requirement</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590949">
         <Level1>planned shipment date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000326" Version="B60adoc1" ContextApps="td">
      <Term>planned warehouse order</Term>
      <Definition>An order created in <GUIRef href="/baanerp/sales" role="package">Sales</GUIRef> that forms the
		basis for most schedule-related processes. Planned warehouse orders, which are
		created during sales schedule approval, decouple schedule updates and revisions
		from warehouse orders. They serve as the interface between <GUIRef href="/baanerp/sales" role="package">Sales</GUIRef> on one hand and <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef> and <GUIRef href="/baanerp/ci" role="package">Invoicing</GUIRef> on the
		other hand.</Definition>
      <Keyword type="glentry" order="d1e1590954">
         <Level1>planned warehouse order</Level1>
      </Keyword>
   </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 ERP Enterprise generates.</Definition>
      <Keyword type="glentry" order="d1e1590972">
         <Level1>planner</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590977">
         <Level1>position number of an order line</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590982">
         <Level1>potential back order</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1590997">
         <Level1>premium</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591002">
         <Level1>price agreements</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="PriceBook_td" Version="B60asy04" ContextApps="td">
      <Term>price book</Term>
      <Definition>An entity in which you can store price information that is
		valid for a given period of time.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>A price book includes the following elements:</ListIntro>
            <ListItem>A price book header,
			 which contains the code, type, and use of the price book.</ListItem>
            <ListItem>One or more price book
			 lines, which contain the items.</ListItem>
         </List>
         <Paragraph>A quantity or value break discount schedule can be linked to
		  a price book.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1591007">
         <Level1>price book</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591022">
         <Level1>price group</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591027">
         <Level1>price matrix</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="PriceUnit_td" Version="B60asy04" ContextApps="td">
      <Term>price unit</Term>
      <Definition>The unit to which the (sales/purchase) price applies.</Definition>
      <Keyword type="glentry" order="d1e1591032">
         <Level1>price unit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="PricinPCG_td" Version="B60adoc0" ContextApps="td">
      <Term>Pricing</Term>
      <Definition>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 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>
      <Keyword type="glentry" order="d1e1591037">
         <Level1>Pricing</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000361" Version="B60adoc1" ContextApps="td">
      <Term>pricing information</Term>
      <Definition>Pricing information includes prices, discounts, promotions, and
		freight rates. If pricing 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 matrix.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
      </ExampleSection>
      <SimpleSection>
         <Paragraph>You can define a price for the following attributes and
		  values:</Paragraph>
         <TABLE border="1" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="4">
               <TR no="1" isLast="false">
                  <TH rowspan="1" colspan="1">Attribute</TH>
                  <TH rowspan="1" colspan="1">Value</TH>
               </TR>
               <TR no="2" isLast="false">
                  <TD rowspan="1" colspan="1">Sold-to
				  business partner</TD>
                  <TD rowspan="1" colspan="1">Apex Wholesalers, Inc.</TD>
               </TR>
               <TR no="3" isLast="false">
                  <TD rowspan="1" colspan="1">Delivery
				  terms</TD>
                  <TD rowspan="1" colspan="1">CoD (cash on delivery)</TD>
               </TR>
               <TR no="4" isLast="true">
                  <TD rowspan="1" colspan="1">Item</TD>
                  <TD rowspan="1" colspan="1">Can opener
				  aw10</TD>
               </TR>
            </TBODY>
         </TABLE>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1591045">
         <Level1>pricing information</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000360" Version="B60adoc1" ContextApps="td">
      <Term>pricing matrices</Term>
      <Definition>A <GUIRef href="/baanerp/td/pcg" role="module">Pricing</GUIRef> matrix is an entity in which prices, discounts, freight rates, or promotions
		are maintained for customers, suppliers and/or items.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>In the <GUIRef href="/baanerp/td/pcg" role="module">Pricing</GUIRef> module, the following types of matrices are
			 available:</ListIntro>
            <ListItem>Price matrices</ListItem>
            <ListItem>Discount matrices</ListItem>
            <ListItem>Promotion matrices</ListItem>
            <ListItem>Freight Rate matrices</ListItem>
         </List>
         <List>
            <ListIntro>Essentially, a <GUIRef href="/baanerp/td/pcg" role="module">Pricing</GUIRef> matrix includes the following elements:</ListIntro>
            <ListItem>A <GUIRef href="/baanerp/td/pcg/tdpcg0130m000#tdpcg030.maty" role="manual">Matrix Type</GUIRef>
            </ListItem>
            <ListItem>A <GUIRef href="/baanerp/td/pcg/tdpcg0130m000#tdpcg030.made" role="manual">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</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" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="4">
               <TR no="1" isLast="false">
                  <TH rowspan="1" colspan="1">Attribute</TH>
                  <TH rowspan="1" colspan="1">Value</TH>
               </TR>
               <TR no="2" isLast="false">
                  <TD rowspan="1" colspan="1">Sold-to
				  business partner</TD>
                  <TD rowspan="1" colspan="1">Apex Wholesalers, Inc.</TD>
               </TR>
               <TR no="3" isLast="false">
                  <TD rowspan="1" colspan="1">Delivery
				  terms</TD>
                  <TD rowspan="1" colspan="1">CoD (cash on delivery)</TD>
               </TR>
               <TR no="4" isLast="true">
                  <TD rowspan="1" colspan="1">Item</TD>
                  <TD rowspan="1" colspan="1">Can opener
				  aw10</TD>
               </TR>
            </TBODY>
         </TABLE>
         <Paragraph>When an order is entered for Apex Wholesalers, Inc. for item
		  Can opener aw10, and the delivery terms are CoD, the price maintained in the
		  price matrix is used to calculate the price for the order.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1591079">
         <Level1>pricing matrices</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591153">
         <Level1>printing/processing jobs</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591166">
         <Level1>priority</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591158">
         <Level1>prior required CUM</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="ProducVarian_td" Version="B60adoc1" ContextApps="td">
      <Term>product variant</Term>
      <Definition>A unique configuration of a configurable item. The variant
		results from the configuration process and includes information such as feature
		options, components, and operations.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>Configurable item: electric drill</Paragraph>
         <List>
            <ListIntro>Options:</ListIntro>
            <ListItem>3 power sources (batteries, 12 V or 220 V)</ListItem>
            <ListItem>2 colors (blue, gray).</ListItem>
         </List>
         <Paragraph>A total of 6 product variants can be produced with these
		  options.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e1591176">
         <Level1>product variant</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591195">
         <Level1>profit amount</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591171">
         <Level1>pro forma invoice</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591200">
         <Level1>project code</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000036" Version="B60asy04" ContextApps="td">
      <Term>promising status</Term>
      <Definition>A status that informs you about whether a sales quotation line,
		sales order line, or sales component line can be promised to a customer, or
		whether inventory checks must still be carried out or insufficient inventory
		situations must still be resolved for the line.</Definition>
      <Keyword type="glentry" order="d1e1591205">
         <Level1>promising status</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591210">
         <Level1>promotion</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591221">
         <Level1>promotional contract</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591215">
         <Level1>promotion group</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000335" Version="B60adoc1" ContextApps="td">
      <Term>pull schedule</Term>
      <Definition>Two types of pull schedules exist:</Definition>
      <SimpleSection>
         <List>
            <ListItemHead>Pull forecast schedules</ListItemHead>
            <ListItem>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>
            <ListItemHead>Pull call-off schedules</ListItemHead>
            <ListItem>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">Warehousing</GUIRef> (KANBAN, Time-phased order point).</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1591226">
         <Level1>pull schedule</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591253">
         <Level1>purchase advice</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="PurchContra_td" Version="B60asy04" ContextApps="td">
      <Term>purchase contract</Term>
      <Definition>Purchase contracts are used to register specific agreements
		with a buy-from business partner that concern the delivery of specific goods.</Definition>
      <SimpleSection>
         <List>
            <ListIntro>A contract is comprised of:</ListIntro>
            <ListItem>A purchase contract header with general business partner
			 data, and optionally, a linked terms and conditions agreement.</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>
      <Keyword type="glentry" order="d1e1591258">
         <Level1>purchase contract</Level1>
      </Keyword>
   </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), ERP Enterprise writes a copy of the
		transaction to the history.</Definition>
      <Keyword type="glentry" order="d1e1591271">
         <Level1>purchase contract history</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591276">
         <Level1>purchase contract lines</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591281">
         <Level1>purchase coordinator</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000019" Version="B60asy04" ContextApps="td">
      <Term>purchase currency</Term>
      <Definition>The monetary unit in which the purchase price is expressed.</Definition>
      <Keyword type="glentry" order="d1e1591286">
         <Level1>purchase currency</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591444">
         <Level1>purchased item</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591291">
         <Level1>purchase invoice</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591299">
         <Level1>purchase office for requisitions</Level1>
      </Keyword>
   </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, payment terms, and delivery terms.</ListItem>
            <ListItem>One or more order lines with more detailed information about
			 the actual items to be delivered.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1591304">
         <Level1>purchase order</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591449">
         <Level1>purchase order acknowledgment</Level1>
      </Keyword>
   </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>Payment terms.</ListItem>
            <ListItem>Delivery terms.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1591318">
         <Level1>purchase order header</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591335">
         <Level1>purchase order history</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="PurchaOrderL_td" Version="B60adoc0" ContextApps="td">
      <Term>purchase order lines</Term>
      <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>
      <Keyword type="glentry" order="d1e1591340">
         <Level1>purchase order lines</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591360">
         <Level1>purchase order type</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591365">
         <Level1>purchase order unit of measure</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000380" Version="B60adoc1" ContextApps="td">
      <Term>purchase payable receipt</Term>
      <Definition>Indicates when billing is applicable for purchased goods and
		contains the payable and invoicing details for an order or schedule. By means
		of purchase payable receipts, updates to and from the <GUIRef href="/baanerp/tf/acp" role="module">Accounts Payable</GUIRef> module
		are handled.</Definition>
      <SimpleSection>
         <Paragraph>If the payment for the purchased goods is set to <GUIRef href="/baanerp/tc/domains/pmnt#pay.on.use" role="option">Pay on Use</GUIRef>, the payable receipt is generated when inventory related to a
		  purchase order or a purchase schedule is consumed, that is, issued from the
		  warehouse. If the payment is set to <GUIRef href="/baanerp/tc/domains/pmnt#pay.on.receipt" role="option">Pay on Receipt</GUIRef>, the payable receipt is generated the moment the purchased
		  goods are received.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1591370">
         <Level1>purchase payable receipt</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591387">
         <Level1>purchase price</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591392">
         <Level1>purchase price unit</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591397">
         <Level1>purchase release</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591418">
         <Level1>purchase requisition</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591433">
         <Level1>purchase schedule</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591439">
         <Level1>purchase unit</Level1>
      </Keyword>
   </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="option">Material Release</GUIRef>: only material releases are sent.
			 Shipping is performed based on the <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="option">Firm</GUIRef> and <GUIRef href="/baanerp/td/domains/pur.rtyp#immediate" role="option">Immediate</GUIRef> requirements in the material release.</ListItem>
            <ListItem>
               <GUIRef href="/baanerp/tc/domains/scrd#shipping" role="option">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="option">Firm</GUIRef> and <GUIRef href="/baanerp/td/domains/pur.rtyp#immediate" role="option">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="option">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="option">Firm</GUIRef> and <GUIRef href="/baanerp/td/domains/pur.rtyp#immediate" role="option">Immediate</GUIRef> requirements in the shipping schedule. No
			 forecasting data is sent to the supplier.</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1591462">
         <Level1>push schedule</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591507">
         <Level1>quantity</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591512">
         <Level1>quantity tolerance (-)</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591517">
         <Level1>quantity tolerance (+)</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591522">
         <Level1>quotation</Level1>
      </Keyword>
   </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 payment terms and delivery terms.</Definition>
      <Keyword type="glentry" order="d1e1591527">
         <Level1>quotation header</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591532">
         <Level1>quotation lines</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591537">
         <Level1>rate (currency exchange rate)</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591548">
         <Level1>raw authorizations</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591543">
         <Level1>raw authorization through date</Level1>
      </Keyword>
   </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" borderstyle="default" space-and-orientation="indented-estimated">
            <TBODY noTR="5">
               <TR no="1" isLast="false">
                  <TH width="135" rowspan="1" colspan="1">Issue/current date</TH>
                  <TH width="135" rowspan="1" colspan="1">Quantity</TH>
               </TR>
               <TR no="2" isLast="false">
                  <TD width="135" rowspan="1" colspan="1">05.07.99</TD>
                  <TD width="135" rowspan="1" colspan="1">100</TD>
               </TR>
               <TR no="3" isLast="false">
                  <TD width="135" rowspan="1" colspan="1">12.07.99</TD>
                  <TD width="135" rowspan="1" colspan="1">100</TD>
               </TR>
               <TR no="4" isLast="false">
                  <TD width="135" rowspan="1" colspan="1">19.07.99</TD>
                  <TD width="135" rowspan="1" colspan="1">100</TD>
               </TR>
               <TR no="5" isLast="true">
                  <TD width="135" rowspan="1" colspan="1">26.07.99</TD>
                  <TD width="135" rowspan="1" colspan="1">100</TD>
               </TR>
            </TBODY>
         </TABLE>
         <Formula space-and-orientation="indented-estimated">
            <Paragraph>
Raw time fence   : 05.07.99 (+ 20 days) = 25.07.99.
Raw authorization: 10000 + 100 + 100 + 100 = 10300.
</Paragraph>
         </Formula>
      </ExampleSection>
      <Keyword type="glentry" order="d1e1591553">
         <Level1>raw period</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591601">
         <Level1>rebate</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591606">
         <Level1>rebate agreement</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591611">
         <Level1>rebate amount</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591616">
         <Level1>received cumulative</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000068" Version="B60asy04" ContextApps="td">
      <Term>received quantity</Term>
      <Definition>The quantity delivered by the supplier identified in the
		purchase unit or the inventory unit.</Definition>
      <Keyword type="glentry" order="d1e1591621">
         <Level1>received quantity</Level1>
      </Keyword>
   </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">Warehousing</GUIRef>.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1591626">
         <Level1>reference</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591643">
         <Level1>reference A</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591648">
         <Level1>reference B</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591654">
         <Level1>reference date</Level1>
      </Keyword>
   </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 ERP Enterprise packages.</Definition>
      <Keyword type="glentry" order="d1e1591659">
         <Level1>referenced schedule</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591664">
         <Level1>regeneration</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000154" Version="B60asy04" ContextApps="td">
      <Term>rejected</Term>
      <Definition>The status assigned to a purchase requisition when an approver
		rejects a requisition with the <GUIRef href="/baanerp/td/domains/pur.rqst#submitted" role="option">Pending Approval</GUIRef> status.</Definition>
      <Keyword type="glentry" order="d1e1591672">
         <Level1>rejected</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000113" Version="B60asy04" ContextApps="td">
      <Term>rejected quantity</Term>
      <Definition>The number of delivered items that is rejected.</Definition>
      <Keyword type="glentry" order="d1e1591680">
         <Level1>rejected quantity</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591685">
         <Level1>relation</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591690">
         <Level1>relation team</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591695">
         <Level1>relation type</Level1>
      </Keyword>
   </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">Warehousing</GUIRef>. The
		release date is calculated by subtracting the warehouse inbound lead time from
		the planned delivery date.</Definition>
      <Keyword type="glentry" order="d1e1591700">
         <Level1>release date</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591708">
         <Level1>release position number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000000000000008" Version="B60asy04" ContextApps="td">
      <Term>release revision number</Term>
      <Definition>A number that uniquely identifies the revision of the release.
		The release revision number indicates the updates that are sent to the business
		partner.</Definition>
      <Keyword type="glentry" order="d1e1591713">
         <Level1>release revision number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000000000000010" Version="B60asy04" ContextApps="td">
      <Term>release type</Term>
      <Definition>A classification used to specify the type of the release based
		on which schedule requirements are grouped and EDI messages can be generated.
		These messages are indicated by the used schedule.</Definition>
      <Keyword type="glentry" order="d1e1591719">
         <Level1>release type</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591724">
         <Level1>reminder</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591729">
         <Level1>replace structure</Level1>
      </Keyword>
   </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, payment terms, delivery
		terms, 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>
      <Keyword type="glentry" order="d1e1591734">
         <Level1>request-for-quotation (RFQ)</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591746">
         <Level1>request-for-quotation (RFQ) line</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591754">
         <Level1>request-for-quotation date</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591759">
         <Level1>required cumulative</Level1>
      </Keyword>
   </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="option">Immediate</GUIRef>.</ListItem>
            <ListItem>
               <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="option">Firm</GUIRef>.</ListItem>
            <ListItem>
               <GUIRef href="/baanerp/td/domains/pur.rtyp#planned" role="option">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="option">Planned</GUIRef> or <GUIRef href="/baanerp/td/domains/pur.rtyp#immediate" role="option">Immediate</GUIRef>. For pull call-off schedules, the requirement
		  type is always <GUIRef href="/baanerp/td/domains/pur.rtyp#firm" role="option">Firm</GUIRef>.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1591764">
         <Level1>requirement type</Level1>
      </Keyword>
   </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 individual
		sales orders/schedules that are not related to a contract.</Definition>
      <Synonym>Synonym: retroactive billing.</Synonym>
      <Keyword type="glentry" order="d1e1591796">
         <Level1>retrobilling</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e1591796">
         <Level1>Synonym: retroactive billing.</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591803">
         <Level1>return date</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591808">
         <Level1>return note</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591814">
         <Level1>return order</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591819">
         <Level1>return reason</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591824">
         <Level1>RFQ criteria set</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591829">
         <Level1>RFQ criterion</Level1>
      </Keyword>
   </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 payment and delivery terms.</Definition>
      <Keyword type="glentry" order="d1e1591834">
         <Level1>rush order</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591839">
         <Level1>safety time</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591844">
         <Level1>sales acknowledgment code</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591849">
         <Level1>sales channel</Level1>
      </Keyword>
      <Keyword type="glentry" order="d1e1591849">
         <Level1>Synonym: channel</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000220" Version="B60asy04" ContextApps="td">
      <Term>sales contract</Term>
      <Definition>Sales contracts are used to register agreements about the
		delivery of goods with a sold-to business partner .</Definition>
      <SimpleSection>
         <List>
            <ListIntro>A contract is comprised of the following:</ListIntro>
            <ListItem>A sales contract header with general business partner data,
			 and optionally, a linked terms and conditions agreement.</ListItem>
            <ListItem>One or more sales contract lines with price/discount
			 agreements and quantity information that apply to an item or price group.</ListItem>
         </List>
      </SimpleSection>
      <SimpleSection/>
      <Keyword type="glentry" order="d1e1591856">
         <Level1>sales contract</Level1>
      </Keyword>
   </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. Optionally, a terms and conditions agreement can be linked to the
		header.</Definition>
      <Keyword type="glentry" order="d1e1591870">
         <Level1>sales contract header</Level1>
      </Keyword>
   </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, ERP Enterprise writes a
		copy of that contract to the history. A copy is created for each transaction.</Definition>
      <Keyword type="glentry" order="d1e1591992">
         <Level1>sales contract history</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591997">
         <Level1>sales contract line history</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000243" Version="B60asy04" ContextApps="td">
      <Term>sales currency</Term>
      <Definition>The monetary unit in which the sales price is expressed.</Definition>
      <Keyword type="glentry" order="d1e1591875">
         <Level1>sales currency</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591881">
         <Level1>sales invoice</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="SalesOffice_td" Version="B60asy04" ContextApps="td">
      <Term>sales office</Term>
      <Definition>A department that is identified in the company business model
		to manage the business partner's sales relations. The sales office is used to
		identify the locations that are responsible for the organization's sales
		activities.</Definition>
      <Keyword type="glentry" order="d1e1591886">
         <Level1>sales office</Level1>
      </Keyword>
   </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, payment
		  terms, and delivery terms 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>
      <Keyword type="glentry" order="d1e1591891">
         <Level1>sales order</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591899">
         <Level1>sales order header</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="InstalOrder_td" Version="B60asy04" ContextApps="td">
      <Term>sales order installment</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>
         <Paragraph>Billed installments are settled (subtracted from the goods
		  amount) when the goods are delivered and invoiced.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1590177">
         <Level1>sales order installment</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591904">
         <Level1>sales order lines</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591909">
         <Level1>sales order number</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591914">
         <Level1>sales order type</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591919">
         <Level1>sales order units of measure</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="SalesPrice_td" Version="B60asy04" ContextApps="td">
      <Term>sales price</Term>
      <Definition>The price for which an item is sold.</Definition>
      <Keyword type="glentry" order="d1e1591924">
         <Level1>sales price</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591929">
         <Level1>sales price list</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000403" Version="B60asy04" ContextApps="td">
      <Term>sales process</Term>
      <Definition>A standard sales methodology that must be followed when working
		on an opportunity. A sales process is split up in phases.</Definition>
      <Keyword type="glentry" order="d1e1591934">
         <Level1>sales process</Level1>
      </Keyword>
   </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, payment terms, and delivery terms 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>
      <Keyword type="glentry" order="d1e1591940">
         <Level1>sales quotations</Level1>
      </Keyword>
   </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>Ship-to address.</ListItem>
            <ListItem>Release type (material release/ shipping schedule/ sequence
			 shipping schedule/ pick-up sheet).</ListItem>
            <ListItem>Shipment based schedule/ delivery based schedule.</ListItem>
            <ListItem>Schedule quantity qualifier.</ListItem>
            <ListItem>Forecast horizon start and end.</ListItem>
            <ListItem>Sales release origin.</ListItem>
            <ListItem>Customer release.</ListItem>
            <ListItem>(Customer order).</ListItem>
         </List>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1591945">
         <Level1>sales release</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591972">
         <Level1>sales representative</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591977">
         <Level1>sales schedule</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1591982">
         <Level1>sales schedule revision number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="SalesUnit_td" Version="B60asy04" ContextApps="td">
      <Term>sales unit</Term>
      <Definition>The unit in which an item is sold.</Definition>
      <Keyword type="glentry" order="d1e1591987">
         <Level1>sales unit</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592002">
         <Level1>salutations</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592007">
         <Level1>schedule issue date</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592018">
         <Level1>schedule line</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592024">
         <Level1>schedule number</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592032">
         <Level1>schedule position number</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592037">
         <Level1>schedule quantity</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592042">
         <Level1>schedule revision number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000010" Version="B60asy04" ContextApps="td">
      <Term>schedule text</Term>
      <Definition>A specific text with for example additional reference
		information.</Definition>
      <Keyword type="glentry" order="d1e1592047">
         <Level1>schedule text</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592052">
         <Level1>search argument</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000255" Version="B60adoc1" ContextApps="td">
      <Term>search priorities</Term>
      <Definition>Search priorities are used to find a valid agreement for the
		entered search combination or search level.</Definition>
      <SimpleSection>
         <Paragraph>If a valid agreement is found for the first priority, the
		  agreement will be used. If not, ERP Enterprise searches for a valid agreement for the second priority and so on.</Paragraph>
      </SimpleSection>
      <Keyword type="glentry" order="d1e1592057">
         <Level1>search priorities</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592065">
         <Level1>segment</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000020" Version="B60asy04" ContextApps="td">
      <Term>segment code</Term>
      <Definition>The code that identifies the schedule segment.</Definition>
      <Keyword type="glentry" order="d1e1592070">
         <Level1>segment code</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592075">
         <Level1>segment length</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592080">
         <Level1>segment set</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592089">
         <Level1>segment time unit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000405" Version="B60adoc1" ContextApps="td">
      <Term>selection</Term>
      <Definition>A predefined set of data that must be printed or processed.
		Such a set is defined by a selection expression (or a selection criterion). You
		can define an expression in the Text Manager, which is used to retrieve data
		from the database for maintenance/printing.</Definition>
      <Keyword type="glentry" order="d1e1592094">
         <Level1>selection</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592099">
         <Level1>sequence number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000034" Version="B60asy04" ContextApps="td">
      <Term>sequence shipping schedule</Term>
      <Definition>A 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>
      <Keyword type="glentry" order="d1e1592104">
         <Level1>sequence shipping schedule</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000156" Version="B60asy04" ContextApps="td">
      <Term>service item</Term>
      <Definition>A standard item that represents services instead of goods.</Definition>
      <Keyword type="glentry" order="d1e1592109">
         <Level1>service item</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592114">
         <Level1>set number</Level1>
      </Keyword>
   </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. ERP Enterprise takes into account
		this value to create valid requirements.</Definition>
      <Keyword type="glentry" order="d1e1592119">
         <Level1>ship-from business partner capacity</Level1>
      </Keyword>
   </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">Warehousing</GUIRef> during
		the advance shipment notice (ASN) process.</Definition>
      <Keyword type="glentry" order="d1e1592124">
         <Level1>shipment ID</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000353" Version="B60adoc1" ContextApps="td">
      <Term>shipment sequence</Term>
      <Definition>The shipment sequence created by <GUIRef href="/baanerp/wh" role="package">Warehousing</GUIRef> during
		the advance shipment notice (ASN) process for a particular shipment ID.</Definition>
      <Keyword type="glentry" order="d1e1592132">
         <Level1>shipment sequence</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592140">
         <Level1>shipped cumulative</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592145">
         <Level1>shipped quantity</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592151">
         <Level1>shipping schedule</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592156">
         <Level1>simulation codes</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="SmoothFactor_td" Version="B60asy04" ContextApps="td">
      <Term>smoothing factor</Term>
      <Definition>The factor used to calculate smoothing data.</Definition>
      <Keyword type="glentry" order="d1e1592161">
         <Level1>smoothing factor</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592166">
         <Level1>sort code</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000165" Version="B60asy04" ContextApps="td">
      <Term>source</Term>
      <Definition>The places, events, or methods where or through which business
		partners come in contact with your company (for example, a trade fair or an
		advertisement).</Definition>
      <Keyword type="glentry" order="d1e1592171">
         <Level1>source</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000229" Version="B60asy04" ContextApps="td">
      <Term>source code</Term>
      <Definition>The code that identifies a source within ERP Enterprise.</Definition>
      <Keyword type="glentry" order="d1e1592176">
         <Level1>source code</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592181">
         <Level1>sourcing percentage</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592186">
         <Level1>sourcing rule</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592191">
         <Level1>special contract</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592199">
         <Level1>specific category</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000233" Version="B60asy04" ContextApps="td">
      <Term>start date</Term>
      <Definition>The date and time the activity started.</Definition>
      <Keyword type="glentry" order="d1e1592204">
         <Level1>start date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000116" Version="B60asy04" ContextApps="td">
      <Term>statistical year</Term>
      <Definition>The tax year.</Definition>
      <Keyword type="glentry" order="d1e1592210">
         <Level1>statistical year</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000305" Version="B60asy04" ContextApps="td">
      <Term>subcategory</Term>
      <Definition>Defines lower levels (catalog pages) of a catalog structure.</Definition>
      <Keyword type="glentry" order="d1e1592215">
         <Level1>subcategory</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="SubconItem_td" Version="B60adoc1" ContextApps="td">
      <Term>subcontracted service</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>
      <Keyword type="glentry" order="d1e1592220">
         <Level1>subcontracted service</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592225">
         <Level1>subcontractor</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592230">
         <Level1>subjective criterion</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592240">
         <Level1>subjective value</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592245">
         <Level1>success percentage</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592250">
         <Level1>suggested retail price</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592255">
         <Level1>supplier capacity</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592260">
         <Level1>supplier order number</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000330" Version="B60adoc1" ContextApps="td">
      <Term>supplier price book</Term>
      <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>
      <Keyword type="glentry" order="d1e1592265">
         <Level1>supplier price book</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592280">
         <Level1>supply chain</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000011" Version="B60adoc1" ContextApps="td">
      <Term>supply time</Term>
      <Definition>The total time required to obtain an item that is forecasted.
		This time is used to calculate an item's order lead time, based on which a
		company takes commitment decisions and executes capacity planning and order
		management.</Definition>
      <ExampleSection>
         <SectionTitle>Example</SectionTitle>
         <Paragraph>For item A, the supplier communicated a <Emphasis>supply
		  time</Emphasis> of 50 days. This is in fact a reduced lead time and is only
		  possible because a three year forecast is sent to the supplier for this item.
		  If additional quantities are needed, which are not included in the forecast,
		  the supplier needs the <Emphasis>full supply time</Emphasis>, which is 300
		  days.</Paragraph>
      </ExampleSection>
      <Keyword type="glentry" order="d1e1592285">
         <Level1>supply time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Surname_td" Version="B60asy04" ContextApps="td">
      <Term>surname</Term>
      <Definition>A person's last name in personnel data.</Definition>
      <Keyword type="glentry" order="d1e1592301">
         <Level1>surname</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000393">
      <Term>surplus</Term>
      <Definition>A quantity of one or more shipped components that makes an
		incomplete kit. The remaining components must still be delivered, unless
		completion of the sales order line is impossible for some reason.</Definition>
      <Keyword type="glentry" order="d1e1592306">
         <Level1>surplus</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e1591854">
      <Term>Synonym: channel</Term>
      <Definition>See: <Link href="#000121" role="internal">sales channel</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e1591801">
      <Term>Synonym: retroactive billing.</Term>
      <Definition>See: <Link href="#000313" role="internal">retrobilling</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry ID="d1e1590836">
      <Term>Synonym: total discount.</Term>
      <Definition>See: <Link href="#000367" role="internal">order discount</Link>
      </Definition>
   </GlossaryEntry>
   <GlossaryEntry ID="000173" Version="B60asy04" ContextApps="td">
      <Term>system date</Term>
      <Definition>The current date that is generated by the system.</Definition>
      <Keyword type="glentry" order="d1e1592311">
         <Level1>system date</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="TableFieldsT_td" Version="B60asy04" ContextApps="td">
      <Term>table fields in CRM</Term>
      <Definition>The table fields from the ERP Enterprise database that can be
		used in selection expressions and letter and report layouts in <GUIRef href="/baanerp/crm" role="package">CRM</GUIRef>.</Definition>
      <Keyword type="glentry" order="d1e1592316">
         <Level1>table fields in CRM</Level1>
      </Keyword>
   </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 <GUIRef href="/baanerp/td/pcg" role="module" Update="No">Pricing</GUIRef>
            </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>
      <Keyword type="glentry" order="d1e1592324">
         <Level1>target price</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="000400" Version="B60adoc0" ContextApps="td">
      <Term>task</Term>
      <Definition>An activity type that specifies an action to be executed for a
		contact, business partner, opportunity, or activity that you want to track
		through completion.</Definition>
      <Keyword type="glentry" order="d1e1592345">
         <Level1>task</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592350">
         <Level1>termination letter</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592355">
         <Level1>thank-you-for-bidding-letter</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592360">
         <Level1>total approved quantity</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592366">
         <Level1>total contract amount</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592371">
         <Level1>transaction date/time</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="Turnover_td" Version="B60asy04" ContextApps="td">
      <Term>turnover</Term>
      <Definition>The annual sales volume.</Definition>
      <Keyword type="glentry" order="d1e1592376">
         <Level1>turnover</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592381">
         <Level1>unit price</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592386">
         <Level1>upper bound</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592394">
         <Level1>upper limit</Level1>
      </Keyword>
   </GlossaryEntry>
   <GlossaryEntry ID="User_td" Version="B60asy04" ContextApps="td">
      <Term>user</Term>
      <Definition>The person that works with an application software package.</Definition>
      <Keyword type="glentry" order="d1e1592399">
         <Level1>user</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592404">
         <Level1>user defaults (sales)</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592409">
         <Level1>user profile (sales)</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592414">
         <Level1>user profiles (purchase)</Level1>
      </Keyword>
   </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>
      <Keyword type="glentry" order="d1e1592419">
         <Level1>vendor rating</Level1>
      </Keyword>
   </GlossaryEntry>
</Glossary>