<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/performance/ci/P000001_unique_definition" xml:lang="en">
   <Header>
      <Title>Transaction types and series</Title>
      <Keyword type="header" order="d1e1378743">
         <Level1>Valid for ERP LN FP0, FP1, FP2, FP3, FP4, FP5, FP6, Infor10, 10.2 ERP Enterprise</Level1>
         <Level2>transaction types and series</Level2>
      </Keyword>
      <Keyword type="header" order="d1e1378748">
         <Level1>Effect on CPU</Level1>
         <Level2>transaction types and series</Level2>
      </Keyword>
   </Header>
   <GeneralSection>
      <Paragraph>In the <GUIRef href="/baanerp/ci/sli/cisli0100m000" role="session">Invoicing Parameters (cisli0100m000)</GUIRef> session, on the <GUIRef href="/baanerp/ci/sli/cisli0100m000#cisli.intfin" role="groupbox">Integration with Finance</GUIRef> tab, you can define <Link href="/baanerp/tf/glossary/glossary#TransaType_tf" role="glossary" Update="No">transaction types</Link> and <Link href="/baanerp/tc/glossary/glossary#Series_tc" role="glossary">series</Link> to be used for invoice numbering, depending on
		the origin of the invoice transactions, such as sales orders and service
		orders.</Paragraph>
      <Paragraph>To avoid locking issues and performance loss
		when ERP Enterprise is retrying
		transactions processing, it is recommended to define <Emphasis>unique</Emphasis> transaction types and series for different invoice
		origins.</Paragraph>
      <GeneralSection>
         <SectionTitle> Performance aspects</SectionTitle>
         <List>
            <ListItem> Effect on CPU: Yes</ListItem>
            <ListItem> Effect on database growth: Not applicable</ListItem>
         </List>
      </GeneralSection>
   </GeneralSection>
</ManualTopic>