<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/td/onlinemanual/000046" xml:lang="en">
   <Header>
      <Title>Purchase organizational data</Title>
      <Keyword type="header" order="d1e1333488">
         <Level1>Purchase master data</Level1>
         <Level2>purchase organizational data</Level2>
      </Keyword>
      <Keyword type="header" order="d1e1333493">
         <Level1>Purchase organizational data</Level1>
      </Keyword>
   </Header>
   <AimSection>
      <Paragraph>Before you can carry out purchase procedures, you must define
		purchase organizational data, such as order types that define the steps that
		are mandatory in a purchase order procedure, purchase offices that you can use
		to create purchase contracts, purchase orders, and purchase schedules, user
		profiles with user-specific default data, and so on.</Paragraph>
   </AimSection>
   <GeneralSection>
      <SectionTitle>To define purchase order types</SectionTitle>
      <Keyword type="section" order="d1e1333502">
         <Level1>Purchase order type</Level1>
         <Level2>defining</Level2>
      </Keyword>
      <Keyword type="section" order="d1e1333507">
         <Level1>Purchase order type</Level1>
         <Level2>activities</Level2>
      </Keyword>
      <Keyword type="section" order="d1e1333512">
         <Level1>Activity</Level1>
      </Keyword>
      <Paragraph>The purchase order type determines the <Link href="/baanerp/td/glossary/glossary#000129" role="glossary">activities</Link> that are included
		in the order procedure, and how and in which sequence the order procedure is
		carried out. When a purchase order type is linked to a purchase order, the
		purchase order is processed according to the activities and the type of order
		defined for the purchase order type.</Paragraph>
      <ProcedureList>
         <ListIntro>To define purchase order types and their activities, take the
		  following steps:</ListIntro>
         <ListItem>Enter a purchase order type in the <GUIRef href="/baanerp/td/pur/tdpur0194m000" role="session">Purchase Order Types (tdpur0194m000)</GUIRef> or the <GUIRef href="/baanerp/td/pur/tdpur0694m000" role="session">Purchase Order Type - Activities (tdpur0694m000)</GUIRef> session. In addition to the normal
		  purchase order type, several special order types exist. By selecting one or
		  more of the check boxes ( <GUIRef href="/baanerp/td/pur/tdpur0194m000#tdpur094.sund" role="manual">Cost Order</GUIRef>, <GUIRef href="/baanerp/td/pur/tdpur0194m000#tdpur094.coun" role="manual">Collect Order</GUIRef>, <GUIRef href="/baanerp/td/pur/tdpur0194m000#tdpur094.reto" role="manual">Return Order</GUIRef>, and so on), the creation and processing
		  of these orders can differ from normal purchase orders.</ListItem>
         <ListItem> 
            <List>
               <ListIntro>On the <GUIRef href="" role="manual" Update="No">Activities</GUIRef> tab of the <GUIRef href="/baanerp/td/pur/tdpur0694m000" role="session">Purchase Order Type - Activities (tdpur0694m000)</GUIRef> session, you must specify for the
				purchase order type:</ListIntro>
               <ListItem>The activities (tasks) to be carried out.</ListItem>
               <ListItem>The sequence in which these activities must be carried
				out.</ListItem>
               <ListItem>Whether the activity must be carried out automatically or
				manually. As a result, you can automate the processing of purchase orders. For
				details, refer to <Link href="/baanerp/td/onlinemanual/000406" role="manual">Flexible purchase order processing</Link>.</ListItem>
            </List>
         </ListItem>
      </ProcedureList>
      <Tip>
         <SectionTitle>Tip</SectionTitle>
         <Paragraph>You must make sure that the list of activities that is linked
		  to an order type is extensive in order to cover all processes that can apply
		  during execution of the order procedure. If an activity is not applicable to
		  the order type, LN automatically skips this activity. You can view the actual activities that are
		  linked to the purchase order (detail) line and the status of the activities in
		  the <Link href="/baanerp/td/pur/tdpur4113m000" role="session">Purchase Order Activities (tdpur4113m000)</Link> session.</Paragraph>
      </Tip>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>To define purchase offices</SectionTitle>
      <Keyword type="section" order="d1e1333571">
         <Level1>Purchase office</Level1>
         <Level2>defining</Level2>
      </Keyword>
      <Paragraph>The purchase office determines the location from which purchase
		orders, contracts, schedules, requisitions, and requests for quotations are
		processed. A purchase office is needed to complete transactions with buy-from
		business partners. Various purchase offices can be set up for one company. Once
		you set up the purchase office, you can define user profiles.</Paragraph>
      <ProcedureList>
         <ListIntro>To define a purchase office, you must complete the following
		  steps:</ListIntro>
         <ListItem>Define the purchase office as a department in the <GUIRef href="/baanerp/tc/mcs/tcmcs0565m000" role="session">Departments (tcmcs0565m000)</GUIRef> session.</ListItem>
         <ListItem>Specify purchase-office-specific data in the <GUIRef href="/baanerp/td/pur/tdpur0112m000" role="session">Purchase Offices (tdpur0112m000)</GUIRef> session. The enterprise unit to which the department
		  is linked informs you about the financial company to which financial
		  transactions for the purchase office are posted. If you want to use purchase
		  offices in combination with purchase orders, purchase schedules, purchase
		  contracts, schedule releases, call-offs, requests for quotations, or
		  requisitions, you must fill the concerned series fields.</ListItem>
      </ProcedureList>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>To define user profiles</SectionTitle>
      <Keyword type="section" order="d1e1333594">
         <Level1>User profile</Level1>
         <Level2>defining</Level2>
      </Keyword>
      <Paragraph>User profiles are used to set up default information for
		purchasing employees, so documents can be processed faster. In the <GUIRef href="/baanerp/td/pur/tdpur0143m000" role="session">Purchase User Profiles (tdpur0143m000)</GUIRef> session, you can link a user to a purchase office,
		order type, and warehouse for each login code. When the user creates a purchase
		order, call-off, purchase contract, purchase requisition, request for
		quotation, approval rule, purchase schedule, or purchase release, the user
		profile determines the defaults. This accelerates the purchase-related
		transaction entry processes.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>To define approval rules</SectionTitle>
      <Keyword type="section" order="d1e1333607">
         <Level1>Approval rule</Level1>
         <Level2>defining</Level2>
      </Keyword>
      <Paragraph>Purchase order approval is a mandatory step in the purchase
		order procedure. You can validate purchase orders against <Link href="/baanerp/td/glossary/glossary#000327" role="glossary" Update="No">approval rules</Link> before their status becomes <GUIRef href="/baanerp/td/domains/pur.hdst#approved" role="option">Approved</GUIRef>.</Paragraph>
      <Paragraph>For more information on defining approval rules, refer to <Link href="/baanerp/td/onlinemanual/000415" role="manual">Purchase order approval</Link>.</Paragraph>
   </GeneralSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000406" role="manual">Flexible purchase order processing</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000415" role="manual">Purchase order approval</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000003" role="manual">Purchase item data</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/td/onlinemanual/000047" role="manual">General purchase data</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>