<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/td/pcg/tdpcg0130m100" xml:lang="en">
   <Header>
      <Title>Discount Matrices (tdpcg0130m100)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <List>
            <ListIntro>Use this session to maintain discount
			 matrices for the following <Link href="/baanerp/td/glossary/glossary#MatrixType_td" role="glossary">matrix types</Link>:</ListIntro>
            <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#soldsc" role="option">Sales Line Discount</GUIRef>
            </ListItem>
            <ListItem>
               <GUIRef href="/baanerp/td/domains/pcg.maty#sodsc" role="option">Sales Total Discount</GUIRef>
            </ListItem>
         </List>
      </AimSection>
      <GeneralSection>
         <List>
            <ListIntro>On the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu you can choose:</ListIntro>
            <ListItem>
               <GUIRef href="/baanerp/td/pcg/tdpcg0130m100#tdpcg0230m100" role="command">Global Update of Discounts</GUIRef>, to globally update
			 discounts for selected matrix attributes in the <Link href="/baanerp/td/pcg/tdpcg0230m100" role="session">Global Update of Discounts (tdpcg0230m100)</Link> session.</ListItem>
            <ListItem>
               <GUIRef href="/baanerp/td/pcg/tdpcg0130m100#tdpcg0200m000" role="command">Global Deletion of Price Information</GUIRef>, to delete pricing
			 information in the <Link href="/baanerp/td/pcg/tdpcg0200m000" role="session">Global Deletion of Price Information (tdpcg0200m000)</Link> session.</ListItem>
            <ListItem>
               <GUIRef href="/baanerp/td/pcg/tdpcg0130m100#tdpcg0230m200" role="command">Rebuild Generic Key</GUIRef>, to rebuild matrix data in case
			 the database is corrupted in the <GUIRef href="/baanerp/td/pcg/tdpcg0230m200" role="session">Rebuild Generic Key (tdpcg0230m200)</GUIRef> session.</ListItem>
         </List>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000027" role="manual">Setting up a discount matrix</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000011" role="manual">Matrix structure</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000016" role="manual">Multiple discount levels</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000380" role="manual">An outline of the pricing information retrieval processes</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/td/onlinemanual/000018" role="manual">Determining/eligible</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tdpcg030.maty">
         <Header>
            <Title>Matrix Type</Title>
         </Header>
         <FuncDesc>Defines the type of a matrix definition and is linked to a set
		of matrix attributes.</FuncDesc>
         <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>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.malv">
         <Header>
            <Title>Matrix Level</Title>
         </Header>
         <FuncDesc>Discount levels enable you to define more than one discount for
		  an order or order line.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>This field refers to the discount level, as set in the <GUIRef href="/baanerp/td/pcg/tdpcg0100m000" role="session">Pricing Parameters (tdpcg0100m000)</GUIRef> session.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.made">
         <Header>
            <Title>Matrix Definition</Title>
         </Header>
         <FuncDesc>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.</FuncDesc>
         <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>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListItem>Matrix definitions
				are maintained in the <GUIRef href="/baanerp/td/pcg/tdpcg0110m000" role="session">Matrix Definitions (tdpcg0110m000)</GUIRef> session.</ListItem>
               <ListItem>You cannot enter a
				matrix definition without matrix attributes linked to it.</ListItem>
            </List>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.prse">
         <Header>
            <Title>Sequence</Title>
         </Header>
         <FuncDesc>For a matrix type, the order in which matrix definitions are
		searched for.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.efdt">
         <Header>
            <Title>Effective Date</Title>
         </Header>
         <FuncDesc>The first date on which the discount matrix is valid. The
		  default effective date is equal to the system date. date is equal</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.exdt">
         <Header>
            <Title>Expiry Date</Title>
         </Header>
         <FuncDesc>The last date the discount matrix is valid. If this field is
		  not filled, the discount matrix is infinitely valid.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.dsty">
         <Header>
            <Title>Discount Type</Title>
         </Header>
         <FuncDesc>The discount type determines the way the discount is
		  calculated.</FuncDesc>
         <AllowedValues>
            <SectionTitle>Allowed values</SectionTitle>
            <Paragraph>
               <Link href="/baanerp/td/domains/pcg.dsty" role="domain">Discount Type</Link>
            </Paragraph>
         </AllowedValues>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.dspr">
         <Header>
            <Title>Discount %</Title>
         </Header>
         <FuncDesc>The discount percentage that you can subtract from the <Link href="/baanerp/td/glossary/glossary#000106" role="glossary">gross amount</Link> or <Link href="/baanerp/td/glossary/glossary#000107" role="glossary">net amount</Link> of an order or
		  order line.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If you enter a
			 discount percentage, you cannot enter an amount or a schedule.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.dsam">
         <Header>
            <Title>Discount Amount</Title>
         </Header>
         <FuncDesc>The discount amount for an order or order line.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>Discount amounts can
			 be entered if the <GUIRef href="/baanerp/td/pcg/tdpcg0130m100#tdpcg030.dsty" role="manual">Discount Type</GUIRef> field
			 is set to <GUIRef href="/baanerp/td/domains/pcg.dsty#amount" role="option">Amount</GUIRef>.</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="home.currency">
         <Header>
            <Title>Home Currency</Title>
         </Header>
         <FuncDesc>One of a company's base currencies in which ERP Enterprise registers and
		reports amounts.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>In a multicurrency system, up to three home currencies can
			 be defined:</ListIntro>
               <ListItem>The <Link href="/baanerp/tc/glossary/glossary#000062" role="glossary">local currency</Link>
               </ListItem>
               <ListItem>Two <Link href="/baanerp/tc/glossary/glossary#000065" role="glossary" Update="No">reporting currencies</Link>
               </ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.dssc">
         <Header>
            <Title>Discount Schedule</Title>
         </Header>
         <FuncDesc>A code that identifies the <Link href="/baanerp/td/glossary/glossary#000363" role="glossary">discount schedule</Link>.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If a discount
			 schedule code is entered, you cannot set the discount percentage and amount in
			 this session. The discount is retrieved from the discount schedule.</Paragraph>
         </Note>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/td/onlinemanual/000020" role="manual">Setting up a discount schedule</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.dsmt">
         <Header>
            <Title>Discount Method</Title>
         </Header>
         <FuncDesc>A code that indicates the way in which discounts are calculated
		if multiple discount levels are used.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>Discounts are calculated according to one of the following
			 amounts:</ListIntro>
               <ListItem>Gross: the discount is calculated over the gross amount</ListItem>
               <ListItem>Net: the discount is calculated over the net amount. The net
			 amount is calculated from the gross amount minus discounts at previous
			 levels</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.dsco">
         <Header>
            <Title>Discount</Title>
         </Header>
         <FuncDesc>The code that is used to identify the discount for reporting
		  purposes.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.dtrm">
         <Header>
            <Title>Determining</Title>
         </Header>
         <FuncDesc>If this check box is selected, the quantity and value
		  from the order line is taken into account when the total order value is
		  calculated. The total order value determines whether an order discount can be
		  applied to an order.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/td/onlinemanual/000018" role="manual">Determining/eligible</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.elgb">
         <Header>
            <Title>Eligible</Title>
         </Header>
         <FuncDesc>If this check box is selected, and if an order discount
		  can be applied to an order, the order line is <Emphasis>eligible</Emphasis> for
		  receiving the order discount when distributing the discount among the order
		  lines of an order.</FuncDesc>
         <SimpleSection>
            <Paragraph>If this check box is cleared, the order line is excluded
			 from receiving an order discount when distributing the discount among the order
			 lines of an order. Other lines of the same order can however be eligible for
			 the discount.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/td/onlinemanual/000018" role="manual">Determining/eligible</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.stds">
         <Header>
            <Title>Stop Discounting</Title>
         </Header>
         <FuncDesc>If this check box is selected, and a discount is found,
		  the discount retrieving process stops.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.item">
         <Header>
            <Title>Item</Title>
         </Header>
         <FuncDesc>In ERP Enterprise,
		the raw materials, subassemblies, finished products, and tools that can be
		purchased, stored, manufactured, sold, and so on.</FuncDesc>
         <SimpleSection>
            <Paragraph>An item can also represent a set of items handled as one kit,
		  or exist in multiple product variants.</Paragraph>
            <List>
               <ListIntro>You can also define nonphysical items, which are not held
			 in inventory but can be used to post costs or to invoice services to customers.
			 The following are examples of nonphysical items:</ListIntro>
               <ListItem>Cost items (for example, electricity)</ListItem>
               <ListItem>Service items</ListItem>
               <ListItem>Subcontracting services</ListItem>
               <ListItem>List items (menus/options)</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.bfbp">
         <Header>
            <Title>Buy-from Business Partner</Title>
         </Header>
         <FuncDesc>The business partner from whom you order goods or services;
		this usually represents a supplier's sales department. The definition includes
		the default price and discount agreements, purchase-order defaults, delivery
		terms, and the related ship-from and invoice-from business partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.bfty">
         <Header>
            <Title>Buy-from Type</Title>
         </Header>
         <FuncDesc> 
            <Link href="/baanerp/tc/glossary/glossary#BusineParTyp_tc" role="glossary">business partner types</Link> are
		  used to classify a group of suppliers, for example, a group of chair suppliers.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.bppo">
         <Header>
            <Title>Pricing BP</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#ParentBusine_tc" role="glossary">parent business partner</Link> used
		  to classify a group of suppliers or vendors with the same prices or pricing
		  agreements.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.poof">
         <Header>
            <Title>Purchase Office</Title>
         </Header>
         <FuncDesc>A department in your organization that is responsible for
		buying the materials and services needed by your organization. You assign
		number groups to the purchase office.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>In this way, you can assign serial numbers to:</ListIntro>
               <ListItem>Purchase orders</ListItem>
               <ListItem>Purchase schedules</ListItem>
               <ListItem>Requests for quotations</ListItem>
               <ListItem>Purchase contracts</ListItem>
            </List>
            <Paragraph>You can also define a default warehouse where goods ordered by
		  the purchase office must be delivered.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.poor">
         <Header>
            <Title>Order Origin</Title>
         </Header>
         <FuncDesc>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.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.bpso">
         <Header>
            <Title>Pricing BP</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#ParentBusine_tc" role="glossary">parent business partner</Link> used
		  to classify a group of suppliers or vendors with the same prices or pricing
		  agreements.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.soof">
         <Header>
            <Title>Sales Office</Title>
         </Header>
         <FuncDesc>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.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.soor">
         <Header>
            <Title>Order Origin</Title>
         </Header>
         <FuncDesc>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.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.shbp">
         <Header>
            <Title>Ship-to BP</Title>
         </Header>
         <FuncDesc>The business partner to which you ship the ordered goods. This
		usually represents a customer's distribution center or warehouse. The
		definition includes the default warehouse from which you send the goods, the
		carrier who carries out the transport, and the related sold-to business
		partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.stbp">
         <Header>
            <Title>Sold-to BP</Title>
         </Header>
         <FuncDesc>Usually a customer's purchase department, the business partner
		who orders goods or services from your organization, that owns the
		configurations you maintain, or for whom you perform a project.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The agreement with the sold-to business partner can include
			 the following:</ListIntro>
               <ListItem>Default price and discount agreements</ListItem>
               <ListItem>Sales order defaults</ListItem>
               <ListItem>Delivery terms</ListItem>
               <ListItem>The related ship-to and invoice-to business partner</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.stty">
         <Header>
            <Title>Sold-to Type</Title>
         </Header>
         <FuncDesc>Used to classify a group of customers.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.itbp">
         <Header>
            <Title>Invoice-to BP</Title>
         </Header>
         <FuncDesc>The business partner to which you send invoices. This usually
		represents a customer's accounts payable department. The definition includes
		the default currency and exchange rate, invoicing method and frequency,
		information about the customer's credit limit, the terms and method of payment,
		and the related pay-by business partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.prls">
         <Header>
            <Title>Price List</Title>
         </Header>
         <FuncDesc>List of default prices and discounts for customers and
		suppliers. You can link price lists to items and item groups, and to sold-to
		and buy-from business partners.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.pame">
         <Header>
            <Title>Payment Method</Title>
         </Header>
         <FuncDesc>The way in which the payment (purchase invoice) or the direct
		debit (sales invoice) takes place. The payment method defines details such as,
		the maximum amount, the type of due date, if foreign currencies are allowed,
		and which details must be printed on the report.</FuncDesc>
         <SimpleSection>
            <Paragraph>These details are default values that you can change on the
		  order or invoice as necessary.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.trde">
         <Header>
            <Title>Delivery Terms</Title>
         </Header>
         <FuncDesc>The agreements with the business partner, concerning the way
		the goods are delivered. Relevant information is printed on various order
		documents.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.prty">
         <Header>
            <Title>Product Type</Title>
         </Header>
         <FuncDesc>User-definable item grouping data that is used as a sorting and
		selecting criterion. The product type is intended for classifying items with
		similar characteristics for production purposes.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.prli">
         <Header>
            <Title>Product Line</Title>
         </Header>
         <FuncDesc>A group of products made by the same producer, that are similar
		but differ in details such as, size, shape, color, and so on. User-definable
		item grouping data, mainly used as an item selection criterion for reporting.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.prcl">
         <Header>
            <Title>Product Class</Title>
         </Header>
         <FuncDesc>User-definable item grouping data that is used to distinguish
		between different groups of items in a product line. The product class is
		mainly used as a selection criterion for reporting.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.manu">
         <Header>
            <Title>Manufacturer</Title>
         </Header>
         <FuncDesc>A supplier of finished goods. User-definable item grouping data
		used for sorting and selecting.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.prgr">
         <Header>
            <Title>Price Group</Title>
         </Header>
         <FuncDesc>A group of items to which the same pricing characteristics
		apply.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.itgr">
         <Header>
            <Title>Item Group</Title>
         </Header>
         <FuncDesc>Group of items with similar characteristics. Each item belongs
		to a particular item group. The item group is used in combination with the item
		type to set up item defaults.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.ccur">
         <Header>
            <Title>Currency</Title>
         </Header>
         <FuncDesc>A generally accepted medium of exchange such as coins, treasury
		notes, and banknotes.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The following currency types are available in ERP Enterprise:</ListIntro>
               <ListItem>Home currency, which is used internally by companies to
			 calculate costs, record budgets, and register tax amounts</ListItem>
               <ListItem>Transaction currency, which is used in transactions with
			 business partners, such as orders and invoices</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.area">
         <Header>
            <Title>Area</Title>
         </Header>
         <FuncDesc>A region used to group business partners, customers, suppliers
		and employees on a geographical basis.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.ifbp">
         <Header>
            <Title>Invoice-from Business Partner</Title>
         </Header>
         <FuncDesc>The business partner that sends invoices to your organization.
		This usually represents a supplier's accounts receivable department. The
		definition includes the default currency and exchange rate, invoicing method
		and frequency, information about your organization's credit limit, the terms
		and method of payment, and the related pay-to business partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="stbp.sol">
         <Header>
            <Title>Sold-to BP</Title>
         </Header>
         <FuncDesc>Usually a customer's purchase department, the business partner
		who orders goods or services from your organization, that owns the
		configurations you maintain, or for whom you perform a project.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The agreement with the sold-to business partner can include
			 the following:</ListIntro>
               <ListItem>Default price and discount agreements</ListItem>
               <ListItem>Sales order defaults</ListItem>
               <ListItem>Delivery terms</ListItem>
               <ListItem>The related ship-to and invoice-to business partner</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="shbp.sol">
         <Header>
            <Title>Ship-to BP</Title>
         </Header>
         <FuncDesc>The business partner to which you ship the ordered goods. This
		usually represents a customer's distribution center or warehouse. The
		definition includes the default warehouse from which you send the goods, the
		carrier who carries out the transport, and the related sold-to business
		partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="itbp.sol">
         <Header>
            <Title>Invoice-to BP</Title>
         </Header>
         <FuncDesc>The business partner to which you send invoices. This usually
		represents a customer's accounts payable department. The definition includes
		the default currency and exchange rate, invoicing method and frequency,
		information about the customer's credit limit, the terms and method of payment,
		and the related pay-by business partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="soor.sol">
         <Header>
            <Title>Sales Order Origin</Title>
         </Header>
         <FuncDesc>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.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.soty">
         <Header>
            <Title>Order Type</Title>
         </Header>
         <FuncDesc>A code used to determine the character or function of an order
		and, consequently, of the message.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>Examples:</ListIntro>
               <ListItem>Normal order versus return order</ListItem>
               <ListItem>Invoice versus credit note</ListItem>
            </List>
            <Paragraph>The classification that determines which sessions (in which
		  sequence) are part of the order procedure. You can also assign one of the
		  following categories to the order type: cost order, collect order, return
		  order, and subcontracting order.</Paragraph>
            <List>
               <ListIntro>Order type codes are required in the ERP EDI messages that
			 relate to a single order. EDI messages that relate to single orders include
			 messages that process:</ListIntro>
               <ListItem>Orders (ANSI X12 850, UN/EDIFACT ORDERS).</ListItem>
               <ListItem>Order changes (ANSI X12 860, UN/EDIFACT ORDCHG).</ListItem>
               <ListItem>Order acknowledgments (ANSI X12 855 and 865, UN/EDIFACT
			 ORDRSP).</ListItem>
               <ListItem>Invoices (ANSI X12 810, UN/EDIFACT INVOIC).</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="soof.sol">
         <Header>
            <Title>Sales Office</Title>
         </Header>
         <FuncDesc>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.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="bpso.sol">
         <Header>
            <Title>SO Business Partner for Pricing</Title>
         </Header>
         <FuncDesc/>
      </FieldHelp>
      <FieldHelp ID="prls.sol">
         <Header>
            <Title>Price List</Title>
         </Header>
         <FuncDesc>List of default prices and discounts for customers and
		suppliers. You can link price lists to items and item groups, and to sold-to
		and buy-from business partners.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="pame.sol">
         <Header>
            <Title>Payment Method</Title>
         </Header>
         <FuncDesc>The way in which the payment (purchase invoice) or the direct
		debit (sales invoice) takes place. The payment method defines details such as,
		the maximum amount, the type of due date, if foreign currencies are allowed,
		and which details must be printed on the report.</FuncDesc>
         <SimpleSection>
            <Paragraph>These details are default values that you can change on the
		  order or invoice as necessary.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="trde.sol">
         <Header>
            <Title>Delivery Terms</Title>
         </Header>
         <FuncDesc>The agreements with the business partner, concerning the way
		the goods are delivered. Relevant information is printed on various order
		documents.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="chan.sol">
         <Header>
            <Title>BP Channel</Title>
         </Header>
         <FuncDesc>A sales or distribution channel used to assign goods to
		customer groups.</FuncDesc>
         <SimpleSection>
            <Paragraph>You can link channels to sold-to business partners and to
		  items. Channels can be used in connection with available-to-promise (ATP).</Paragraph>
            <Paragraph>You can assign a certain ATP volume to a channel. This volume
		  limits the ATP for that channel to a maximum.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="prty.sol">
         <Header>
            <Title>Product Type</Title>
         </Header>
         <FuncDesc>User-definable item grouping data that is used as a sorting and
		selecting criterion. The product type is intended for classifying items with
		similar characteristics for production purposes.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="prli.sol">
         <Header>
            <Title>Product Line</Title>
         </Header>
         <FuncDesc>A group of products made by the same producer, that are similar
		but differ in details such as, size, shape, color, and so on. User-definable
		item grouping data, mainly used as an item selection criterion for reporting.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="prcl.sol">
         <Header>
            <Title>Product Class</Title>
         </Header>
         <FuncDesc>User-definable item grouping data that is used to distinguish
		between different groups of items in a product line. The product class is
		mainly used as a selection criterion for reporting.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="manu.sol">
         <Header>
            <Title>Manufacturer</Title>
         </Header>
         <FuncDesc>A supplier of finished goods. User-definable item grouping data
		used for sorting and selecting.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="prgr.sol">
         <Header>
            <Title>Price Group</Title>
         </Header>
         <FuncDesc>A group of items to which the same pricing characteristics
		apply.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="itgr.sol">
         <Header>
            <Title>Item Group</Title>
         </Header>
         <FuncDesc>Group of items with similar characteristics. Each item belongs
		to a particular item group. The item group is used in combination with the item
		type to set up item defaults.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.pcor">
         <Header>
            <Title>Price Origin</Title>
         </Header>
         <FuncDesc>Select the sales price's origin.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="area.sol">
         <Header>
            <Title>Area</Title>
         </Header>
         <FuncDesc>A region used to group business partners, customers, suppliers
		and employees on a geographical basis.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="stty.sol">
         <Header>
            <Title>Sold-to Type</Title>
         </Header>
         <FuncDesc>Used to classify a group of customers.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ccur.sol">
         <Header>
            <Title>Currency</Title>
         </Header>
         <FuncDesc>A generally accepted medium of exchange such as coins, treasury
		notes, and banknotes.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The following currency types are available in ERP Enterprise:</ListIntro>
               <ListItem>Home currency, which is used internally by companies to
			 calculate costs, record budgets, and register tax amounts</ListItem>
               <ListItem>Transaction currency, which is used in transactions with
			 business partners, such as orders and invoices</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="item.sol">
         <Header>
            <Title>Item</Title>
         </Header>
         <FuncDesc>In ERP Enterprise,
		the raw materials, subassemblies, finished products, and tools that can be
		purchased, stored, manufactured, sold, and so on.</FuncDesc>
         <SimpleSection>
            <Paragraph>An item can also represent a set of items handled as one kit,
		  or exist in multiple product variants.</Paragraph>
            <List>
               <ListIntro>You can also define nonphysical items, which are not held
			 in inventory but can be used to post costs or to invoice services to customers.
			 The following are examples of nonphysical items:</ListIntro>
               <ListItem>Cost items (for example, electricity)</ListItem>
               <ListItem>Service items</ListItem>
               <ListItem>Subcontracting services</ListItem>
               <ListItem>List items (menus/options)</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="stbp.so">
         <Header>
            <Title>Sold-to BP</Title>
         </Header>
         <FuncDesc>Usually a customer's purchase department, the business partner
		who orders goods or services from your organization, that owns the
		configurations you maintain, or for whom you perform a project.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The agreement with the sold-to business partner can include
			 the following:</ListIntro>
               <ListItem>Default price and discount agreements</ListItem>
               <ListItem>Sales order defaults</ListItem>
               <ListItem>Delivery terms</ListItem>
               <ListItem>The related ship-to and invoice-to business partner</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="itbp.so">
         <Header>
            <Title>Invoice-to BP</Title>
         </Header>
         <FuncDesc>The business partner to which you send invoices. This usually
		represents a customer's accounts payable department. The definition includes
		the default currency and exchange rate, invoicing method and frequency,
		information about the customer's credit limit, the terms and method of payment,
		and the related pay-by business partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="soor.so">
         <Header>
            <Title>Order Origin</Title>
         </Header>
         <FuncDesc>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.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="soof.so">
         <Header>
            <Title>Sales Office</Title>
         </Header>
         <FuncDesc>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.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="bpso.so">
         <Header>
            <Title>Pricing BP</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#ParentBusine_tc" role="glossary">parent business partner</Link> used
		  to classify a group of customers with the same prices or pricing agreements.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="prls.so">
         <Header>
            <Title>Price List</Title>
         </Header>
         <FuncDesc>List of default prices and discounts for customers and
		suppliers. You can link price lists to items and item groups, and to sold-to
		and buy-from business partners.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="pame.so">
         <Header>
            <Title>Payment Method</Title>
         </Header>
         <FuncDesc>The way in which the payment (purchase invoice) or the direct
		debit (sales invoice) takes place. The payment method defines details such as,
		the maximum amount, the type of due date, if foreign currencies are allowed,
		and which details must be printed on the report.</FuncDesc>
         <SimpleSection>
            <Paragraph>These details are default values that you can change on the
		  order or invoice as necessary.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="trde.so">
         <Header>
            <Title>Delivery Terms</Title>
         </Header>
         <FuncDesc>The agreements with the business partner, concerning the way
		the goods are delivered. Relevant information is printed on various order
		documents.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="area.so">
         <Header>
            <Title>Area</Title>
         </Header>
         <FuncDesc>A region used to group business partners, customers, suppliers
		and employees on a geographical basis.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="stty.so">
         <Header>
            <Title>Sold-to Type</Title>
         </Header>
         <FuncDesc>Used to classify a group of customers.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ccur.so">
         <Header>
            <Title>Currency</Title>
         </Header>
         <FuncDesc>A generally accepted medium of exchange such as coins, treasury
		notes, and banknotes.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The following currency types are available in ERP Enterprise:</ListIntro>
               <ListItem>Home currency, which is used internally by companies to
			 calculate costs, record budgets, and register tax amounts</ListItem>
               <ListItem>Transaction currency, which is used in transactions with
			 business partners, such as orders and invoices</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="chan.so">
         <Header>
            <Title>BP Channel</Title>
         </Header>
         <FuncDesc>A sales or distribution channel used to assign goods to
		customer groups.</FuncDesc>
         <SimpleSection>
            <Paragraph>You can link channels to sold-to business partners and to
		  items. Channels can be used in connection with available-to-promise (ATP).</Paragraph>
            <Paragraph>You can assign a certain ATP volume to a channel. This volume
		  limits the ATP for that channel to a maximum.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="bfbp.pol">
         <Header>
            <Title>Buy-from Business Partner</Title>
         </Header>
         <FuncDesc>The business partner from whom you order goods or services;
		this usually represents a supplier's sales department. The definition includes
		the default price and discount agreements, purchase-order defaults, delivery
		terms, and the related ship-from and invoice-from business partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="poor.pol">
         <Header>
            <Title>Order Origin</Title>
         </Header>
         <FuncDesc>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.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ifbp.pol">
         <Header>
            <Title>Invoice-from Business Partner</Title>
         </Header>
         <FuncDesc>The business partner that sends invoices to your organization.
		This usually represents a supplier's accounts receivable department. The
		definition includes the default currency and exchange rate, invoicing method
		and frequency, information about your organization's credit limit, the terms
		and method of payment, and the related pay-to business partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdpcg030.poty">
         <Header>
            <Title>Order Type</Title>
         </Header>
         <FuncDesc>A code used to determine the character or function of an order
		and, consequently, of the message.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>Examples:</ListIntro>
               <ListItem>Normal order versus return order</ListItem>
               <ListItem>Invoice versus credit note</ListItem>
            </List>
            <Paragraph>The classification that determines which sessions (in which
		  sequence) are part of the order procedure. You can also assign one of the
		  following categories to the order type: cost order, collect order, return
		  order, and subcontracting order.</Paragraph>
            <List>
               <ListIntro>Order type codes are required in the ERP EDI messages that
			 relate to a single order. EDI messages that relate to single orders include
			 messages that process:</ListIntro>
               <ListItem>Orders (ANSI X12 850, UN/EDIFACT ORDERS).</ListItem>
               <ListItem>Order changes (ANSI X12 860, UN/EDIFACT ORDCHG).</ListItem>
               <ListItem>Order acknowledgments (ANSI X12 855 and 865, UN/EDIFACT
			 ORDRSP).</ListItem>
               <ListItem>Invoices (ANSI X12 810, UN/EDIFACT INVOIC).</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="poof.pol">
         <Header>
            <Title>Purchase Office</Title>
         </Header>
         <FuncDesc>A department in your organization that is responsible for
		buying the materials and services needed by your organization. You assign
		number groups to the purchase office.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>In this way, you can assign serial numbers to:</ListIntro>
               <ListItem>Purchase orders</ListItem>
               <ListItem>Purchase schedules</ListItem>
               <ListItem>Requests for quotations</ListItem>
               <ListItem>Purchase contracts</ListItem>
            </List>
            <Paragraph>You can also define a default warehouse where goods ordered by
		  the purchase office must be delivered.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="bppo.pol">
         <Header>
            <Title>Pricing BP</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#ParentBusine_tc" role="glossary">parent business partner</Link> used
		  to classify a group of suppliers or vendors with the same prices or pricing
		  agreements.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="prls.pol">
         <Header>
            <Title>Price List</Title>
         </Header>
         <FuncDesc>List of default prices and discounts for customers and
		suppliers. You can link price lists to items and item groups, and to sold-to
		and buy-from business partners.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="pame.pol">
         <Header>
            <Title>Payment Method</Title>
         </Header>
         <FuncDesc>The way in which the payment (purchase invoice) or the direct
		debit (sales invoice) takes place. The payment method defines details such as,
		the maximum amount, the type of due date, if foreign currencies are allowed,
		and which details must be printed on the report.</FuncDesc>
         <SimpleSection>
            <Paragraph>These details are default values that you can change on the
		  order or invoice as necessary.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="trde.pol">
         <Header>
            <Title>Delivery Terms</Title>
         </Header>
         <FuncDesc>The agreements with the business partner, concerning the way
		the goods are delivered. Relevant information is printed on various order
		documents.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="prty.pol">
         <Header>
            <Title>Product Type</Title>
         </Header>
         <FuncDesc>User-definable item grouping data that is used as a sorting and
		selecting criterion. The product type is intended for classifying items with
		similar characteristics for production purposes.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="prli.pol">
         <Header>
            <Title>Product Line</Title>
         </Header>
         <FuncDesc>A group of products made by the same producer, that are similar
		but differ in details such as, size, shape, color, and so on. User-definable
		item grouping data, mainly used as an item selection criterion for reporting.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="prcl.pol">
         <Header>
            <Title>Product Class</Title>
         </Header>
         <FuncDesc>User-definable item grouping data that is used to distinguish
		between different groups of items in a product line. The product class is
		mainly used as a selection criterion for reporting.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="manu.pol">
         <Header>
            <Title>Manufacturer</Title>
         </Header>
         <FuncDesc>A supplier of finished goods. User-definable item grouping data
		used for sorting and selecting.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="prgr.pol">
         <Header>
            <Title>Price Group</Title>
         </Header>
         <FuncDesc>A group of items to which the same pricing characteristics
		apply.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="itgr.pol">
         <Header>
            <Title>Item Group</Title>
         </Header>
         <FuncDesc>Group of items with similar characteristics. Each item belongs
		to a particular item group. The item group is used in combination with the item
		type to set up item defaults.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="area.pol">
         <Header>
            <Title>Area</Title>
         </Header>
         <FuncDesc>A region used to group business partners, customers, suppliers
		and employees on a geographical basis.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="bfty.pol">
         <Header>
            <Title>Buy-from Type</Title>
         </Header>
         <FuncDesc> 
            <Link href="/baanerp/tc/glossary/glossary#BusineParTyp_tc" role="glossary"
                  Update="No">Business partner types</Link> are used to classify a group of suppliers, for example, a group of
		  chair suppliers.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ccur.pol">
         <Header>
            <Title>Currency</Title>
         </Header>
         <FuncDesc>A generally accepted medium of exchange such as coins, treasury
		notes, and banknotes.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The following currency types are available in ERP Enterprise:</ListIntro>
               <ListItem>Home currency, which is used internally by companies to
			 calculate costs, record budgets, and register tax amounts</ListItem>
               <ListItem>Transaction currency, which is used in transactions with
			 business partners, such as orders and invoices</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="item.pol">
         <Header>
            <Title>Item</Title>
         </Header>
         <FuncDesc>In ERP Enterprise,
		the raw materials, subassemblies, finished products, and tools that can be
		purchased, stored, manufactured, sold, and so on.</FuncDesc>
         <SimpleSection>
            <Paragraph>An item can also represent a set of items handled as one kit,
		  or exist in multiple product variants.</Paragraph>
            <List>
               <ListIntro>You can also define nonphysical items, which are not held
			 in inventory but can be used to post costs or to invoice services to customers.
			 The following are examples of nonphysical items:</ListIntro>
               <ListItem>Cost items (for example, electricity)</ListItem>
               <ListItem>Service items</ListItem>
               <ListItem>Subcontracting services</ListItem>
               <ListItem>List items (menus/options)</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="bfbp.po">
         <Header>
            <Title>Buy-from Business Partner</Title>
         </Header>
         <FuncDesc>The business partner from whom you order goods or services;
		this usually represents a supplier's sales department. The definition includes
		the default price and discount agreements, purchase-order defaults, delivery
		terms, and the related ship-from and invoice-from business partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ifbp.po">
         <Header>
            <Title>Invoice-from Business Partner</Title>
         </Header>
         <FuncDesc>The business partner that sends invoices to your organization.
		This usually represents a supplier's accounts receivable department. The
		definition includes the default currency and exchange rate, invoicing method
		and frequency, information about your organization's credit limit, the terms
		and method of payment, and the related pay-to business partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="poor.po">
         <Header>
            <Title>Order Origin</Title>
         </Header>
         <FuncDesc>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.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="poof.po">
         <Header>
            <Title>Purchase Office</Title>
         </Header>
         <FuncDesc>A department in your organization that is responsible for
		buying the materials and services needed by your organization. You assign
		number groups to the purchase office.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>In this way, you can assign serial numbers to:</ListIntro>
               <ListItem>Purchase orders</ListItem>
               <ListItem>Purchase schedules</ListItem>
               <ListItem>Requests for quotations</ListItem>
               <ListItem>Purchase contracts</ListItem>
            </List>
            <Paragraph>You can also define a default warehouse where goods ordered by
		  the purchase office must be delivered.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="bppo.po">
         <Header>
            <Title>Pricing BP</Title>
         </Header>
         <FuncDesc>The <Link href="/baanerp/tc/glossary/glossary#ParentBusine_tc" role="glossary">parent business partner</Link> used
		  to classify a group of suppliers or vendors with the same prices or pricing
		  agreements.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="prls.po">
         <Header>
            <Title>Price List</Title>
         </Header>
         <FuncDesc>List of default prices and discounts for customers and
		suppliers. You can link price lists to items and item groups, and to sold-to
		and buy-from business partners.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="pame.po">
         <Header>
            <Title>Payment Method</Title>
         </Header>
         <FuncDesc>The way in which the payment (purchase invoice) or the direct
		debit (sales invoice) takes place. The payment method defines details such as,
		the maximum amount, the type of due date, if foreign currencies are allowed,
		and which details must be printed on the report.</FuncDesc>
         <SimpleSection>
            <Paragraph>These details are default values that you can change on the
		  order or invoice as necessary.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="trde.po">
         <Header>
            <Title>Delivery Terms</Title>
         </Header>
         <FuncDesc>The agreements with the business partner, concerning the way
		the goods are delivered. Relevant information is printed on various order
		documents.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="area.po">
         <Header>
            <Title>Area</Title>
         </Header>
         <FuncDesc>A region used to group business partners, customers, suppliers
		and employees on a geographical basis.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="bfty.po">
         <Header>
            <Title>Buy-from Type</Title>
         </Header>
         <FuncDesc> 
            <Link href="/baanerp/tc/glossary/glossary#BusineParTyp_tc" role="glossary"
                  Update="No">Business partner types</Link> are used to classify a group of suppliers, for example, a group of
		  chair suppliers.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="ccur.po">
         <Header>
            <Title>Currency</Title>
         </Header>
         <FuncDesc>A generally accepted medium of exchange such as coins, treasury
		notes, and banknotes.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The following currency types are available in ERP Enterprise:</ListIntro>
               <ListItem>Home currency, which is used internally by companies to
			 calculate costs, record budgets, and register tax amounts</ListItem>
               <ListItem>Transaction currency, which is used in transactions with
			 business partners, such as orders and invoices</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
   </Fields>
</Session>