<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tf/integrations/400001" xml:lang="en">
   <Header>
      <Title>Financial integrations - concepts and components</Title>
      <Keyword type="header" order="d1e1599808">
         <Level1>Integration mapping scheme</Level1>
         <Level2>concepts and components</Level2>
      </Keyword>
      <Keyword type="header" order="d1e1599813">
         <Level1>Mapping scheme</Level1>
         <Level2>concepts and components</Level2>
      </Keyword>
   </Header>
   <GeneralSection ID="business.object">
      <SectionTitle>Business object</SectionTitle>
      <Paragraph>In the context of financial integration transaction processing,
		a business object is a logistic entity or event such as an item, a purchase
		order, a business partner, or a warehouse issue.</Paragraph>
      <Paragraph>The integration document types supplied by LN each have the
		corresponding business object attached to them. For example, the integration
		document types for the various <GUIRef href="/baanerp/td/domains/sls.otyp#order" role="option">Sales Order</GUIRef> transactions have the <GUIRef href="/baanerp/td/domains/sls.otyp#order" role="option">Sales Order</GUIRef> business object linked to them.</Paragraph>
      <GeneralSection ID="business.object.attribute">
         <SectionTitle>Business object attribute</SectionTitle>
         <Paragraph>Each business object has various attributes, such as item,
		  warehouse, and department. These attributes are characteristics of the business
		  object that can be used to map the integration transaction to specific ledger
		  accounts and dimensions. For example, the <GUIRef href="/baanerp/td/domains/sls.otyp#order" role="option">Sales Order</GUIRef> business object has the <GUIRef href="/baanerp/tf/domains/gld.inop#saof" role="option">Sales Office</GUIRef> attribute and the <GUIRef href="/baanerp/tf/domains/gld.inop#orty" role="option">Sales Order Type</GUIRef> attribute, among others.</Paragraph>
      </GeneralSection>
      <GeneralSection ID="business.object.ID">
         <SectionTitle>Business object ID</SectionTitle>
         <Paragraph>The business object ID is the unique code that identifies a
		  specific business object. For example, the business object ID of a <GUIRef href="/baanerp/td/domains/sls.otyp#order" role="option">Sales Order</GUIRef> business object is the sales order number.</Paragraph>
      </GeneralSection>
   </GeneralSection>
   <GeneralSection ID="integration.document.type">
      <SectionTitle>Integration document type</SectionTitle>
      <Paragraph>An integration document type represents an <Link href="/baanerp/tf/glossary/glossary#000348" role="glossary">integration transaction</Link> type in <GUIRef href="/baanerp/tf" role="package">Financials</GUIRef> for the mapping and posting of the
		integration transactions and for the reconciliation process.</Paragraph>
      <Paragraph>The non-financial LN packages are collectively referred to as Operations
		Management. In Operations Management, each integration transaction is
		represented by its combination of operational transaction origin and financial
		transaction (in technical terms, the <Code>tror/fitr</Code> combination). For example, <GUIRef href="" role="manual" Update="No">Sales Order/Issue</GUIRef>.</Paragraph>
      <Paragraph>In the <GUIRef href="/baanerp/tc/fin" role="module">Finance/Logistics</GUIRef> module of <GUIRef href="/baanerp/tc" role="package">Common</GUIRef>, the transaction
		origin/financial transaction combinations are translated to integration
		document types. For example, the <GUIRef href="" role="manual" Update="No">Sales Order/Issue</GUIRef> transaction is translated to the <GUIRef href="" role="manual" Update="No">10002052</GUIRef> integration document type with the description <GUIRef href="" role="manual" Update="No">Sales Order/Issue</GUIRef>. LN provides predefined integration document types for all the integration
		transactions that can occur.</Paragraph>
      <List>
         <ListIntro>Integration document types are required:</ListIntro>
         <ListItem>To map integration transactions.</ListItem>
         <ListItem>To log the reconciliation data of a transaction.</ListItem>
      </List>
      <Paragraph>A number of predefined integration document types are only used
		to log the reconciliation data, for example, the <GUIRef href="/baanerp/tf/domains/cmg.tcsh#cdif" role="option">Currency Difference</GUIRef> integration document types. You cannot map these
		integration document types and the <GUIRef href="/baanerp/tf/gld/tfgld4557m000#tfgld457.maal" role="manual">Mapping Allowed</GUIRef> check box is cleared in the <GUIRef href="/baanerp/tf/gld/tfgld4557m000" role="session">Integration Document Types (tfgld4557m000)</GUIRef> session.</Paragraph>
      <Paragraph>For a list of the integration document types, refer to <Link href="/baanerp/tf/integrations/400009" role="manual">Integration document types</Link>. For each
		Integration document type, the mapping is given as defined in the demo
		companies that are delivered with the LN application.</Paragraph>
   </GeneralSection>
   <GeneralSection ID="mapping.element">
      <SectionTitle>Mapping element</SectionTitle>
      <Paragraph>A mapping element is a characteristic of a logistic transaction
		that you can map to a ledger account or dimension. Some examples of the mapping
		elements of a warehouse receipt transaction are: <GUIRef href="/baanerp/tf/domains/gld.inop#item" role="option">Item</GUIRef>, <GUIRef href="/baanerp/tf/domains/gld.inop#citg" role="option">Item Group</GUIRef>, <GUIRef href="/baanerp/tf/domains/gld.inop#cwar" role="option">Warehouse</GUIRef>, and <GUIRef href="/baanerp/tf/domains/gld.inop#cmnf" role="option">Manufacturer</GUIRef>. You can map specific values, ranges, or the
		full range of a mapping element to specific ledger accounts and dimensions.</Paragraph>
      <Paragraph>A mapping element consists of the combination of a business
		object and a business object attribute. For example, the mapping element item
		group/item represents the business object attribute item group of the business
		object item.</Paragraph>
      <Paragraph>LN supplies
		a complete list (about 1800) of the mapping elements that correspond to the
		business object attributes. For each integration document type, you can select
		the mapping elements from the attributes of its related business objects. You
		cannot add, change, or delete mapping elements.</Paragraph>
   </GeneralSection>
   <GeneralSection ID="parent.element">
      <SectionTitle>Parent element</SectionTitle>
      <Paragraph>A mapping element consists of the combination of a business
		object and a business object attribute. <Link href="/baanerp/tf/glossary/glossary#000453" role="glossary">Business object attributes</Link> can themselves be business objects. The business objects of attributes appear
		as child business objects, with a higher level number. The attributes of child
		business objects are also available as mapping elements for the integration
		document types.</Paragraph>
      <Paragraph>For example, a <GUIRef href="/baanerp/td/domains/sls.otyp#order" role="option">Sales Order</GUIRef> business object has the <GUIRef href="/baanerp/tf/domains/gld.inop#item" role="option">Item</GUIRef> attribute. <GUIRef href="/baanerp/tf/domains/gld.inop#item" role="option">Item</GUIRef> is also a business object which has the <GUIRef href="/baanerp/tf/domains/gld.inop#citg" role="option">Item Group</GUIRef> and the <GUIRef href="/baanerp/tf/domains/gld.inop#cmnf" role="option">Manufacturer</GUIRef> attributes, among others. As a result, you
		can select the manufacturer of the item of the sales order as a mapping element
		for <GUIRef href="/baanerp/td/domains/sls.otyp#order" role="option">Sales Order</GUIRef> integration document types.</Paragraph>
      <Paragraph>If a mapping element has parent attributes, LN displays the parent
		attributes and their levels in the various mapping scheme related sessions.</Paragraph>
   </GeneralSection>
   <GeneralSection ID="sort.element">
      <SectionTitle>Sort element</SectionTitle>
      <Paragraph>The sort element is a mapping element on which the integration
		transactions can be sorted. You can use the sort element to group the
		integration transactions that belong to different integration document types.</Paragraph>
      <Paragraph>For example, the integration transactions for a project or for a
		service order belong to various integration document types. If you assign <GUIRef href="/baanerp/tf/domains/gld.intr#pcs" role="option">PCS Project</GUIRef> or <GUIRef href="/baanerp/tf/domains/gld.inop#sety" role="option">Service Type</GUIRef> as the sort element to those integration document types, you can
		group the integration transactions by project, or by service order.</Paragraph>
      <Paragraph>To every integration document type, you can assign one of the
		available mapping elements as the sort element in the <GUIRef href="/baanerp/tf/gld/tfgld4557m000" role="session">Integration Document Types (tfgld4557m000)</GUIRef> session. The sort element can be an
		element that you do not actually use for the mapping. In the <GUIRef href="/baanerp/tf/gld/tfgld4582m000" role="session">Integration Transactions (tfgld4582m000)</GUIRef> session, you can display the integration
		transactions in the order of the values of the sort element.</Paragraph>
   </GeneralSection>
   <GeneralSection ID="element.group">
      <SectionTitle>Element group</SectionTitle>
      <Paragraph>An element group is a selection of <Link href="/baanerp/tf/glossary/glossary#000016" role="glossary">mapping element</Link> and in this way represents a mapping. To map the integration
		transactions, or integration document types, you must link one or more element
		groups to the integration document types. An element group must contain at
		least one mapping element and can contain up to 15 mapping elements.</Paragraph>
      <Paragraph>Before you select the elements of an element group, it is
		recommended that you link the element group to an integration document type.
		For the selection, LN only
		displays the mapping elements that apply to the integration document type.</Paragraph>
      <Paragraph>You can link an element group to multiple integration document
		types, provided that the mapping elements of the group are available for all
		the integration document types. If you do this, the ledger account mapping or
		the dimension mapping of those integration document types will be exactly the
		same.</Paragraph>
      <Paragraph>You can use the <GUIRef href="/baanerp/tf/gld/tfgld4466m000" role="session">Print Where Used Element Groups (tfgld4466m000)</GUIRef> session to generate a report of a range
		of element groups and the integration document types to which they are linked.
		You can use this report to see which integration document types are affected if
		you change the mapping for an element group.</Paragraph>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>The element group, not the integration document type, defines
		  the ledger account mapping and the dimension mapping. If you change the mapping
		  for one integration document type, you change the mapping of all the
		  integration document types that use the element group.</Paragraph>
      </Note>
   </GeneralSection>
   <GeneralSection ID="mapping.priority">
      <SectionTitle>Mapping priority</SectionTitle>
      <Paragraph>You can define the ledger mapping and dimension mapping of the
		element groups on decreasing priority levels, where level one represents the
		highest priority. If LN cannot map the transaction based on the mapping with priority one, LN uses the mapping with
		priority two, and so on. If the transaction cannot be mapped, LN reports an error.</Paragraph>
      <Paragraph>If you want to ensure that each integration transaction can be
		mapped and posted, it is recommended that for the lowest priority, you map the
		full range of each mapping element to a default ledger account or dimension as
		applicable.</Paragraph>
   </GeneralSection>
   <GeneralSection ID="mapping.sequence">
      <SectionTitle>Mapping sequence</SectionTitle>
      <Paragraph>Within every mapping priority every mapping has a mapping
		sequence. The mapping sequence is the order in which LN searches the values of
		the mapping elements to find the mapping of an integration transaction. As you
		define the mapping for various combinations of the elements of an element
		group, LN generates a
		sequence number for every mapping. For performance reasons it is recommended
		that the most specific mapping has mapping sequence number one.</Paragraph>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <List>
            <ListIntro>The following rules apply to the mapping priority and the
			 mapping sequence:</ListIntro>
            <ListItem>For different priorities, the mapped values and value ranges
			 of the mapping elements can overlap.</ListItem>
            <ListItem>For the mapping sequences within a mapping priority, the
			 mapped values and values ranges of the mapping elements cannot overlap.</ListItem>
         </List>
      </Note>
   </GeneralSection>
   <GeneralSection ID="default.account">
      <SectionTitle>Default account</SectionTitle>
      <Paragraph>If you do not wish to define a detailed mapping to various
		ledger accounts for specific integration transactions, you can map the
		corresponding integration document type to a default account. All the
		transactions of the integration document type for which LN cannot determine an
		account based on the mapping scheme details, are posted to the default account.</Paragraph>
      <Paragraph>The mapping of an integration document type to a default account
		is direct, without the need for element groups and mapping elements. No
		distinction is made on any of the transaction details.</Paragraph>
      <List>
         <ListIntro>Default accounts can be used in two ways:</ListIntro>
         <ListItem>Instead of a detailed mapping to various ledger accounts. All
		  the transactions are posted to the same account. For example, all warehouse
		  receipts are posted to the Inventory ledger account, without any distinction.</ListItem>
         <ListItem>In addition to a detailed mapping. If a transaction cannot be
		  mapped based on the detailed mapping scheme, it is posted to the default
		  account.</ListItem>
      </List>
      <Paragraph>You cannot set up the dimension mapping for the default ledger
		accounts in this way. If dimension mapping is required for an integration
		document type, you must define the dimension mapping in the regular way by
		means of an element group and mapping elements.</Paragraph>
   </GeneralSection>
   <GeneralSection ID="gl.code">
      <SectionTitle>GL code</SectionTitle>
      <Paragraph>A GL code represents a ledger account and the corresponding
		dimensions. GL codes are used to represent ledger accounts to users who are not
		familiar with the structure of the chart of accounts. For some logistic
		transactions, you can use a GL code to indicate the ledger account and the
		dimensions to which the transaction must be posted.</Paragraph>
      <Paragraph>You can define GL codes in the <GUIRef href="/baanerp/tf/gld/tfgld4575m000" role="session">GL Codes (tfgld4575m000)</GUIRef> session. Every GL code refers to one ledger account.
		The ledger account must be an integration account. If mandatory or optional
		dimensions are linked to the ledger account, these are included in the GL code
		definition.</Paragraph>
      <Paragraph>Before you can use the GL code, in the <GUIRef href="/baanerp/tf/gld/tfgld4575m000" role="session">GL Codes (tfgld4575m000)</GUIRef> session you must select the <GUIRef href="/baanerp/tf/gld/tfgld4575m000#tfgld475.actv" role="manual">Active</GUIRef> check box. To block the GL code for use, you
		can clear the <GUIRef href="/baanerp/tf/gld/tfgld4575m000#tfgld475.actv" role="manual">Active</GUIRef> check box. If you block a GL code, new lines
		of existing orders are still mapped using the GL code but you cannot select the
		GL code for newly created orders.</Paragraph>
      <Paragraph>As soon as any integration transactions are mapped using the GL
		code, you cannot change the ledger account or the dimensions of the GL code, or
		delete the GL code.</Paragraph>
      <Paragraph>If you enter a GL code for the transaction, the integration
		transactions are not included in the mapping process but mapped directly to the
		ledger account and dimensions of the GL code. The values of the mapping
		elements of such transactions do not have any effect on the mapping. In the <GUIRef href="/baanerp/tf/gld/tfgld4582m000" role="session">Integration Transactions (tfgld4582m000)</GUIRef> session, LN indicates that a GL
		code was used to map the transaction, and displays the GL code.</Paragraph>
      <List>
         <ListIntro>Mapping through GL codes can be used for the following
		  transactions:</ListIntro>
         <ListItem>The credit posting of manual sales invoices created in the <GUIRef href="/baanerp/ci/sli/cisli2520m000" role="session">Manual Sales Invoice Data (cisli2520m000)</GUIRef>.</ListItem>
         <ListItem>The debit or credit posting of any type of integration
		  transaction that you want to remap in the <GUIRef href="/baanerp/tf/gld/tfgld4282m100" role="session">Remap Posted Integration Transactions (tfgld4282m100)</GUIRef> session.</ListItem>
         <ListItem> 
            <List>
               <ListIntro>The debit postings of:</ListIntro>
               <ListItem>
                  <GUIRef href="" role="manual">Purchase Order / General Costs</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="" role="manual">Purchase Order / General Costs Variance</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="" role="manual">Purchase Order / Costs to be Specified</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="" role="manual">Purchase Order / Costs to be Specified Variance</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="" role="manual">Purchase Schedule / General Costs</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="" role="manual">Purchase Schedule / General Costs Variance</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="" role="manual">Purchase Schedule / Costs to be Specified</GUIRef>
               </ListItem>
               <ListItem>
                  <GUIRef href="" role="manual">Purchase Schedule / Costs to be Specified Variance</GUIRef>
               </ListItem>
            </List>
         </ListItem>
      </List>
   </GeneralSection>
   <GeneralSection ID="tr.typ.series">
      <SectionTitle>Transaction type and series</SectionTitle>
      <Paragraph>LN generates the document numbers for the integration transactions based on a
		transaction type and series. On the <GUIRef href="" role="manual">Document Numbering/Compression</GUIRef> tab in the <GUIRef href="/baanerp/tf/gld/tfgld4573m000" role="session">Mapping Scheme (tfgld4573m000)</GUIRef> session, you can define a transaction type and a
		series for each integration document type. If you use different transaction
		types and series, each type of integration transaction gets its own range of
		document numbers in the General Ledger.</Paragraph>
      <Paragraph>One exception to this rule exists: <GUIRef href="/baanerp/tf/fam" role="module">Fixed Assets</GUIRef> transactions use the transaction type entered in the <GUIRef href="/baanerp/tf/fam/tffam0100s000" role="session">FAM Parameter (tffam0100s000)</GUIRef> session.</Paragraph>
   </GeneralSection>
   <GeneralSection ID="compression">
      <SectionTitle>Compression</SectionTitle>
      <Paragraph>Integration transactions can be compressed before they are
		posted. For each integration document type, you can indicate whether the debit
		transactions and /or the credit transactions must be compressed.</Paragraph>
      <List>
         <ListIntro>Transactions can be compressed if the following transaction
		  details have the same value:</ListIntro>
         <ListItem>The source financial company.</ListItem>
         <ListItem>The destination financial company.</ListItem>
         <ListItem>The transaction type and series.</ListItem>
         <ListItem>The ledger account and dimensions.</ListItem>
         <ListItem>The transaction currency.</ListItem>
         <ListItem>The fiscal year and the financial period, the tax period, and
		  the reporting period.</ListItem>
         <ListItem>The integration document type and the <GUIRef href="" role="manual" Update="No">Debit/Credit</GUIRef> indicator.</ListItem>
         <ListItem>If related gain and loss transactions are generated, the same
		  compression criteria are used to compress these.</ListItem>
      </List>
      <Note>
         <SectionTitle>Note</SectionTitle>
         <Paragraph>Intergroup transactions are not compressed.</Paragraph>
      </Note>
   </GeneralSection>
   <GeneralSection ID="reconciliation.group">
      <SectionTitle>Reconciliation group</SectionTitle>
      <Paragraph>A reconciliation group is used to group related integration
		transactions for reconciliation purposes. Every integration document type
		belongs to a reconciliation group.</Paragraph>
      <Paragraph>For example, the <GUIRef href="" role="manual" Update="No">Purchase Order/Receipt</GUIRef> and the <GUIRef href="" role="manual" Update="No">Purchase Order/Price Variance</GUIRef> integration document types both belong to the same
		reconciliation group (reconciliation group <GUIRef href="" role="manual" Update="No">Invoice Accrual 3</GUIRef>).</Paragraph>
   </GeneralSection>
   <GeneralSection ID="integration.account">
      <SectionTitle>Integration account</SectionTitle>
      <Paragraph>To support full reconciliation possibilities, the integration
		transactions can only be posted to ledger accounts that are marked as
		Integration accounts in the <GUIRef href="/baanerp/tf/gld/tfgld0508m000" role="session">Chart of Accounts (tfgld0508m000)</GUIRef> session. If an account is marked as <GUIRef href="/baanerp/tf/gld/tfgld0508m000#tfgld008.inta" role="manual">Integration Account</GUIRef>, you cannot manually enter
		transactions on the account.</Paragraph>
      <Paragraph>As you cannot create manual transactions on the integration
		accounts to make corrections, the posting of the integration transactions is
		irreversible. You can only make corrections to the postings on the integration
		ledger accounts in the reconciliation sessions. You must make the corrections
		to other ledger accounts with the same parent as the integration ledger
		account. The result will then appear in the parent account.</Paragraph>
   </GeneralSection>
   <GeneralSection ID="mapping.scheme.status">
      <SectionTitle>The integration mapping scheme status</SectionTitle>
      <Paragraph>Two fields indicate a mapping scheme version status:</Paragraph>
      <List>
         <ListItemHead>The active indicator</ListItemHead>
         <ListItem>Every mapping scheme version has an <GUIRef href="/baanerp/tf/domains/acp.crst#active" role="option">Active</GUIRef> indicator which is either on or off. If a versions is <GUIRef href="/baanerp/tf/domains/acp.crst#active" role="option">Active</GUIRef>, LN uses that version to
		  map integration transactions. Before you can make a mapping scheme version
		  active, it must have been validated and it must not contain any blocking
		  errors. Only one integration mapping scheme version can be <GUIRef href="/baanerp/tf/domains/acp.crst#active" role="option">Active</GUIRef> at a time.</ListItem>
         <ListItemHead>The check status</ListItemHead>
         <ListItem>The check status indicates the stage reached in the mapping
		  scheme definition process. A mapping scheme version can have the following
		  check statuses: <List>
               <ListItemHead>
                  <GUIRef href="/baanerp/tf/domains/gld.chks#not.checked" role="option">Not Checked</GUIRef>
               </ListItemHead>
               <ListItem>The version has not been checked for consistency. The
				version cannot be made <GUIRef href="/baanerp/tf/domains/acp.crst#active" role="option">Active</GUIRef>.</ListItem>
               <ListItemHead>
                  <GUIRef href="/baanerp/tf/domains/gld.chks#incon.block" role="option">Inconsistent - Blocking</GUIRef>
               </ListItemHead>
               <ListItem>The version has been checked for consistency and blocking
				errors were found. The version cannot be made <GUIRef href="/baanerp/tf/domains/acp.crst#active" role="option">Active</GUIRef>.</ListItem>
               <ListItemHead>
                  <GUIRef href="/baanerp/tf/domains/gld.chks#incon.not.block" role="option">Inconsistent - Not Blocking</GUIRef>
               </ListItemHead>
               <ListItem>The version has been checked for consistency and no
				blocking errors were found. However, inconsistencies were found that resulted
				in warning messages. You can make the version <GUIRef href="/baanerp/tf/domains/acp.crst#active" role="option">Active</GUIRef> if you wish.</ListItem>
               <ListItemHead>
                  <GUIRef href="/baanerp/tf/domains/gld.chks#consistent" role="option">Consistent</GUIRef>
               </ListItemHead>
               <ListItem>The version has been checked for consistency and no errors
				were found. You can make the version <GUIRef href="/baanerp/tf/domains/acp.crst#active" role="option">Active</GUIRef>.</ListItem>
            </List>
         </ListItem>
      </List>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Other concepts</SectionTitle>
      <List>
         <ListIntro>Other mapping-scheme related concepts are:</ListIntro>
         <ListItem>
            <Link href="/baanerp/tf/integrations/400021" role="manual">Integration user groups</Link>
         </ListItem>
      </List>
   </GeneralSection>
   <RelatedTopics>
      <SectionTitle>Related topics</SectionTitle>
      <RelTopic>
         <Link href="/baanerp/tf/integrations/400002" role="manual">To set up an integration mapping scheme</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/tf/integrations/400009" role="manual">Integration document types</Link>
      </RelTopic>
      <RelTopic>
         <Link href="/baanerp/tf/integrations/400009" role="manual" Update="No">Integration transactions</Link>
      </RelTopic>
   </RelatedTopics>
</ManualTopic>