<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tc/trm/tctrm1120m000" xml:lang="en">
   <Header>
      <Title>Terms and Conditions Lines (tctrm1120m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to view, enter, and
		  maintain <Link href="/baanerp/tc/glossary/glossary#000505" role="glossary" Update="No">terms and conditions lines</Link> for a combination
		  of <Link href="/baanerp/tc/glossary/glossary#000500" role="glossary" Update="No">terms and conditions agreement</Link> and <Link href="/baanerp/tc/glossary/glossary#000503" role="glossary" Update="No">terms and conditions search level</Link>.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>To start the <Link href="/baanerp/tc/trm/tctrm1620m000" role="session">Terms and Conditions Line (tctrm1620m000)</Link> session, double-click a
		  record.</Paragraph>
      </GeneralSection>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>This session can be displayed in different views. If you click <GUIRef href="" role="manual">Sort by</GUIRef> on the <GUIRef href="" role="manual">View</GUIRef> menu, you can change the
		  terms and conditions lines' view. Therefore, ERP Enterprise changes the
		  session's title bar and column sequence.</Paragraph>
      </Note>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/tc/onlinemanual/000500" role="manual">Overview of terms and conditions</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/tc/onlinemanual/000503" role="manual">Setting up terms and conditions</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tctrm120.trid">
         <Header>
            <Title>Terms and Conditions ID</Title>
         </Header>
         <FuncDesc>An agreement between business partners about the sale,
		purchase, or transfer of goods, in which you can define detailed terms and
		conditions about orders, schedules, planning, logistics, invoicing, and demand
		pegging, and define the search mechanism to retrieve the correct terms and
		conditions.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The agreement includes the following:</ListIntro>
               <ListItem>A header with the type of agreement and the business
			 partner(s).</ListItem>
               <ListItem>Search levels with a search priority and a selection of
			 search attributes (fields) and linked terms and conditions groups.</ListItem>
               <ListItem>One or more lines with the values for the search levels’
			 search attributes.</ListItem>
               <ListItem>Terms and conditions groups with detailed terms and
			 conditions about orders, schedules, planning, logistics, invoicing, and demand
			 pegging for the lines.</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tctrm120.slev">
         <Header>
            <Title>Search Level</Title>
         </Header>
         <FuncDesc>A priority level for searching and selecting a terms and
		conditions line. Search levels include a selection of search attributes
		(fields) and linked terms and conditions groups.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tctrm120.pono">
         <Header>
            <Title>Position</Title>
         </Header>
         <FuncDesc>The number used to identify the position of the <Link href="/baanerp/tc/glossary/glossary#000505" role="glossary">terms and conditions line</Link> on the <Link href="/baanerp/tc/glossary/glossary#000500" role="glossary">terms and conditions agreement</Link> or the <Link href="/baanerp/tc/glossary/glossary#000508" role="glossary">terms and conditions template</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tctrm120.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>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If the <GUIRef href="/baanerp/tc/trm/tctrm1610m000#tctrm110.plng" role="manual">Planning</GUIRef> check box is selected in the <GUIRef href="/baanerp/tc/trm/tctrm1610m000" role="session">Terms and Conditions Search Level - Lines (tctrm1610m000)</GUIRef> session, only items
			 for which the <Link href="/baanerp/tc/glossary/glossary#000003" role="glossary">order system</Link> is set to <GUIRef href="/baanerp/tc/domains/osys#mps" role="option">Planned</GUIRef> or <GUIRef href="/baanerp/tc/domains/osys#fas" role="option">FAS</GUIRef> and for
			 which ordering data is defined in the <GUIRef href="/baanerp/tc/ibd/tcibd2500m000" role="session">Items - Ordering (tcibd2500m000)</GUIRef> session, can be entered in this field.</Paragraph>
            <Paragraph/>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tctrm120.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="tctrm120.prtp">
         <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="tctrm120.prln">
         <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="tctrm120.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="tctrm120.wrcm">
         <Header>
            <Title>Warehouse Company</Title>
         </Header>
         <FuncDesc>The warehouse's <Link href="/baanerp/tc/glossary/glossary#Company_tc" role="glossary">company</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tctrm120.wrhs">
         <Header>
            <Title>Warehouse</Title>
         </Header>
         <FuncDesc>A place for storing goods. For each warehouse, you can enter
		address data and data relating to its type.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tctrm120.wrst">
         <Header>
            <Title>Warehouse Set</Title>
         </Header>
         <FuncDesc>A group of warehouses with similar characteristics. A warehouse
		can belong to one particular warehouse set.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tctrm120.ofbp">
         <Header>
            <Title>Sold-to Business Partner</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="tctrm120.stbp">
         <Header>
            <Title>Ship-to Business Partner</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="tctrm120.itbp">
         <Header>
            <Title>Invoice-to Business Partner</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="tctrm120.otbp">
         <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="tctrm120.sfbp">
         <Header>
            <Title>Ship-from Business Partner</Title>
         </Header>
         <FuncDesc>The business partner that ships the ordered goods to your
		organization. This usually represents a supplier's distribution center or
		warehouse. The definition includes the default warehouse at which you want to
		receive the goods and if you want to inspect the goods, the carrier that takes
		care of the transport, and the related buy-from business partner.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tctrm120.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="tctrm120.dpcm">
         <Header>
            <Title>Department</Title>
         </Header>
         <FuncDesc>The department's <Link href="/baanerp/tc/glossary/glossary#Company_tc" role="glossary">company</Link>.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tctrm120.dpmt">
         <Header>
            <Title>Department</Title>
         </Header>
         <FuncDesc>A company's organizational unit that carries out a specific set
		of tasks, for example, a sales office or a purchase office. Departments are
		assigned number groups for the orders they issue. The department's enterprise
		unit determines the financial company to which the financial transactions that
		the department generates are posted.</FuncDesc>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="generate.terms.groups">
         <Header>
            <Title>Generate Default Terms and Conditions</Title>
         </Header>
         <FuncDesc>If the <Link href="/baanerp/tc/glossary/glossary#000500" role="glossary" Update="No">terms and conditions agreement</Link> is generated
		  from a <Link href="/baanerp/tc/glossary/glossary#000508" role="glossary" Update="No">terms and conditions template</Link>, use this
		  command to copy the template's <Link href="/baanerp/tc/glossary/glossary#000506" role="glossary" Update="No">terms and conditions groups</Link> after the <Link href="/baanerp/tc/glossary/glossary#000505" role="glossary" Update="No">terms and conditions lines</Link> are manually
		  defined.</FuncDesc>
         <SimpleSection>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>In <Link href="/baanerp/tc/glossary/glossary#000500" role="glossary" Update="No">terms and conditions agreements</Link> it is
			 mandatory to specify the <Link href="/baanerp/tc/glossary/glossary#000505" role="glossary" Update="No">terms and conditions lines</Link>. However, in <Link href="/baanerp/tc/glossary/glossary#000508" role="glossary" Update="No">terms and conditions templates</Link>, the lines can
			 be left empty, while the <Link href="/baanerp/tc/glossary/glossary#000506" role="glossary" Update="No">terms and conditions groups</Link> are
			 filled.</Paragraph>
         </SimpleSection>
      </CommandHelp>
   </FormCommands>
</Session>