<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/ci/sli/cisli2100m000" xml:lang="en">
   <Header>
      <Title>Billing Requests (cisli2100m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph> Use this session to define and maintain ranges of order invoicing data selected for invoicing in
		  the <Link href="/baanerp/ci/glossary/glossary#000001" role="glossary">billing request</Link>.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>The types and number of orders that you can
		  select is determined by the <Link href="/baanerp/ci/glossary/glossary#000002" role="glossary">billing request template</Link> that you select for the billing request. For details,
		  refer to <Link href="/baanerp/ci/onlinemanual/000005" role="manual">Selecting order data for invoicing</Link>.</Paragraph>
         <Paragraph>From he selected ranges, ERP Enterprise only generates
		  invoices for the invoicing data lines that have the <GUIRef href="/baanerp/ci/domains/sli.stat#confirmed" role="option">Confirmed</GUIRef> status when you process the billing request.</Paragraph>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle> Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/ci/onlinemanual/000005" role="manual">Selecting order data for invoicing</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/ci/onlinemanual/000001" role="manual">Invoicing procedure</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldGroup>
         <Title> Common</Title>
         <FieldHelp ID="cisli200.scmp">
            <Header>
               <Title>Sales Invoice Company</Title>
            </Header>
            <FuncDesc>A company that is used for posting financial data in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>. You can link one
		or more enterprise units from multiple logistic companies to one financial
		company.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="cisli200.brid">
            <Header>
               <Title>Billing Request</Title>
            </Header>
            <FuncDesc>The number that ERP Enterprise generates for the <Link href="/baanerp/ci/glossary/glossary#000001" role="glossary">billing request</Link>.</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="cisli200.dsca">
            <Header>
               <Title>Description</Title>
            </Header>
            <FuncDesc> The description or name of the code.</FuncDesc>
         </FieldHelp>
         <FieldGroup>
            <Title> Details</Title>
            <FieldHelp ID="cisli200.brtp" OtherIDs="cisli201.dsca">
               <Header>
                  <Title>Template</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/ci/glossary/glossary#000002" role="glossary">billing request template</Link> used for this billing request.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.brad" OtherIDs="cisli120.dsca">
               <Header>
                  <Title>Billing Request Addition</Title>
               </Header>
               <FuncDesc>The <Link href="/baanerp/ci/glossary/glossary#000003" role="glossary">billing request addition</Link> used for this billing request.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.ityp">
               <Header>
                  <Title>Sales Invoice Transaction Type</Title>
               </Header>
               <FuncDesc>If the <Link href="/baanerp/ci/glossary/glossary#000003" role="glossary">billing request addition</Link> allows you to overwrite the default transaction types
				entered in the <Link href="/baanerp/ci/sli/cisli0100m000" role="session">Invoicing Parameters (cisli0100m000)</Link> session, you can enter a transaction type.</FuncDesc>
               <RelatedTopics>
                  <SectionTitle> Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/ci/onlinemanual/000005#Overwrite.defaults" role="manual">Overwriting the transaction types and series</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cisli200.seri">
               <Header>
                  <Title>Series Number</Title>
               </Header>
               <FuncDesc>If the <Link href="/baanerp/ci/glossary/glossary#000003" role="glossary">billing request addition</Link> allows you to overwrite the default series entered in
				the <Link href="/baanerp/ci/sli/cisli0100m000" role="session">Invoicing Parameters (cisli0100m000)</Link> session, you can enter the series.</FuncDesc>
               <RelatedTopics>
                  <SectionTitle> Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/ci/onlinemanual/000005#Overwrite.defaults" role="manual">Overwriting the transaction types and series</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Common Selection Criteria</Title>
            <FieldHelp ID="cisli200.fcpf" OtherIDs="cisli200.fcpt">
               <Header>
                  <Title>Financial Company</Title>
               </Header>
               <FuncDesc>A company that is used for posting financial data in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>. You can link one
		or more enterprise units from multiple logistic companies to one financial
		company.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.ofbf" OtherIDs="cisli200.ofbt">
               <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="cisli200.soff" OtherIDs="cisli200.soft">
               <Header>
                  <Title>Department</Title>
               </Header>
               <FuncDesc>The department that determines the financial company to which
		the transaction must be posted and which is responsible for the tax declaration
		in the <Link href="/baanerp/tc/glossary/glossary#000337" role="glossary">tax country</Link> of the order. The financial company's home
		country must be the tax country of the order. The financial department is an <Link href="/baanerp/tc/glossary/glossary#000334" role="glossary">accounting office</Link> of the financial company.</FuncDesc>
               <SimpleSection>
                  <Paragraph>If the financial company of the administrative department has
		  a tax number in the tax country of the order, the financial department is the
		  same department as the administrative department.</Paragraph>
               </SimpleSection>
            </FieldHelp>
            <FieldHelp ID="cisli200.crpf" OtherIDs="cisli200.crpt">
               <Header>
                  <Title>Sales Representative</Title>
               </Header>
               <FuncDesc>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.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.codt">
               <Header>
                  <Title>Cut Off Date</Title>
               </Header>
               <FuncDesc>The latest date for which transactions are processed.
		Transactions with a transaction date later than the cut-off date specified for
		a process are not included in the process.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Background Information</Title>
            <FieldHelp ID="cisli200.brst">
               <Header>
                  <Title>Status</Title>
               </Header>
               <FuncDesc> 
                  <Link href="/baanerp/ci/domains/sli.brst" role="domain">Billing request status</Link>
               </FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.bred">
               <Header>
                  <Title>Entry Date</Title>
               </Header>
               <FuncDesc>The date and time when the billing request was created.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.brlu">
               <Header>
                  <Title>Last Update</Title>
               </Header>
               <FuncDesc>The date and time when the billing request was last
				updated.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.user">
               <Header>
                  <Title>User</Title>
               </Header>
               <FuncDesc>The logon name of the user who last updated the billing
				request.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.uslu">
               <Header>
                  <Title>User Last Update</Title>
               </Header>
               <FuncDesc>The user who last updated the billing request.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title> Sales/Rebates/Self-Billed Invoices</Title>
         <FieldGroup>
            <Title> Sales</Title>
            <FieldHelp ID="cisli200.cslf" OtherIDs="cisli200.cslt">
               <Header>
                  <Title>Logistic Company</Title>
               </Header>
               <FuncDesc>An ERP Enterprise company used for logistic transactions, such as the production and
		transportation of goods. All the logistic data concerning the transactions is
		stored in the company's database.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.slsf" OtherIDs="cisli200.slst">
               <Header>
                  <Title>Sales / Warehouse Order</Title>
               </Header>
               <FuncDesc>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.</FuncDesc>
               <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>
            </FieldHelp>
            <FieldHelp ID="cisli200.sltf" OtherIDs="cisli200.sltt">
               <Header>
                  <Title>Sales Order Type</Title>
               </Header>
               <FuncDesc>A sales order property that allows you to identify the kind of
		sale made and the kind of receivable. This property is used to post the sales
		to the correct <GUIRef href="/baanerp/tf/acr" role="module">Accounts Receivable</GUIRef> account when the invoice is created. To post a sales
		invoice, ERP Enterprise retrieves
		the control account from the sales type linked to the sales order line, project
		contract, and so on.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.sdnf" OtherIDs="cisli200.sdnt">
               <Header>
                  <Title>Delivery Note From</Title>
               </Header>
               <FuncDesc>A transport document that provides information on a consignment
		contained in one truck (or other vehicle) and refers to an order or a set of
		orders for one consignee at a delivery address. If the truck load contains
		shipments for various business partners, the load includes more than one
		delivery note. The information on a delivery note includes the delivery date
		and address, the customer's name, the contents of the consignment, and so on.
		In Italy, a delivery note is a legally required document, where it used to be
		called BAM (Bolla Accompagnamento Merci). Currently it is called DDT (Documento
		di Trasporto). In Portugal and Spain delivery notes are also used, but there
		they do not have the same legal status as in Italy.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Rebates</Title>
            <FieldHelp ID="cisli200.rslf" OtherIDs="cisli200.rslt">
               <Header>
                  <Title>Logistic Company From</Title>
               </Header>
               <FuncDesc>An ERP Enterprise company used for logistic transactions, such as the production and
		transportation of goods. All the logistic data concerning the transactions is
		stored in the company's database.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.rsof" OtherIDs="cisli200.rsot">
               <Header>
                  <Title>Sales Order - From</Title>
               </Header>
               <FuncDesc>Order related to <Link href="/baanerp/td/glossary/glossary#Rebate_td" role="glossary">rebate</Link>.</FuncDesc>
               <RelatedTopics>
                  <SectionTitle> Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/ci/onlinemanual/000020" role="manual">Rebates</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
            <FieldHelp ID="cisli200.relf" OtherIDs="cisli200.relt">
               <Header>
                  <Title>Relation - From</Title>
               </Header>
               <FuncDesc>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.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title> Internal Invoices</Title>
         <FieldGroup>
            <Title> Purchase Order</Title>
            <FieldHelp ID="cisli200.cpof" OtherIDs="cisli200.cpot">
               <Header>
                  <Title>Logistic Company From</Title>
               </Header>
               <FuncDesc>An ERP Enterprise company used for logistic transactions, such as the production and
		transportation of goods. All the logistic data concerning the transactions is
		stored in the company's database.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.pofr" OtherIDs="cisli200.poft">
               <Header>
                  <Title>Purchase Order From</Title>
               </Header>
               <FuncDesc>The order that indicates which items are delivered by a
		buy-from business partner according to certain terms and conditions.</FuncDesc>
               <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>
            </FieldHelp>
            <FieldHelp ID="cisli200.potf" OtherIDs="cisli200.pott">
               <Header>
                  <Title>Purchase Order Type From</Title>
               </Header>
               <FuncDesc>The order type determines which sessions are part of the order
		procedure and how and in which sequence this procedure is executed.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> PCS Order</Title>
            <FieldHelp ID="cisli200.pclf" OtherIDs="cisli200.pclt">
               <Header>
                  <Title>Logistic Company From</Title>
               </Header>
               <FuncDesc>An ERP Enterprise company used for logistic transactions, such as the production and
		transportation of goods. All the logistic data concerning the transactions is
		stored in the company's database.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.pcsf" OtherIDs="cisli200.pcst">
               <Header>
                  <Title>PCS Order From</Title>
               </Header>
               <FuncDesc>Order related to a <Link href="/baanerp/ti/glossary/glossary#000023" role="glossary">PCS project</Link>.</FuncDesc>
               <RelatedTopics>
                  <SectionTitle> Related topics</SectionTitle>
                  <RelTopic>
                     <Link href="/baanerp/ti/onlinemanual/000435" role="manual">COGS and revenue postings for PCS projects in a multisite environment</Link>
                  </RelTopic>
               </RelatedTopics>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Warehouse</Title>
            <FieldHelp ID="cisli200.cwhf" OtherIDs="cisli200.cwht">
               <Header>
                  <Title>Source Logistic Company</Title>
               </Header>
               <FuncDesc>An ERP Enterprise company used for logistic transactions, such as the production and
		transportation of goods. All the logistic data concerning the transactions is
		stored in the company's database.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.wogf" OtherIDs="cisli200.wogt">
               <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="cisli200.whof" OtherIDs="cisli200.whot">
               <Header>
                  <Title>Warehouse Order</Title>
               </Header>
               <FuncDesc>An order for handling goods in the warehouse.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListIntro>A warehouse order can be of the following
			 inventory-transaction types:</ListIntro>
                     <ListItem> 
                        <GUIRef href="/baanerp/wh/domains/inh.ittp#receipt" role="option">Receipt</GUIRef>
                     </ListItem>
                     <ListItem> 
                        <GUIRef href="/baanerp/wh/domains/inh.ittp#issue" role="option">Issue</GUIRef>
                     </ListItem>
                     <ListItem> 
                        <GUIRef href="/baanerp/wh/domains/inh.ittp#transfer" role="option">Transfer</GUIRef>
                     </ListItem>
                     <ListItem>
                        <GUIRef href="/baanerp/wh/domains/inh.ittp#wip.transfer" role="option">WIP Transfer</GUIRef>
                     </ListItem>
                  </List>
                  <Paragraph>Each order has an origin and contains all the information
		  required for warehouse handling. Depending on the item (lot or non-lot) and
		  warehouse (with or without locations), lots and/or locations can be assigned.
		  The order follows a predefined warehousing procedure.</Paragraph>
               </SimpleSection>
               <Note>
                  <SectionTitle>Note</SectionTitle>
                  <Paragraph>In <GUIRef href="/baanerp/ti" role="package">Manufacturing</GUIRef> a warehousing order is often called a
		  warehouse order.</Paragraph>
               </Note>
            </FieldHelp>
            <FieldHelp ID="cisli200.whtf" OtherIDs="cisli200.whtt">
               <Header>
                  <Title>Warehouse Order Types</Title>
               </Header>
               <FuncDesc>A code that identifies the type of a warehousing order. The
		default warehousing procedure that you link to a warehousing order type
		determines how the warehousing orders to which the order type is allocated are
		processed in the warehouse, although you can modify the default procedure for
		individual warehousing orders or order lines.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.wdnf" OtherIDs="cisli200.wdnt">
               <Header>
                  <Title>Delivery Note From</Title>
               </Header>
               <FuncDesc>A transport document that provides information on a consignment
		contained in one truck (or other vehicle) and refers to an order or a set of
		orders for one consignee at a delivery address. If the truck load contains
		shipments for various business partners, the load includes more than one
		delivery note. The information on a delivery note includes the delivery date
		and address, the customer's name, the contents of the consignment, and so on.
		In Italy, a delivery note is a legally required document, where it used to be
		called BAM (Bolla Accompagnamento Merci). Currently it is called DDT (Documento
		di Trasporto). In Portugal and Spain delivery notes are also used, but there
		they do not have the same legal status as in Italy.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title> Contract</Title>
         <FieldGroup>
            <Title> Project Invoice Types</Title>
            <FieldHelp ID="cisli200.sadv"
                       OtherIDs="cisli200.sist cisli200.sext cisli200.scpl cisli200.shbk cisli200.sunr cisli200.sadc">
               <Header>
                  <Title>Project Invoice Data</Title>
               </Header>
               <FuncDesc> If this check box is selected, Project invoice data of
				this type is selected when you process the billing request.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.sadv">
               <Header>
                  <Title>Advance Receipt Request</Title>
               </Header>
               <FuncDesc> If this check box is selected, <Link href="/baanerp/tf/glossary/glossary#000046" role="glossary">advance receipt requests</Link> are taken into account when you process the billing
				request.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.sist">
               <Header>
                  <Title>Installments</Title>
               </Header>
               <FuncDesc> If this check box is selected, <Link href="/baanerp/tp/glossary/glossary#000089" role="glossary">installments</Link> are taken into account when you process the
				billing request.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.scpl">
               <Header>
                  <Title>Cost Plus</Title>
               </Header>
               <FuncDesc> If this check box is selected, <Link href="/baanerp/tp/glossary/glossary#000078" role="glossary">cost plus contracts</Link> are taken into account when you process the billing request.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.sunr">
               <Header>
                  <Title>Unit Rate</Title>
               </Header>
               <FuncDesc> If this check box is selected, <Link href="/baanerp/tp/glossary/glossary#UnitRate_tp" role="glossary">unit rates</Link> are taken into account when you process the billing request.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.shbk">
               <Header>
                  <Title>Holdback</Title>
               </Header>
               <FuncDesc> If this check box is selected, <Link href="/baanerp/tp/glossary/glossary#000052" role="glossary">holdback</Link> amounts are taken into account when you process
				the billing request.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.sext">
               <Header>
                  <Title>Extensions</Title>
               </Header>
               <FuncDesc> If this check box is selected, <Link href="/baanerp/tp/glossary/glossary#000017" role="glossary">extensions</Link> are taken into account when you process the
				billing request.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.sadc">
               <Header>
                  <Title>Installment Additional Costs</Title>
               </Header>
               <FuncDesc> If this check box is selected, <Link href="/baanerp/tf/glossary/glossary#000025" role="glossary">additional costs</Link> related to installments are taken into account when you process
				the billing request.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Selection Range</Title>
            <FieldHelp ID="cisli200.cpjf" OtherIDs="cisli200.cpjt">
               <Header>
                  <Title>Logistic Company</Title>
               </Header>
               <FuncDesc>An ERP Enterprise company used for logistic transactions, such as the production and
		transportation of goods. All the logistic data concerning the transactions is
		stored in the company's database.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.prjf" OtherIDs="cisli200.prjt">
               <Header>
                  <Title>Project</Title>
               </Header>
               <FuncDesc>The code that identifies the project.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.cstf" OtherIDs="cisli200.cstl">
               <Header>
                  <Title>Extension</Title>
               </Header>
               <FuncDesc>The code that identifies the extension.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title> Service</Title>
         <FieldGroup>
            <Title> Service Orders</Title>
            <FieldHelp ID="cisli200.csvf" OtherIDs="cisli200.csvt">
               <Header>
                  <Title>Logistic Company</Title>
               </Header>
               <FuncDesc>An ERP Enterprise company used for logistic transactions, such as the production and
		transportation of goods. All the logistic data concerning the transactions is
		stored in the company's database.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.svof" OtherIDs="cisli200.svot">
               <Header>
                  <Title>Service Order</Title>
               </Header>
               <FuncDesc>Orders that are used to plan, carry out, and control all repair
		and maintenance on configurations as present on customer sites or as present
		with the company.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.svtf" OtherIDs="cisli200.svtt">
               <Header>
                  <Title>Service Type</Title>
               </Header>
               <FuncDesc>The service classification that service providers offer. The
		service type determines which availability type applies to a service order
		header, and provides a default order procedure and coverage type.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.scff" OtherIDs="cisli200.scft">
               <Header>
                  <Title>Installation Group</Title>
               </Header>
               <FuncDesc>A set of serialized items that have the same location and are
		owned by the same business partner. Grouping serialized items into an
		
Installation
		group enables you to maintain them collectively.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Service Call</Title>
            <FieldHelp ID="cisli200.cmlf" OtherIDs="cisli200.cmlt">
               <Header>
                  <Title>Logistic Company</Title>
               </Header>
               <FuncDesc>An ERP Enterprise company used for logistic transactions, such as the production and
		transportation of goods. All the logistic data concerning the transactions is
		stored in the company's database.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.svcf" OtherIDs="cisli200.svct">
               <Header>
                  <Title>Service Call</Title>
               </Header>
               <FuncDesc>A question, complaint, or malfunction that is communicated to
		the party responsible for the service or maintenance of the item concerned.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Maintenance Sales Order</Title>
            <FieldHelp ID="cisli200.smlf" OtherIDs="cisli200.smlt">
               <Header>
                  <Title>Logistic Company</Title>
               </Header>
               <FuncDesc>An ERP Enterprise company used for logistic transactions, such as the production and
		transportation of goods. All the logistic data concerning the transactions is
		stored in the company's database.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.smof" OtherIDs="cisli200.smot">
               <Header>
                  <Title>Maintenance Sales Order From</Title>
               </Header>
               <FuncDesc>Orders that are used to plan, carry out, and control the
		maintenance on customer-owned components, products and the logistic handling of
		spare parts.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.smtf">
               <Header>
                  <Title>Service Type</Title>
               </Header>
               <FuncDesc>The service classification that service providers offer. The
		service type determines which availability type applies to a service order
		header, and provides a default order procedure and coverage type.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Contracts</Title>
            <FieldHelp ID="cisli200.cscf" OtherIDs="cisli200.csct">
               <Header>
                  <Title>Log. Company Service Contracts</Title>
               </Header>
               <FuncDesc>An ERP Enterprise company used for logistic transactions, such as the production and
		transportation of goods. All the logistic data concerning the transactions is
		stored in the company's database.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.scof" OtherIDs="cisli200.scot">
               <Header>
                  <Title>Service Contract</Title>
               </Header>
               <FuncDesc>A sales agreement between a service organization and a customer
		for a specific period, that states the configurations (Installation
		groups or serialized items) to be maintained, the
		coverage terms, and the agreed price.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.sctf" OtherIDs="cisli200.sctt">
               <Header>
                  <Title>Contract Type</Title>
               </Header>
               <FuncDesc>A way of categorizing contracts based on similarities and
		shared characteristics.</FuncDesc>
               <SimpleSection>
                  <Paragraph>Each contract type is identified by an alphanumeric code of
		  up to three characters.</Paragraph>
               </SimpleSection>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
      <FieldGroup>
         <Title> Financial/Freight</Title>
         <FieldGroup>
            <Title> Manual Sales</Title>
            <FieldHelp ID="cisli200.cmsf" OtherIDs="cisli200.cmst">
               <Header>
                  <Title>Fin. Company Manual Sales</Title>
               </Header>
               <FuncDesc>A company that is used for posting financial data in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>. You can link one
		or more enterprise units from multiple logistic companies to one financial
		company.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.msif" OtherIDs="cisli200.msit">
               <Header>
                  <Title>Manual Sales ID</Title>
               </Header>
               <FuncDesc>An invoice without a related sales order or goods receipt and
		which is directly created in <GUIRef href="/baanerp/ci" role="package">Invoicing</GUIRef>.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Interest Invoices</Title>
            <FieldHelp ID="cisli200.ciif" OtherIDs="cisli200.ciit">
               <Header>
                  <Title>Fin. Company Interest Invoices</Title>
               </Header>
               <FuncDesc>A company that is used for posting financial data in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>. You can link one
		or more enterprise units from multiple logistic companies to one financial
		company.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.iivf" OtherIDs="cisli200.iivt">
               <Header>
                  <Title>Interest Invoice Identification</Title>
               </Header>
               <FuncDesc>An invoice to charge interest.</FuncDesc>
               <SimpleSection>
                  <List>
                     <ListIntro>You can create interest invoices for:</ListIntro>
                     <ListItem>Unpaid overdue invoices.</ListItem>
                     <ListItem>Invoices that were paid or partially paid later than their
			 due dates.</ListItem>
                  </List>
               </SimpleSection>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Debit/Credit Note (Finance)</Title>
            <FieldHelp ID="cisli200.fdcn" OtherIDs="cisli200.tdcn">
               <Header>
                  <Title>From Financial Company Debit/Credit Note (Finance)</Title>
               </Header>
               <FuncDesc>A company that is used for posting financial data in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef>. You can link one
		or more enterprise units from multiple logistic companies to one financial
		company.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.fdci" OtherIDs="cisli200.tdci">
               <Header>
                  <Title>From Debit/Credit Note (Finance) ID</Title>
               </Header>
               <FuncDesc>Debit/Credit note number.</FuncDesc>
            </FieldHelp>
         </FieldGroup>
         <FieldGroup>
            <Title> Freight Orders</Title>
            <FieldHelp ID="cisli200.cfrf" OtherIDs="cisli200.cfrt">
               <Header>
                  <Title>Logistic Company From</Title>
               </Header>
               <FuncDesc>An ERP Enterprise company used for logistic transactions, such as the production and
		transportation of goods. All the logistic data concerning the transactions is
		stored in the company's database.</FuncDesc>
            </FieldHelp>
            <FieldHelp ID="cisli200.frtf" OtherIDs="cisli200.frtt">
               <Header>
                  <Title>Freight Order - From</Title>
               </Header>
               <FuncDesc>A commission to transport a particular number of goods. A
		freight order includes an order header and one or more order lines.</FuncDesc>
               <SimpleSection>
                  <Paragraph>A freight order header includes some general information,
		  such as the delivery date and the name and address of the customer who is to
		  receive the goods listed on the freight order.</Paragraph>
                  <Paragraph>A freight order line includes an item to be transported and
		  some details about the item, such as the quantity and the dimensions.</Paragraph>
               </SimpleSection>
            </FieldHelp>
         </FieldGroup>
      </FieldGroup>
   </Fields>
</Session>