<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/td/sls/tdsls0100s000" xml:lang="en">
   <Header>
      <Title>Sales Parameters (tdsls0100s000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <List>
            <ListIntro>Use this session to:</ListIntro>
            <ListItem>View historical parameter settings, by double-clicking one of
			 the historical parameter sets.</ListItem>
            <ListItem>Modify current parameter settings, by double-clicking the set
			 without an effective date that appears at the top of the list.</ListItem>
         </List>
      </AimSection>
      <GeneralSection>
         <List>
            <ListIntro>If you make the required changes and save the new parameter
			 set, ERP Enterprise performs the
			 following actions:</ListIntro>
            <ListItem>Adds the new set to the history list.</ListItem>
            <ListItem>Updates the current set (at the top of the list).</ListItem>
         </List>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>By default, the <GUIRef href="/baanerp/td/sls/tdsls0100s000#tdsls000.dsca" role="manual">Description</GUIRef> field contains the date and time when the
			 previous parameter set was saved.</Paragraph>
         </Note>
      </GeneralSection>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tdsls000.indt">
         <Header>
            <Title>Effective Date</Title>
         </Header>
         <FuncDesc>The date and time when the parameters are valid. The parameters
		  are valid until the effective date of a more recent parameter setting.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls000.dsca">
         <Header>
            <Title>Description</Title>
         </Header>
         <FuncDesc>A user-defined name that identifies the parameter settings.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tdsls000.suom">
         <Header>
            <Title>Sales Order Unit of Measure</Title>
         </Header>
         <FuncDesc>The units in which item dimensions in sales orders are
		expressed.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <List>
               <ListItem>If the physical quantities length, area, or volume are
				defined for the item's sales unit, you can enter its corresponding measurements
				in the <GUIRef href="/baanerp/td/sls/tdsls4811s000" role="session">Item Dimensions (tdsls4811s000)</GUIRef> session. The <GUIRef href="/baanerp/td/sls/tdsls4811s000" role="session">Item Dimensions (tdsls4811s000)</GUIRef> session is automatically started when you enter order
				lines in the <GUIRef href="/baanerp/td/sls/tdsls4100m900" role="session">Sales Order - Lines (tdsls4100m900)</GUIRef> session. The unit in which the
				measurements are entered must be linked to the physical quantity length.</ListItem>
               <ListItem>If you do not set this parameter, the item measurements are
				not retrieved when you enter order lines.</ListItem>
            </List>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tdsls000.citt">
         <Header>
            <Title>Default Alternative Item Code System</Title>
         </Header>
         <FuncDesc>You can enter items in the <GUIRef href="/baanerp/td/sls/tdsls1501m000" role="session">Sales Quotation Lines (tdsls1501m000)</GUIRef> session, the <GUIRef href="/baanerp/td/sls/tdsls3501m000" role="session">Sales Contract Lines (tdsls3501m000)</GUIRef> session, or the <GUIRef href="/baanerp/td/sls/tdsls4101m000" role="session">Sales Order Lines (tdsls4101m000)</GUIRef> session using an alternative item code system. For
		  example, you can enter a specific business partner's item code or the general
		  standard (= EAN) code. ERP Enterprise converts this code into an internal item code.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>ERP Enterprise first checks whether a specific item code system is defined for the business
			 partner in the <GUIRef href="/baanerp/tc/ibd/tcibd0504m000" role="session">Item Codes by Item Code System (tcibd0504m000)</GUIRef> session. If not, ERP Enterprise uses the code system
			 defined in the <GUIRef href="/baanerp/td/sls/tdsls0100s000" role="session">Sales Parameters (tdsls0100s000)</GUIRef> session, which must be of the <GUIRef href="/baanerp/tc/domains/citt.type#general" role="option">General</GUIRef> type (see the <GUIRef href="/baanerp/tc/ibd/tcibd0106m000" role="session">Item Code Systems (tcibd0106m000)</GUIRef> session).</Paragraph>
         </Note>
      </FieldHelp>
      <FieldHelp ID="tdsls000.nbol">
         <Header>
            <Title>Maximum Number of Phantom Levels to be Skipped</Title>
         </Header>
         <FuncDesc>This parameter determines the default number of <Link href="/baanerp/ti/glossary/glossary#BomLevel_ti" role="glossary">bill of material (BOM)</Link> levels that are summarized when you use <Link href="/baanerp/ti/glossary/glossary#Phantom_ti" role="glossary">phantoms</Link>.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>You can copy bills of material to quotations in the <GUIRef href="/baanerp/td/sls/tdsls1812s000" role="session">Copy BOM Components to Sales Quotation (tdsls1812s000)</GUIRef> session and to sales orders in the <GUIRef href="/baanerp/td/sls/tdsls4812s000" role="session">Copy Bill of Material to Sales Order (tdsls4812s000)</GUIRef> session.</Paragraph>
         </Note>
         <AllowedValues>
            <SectionTitle>Allowed values</SectionTitle>
            <Paragraph>The number of bill of material levels must be one or
			 higher.</Paragraph>
         </AllowedValues>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/td/onlinemanual/000517" role="manual">To skip phantom levels</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tdsls000.clgr">
         <Header>
            <Title>List Group</Title>
         </Header>
         <FuncDesc>A way to group list items. For example, you can use an SLS list
		group to group list items used on sales orders. A list item can belong to
		different list groups.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/td/onlinemanual/000397" role="manual">Selling items from list groups</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tdsls000.codt">
         <Header>
            <Title>Configuration Date (PCS)</Title>
         </Header>
         <FuncDesc>The date on which the bill of material is exploded.</FuncDesc>
         <Note>
            <SectionTitle>Note</SectionTitle>
            <Paragraph>If this parameter is set to <GUIRef href="/baanerp/td/domains/pur.pric#system.date" role="option">System Date</GUIRef>, this parameter also determines which <Link href="/baanerp/ti/glossary/glossary#Revision_ti" role="glossary">revision</Link> of an <Link href="/baanerp/ti/glossary/glossary#EngineItem_ti" role="glossary">engineering item</Link> is
			 valid for sales schedules. In this case, the current date is compared with the <Link href="/baanerp/tc/glossary/glossary#EffectDate_tc" role="glossary">effective date</Link> or the <Link href="/baanerp/td/glossary/glossary#000210" role="glossary">expiry date</Link> in the revision. If this parameter has another value, the <GUIRef href="/baanerp/td/sls/tdsls3107m000#tdsls307.sdat" role="manual">Start Date</GUIRef> in the <GUIRef href="/baanerp/td/sls/tdsls3107m000" role="session">Sales Schedule Lines (tdsls3107m000)</GUIRef> session determines which revision is
			 valid.</Paragraph>
         </Note>
         <SimpleSection>
            <List>
               <ListIntro>The configuration date can be the following date on the
				sales order/schedule:</ListIntro>
               <ListItem> 
                  <Link href="/baanerp/td/glossary/glossary#000046" role="glossary">Order date</Link>
               </ListItem>
               <ListItem> 
                  <Link href="/baanerp/td/glossary/glossary#000173" role="glossary">System date</Link>
               </ListItem>
               <ListItem> 
                  <Link href="/baanerp/td/glossary/glossary#000088" role="glossary">Planned delivery date</Link>
               </ListItem>
            </List>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle> Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/tibom" role="manual">Bill of Material (BOM)</Link>
            </RelTopic>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000114" role="manual">Engineering items</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tdsls000.cudt">
         <Header>
            <Title>Configuration Date (UEF)</Title>
         </Header>
         <FuncDesc>The date that is used to configure an <Link href="/baanerp/tc/glossary/glossary#000304" role="glossary">effectivity unit</Link> in the <GUIRef href="/baanerp/tc/uef" role="module">Unit Effectivity</GUIRef> module
		  of <GUIRef href="/baanerp/tc" role="package">Common</GUIRef>.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The configuration date can be the following date on the
				sales order/quotation:</ListIntro>
               <ListItem> 
                  <Link href="/baanerp/td/glossary/glossary#000046" role="glossary">Order date</Link>
               </ListItem>
               <ListItem> 
                  <Link href="/baanerp/td/glossary/glossary#000173" role="glossary">System date</Link>
               </ListItem>
               <ListItem> 
                  <Link href="/baanerp/td/glossary/glossary#000088" role="glossary">Planned delivery date</Link>
               </ListItem>
            </List>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/tc/onlinemanual/000358" role="manual">Unit effectivity as a lean configurator in Sales</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tdsls000.lsof">
         <Header>
            <Title>Log Financial Economic Transactions</Title>
         </Header>
         <FuncDesc>When you save a sales order, this field indicates how <Link href="/baanerp/tf/glossary/glossary#000013" role="glossary">financial transactions</Link> are created.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>You have the following options:</ListIntro>
               <ListItemHead>
                  <GUIRef href="/baanerp/td/domains/sls.lsof#no" role="option">No</GUIRef>
               </ListItemHead>
               <ListItem>No financial transactions are created.</ListItem>
               <ListItemHead>
                  <GUIRef href="/baanerp/td/domains/sls.lsof#orderprice" role="option">Order Price</GUIRef>
               </ListItemHead>
               <ListItem>Financial transactions are created based on the order
				price for the order lines. No financial transactions are created on <Link href="/baanerp/td/glossary/glossary#000392" role="glossary">component</Link> line level.</ListItem>
               <ListItemHead>
                  <GUIRef href="/baanerp/td/domains/sls.lsof#costprice" role="option">Valuation Price</GUIRef>
               </ListItemHead>
               <ListItem>Financial transactions are created based on the cost price
				for the order component lines, if available, or for the order lines.</ListItem>
            </List>
         </SimpleSection>
         <SimpleSection>
            <SectionTitle>Performance aspects</SectionTitle>
            <Paragraph>The setting of this field could affect system performance and database growth. For more information, refer to <Link href="/baanerp/performance/td/P000001_financial_economic_transactions"
                     role="manual">Financial economic transactions</Link>.</Paragraph>
         </SimpleSection>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/td/onlinemanual/000515" role="manual">Overview of kit handling in Sales</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tdsls000.erac.4">
         <Header>
            <Title>Engineering Revisions Active in Sales</Title>
         </Header>
         <FuncDesc>If this check box is selected, <Link href="/baanerp/ti/glossary/glossary#Revision_ti" role="glossary">revisions</Link> of <Link href="/baanerp/ti/glossary/glossary#EngineItem_ti" role="glossary">engineering items</Link> can
		  be used in <GUIRef href="/baanerp/sales" role="package">Sales</GUIRef>.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000114" role="manual">Engineering items</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tdsls000.erdc.4">
         <Header>
            <Title>Engineering Revisions on Sales Documents</Title>
         </Header>
         <FuncDesc>If this check box is selected, <Link href="/baanerp/ti/glossary/glossary#Revision_ti" role="glossary">revisions</Link> of <Link href="/baanerp/ti/glossary/glossary#EngineItem_ti" role="glossary">engineering items</Link> are
		  printed on sales documents.</FuncDesc>
         <RelatedTopics>
            <SectionTitle>Related topics</SectionTitle>
            <RelTopic>
               <Link href="/baanerp/ti/onlinemanual/000114" role="manual">Engineering items</Link>
            </RelTopic>
         </RelatedTopics>
      </FieldHelp>
      <FieldHelp ID="tdsls000.ptax">
         <Header>
            <Title>Print Tax on External Sales Documents</Title>
         </Header>
         <FuncDesc>If this check box is selected, tax information is
		  printed on <Link href="/baanerp/td/glossary/glossary#OrderAcknow_td" role="glossary">sales order acknowledgement</Link> documents.</FuncDesc>
      </FieldHelp>
   </Fields>
</Session>