<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/td/onlinemanual/000047" xml:lang="en">
   <Header>
      <Title>General purchase data</Title>
      <Keyword type="header" order="d1e1333645">
         <Level1>Purchase master data</Level1>
         <Level2>general purchase data</Level2>
      </Keyword>
      <Keyword type="header" order="d1e1333650">
         <Level1>General purchase data</Level1>
      </Keyword>
   </Header>
   <AimSection>
      <Paragraph>Before you can carry out
		the various processes that are related to the purchase functionality, you must
		define general purchase master data.</Paragraph>
      <List>
         <ListIntro>The general purchase data includes the following:</ListIntro>
         <ListItem>Set up the approver list that is used in the purchase
		  requisition procedure.</ListItem>
         <ListItem>Define data to track order changes and to determine the reason
		  for the changes.</ListItem>
         <ListItem>Define criteria and criteria sets for requests for quotations.</ListItem>
         <ListItem>Define additional cost sets.</ListItem>
      </List>
   </AimSection>
   <GeneralSection>
      <SectionTitle>To set up the approver list</SectionTitle>
      <Keyword type="section" order="d1e1333670">
         <Level1>Approver list</Level1>
         <Level2>setting up</Level2>
      </Keyword>
      <Paragraph>Before a <Link href="/baanerp/td/glossary/glossary#000153" role="glossary" Update="No">purchase requisition</Link> can be converted to a <Link href="/baanerp/td/glossary/glossary#PurchaOrders_td" role="glossary">purchase order</Link> or a <Link href="/baanerp/td/glossary/glossary#RequesForQuo_td" role="glossary">request-for-quotation (RFQ)</Link>, it must be
		approved by an approver that appears on the approver list.</Paragraph>
      <Paragraph>For more information on setting up the approver list, refer to <Link href="/baanerp/td/onlinemanual/000025" role="manual">Purchase requisition approval process</Link>.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>To define data to track order changes and to determine the
		reason for the changes</SectionTitle>
      <Keyword type="section" order="d1e1333694">
         <Level1>Change code</Level1>
      </Keyword>
      <Keyword type="section" order="d1e1333697">
         <Level1>Change reason</Level1>
      </Keyword>
      <Keyword type="section" order="d1e1333700">
         <Level1>Change type</Level1>
      </Keyword>
      <Keyword type="section" order="d1e1333703">
         <Level1>Acknowledgement code</Level1>
      </Keyword>
      <Paragraph>Purchase orders can be dynamic documents, as a company’s
		requirements can change during the life of the order process. You can define
		information that enables you to track these changes and the reasons why these
		changes occurred. Change codes and acknowledgement codes are used in LN to track the various
		changes to an order. Although this functionality is designed to work
		specifically with EDI, a company without EDI functionality can also use these
		codes to record changes.</Paragraph>
      <Paragraph>You can use change codes to maintain information regarding order
		changes that are tracked for historical purposes. You can use acknowledgement
		codes to manually record information concerning changes that are communicated
		by the purchase business partner. A purchase order acknowledgment is a message
		that the purchase business partner sends to the purchaser to confirm the
		receipt of the purchase order, which usually implies the acceptance of the
		order by the purchase business partner.</Paragraph>
      <ProcedureList>
         <ListIntro>To be able to maintain and track changes, take the following
		  steps:</ListIntro>
         <ListItem>Use the <GUIRef href="/baanerp/td/pur/tdpur0197m000" role="session">Change Reasons (tdpur0197m000)</GUIRef> session to maintain codes that represent the change
		  reasons, which can be assigned to a changed order or an order acknowledgement
		  to clarify why a change is made. This information can be tracked for historical
		  reporting.</ListItem>
         <ListItem>Use the <GUIRef href="/baanerp/td/pur/tdpur0198m000" role="session">Change Types (tdpur0198m000)</GUIRef> session to define change types that indicate the kind
		  of change of a changed purchase order or order acknowledgement. Possible types
		  of change are, for instance, change order line, add order line, or change
		  header data. The change types are assigned to the purchase order after the
		  change is made on the order.</ListItem>
         <ListItem>Use the <GUIRef href="/baanerp/td/pur/tdpur0100m400" role="session">Purchase Order Parameters (tdpur0100m400)</GUIRef> session to define various default change
		  codes and change types, which are defaulted to the purchase order line in case
		  of changes.</ListItem>
         <ListItem>Use the <GUIRef href="/baanerp/td/pur/tdpur0154m000" role="session">Purchase Acknowledgments (tdpur0154m000)</GUIRef> session to define purchase order
		  acknowledgements and the destination of the codes, which can be <GUIRef href="/baanerp/tc/domains/mcs.cdst#header" role="option">Header</GUIRef>, <GUIRef href="/baanerp/tc/domains/mcs.cdst#line" role="option">Line</GUIRef>, or <GUIRef href="/baanerp/tc/domains/mcs.cdst#any" role="option">Any</GUIRef>. The
		  acknowledgement code contains a group of information, which appears on the
		  purchase acknowledgment document. This code can represent the reasons for a
		  change of a purchase order.</ListItem>
      </ProcedureList>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>To define criteria and criteria sets for requests for
		quotations</SectionTitle>
      <Keyword type="section" order="d1e1333745">
         <Level1>Criteria</Level1>
         <Level2>defining</Level2>
      </Keyword>
      <Keyword type="section" order="d1e1333750">
         <Level1>Criteria set</Level1>
         <Level2>defining</Level2>
      </Keyword>
      <Paragraph>If you want to compare quotations from different purchase
		business partners, you can set up criteria for RFQs. RFQ-criteria enable you to
		make a better deliberation in selecting a quotation. You can compare the
		quotations based on objective criteria and subjective criteria.</Paragraph>
      <Paragraph>When evaluating returned RFQs, you can use objective criteria
		and subjective criteria. Objective criteria are criteria tracked by LN, while subjective
		criteria are user-defined criteria. When RFQs are evaluated, LN considers all
		objective and subjective criteria that are assigned to the RFQ. Based on user
		weightings, LN places
		the RFQs in order of favouritism (rank).</Paragraph>
      <ProcedureList>
         <ListIntro>If you want to use criteria to evaluate quotations, you must
		  define the criteria and their ratings as follows:</ListIntro>
         <ListItem>Define criteria sets in the <GUIRef href="/baanerp/td/pur/tdpur1190m000" role="session">RFQ Criteria Sets (tdpur1190m000)</GUIRef> session. A criteria set is a list of request for
		  quotation (RFQ) criterions that can be linked to an RFQ header. The RFQs are
		  evaluated following these criteria.</ListItem>
         <ListItem>Define RFQ subjective criteria in the <GUIRef href="/baanerp/td/pur/tdpur1191m000" role="session">RFQ Subjective Criteria (tdpur1191m000)</GUIRef> session. You must only define the subjective
		  RFQ criteria, because the objective criteria are already predefined in LN.</ListItem>
         <ListItem>Put together a criteria set by linking criteria to a set in the <GUIRef href="/baanerp/td/pur/tdpur1192m000" role="session">Criteria Set - Criteria (tdpur1192m000)</GUIRef> session. In this session, you must also
		  indicate the importance of the several criteria by assigning weights to
		  them.</ListItem>
         <ListItem> 
            <List>
               <ListIntro>In the <GUIRef href="/baanerp/td/pur/tdpur1193m000" role="session">Criteria Set - Scoring Schemes (tdpur1193m000)</GUIRef> session, you must assign objective
				values and subjective values to the criteria of the following types:</ListIntro>
               <ListItem>
                  <GUIRef href="/baanerp/td/domains/pur.ctype#quantity" role="option">Quantity</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/domains/pur.ctype#delivery" role="option">Delivery Time</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="/baanerp/td/domains/pur.ctype#subjective" role="option">Subjective</GUIRef>
               </ListItem>
            </List>
         </ListItem>
      </ProcedureList>
      <Paragraph>After the objective values and subjective values are assigned,
		you must assign scoring values to them in the <GUIRef href="/baanerp/td/pur/tdpur1193m000" role="session">Criteria Set - Scoring Schemes (tdpur1193m000)</GUIRef> session. If you do not specify a
		scoring scheme for objective criteria, LN uses predefined
		system values.</Paragraph>
      <Note>
         <SectionTitle>Notes</SectionTitle>
         <List>
            <ListItem>LN always takes into account prices when comparing quotations.</ListItem>
            <ListItem>When the concerned business partner is selected for <Link href="/baanerp/td/glossary/glossary#VendorRating_td" role="glossary">vendor rating</Link>, LN also takes into
			 account vendor rating when comparing quotations.</ListItem>
         </List>
      </Note>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>To define additional cost sets</SectionTitle>
      <Keyword type="section" order="d1e1333813">
         <Level1>Additional cost set</Level1>
         <Level2>defining</Level2>
      </Keyword>
      <Paragraph>Additional costs can be placed on an order as extra cost (items)
		after the last item recorded. Several additional cost items can be assigned to
		an order by bringing them together in a <Link href="/baanerp/td/glossary/glossary#CostSets_td" role="glossary" Update="No">cost set</Link>. LN can automatically
		apply these cost sets to purchase orders.</Paragraph>
      <Paragraph>For more information on defining additional cost sets, refer to <Link href="/baanerp/td/onlinemanual/000412" role="manual">Additional costs on purchase orders</Link>.</Paragraph>
   </GeneralSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000025" role="manual">Purchase requisition approval process</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000412" role="manual">Additional costs on purchase orders</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000080" role="manual">To set up vendor ratings</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000003" role="manual">Purchase item data</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000046" role="manual">Purchase organizational data</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>