| # Procedure Before you can actually import integration transactions into Financials from an external source, you must first initialize a number of master data, and extend the mapping scheme with the mapping setup for the integration document types that are used in the external integration. Master data The integration mapping in LN Financials differs from the integration mapping in previous LN versions in many aspects. A major difference is that in LN, integration mapping makes use of a meta-modeled data model. Among other things, this means that database fields neither directly refer to specific objects, such as purchase order, service order, nor to specific elements, such as business partner, cost component, item. 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). This meta-modeled master data must be initialized for use in the mapping scheme by an initialization script. For more information, refer to Chapter 3, "Master Data Setup." Mapping scheme 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, that is, the new external integration document types. For the procedure, refer to Chapter 4. "Mapping Scheme Setup." Integration transactions After the new mapping scheme version has been activated, LN is ready to receive the new external integration transactions. 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 was done for previous LN versions. Compared to previous LN versions, in some respects different data must be provided (including the business object and elements), and it is mandatory to log more data. For details, refer to Chapter 5, "External Integration Transactions." |