<?xml version="1.0" encoding="utf-8"?>
<ManualTopic ID="/baanerp/tf/onlinemanual/cus200" xml:lang="en">
   <Header>
      <Title>Procedure</Title>
      <Keyword type="header" order="d1e1967994">
         <Level1>Procedure</Level1>
      </Keyword>
   </Header>
   <AimSection>
      <Paragraph/>
   </AimSection>
   <GeneralSection>
      <SectionTitle>Introduction</SectionTitle>
      <Paragraph>Before you can actually import integration transactions into
		Financials from an external source, you must first initialize a series of
		master data, and extend the mapping scheme with the mapping setup for the
		integration document types that are used in the external
		integration.</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Master data</SectionTitle>
      <Paragraph>The integration mapping in ERP LN 6.1 Financials differs from
		the integration mapping in previous ERP LN versions in many aspects. A main
		difference is that in ERP LN 6.1, integration mapping makes use of a
		meta-modeled data model. Among other things, this means that database fields
		neither directly refer to concrete objects, such as purchase order, service
		order, and so on, nor to concrete elements, such as business partner, cost
		component, item, and so on. Instead, a meta model defines which business object
		and which element are referred to for a specific integration transaction (table
		tfgld482) or logged element (table tfgld481).</Paragraph>
      <Paragraph>These meta-modeled master data have to be initialized for use in
		the mapping scheme by an initialization script. For more information, refer to
		Chapter 3, "Master Data Setup."</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Mapping scheme</SectionTitle>
      <Paragraph>After initialization of the external master data, create a new
		mapping scheme version (by copying an existing mapping scheme). This new
		mapping scheme version must be extended with the mapping setup for the external
		master data, namely, the new external integration document types. For the
		procedure, refer to Chapter 4. "Mapping Scheme Setup."</Paragraph>
   </GeneralSection>
   <GeneralSection>
      <SectionTitle>Integration transactions</SectionTitle>
      <Paragraph>After the new mapping scheme versions has been activated, the
		system is fit to receive the new external integration transactions.</Paragraph>
      <Paragraph>One of the most obvious methods to import external transactions
		into the Financials integration transactions tables, is to make use of an
		Exchange scheme, as has been done for previous ERP LN versions.</Paragraph>
      <Paragraph>Compared to previous ERP LN versions, in some respects different
		data has to be provided (among others, the business object and elements already
		mentioned earlier), and it is mandatory to log more data. For details, refer to
		Chapter 5, "External Integration Transactions."</Paragraph>
   </GeneralSection>
</ManualTopic>