<?xml version="1.0" encoding="utf-8"?>
<Session ID="/baanerp/tf/gld/tfgld4150s000" xml:lang="en">
   <Header>
      <Title>Integration Parameters (tfgld4150s000)</Title>
   </Header>
   <HelpTopic>
      <AimSection>
         <Paragraph> Use this session to maintain the integration
		  parameters.</Paragraph>
      </AimSection>
      <GeneralSection>
         <Paragraph>The integration parameters control the way in which ERP Enterprise handles <Link href="/baanerp/tf/glossary/glossary#000348" role="glossary">integration transactions</Link> during logging and posting.</Paragraph>
      </GeneralSection>
      <RelatedTopics>
         <SectionTitle> Related topics</SectionTitle>
         <RelTopic>
            <Link href="/baanerp/tf/integrations/400003" role="manual">Mapping scheme prerequisites</Link>
         </RelTopic>
      </RelatedTopics>
   </HelpTopic>
   <Fields>
      <FieldGroup>
         <Title> Settings</Title>
         <FieldHelp ID="tfgld450.hdoc">
            <Header>
               <Title>Handling of Document Numbers</Title>
            </Header>
            <FuncDesc>The method to assign document numbers to the financial
			 integration transactions.</FuncDesc>
            <Note>
               <SectionTitle> Note</SectionTitle>
               <Paragraph>In all methods, the
				date is the transaction date.</Paragraph>
            </Note>
         </FieldHelp>
         <FieldHelp ID="tfgld450.htyp">
            <Header>
               <Title>Handling of Batch Numbers</Title>
            </Header>
            <FuncDesc>The way in which batches are created for the posting of the
			 integration transactions.</FuncDesc>
            <SimpleSection>
               <Paragraph>The selected method
				has an effect on the size of the batches. Usually, small batches are processed
				faster than large batches. If an error occurs in one of the transactions,
				processing the batch cannot continue until the error is solved. By reducing the
				batch size, you decrease the number of transactions that cannot be processed if
				an error occurs.</Paragraph>
               <Paragraph>This field can have the following values: <Link href="/baanerp/tf/domains/gld.htyp" role="domain">Batchnumber handling</Link>
               </Paragraph>
               <Paragraph>To form smaller and more batches and increase the pace of
				the process, you can select <GUIRef href="/baanerp/tf/domains/gld.htyp#per.ttyp" role="option">Date/Trans. Type</GUIRef> or <GUIRef href="/baanerp/tf/domains/gld.htyp#day.ttyp.usgp" role="option">Date/Trans.Type/User Grp.</GUIRef>
               </Paragraph>
            </SimpleSection>
            <Note>
               <SectionTitle> Note</SectionTitle>
               <Paragraph>In all methods, the
				date is the transaction date.</Paragraph>
            </Note>
            <RelatedTopics>
               <SectionTitle> Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/tf/integrations/400021" role="manual">Integration user groups</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="tfgld450.dtrt">
            <Header>
               <Title>Default Transaction Type</Title>
            </Header>
            <FuncDesc>The default transaction type for the integration
			 transactions.</FuncDesc>
            <SimpleSection>
               <Paragraph>By default, ERP Enterprise uses this transaction type and series to generate document numbers
				for the integration transactions.</Paragraph>
               <Paragraph>In the <GUIRef href="/baanerp/tf/gld/tfgld4573m000" role="session">Mapping Scheme (tfgld4573m000)</GUIRef> session, newly entered integration document types are
				only inserted automatically on the <GUIRef href="" role="manual">Document Numbering and Compression</GUIRef> tab if a default transaction type and series are
				available.</Paragraph>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="tfgld450.dtts">
            <Header>
               <Title>Default Transaction Type Series</Title>
            </Header>
            <FuncDesc>The default series for the integration transactions.</FuncDesc>
            <SimpleSection>
               <Paragraph>By default, ERP Enterprise uses this transaction type and series to generate document numbers
				for the integration transactions.</Paragraph>
               <Paragraph>In the <GUIRef href="/baanerp/tf/gld/tfgld4573m000" role="session">Mapping Scheme (tfgld4573m000)</GUIRef> session, newly entered integration document types are
				only inserted automatically on the <GUIRef href="" role="manual">Document Numbering and Compression</GUIRef> tab if a default transaction type and series are
				available.</Paragraph>
            </SimpleSection>
         </FieldHelp>
      </FieldGroup>
      <FieldGroup>
         <Title> Options</Title>
         <FieldHelp ID="tfgld450.dlep">
            <Header>
               <Title>Delete Logged Elements during Posting</Title>
            </Header>
            <FuncDesc> If this check box is selected, ERP Enterprise automatically
			 deletes the logged <Link href="/baanerp/tf/glossary/glossary#000016" role="glossary">mapping elements</Link> from the Logged Elements (tfgld 481)
			 table when the integration transactions are posted.</FuncDesc>
            <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/tf/P000003_logged_elements" role="manual">Logged elements</Link>.</Paragraph>
            </SimpleSection>
            <SimpleSection>
               <SectionTitle> Warning</SectionTitle>
               <Paragraph>Deleting logged mapping elements can make it impossible to
				create correction transactions. Especially if you wish to archive the mapping
				elements, it is recommended that you clear this check box and use the <GUIRef href="/baanerp/tf/gld/tfgld4283m000" role="session">Archive / Delete Integration Elements and Integration Transactions (tfgld4283m000)</GUIRef> session instead.</Paragraph>
            </SimpleSection>
         </FieldHelp>
         <FieldHelp ID="tfgld450.clha">
            <Header>
               <Title>Closed Period Handling</Title>
            </Header>
            <FuncDesc>The default action ERP Enterprise performs if you create an integration
			 transaction with a transaction date in a period that is already closed.</FuncDesc>
            <SimpleSection>
               <List>
                  <ListIntro> If this check box is cleared,, you cannot post
				  integration transactions to financial periods that:</ListIntro>
                  <ListItem>Have the <GUIRef href="/baanerp/tf/domains/gld.sper#closed" role="option">Closed</GUIRef> status.</ListItem>
                  <ListItem>Do not correspond with the transaction date.</ListItem>
               </List>
            </SimpleSection>
            <RelatedTopics>
               <SectionTitle> Related topics</SectionTitle>
               <RelTopic>
                  <Link href="/baanerp/tf/integrations/400018" role="manual">Period handling for integration transactions</Link>
               </RelTopic>
            </RelatedTopics>
         </FieldHelp>
         <FieldHelp ID="tfgld450.pech">
            <Header>
               <Title>Check Period Status on</Title>
            </Header>
            <FuncDesc>The period type on which you want to base the closed period
			 handling for integration transactions.</FuncDesc>
            <SimpleSection>
               <Paragraph> ERP Enterprise checks the status of the periods of this period type to detect whether the
				period is <GUIRef href="/baanerp/tf/domains/gld.sper#open" role="option">Open</GUIRef>.</Paragraph>
               <Paragraph>It is usually correct to check the <GUIRef href="/baanerp/tf/domains/gld.pech#int" role="option">INT</GUIRef> period. In exceptional situations, you can select the other period types.</Paragraph>
            </SimpleSection>
         </FieldHelp>
      </FieldGroup>
      <FieldGroup>
         <Title> Mapping Scheme Parameters</Title>
         <FieldHelp ID="gld450.acsq">
            <Header>
               <Title>Active Sequence Number</Title>
            </Header>
            <FuncDesc>...</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="gld450.asei">
            <Header>
               <Title>Active Sequence for Elements by IDT</Title>
            </Header>
            <FuncDesc>...</FuncDesc>
         </FieldHelp>
         <FieldHelp ID="gld450.asei">
            <Header>
               <Title>Update Element by IDT</Title>
            </Header>
            <FuncDesc> If this check box is selected, ERP Enterprise will rebuild the
			 Integration Elements (tfgld493) table the next time the mapping scheme is
			 activated.</FuncDesc>
            <SimpleSection>
               <Paragraph>To select this option, on the <Link href="/baanerp/tc/glossary/glossary#specific" role="glossary">appropriate</Link> menu, click <GUIRef href="/baanerp/tf/gld/tfgld4150s000#update.element.by.idt" role="command">Reset "Update Element by IDT" field</GUIRef>.</Paragraph>
            </SimpleSection>
         </FieldHelp>
      </FieldGroup>
   </Fields>
   <FormCommands>
      <CommandHelp ID="initialize.descriptions">
         <Header>
            <Title>Initialize Descriptions</Title>
         </Header>
         <FuncDesc>Initializes the descriptions of the business objects,
		  integration document types, and business object attributes, in the installed
		  languages.</FuncDesc>
         <SimpleSection>
            <Paragraph> For more information, refer to <Link href="/baanerp/tf/integrations/400003" role="manual">Mapping scheme prerequisites</Link>.</Paragraph>
         </SimpleSection>
      </CommandHelp>
      <CommandHelp ID="update.element.by.idt">
         <Header>
            <Title>Reset "Update Element by IDT" field</Title>
         </Header>
         <FuncDesc>Rebuilds the Integration Elements (tfgld493) table the next
		  time the mapping scheme is activated.</FuncDesc>
         <SimpleSection>
            <Paragraph>Choosing this command selects the <GUIRef href="/baanerp/tf/gld/tfgld4150s000#tfgld450.upei" role="manual">Update Element by IDT</GUIRef> check box.</Paragraph>
         </SimpleSection>
      </CommandHelp>
   </FormCommands>
</Session>