<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tf/integrations/400023" xml:lang="en">
   <Header>
      <Title>Integration mapping scheme features</Title>
      <Keyword type="header" order="d1e1607559">
         <Level1>Integration mapping scheme</Level1>
         <Level2>features</Level2>
      </Keyword>
   </Header>
   <GeneralSection ID="integration.user.group">
      <Paragraph>This topic describes the main features of the LN integration mapping
		scheme.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Flexibility and consistency</SectionTitle>
      <List>
         <ListIntro>The following features ensure the flexibility and consistency
		  of the mapping scheme:</ListIntro>
         <ListItem>A large number of the attributes of logistic transactions are
		  available for the mapping, for example, the business partner, the item group,
		  the item, the warehouse, and the sales office.</ListItem>
         <ListItem>The same transaction attributes are available for the ledger
		  account mapping and the dimension mapping.</ListItem>
         <ListItem>You can define the ledger mapping and dimension mapping of the
		  element groups on decreasing priority levels. If LN cannot map a
		  transaction based on the mapping with priority one, LN uses the mapping of
		  priority two, and so on.</ListItem>
         <ListItem>For each type of integration transaction, you define the
		  mapping for the debit side and for the credit side in the same way.</ListItem>
         <ListItem>Before the integration mapping scheme can become effective, LN checks the scheme’s
		  consistency. You can only make a mapping scheme version active if no blocking
		  errors occur.</ListItem>
         <ListItem>New types of integration transactions can relatively easy be
		  added to the mapping scheme. In this way, the mapping scheme is open to
		  extensions of the standard LN software, customizations, and third-party
		  applications.</ListItem>
      </List>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Reconciliation support</SectionTitle>
      <Paragraph>The reconciliation process matches the financial transactions to
		the related logistic transaction data to check whether the financial postings
		are correct and complete and to correct any detected differences. The way in
		which the mapping scheme is set up also partly determines the extent to which
		reconciliation is possible.</Paragraph>
      <List>
         <ListIntro>The following features of the mapping scheme support extensive
		  reconciliation:</ListIntro>
         <ListItem>Consistent mapping of debit and credit transactions on a ledger
		  account.</ListItem>
         <ListItem>Consistent use of the currency exchange rate type for the
		  related debit and credit transactions on a ledger account.</ListItem>
         <ListItem>Separation of currency results from the actual integration
		  transactions</ListItem>
         <ListItem>Improved handling of the rounding of quantities and the
		  conversion of units.</ListItem>
         <ListItem>Improved handling of amount rounding.</ListItem>
         <ListItem>Preservation of the link between a financial transaction and
		  the originating logistic transaction</ListItem>
      </List>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Version control</SectionTitle>
      <Paragraph>LN performs version control of the mapping schemes. Multiple mapping scheme
		versions can exist simultaneously, however, only one integration mapping scheme
		version at a time is the active version used to map the integration
		transactions.</Paragraph>
      <Paragraph>You cannot make changes to the active mapping scheme version.
		You can manually map individual backdated transactions according to a mapping
		scheme version that was previously active. For example, you can map backdated
		transactions according to the mapping scheme version that was effective at the
		transaction time.</Paragraph>
      <Paragraph>If the mapping requirements in your company change, you can
		create a new version of the mapping scheme in advance and make the changes
		without affecting the current integration transactions.</Paragraph>
      <List>
         <ListIntro>The following components of an integration mapping scheme
		  uniquely apply to a single mapping scheme code/version combination:</ListIntro>
         <ListItem>Element groups by integration document type</ListItem>
         <ListItem>Mapping elements by element group</ListItem>
         <ListItem>Ledger mapping and dimension mapping of the elements</ListItem>
         <ListItem>Document numbering and compression options</ListItem>
      </List>
      <Paragraph>LN can
		print a comparison report of the differences between two mapping scheme
		versions.</Paragraph>
      <Paragraph>A revision text is attached to each mapping scheme version,
		which you can use to indicate the reason for the new version. If you make a new
		mapping scheme version active, previous versions are maintained.</Paragraph>
      <Paragraph>The mapping scheme version is part of the integration
		transaction logging data, so that you can always check why a specific
		integration transaction was posted in a particular way.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Open for extensions</SectionTitle>
      <Paragraph>The integration mapping scheme is open, which means that new
		types of integration transactions generated by future extensions of <Link href="/baanerp/tf/glossary/glossary#000451" role="glossary">Operations Management</Link> and integrated third-party
		applications can easily be added to the integration mapping scheme, without the
		need for data-model changes.</Paragraph>
      <Paragraph>For this purpose, instead of user-defined codes, generic and
		unique codes are generated for the various components of the integration
		mapping scheme, based on predefined internal codes. For example, integration
		document types have codes such as 10001024 and 10072089, and mapping elements
		have codes such as 014505000000 and 014505495600. As a result, in various LN installations, the
		same integration document types and mapping elements have the same generated
		codes.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Mapping scheme components</SectionTitle>
      <Paragraph>The mapping scheme consists of the following components:</Paragraph>
      <List>
         <ListItemHead>
            <Link href="/baanerp/tf/glossary/glossary#000450" role="glossary">Integration document types</Link>
         </ListItemHead>
         <ListItem>Represent the various types of integration transactions</ListItem>
         <ListItemHead>
            <Link href="/baanerp/tf/glossary/glossary#000016" role="glossary">Mapping elements</Link>
         </ListItemHead>
         <ListItem>Logistic transaction details, such as the item, the project,
		  and the warehouse, that you can use to distinguish similar integration
		  transactions</ListItem>
         <ListItemHead>
            <Link href="/baanerp/tf/glossary/glossary#000455" role="glossary">Element groups</Link>
         </ListItemHead>
         <ListItem>A method to group mapping elements</ListItem>
      </List>
      <ProcedureList>
         <ListIntro>The basic procedure to set up the integration mapping scheme
		  consists of the following steps:</ListIntro>
         <ListItem>Add integration document types to the mapping scheme.</ListItem>
         <ListItem>Create element groups and link element groups to the
		  integration document types.</ListItem>
         <ListItem>Link mapping elements to the element groups.</ListItem>
         <ListItem>Define the ledger account mapping and/or dimension mapping for
		  the mapping elements.</ListItem>
      </ProcedureList>
   </GeneralSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/tf/integrations/400001" role="manual">Financial integrations - concepts and components</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/tf/integrations/400002" role="manual">To set up an integration mapping scheme</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>