<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tc/mcs/tcmcs2104m000" xml:lang="en">
   <Header>
      <Title>Sales Type Exceptions (tcmcs2104m000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph>Use this session to define <Link href="/baanerp/tf/glossary/glossary#000432" role="glossary">sales type</Link> exceptions. Sales types exceptions link sales types (and through
		  the sales type, a control account) to transactions that involve specific
		  details for an invoice-to business partner and order origin.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>Transactions for which you do not define a sales type
		  exception are posted to the control account linked to the default sales type
		  for the business partner group.</Paragraph>
         <List>
            <ListIntro>You can define exceptions for various logistic order
			 origins, such as Sales, Project, and Freight. You can define exceptions for the
			 following types of order details:</ListIntro>
            <ListItem>Item groups.</ListItem>
            <ListItem>Items.</ListItem>
            <ListItem>Project categories.</ListItem>
            <ListItem>Projects.</ListItem>
         </List>
         <Paragraph>If the order origin is <GUIRef href="" role="manual">Sales</GUIRef>, you can
		  indicate whether the exception is valid for direct delivery orders.</Paragraph>
         <Paragraph>You can specify exceptions that apply to a specific business
		  partner and you can specify exceptions that apply generally to all the
		  transactions. To define general exceptions, leave the <GUIRef href="/baanerp/tc/mcs/tcmcs2104m000#tcmcs204.itbp" role="manual">Invoice-to Business Partner</GUIRef> field empty.</Paragraph>
         <Paragraph>For each exception, you can indicate the priority. If more
		  than one exception is found, ERP Enterprise uses the details of the exception with the
		  highest priority. For example, if the exception for an item has a higher
		  priority than the exception for a specific project, transactions concerning
		  both the item and the project are posted to the control account linked to the
		  sales type specified for the item.</Paragraph>
         <Paragraph>Each combination of order origin, item, item group, project
		  category, project, direct delivery indicator, and sales type that you define as
		  an exception, must be unique.</Paragraph>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle>Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/tf/onlinemanual/000400" role="manual">Control accounts</Link>
         </RelTopic>
         <RelTopic>
            <Link href="/baanerp/tf/onlinemanual/000401" role="manual">To set up control accounts</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldHelp ID="tcmcs204.itbp">
         <Header>
            <Title>Invoice-to Business Partner</Title>
         </Header>
         <FuncDesc>The invoice-to business partner to whom the exceptions apply.</FuncDesc>
         <SimpleSection>
            <Paragraph>To define exceptions that apply to all sales invoices
			 independent of the invoice-to business partner, leave this field empty.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tcmcs204.orig">
         <Header>
            <Title>Order Origin</Title>
         </Header>
         <FuncDesc>The logistic origin of the order.</FuncDesc>
         <SimpleSection>
            <List>
               <ListIntro>The order origin can be:</ListIntro>
               <ListItem>Sales.</ListItem>
               <ListItem>Internal invoice.</ListItem>
               <ListItem>Freight.</ListItem>
               <ListItem>Project.</ListItem>
               <ListItem>All origins.</ListItem>
            </List>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tcmcs204.prio">
         <Header>
            <Title>Priority</Title>
         </Header>
         <FuncDesc>The priority of the exception. A low value indicates a high
		  priority. The value 1 indicates the highest priority.</FuncDesc>
         <SimpleSection>
            <Paragraph>For example, if the exception for an item has priority 1 and
			 the exception for a specific project has priority 2, the sales type defined for
			 the item is the default sales type for the order lines with both the item and
			 the project.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tcmcs204.citg">
         <Header>
            <Title>Item Group</Title>
         </Header>
         <FuncDesc>Subject to the priority rules, the sales type for this item
		  group is the default sales type for the order line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcmcs204.item">
         <Header>
            <Title>Item</Title>
         </Header>
         <FuncDesc>Subject to the priority rules, the sales type for this item is
		  the default sales type for the order line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcmcs204.catg">
         <Header>
            <Title>Project Category</Title>
         </Header>
         <FuncDesc>Subject to the priority rules, the sales type for this project
		  category is the default sales type for the order line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcmcs204.cprj">
         <Header>
            <Title>Project</Title>
         </Header>
         <FuncDesc>Subject to the priority rules, the sales type for this project
		  is the default sales type for the order line.</FuncDesc>
      </FieldHelp>
      <FieldHelp ID="tcmcs204.ddel">
         <Header>
            <Title>Direct Delivery</Title>
         </Header>
         <FuncDesc>If this check box is selected, subject to the priority
		  rules, the sales type is the default sales type for order lines with direct
		  delivery.</FuncDesc>
         <SimpleSection>
            <Paragraph>If this check box is cleared, subject to the priority
			 rules the sales type is the default sales type for the order lines for all
			 orders.</Paragraph>
         </SimpleSection>
      </FieldHelp>
      <FieldHelp ID="tcmcs204.styp">
         <Header>
            <Title>Sales Type</Title>
         </Header>
         <FuncDesc>The sales type that ERP Enterprise uses to determine the control account to be
		  used for the invoice transactions.</FuncDesc>
         <SimpleSection>
            <Paragraph>The transactions are posted to the control account that you
			 linked to the sales type in the <GUIRef href="/baanerp/tf/acr/tfacr0515m000" role="session">Control Accounts by Business Parter Group (tfacr0515m000)</GUIRef> session.</Paragraph>
         </SimpleSection>
      </FieldHelp>
   </Fields>
   <FormCommands>
      <CommandHelp ID="increment.prio.as.fr.mark">
         <Header>
            <Title>Increment Priority</Title>
         </Header>
         <FuncDesc>Increases each priority number by one, starting at the selected
		  line. For example, you can use this to insert a line between two existing lines
		  with consecutive priorities.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="renumber">
         <Header>
            <Title>Renumber</Title>
         </Header>
         <FuncDesc>Renumbers the priorities to remove any gaps in the numbers. For
		  example, if you define exceptions with the priorities 1, 4, 6, 7, then after
		  renumbering the priorities will be 1, 2, 3, 4.</FuncDesc>
      </CommandHelp>
      <CommandHelp ID="tcmcs2204m000">
         <Header>
            <Title>Copy Sales Type Exceptions</Title>
         </Header>
         <FuncDesc>Starts the <GUIRef href="/baanerp/tc/mcs/tcmcs2204m000" role="session">Copy Sales Type Exceptions (tcmcs2204m000)</GUIRef> session, which you can use to copy the
		  sales type exceptions that you defined for the invoice-to business partner and
		  order origin, to a different order origin of the same business partner or to an
		  order origin for a different invoice-to business partner.</FuncDesc>
      </CommandHelp>
   </FormCommands>
</Session>