You are on page 1of 47

SAP HANA Configuration Guide SAP LT Trigger-Based Data Replication

Using SAP LT (Landscape Transformation) Replication Server for SAP HANA

SAP HANA Appliance Software SPS 05

Target Audience Consultants Administrators Others

Public Document version 1.1 2012/11/29

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

Java is a registered trademark of Sun Microsystems, Inc. Copyright 2012 SAP AG. All rights reserved. JavaScript is a registered trademark of Sun Microsystems, Inc., used No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. in the United States and in other countries. under license for technology invented and implemented by Netscape.

Any Java Source Code delivered with this product is only to be used by SAPs Support Services and may not be modified or altered in any way. Documentation in the SAP Service Marketplace You can find this documentation at the following address:
http://service.sap.com/hana

A) SAP grants Customer a non-exclusive, non-transferrable, royaltyfree license to use the STLport.org C++ library (STLport) and its documentation without fee. B) By downloading, using, or copying STLport or any portion thereof Customer agrees to abide by the intellectual property laws, and to all of the terms and conditions of this Agreement. C) The Customer may distribute binaries compiled with STLport (whether original or modified) without any royalties or restrictions. D) Customer shall maintain the following copyright and permissions notices on STLport sources and its documentation unchanged: Copyright 2001 SAP AG E) The Customer may distribute original or modified STLport sources, provided that: o The conditions indicated in the above permissions notice are met; o The following copyright notices are retained when present, and conditions provided in accompanying permission notices are met: Coypright 1994 Hewlett-Packard Company Copyright 1996,97 Silicon Graphics Computer Systems Inc. Copyright 1997 Moscow Center for SPARC Technology. Copyright 1999,2000 Boris Fomitchev Copyright 2001 SAP AG Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Hewlett-Packard Company makes no representations about the suitability of this software for any purpose. It is provided as is without express or implied warranty. Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Silicon Graphics makes no representations about the suitability of this software for any purpose. It is provided as is without express or implied warranty. Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in

Terms for Included Open Source Software


This SAP software contains also the third party open source software products listed below. Please note that for these third party products the following special terms and conditions shall apply. 1. This software was developed using ANTLR. 2. gSOAP Part of the software embedded in this product is gSOAP software. Portions created by gSOAP are Copyright (C) 2001-2004 Robert A. van Engelen, Genivia inc. All Rights Reserved. THE SOFTWARE IN THIS PRODUCT WAS IN PART PROVIDED BY GENIVIA INC AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 3. SAP License Agreement for STLport SAP License Agreement for STLPort between SAP Aktiengesellschaft Systems, Applications, Products in Data Processing Neurottstrasse 16 69190 Walldorf, Germany (hereinafter: SAP) and you (hereinafter: Customer) a) Subject Matter of the Agreement

supporting documentation. Moscow Center for SPARC makes no representations about the suitability of this software for any purpose. It is provided as is without express or implied warranty. Boris Fomitchev makes no representations about the suitability of this software for any purpose. This material is provided "as is", with absolutely no warranty expressed or implied. Any use is at your own risk. Permission to use or copy this software for any purpose is hereby granted without fee, provided the above notices are retained on all copies. Permission to modify the code and to distribute modified code is granted, provided the above notices are retained, and a notice that the code was modified is included with the above copyright notice. Permission to use, copy, modify, distribute and sell this software and its documentation for any purposes is hereby granted without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation. SAP makes no representations about the suitability of this software for any purpose. It is provided with a limited warranty and liability as set forth in the License Agreement distributed with this copy. SAP offers this liability and warranty obligations only towards its customers and only referring to its modifications. b) Support and Maintenance SAP does not provide software maintenance for the STLport. Software maintenance of the STLport therefore shall be not included. All other services shall be charged according to the rates for services quoted in the SAP List of Prices and Conditions and shall be subject to a separate contract. c) Exclusion of warranty As the STLport is transferred to the Customer on a loan basis and free of charge, SAP cannot guarantee that the STLport is error-free, without material defects or suitable for a specific application under third-party rights. Technical data, sales brochures, advertising text and

quality descriptions produced by SAP do not indicate any assurance of particular attributes. d) Limited Liability A) Irrespective of the legal reasons, SAP shall only be liable for damage, including unauthorized operation, if this (i) can be compensated under the Product Liability Act or (ii) if caused due to gross negligence or intent by SAP or (iii) if based on the failure of a guaranteed attribute. B) If SAP is liable for gross negligence or intent caused by employees who are neither agents or managerial employees of SAP, the total liability for such damage and a maximum limit on the scope of any such damage shall depend on the extent to which its occurrence ought to have anticipated by SAP when concluding the contract, due to the circumstances known to it at that point in time representing a typical transfer of the software. C) In the case of Art. 4.2 above, SAP shall not be liable for indirect damage, consequential damage caused by a defect or lost profit. D) SAP and the Customer agree that the typical foreseeable extent of damage shall under no circumstances exceed EUR 5,000. E) The Customer shall take adequate measures for the protection of data and programs, in particular by making backup copies at the minimum intervals recommended by SAP. SAP shall not be liable for the loss of data and its recovery, notwithstanding the other limitations of the present Art. 4 if this loss could have been avoided by observing this obligation. F) The exclusion or the limitation of claims in accordance with the present Art. 4 includes claims against employees or agents of SAP. 4. Adobe Document Services Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and / or other countries. For information on Third Party software delivered with Adobe document services and Adobe LiveCycle Designer, see SAP Note 854621.

Typographic Conventions
Type Style Example Text Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation Emphasized words or phrases in body text, graphic titles, and table titles Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER.

Icons
Icon Meaning Caution Example Note Recommendation Syntax Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Example text

EXAMPLE TEXT

Example text

Example text

<Example text>

EXAMPLE TEXT

Advanced Replication Settings

Contents
1 Getting Started............................................................................7
1.1 1.2 1.3 Global Definitions ........................................................................ 7 Important SAP Notes ................................................................... 9 History of Changes ...................................................................... 9

2 Introduction...............................................................................10 3 Configuration Overview ...........................................................11


3.1 3.2 3.3 4.1 4.2 4.3
4.3.1 4.3.2
4.3.2.1 4.3.2.2 4.3.2.3

Configuration List ...................................................................... 11 Configuration Details and Selection ........................................ 12 Remote Maintenance ................................................................. 13 Replication Settings for Source Tables ................................... 16 Add Source Table ....................................................................... 18 Managing Files ...........................................................................19
Export to File ................................................................................. 19 Import from File ............................................................................. 20
Load All, Discard Original Settings ....................................................................... 20 Load All, Update Original Settings ........................................................................ 21 Load Selected Settings ......................................................................................... 23

4 Replication Settings Overview ................................................16

4.4
4.4.1 4.4.2

Tables in Target System ............................................................ 27


Update Replication Status ............................................................ 28 Add Tables from Target System .................................................. 28

5 Customizing the Replication Settings .....................................29


5.1 5.2
5.2.1 5.2.2
5.2.2.1 5.2.2.2 5.2.2.3

Overview .....................................................................................29 Source Table Management........................................................ 29


Active Source Table ...................................................................... 30 Source Table Overview ................................................................. 30
Displaying Tables in the Tables for Replication Settings...................................... 31 Adding and Deleting Tables .................................................................................. 32 Copying Settings ................................................................................................... 32

5.3
5.3.1 5.3.2 5.3.3

Table Settings .............................................................................33


Table IUUC_REPL_TABSTG ......................................................... 34 Table IUUC_REPL_TAB_DV ......................................................... 37 Table IUUC_ASS_RUL_MAP ......................................................... 40
Includes, and Lines of Code ................................................................................. 40

5.3.3.1

5.3.4 5.3.5

Table IUUC_SPC_PROCOPT ........................................................ 46 Table IUUC_PERF_OPTION .......................................................... 46

November 2012

1 Getting Started 1.1 Global Definitions

1 Getting Started
This guide does not replace the daily operations handbook that we recommend customers to create for their specific production operations. Target Groups 1. Technical Consultants 2. System Administrators 3. Solution Consultants 4. Business Process Owner 5. Support Specialist

1.1 Global Definitions


The following table contains key terms related to the SAP LT Replication Server: Term Advanced Replication Settings Definition A transaction that runs on the SAP LT Replication Server that you can use to specify advanced replication settings. For example, you can: Modify target table structures Specify performance optimization settings Define transformation rules The definition of the parameters that the SAP LT Replication Server uses to replicate data from one or more source systems to one or more target systems. The configuration specifies the source system, the target system, and the relevant connections. An application that runs on the SAP LT Replication Server that you use to specify configuration information (such as the source and target systems, and relevant connections) so that data can be replicated. You can also use it to monitor the replication status. A piece of code that updates a database automatically in response to a certain event. A job that is used for the data transfer process in the SAP LT Replication Server. A step within the trigger-based replication process that loads data from the source system to target system. A job that is used for the initial load process in

Configuration

Configuration and Monitoring Dashboard

Database trigger Data transfer Job Initial load

Initial load Job

November 2012

Getting Started Global Definitions

the SAP LT Replication Server. Latency The length of time to replicate data (a table entry) from the source system to the target system. A table in the source system that records any changes to a table that is being replicated. This ensures that the SAP LT Replication Server can replicate these changes to the target system. A job that exists for each configuration that calls the initial load jobs and the data transfer jobs in the SAP LT Replication Server. The maximum time taken to replicate data (a table entry) from the source to target system. The median time taken to replicate data (a table entry) from the source to target system. The minimum time taken to replicate data (a table entry) from the source to target system. A technique for reading data from tables in the target system during the initial load process. A phase in the trigger-based replication process whereby only changes to the source database (recorded by databases triggers) are replicated to the target database, thereby facilitating realtime data replication. An SAP system that facilitates the replication of data from one or more source systems to one or more target systems. The source systems can be SAP or non-SAP systems. The set of tables in the SAP LT Replication Server that contain the replication settings for a specific configuration. A technique for replicating data where an initial load is first performed that loads data from the source to the target system, and a replication phase begins whereby only changes to the source database (recorded by databases triggers) are replicated to the target database, thereby facilitating data replication in real-time. A rule that you can specify in the Advanced Replication Settings transaction for source tables such that data is transformed during the replication process. The transformed data will then be present in the target table. For example, you can specify a rule to: Convert fields Fill empty fields Skip records

Logging table

Master job

Maximum latency Median latency Minimum latency Reading type Replication phase

SAP LT Replication Server

Tables for replication settings

Trigger-based replication

Transformation rules

November 2012

1 Getting Started 1.2 Important SAP Notes

1.2 Important SAP Notes


Important SAP Notes SAP Note Number Title Comment

1.3 History of Changes


The following table provides an overview of the most important changes in prior versions. Version 1.0 1.1 Important Changes First version of the guide Revised by information development

November 2012

Introduction History of Changes

2 Introduction
This guide describes the replication settings that are available for the SAP LT Replication Server. You access the Replication Settings UI by using transaction IUUC_REPL_CONTENT. The system landscape comprises a dedicated replication server (the SAP LT Replication Server connected to a source system and to the target HANA database (target system). A master control job that runs in the SAP LT Replication Server initiates all required processing steps. In particular, after adding a table to a configuration for replication, a logging table and database triggers must be set up in the source system in order to keep track of data changes for real-time replication. In the target HANA system, a new database table must be created for the data read from the source system. The data can then be transferred to the HANA system. The first step is an initial load that loads all data from the source system to a table in the target system. The table entries are first retrieved from the source table, and then processed in the SAP LT Replication Server before they are sent to the target HANA database. After the initial load is finished, a delta replay phase starts which continuously copies any recorded changes from the logging table to the target table such the data is replicated in real time. This approach has the following advantages: The impact on the source and target systems is minimized as most of the processing occurs in the dedicated SAP LT Replication Server. The replication settings are stored centrally, and can be edited from one central location in the SAP LT Replication Server. These replication settings specify which tables are to be transferred to the target system

The replication settings are stored in five tables in the SAP LT Replication Server. In the Replication Settings UI, you can all access all replication settings from one central transaction. For a configuration, the replication settings are stored in five different tables in the SAP LT Replication Server: Table IUUC_REPL_TABSTG Description Contains the settings that specify how changes of table structure from source to target system, for example the table name, different line type defined in the ABAP Dictionary You can change the structure of the table at field level without defining a new line type in the ABAP Dictionary in the sender system or in the SAP LT Replication Server. You can specify mapping rules that are executed during the replication process. You can apply Customizing settings for database triggers in order to record changes to the source table. Contains settings regarding the performance of the replication, for example you can define settings for the reading type and portion sizes.

IUUC_REPL_TAB_DV

IUUC_ASS_RUL_MAP IUUC_SPC_PROCOPT IUUC_PERF_OPTION

Table 1 Tables used for storing the replication settings for a configuration.

10

November 2012

3 Configuration Overview 3.1 Configuration List

3 Configuration Overview
When you execute transaction IUUC_REPL_CONTENT, the system displays an overview of all available configurations for the SAP LT Replication Server. You can view a list of all configurations as well as information about source and target systems. To display additional information about a configuration, choose the Display Details pushbutton. You can also specify replication settings for a configuration that exists in a remote system (a remote SAP LT Replication Server).

Figure 1 The initial screen of the Replication Settings screen.

3.1 Configuration List


In the initial screen, the system displays a summary of all the configurations that exist in the current SAP LT Replication Server, see Figure 2. In addition to the configuration name, you can view information about the source and target systems. In general, the schema name does not uniquely identify a configuration. For instance, a HANA database schema could be filled from different source systems. The name of the configuration and the target system would be the same, so the configurations could only be distinguished by their source system information. You can use the SAP LT Replication Server to replicate database tables from SAP and non-SAP sources into a HANA system. For non-SAP systems, the underlying database is accessed directly by SQL statements.

November 2012

11

Configuration Overview Configuration Details and Selection

Figure 2 A highlighted schema, and pushbuttons. The following table details the fields from the Available Schemas table: Field Schema Name Target Type Source Type Target System Source System Description The name of the target database schema Type of the target system Type of the source system (either an SAP system or a non-SAP system) This field contains a concatenation of the host and instance number for the target system This field contains a concatenation of the system ID, host number and instance number for the source system

3.2 Configuration Details and Selection

You can view detailed information for a schema, for example the mass transfer ID and the SAP release of the source system. To view this information, choose the Display Details pushbutton. The mass transfer ID is an identifier that is used to group the objects contained in a configuration. The tables that contain the replication settings have the mass transfer ID as a key field in addition to the source table name.

12

November 2012

3 Configuration Overview 3.3 Remote Maintenance

To specify the replication settings for a configuration, select the relevant configuration and choose the Select Schema pushbutton (the system displays a new screen for this purpose).

3.3 Remote Maintenance


In complex system landscapes, it might be necessary to use more than one SAP LT Replication Server, and each server has its own configurations. Instead of logging onto each of these systems in order to specify the replication settings, you can specify the settings remotely. You can specify an RFC connection, and read and write the replication settings to the relevant database tables in the remote SAP LT Replication Server. Note that the RFC user must have sufficient authorizations to run transaction IUUC_REPL_CONTENT in the remote server. To specify replication settings for a remote system, select the Change to Remote Replicator checkbox, and choose the appropriate RFC connection from the dropdown list. Note that you can create RFC connections in transaction SM59. The system updates the configuration list with the configurations from the remote system. When you have specified the relevant setting for the remote schemas, you can change back to the local system schemas by selecting the empty RFC connection from the end of the dropdown list.

Figure 3 Screen for selecting an RFC connection to a remote SAP LT Replication Server.

Figure 4 Select the checkbox to activate the input field, and choose the RFC connection from the dropdown list.

November 2012

13

Configuration Overview Remote Maintenance

Figure 5 The system displays a dialog box that informs you that the connection is established and operating correctly.

Figure 6 The schema list for a remote SAP LT Replication Server. The RFC connection field shows the name of the used connection as defined in transaction SM59.

14

November 2012

3 Configuration Overview 3.3 Remote Maintenance

Figure 7 To change back to local schemas, select the empty line from the dropdown list.

November 2012

15

Replication Settings Overview Replication Settings for Source Tables

4 Replication Settings Overview


After you select a configuration, the system displays a new screen that contains a summary of the configuration. On the left-hand side, you can view information about the schema details such as the schema name, mass transfer ID, and the SAP LT Replication Server as well as information about the source and target systems. You can add tables in order to specify specific replication settings, and also import and export settings. You can also retrieve source tables that are already processed from the SAP LT Replication Server. On the right-hand side, you can view all the tables, together with their custom replication settings that have been added either manually or from the replication server. In addition, you can view the replication status. Checkboxes indicate which of the tables for the replication settings have entries for each source table.

Figure 8 Overview of all the tables (together with their custom replication settings) that are contained in a schema.

4.1 Replication Settings for Source Tables


The system displays the source tables in table Replication Settings for Source Tables. The table contains the following fields: Field Source Table Name Replication Status REPL_TABSTG Description The name of the table in the source system Current replication status of the table This table contains custom table settings such as a changed table names or structures. A selected checkbox indicates that this table contains entries for the relevant source table.

16

November 2012

4 Replication Settings Overview 4.1 Replication Settings for Source Tables

ASS_RUL_MAP

SPC_PROCOPT PERF_OPTION

This table contains the settings for mapping rules that are used during the replication process. A selected checkbox indicates that this table contains entries for the relevant source table. This table contains the settings for database triggers. A selected checkbox indicates that this table contains entries for the relevant source table. This table contains the performance settings, such as the reading type. A selected checkbox indicates that this table contains entries for the relevant source table.

You can change the Source Table Name field. If you change this field, all the settings that exist for the table are copied to this new source table. The Replication Status field indicates whether a table is already being replicated or not. Changes made to the settings of tables that are being replicated will have no effect as the corresponding runtime objects have already been created. In general, if you want to change the settings of such tables, you must reload the tables - that is, stop and restart the replication. Below the table, there are standard pushbuttons for managing tables. You can use these pushbuttons to select or deselect all entries, add a line before the currently selected line, delete the marked lines, or sort the entries. If you delete a table name from this list, all settings for this table will also be deleted. To edit the replication settings for selected tables, choose the Edit Settings for Selected Tables pushbutton.

November 2012

17

Replication Settings Overview Add Source Table

Figure 9 Overview of all tables together with their custom replication settings. The first column contains the source table names. The replication status for any of the tables has not been set yet meaning that they are either not in replication or their status has not been updated yet. The checkboxes indicate whether a source tables has entries in the corresponding settings tables. For instance, the table SAPLANE has custom settings in IUUC_REPL_TABSTG, IUUC_ASS_RUL_MAP, and IUUC_PERF_OPTION but none in IUUC_SPC_PROCOPT.

4.2 Add Source Table


To add a source table in order to customize the replication settings, you have two options. You can either add a line, and change its name, (see Figure 9), or, you can use the input field on the lefthand side of the screen. If you use the input field, the system checks whether the table already exists in the list or not.

18

November 2012

4 Replication Settings Overview 4.3 Managing Files

Figure 10 Adding a table manually.

4.3 Managing Files


Exporting replication settings to a file is a convenient way of saving replication settings for later use in a different replication. The entries of the replication settings tables (see Table 1) and also the code for the includes specified as mapping rules in table IUUC_ASS_RUL_MAP (see section 5.3.3 for more information) are saved to a file. When importing a saved configuration, only the entries of the replication settings tables are uploaded to the system. Code for includes is not created if the new configuration runs on the same server, these includes would already be there, if a different server is used, they must be created manually. In addition, during the upload, the mass transfer ID and the SAP release of the sender system will be updated in the relevant tables automatically.

Figure 11 Pushbuttons for importing and exporting a configuration.

4.3.1 Export to File


When you export the replication settings to a file, (pushbutton Save Settings to File), the system displays a dialog box where you can specify the location for the file (see Figure 12). All entries of the settings tables as well as includes specified as mapping rules in IUUC_ASS_RUL_MAP will be saved in the file.

Figure 12 Dialog box for saving the settings as a template to file.

November 2012

19

Replication Settings Overview Managing Files

4.3.2 Import from File

Figure 13 Dialog box for importing settings from file. You can import replication settings from a file. You have the following options for uploading settings: Load All, Discard Original Settings - The system uses the uploaded settings only; the existing settings are not used Load All, Update Original Settings - The existing settings are updated with the information specified in the uploaded settings. Load Selected Settings - You can decided with of the uploaded and existing settings should apply

4.3.2.1

Load All, Discard Original Settings

Figure 14 Upload option 1: Load All, Discard Original Settings.

20

November 2012

4 Replication Settings Overview 4.3 Managing Files

You can discard the existing settings, and use new settings for all tables. All the entries in the settings tables are deleted and the uploaded entries are used. If a table has Customizing settings in the original configuration but none in the new one, it will not have any settings afterwards. For example, if the tables SAIRPORT and SPFLI have customized settings, but the template contains only entries for SPFLI and SFLIGHT, the new configuration after the upload would only contain settings for tables SPFLI and SFLIGHT, not for SAIRPORT.

4.3.2.2

Load All, Update Original Settings

Figure 15 Upload option 2: Load All, Update Original Settings. You can use this option to keep the original settings for a table if the table is not contained in the template file (see Figure 16). For example, if tables SAIRPORT and SPFLI have customized settings but the template has entries for the tables SPFLI and SFLIGHT, the new configuration would include all three tables. This option is particularly useful if settings are uploaded from several files.

November 2012

21

Replication Settings Overview Managing Files

Figure 16 Originally, the tables in the section highlighted on the top of the screen, and some of the tables highlighted in the section on the bottom of the screen have customized replication settings, (see Figure 9). When updating the settings from a template file that only contains settings for the tables in the bottom section, tables from the both sections will have custom settings. In the first case, (see Figure 14), the settings for the tables in the top section would be deleted.

22

November 2012

4 Replication Settings Overview 4.3 Managing Files

4.3.2.3

Load Selected Settings

Figure 17 Upload option 3: Load Selected Settings. You can use this option to merge original and uploaded settings manually for each table. You can compare the settings for each table, and you can choose which one will be used or whether the settings for this table should be deleted (see Figure 18). The default behavior is to keep the original settings if they exist, and use the template if they do not (the opposite behavior of the previous option (see Figure 15). In addition, you can compare the original and uploaded settings for each table, see Figure 19, and decide which should be used. It is also possible to use neither and omit the settings for a table, that is, to use neither the original nor the uploaded configuration for that table, (see Figure 20 and Figure 21 as an example).

November 2012

23

Replication Settings Overview Managing Files

Figure 18 List of all tables either contained in the current (original) settings or in the imported template. The checkboxes in the second and third column indicate what kind of settings exists. In this example, the first five tables are part of the current configuration only. The next four tables have settings defined in the current configuration as well as in the template and the remaining tables are only included in the file.

24

November 2012

4 Replication Settings Overview 4.3 Managing Files

Figure 19 Comparison of original settings and those imported from file (template). Here, the only difference is the target table name. Choose the pushbutton Keep Current Settings to use the current setting (Z_SCOUNTER), the pushbutton Use Template to use the uploaded (ZFLIGHTS_SCOUNTER), or use the pushbutton Omit Table to omit both settings and use the original name (SCOUNTER).

November 2012

25

Replication Settings Overview Managing Files

Figure 20 Example of the settings that will be used for the different tables. The resulting overview list is shown in Figure 21.

26

November 2012

4 Replication Settings Overview 4.4 Tables in Target System

Figure 21 Overview of the replication settings for the tables from Figure 20 for the upload. The omitted tables SCOUNTER, SCPLANE, SCURR, SCURX, and SCUSTOM do not appear any more.

4.4 Tables in Target System


Before customizing the replication settings for a table, it is generally advantageous to check the replication status. If a table is already in replication, it usually must be reloaded for the changed settings to take effect. You can use the pushbutton Update Replication Status to obtain the replication status of each table already contained in the configuration, and the pushbutton Add Tables from Target System to add all tables to the list which are already processed.

Figure 22 Section Tables in Target System.

November 2012

27

Replication Settings Overview Tables in Target System

4.4.1 Update Replication Status

Figure 23 The tables DD02L, DD02T, and DD08L are always loaded automatically when a new configuration is created. When manually adding these tables to the Replication Settings for Source Tables table, their replication status will be empty, but can be updated from the SAP LT Replication Server see Figure 24.

Figure 24 The replication status of the tables DD02L and DD02T has been obtained from the SAP LT Replication Server. The table DD08L was not added manually and therefore is not shown when updating the status.

4.4.2 Add Tables from Target System


If the tables are added from the SAP LT Replication Server (pushbutton Add from Target System), all tables which are in process or which have been processed will be added to the table list and the replication status of all table will be set (see Figure 25).

Figure 25 After adding the tables from the target system, the third table currently in replication, DD08L, has also been added.

28

November 2012

5 Customizing the Replication Settings 5.1 Overview

5 Customizing the Replication Settings


5.1 Overview
To customize the replication settings, choose the Edit Settings for Selected Tables pushbutton. It consists of the following sections (see Figure 26): Configuration Details - You can view information about the current configuration. Active Source Table - You can add lines to the tables for replication settings for only active tables Replication Settings for Tables - You can add or delete source tables. You can specify an active source table for which lines can be added to the tables for replication settings. You can also see whether entries exist for the tables for replication settings for a source table. Tables for Replication Settings -You can view the tables for the replication settings. Note that source table names cannot be changed in the settings tables.

Figure 26 The screen for editing the replication settings shows the schema details on top left, the bottom left is used for managing the source tables and the right side contains the settings tables.

5.2 Source Table Management


In section Replication Settings for Tables, you can view all source tables in the configuration. You can choose which table settings are displayed. All the replication settings can be modified with the exception of the Source Table Name field. This field cannot be changed as accidental changes might invalidate the entire settings and, if so, the code generator would not be able to find the settings for a source table, or, even worse, might apply them to a different source table.

November 2012

29

Customizing the Replication Settings Source Table Management

5.2.1 Active Source Table


In order to add new settings for a source table, you must make the table active (see Figure 27). To do this, either double-click an entry in the Replication Settings for Tables table, or enter the name in the Add Settings for Table field and choose return.

Figure 27 Active source table. Note that the table does not need to be part of the configuration yet. The system adds an entry to the Replication Settings for Tables table automatically after you add a new line to any of the tables for replication settings. For instance, the overview does not contain the table SPFLI (see Figure 28). If you want to customize the replication settings for that table, enter the name in the Add Setting for Table field and you can add settings for the source table SPFLI. Note that you can also double-click its name in the Replication Settings for Tables table, (see Figure 28). The system copies the name to the Add Settings for Table field and you can then change the replication settings.

5.2.2 Source Table Overview


In the Replication Settings for Tables table, you can see which tables are part of the configuration. The source table name is in the first field and the last four columns indicate which settings are customized for that table (see Figure 21). If the Display flag is set for a source table, the corresponding entries for the settings tables are shown. Besides changing which tables are displayed, you can add tables to the configuration, copy the settings for one table to another, or set the active table by double-clicking a table name.

Figure 28 List of the source tables with individual replication settings: The second column shows if the configuration for the source table given in the first field will be displayed or not. The last four

30

November 2012

5 Customizing the Replication Settings 5.2 Source Table Management

flags indicate if corresponding entries in the settings tables IUUC_REPL_TABSTG, IUUC_ASS_RUL_MAP, IUUC_SPC_PROCOPT, and IUUC_PERF_OPTION (from left to right) exist.

5.2.2.1 Displaying Tables in the Tables for Replication Settings


In order to change the displayed tables, you have two options. The first option is to select a table individually. To do this, select the display checkbox (see Figure 29). If the table is not displayed before, its settings will be shown and vice versa. Note that the active table is always displayed. The second option is to select several tables by selecting lines in the table list and choosing the Display Selection pushbutton (see Figure 30). Only the settings for the selected tables will be shown afterwards, that is, if a table is displayed before but not in the selection, it will not be shown. The active table will be reset.

Figure 29 Change whether a table will be displayed or not by selecting the Display checkbox. The settings for table SAIRPORT are not displayed and those for SBOOK are shown. If you select the Display checkbox for SAIRPORT, the system will display its replication settings.

Figure 30 Besides setting displayed status for each table individually, it is also possible to select and display the settings for several tables at once. You can use the pushbuttons on the left for selecting or deselecting all tables, and the Display Selection pushbutton to display the marked tables.

November 2012

31

Customizing the Replication Settings Source Table Management

5.2.2.2

Adding and Deleting Tables

Apart from the active table field, new tables can be also be added in the Replication Settings for Tables table. To do this, you add a new line, and change the empty table name to the required source table. The new table will not have any settings yet, though. Similarly, you can also delete lines from the Replication Settings for Tables table list. In this case, all corresponding entries in the replication settings tables will be deleted as well, that is, those tables will not have any custom replication settings. Note that the active table name will not be reset. If you delete the active table from the overview list, you can add settings for that table right away without entering the name in the active table field.

Figure 31 In order to add or delete source tables, you can use the buttons located below the overview list. If you add a line (left hand side), a blank line is added, where you can manually add the table name. When removing entries (right hand side), the replication settings for the tables will be deleted. In this example, the entries in IUUC_REPL_TABSTG (the other tables do not have custom settings for this source table - the relevant checkboxes are not selected) for table SBOOK_2 would be removed.

5.2.2.3

Copying Settings

In the Replication Settings for Tables table, you can change the source table names. The replication settings for the old table would then be applied to the new source table. After entering the new name in the Table Name field (see Figure 32), the system displays a dialog box that asks you how you want to proceed. The options are to either rename the table name, or to copy the settings. If you copy the settings, the table name in the Replication Settings for Tables table and all associated entries in the settings tables will be changed to the new name. There will be no replication settings for the old source table any more. Whereas in the latter case, all entries will be copied to the new name such that old and new source table will have identical settings apart from the table name.

32

November 2012

5 Customizing the Replication Settings 5.3 Table Settings

Figure 32 Change of table name in the table list

Figure 33 Options for changing the table name in the Replication Settings for Tables table. Rename all settings assigned to the original table (SBOOK) will be assigned to the new table (SBOOK_2). Copy the settings for the original table will be copied for the new table and both tables will have the same replication settings afterwards.

Figure 34 The two options when changing the source table name in the overview list. If you rename the source table, only the new table will have custom replication settings (left). When copying the settings, both tables will have identical settings (right).

5.3 Table Settings


On the right-hand side of the settings screen, there are the actual settings tables. Four of the five settings tables, IUUC_REPL_TABSTG, IUUC_ASS_RUL_MAP, IUUC_SPC_PROCOPT, and IUUC_PERF_OPTION can be accessed from tab pages where these tables can be edited directly. The fifth table, IUUC_REPL_TAB_DV, can be accessed from the IUUC_REPL_TABSTG tab page. All tab pages have generic functionality for selecting or deselecting all entries. New lines can be added, where the active source table will be filled into the table name field, (see section 5.2.1). If there is no active source table, no lines can be added. Furthermore, selected lines can be deleted. The file interface introduced in section 4.3 is implemented through the two pushbuttons on the right without having to navigate back to the previous screen.

November 2012

33

Customizing the Replication Settings Table Settings

Figure 35 Screen for editing the table settings. This screen consists of four tab pages, one for each of the four main settings tables. The first two buttons can be used to select or deselect all table entries. The next two buttons are for adding and deleting lines followed by buttons for sorting the entries by their table names in ascending or descending order. In addition, you can import all settings from a file or export them to a file.

5.3.1 Table IUUC_REPL_TABSTG


The table IUUC_REPL_TABSTG contains the settings for the basic table properties, such as table name and structure, in the target system.

34

November 2012

5 Customizing the Replication Settings 5.3 Table Settings

Figure 36 IUUC_REPL_TABSTG describes the changes of the target table properties with respect to the source system. By default, the table created in the target system will have the same name and structure as the source table. However, it might be necessary to change the name or alter the table structure depending on your requirements. For instance, tables from different sources could be replicated to one target system, some table fields might have become obsolete, or several fields could be combined into one field. A new table name can be entered in the Target Table Name field. Modifications to the table structure can be achieved in two different ways (see Figure 37). Firstly, a different ABAP Dictionary data type can be used. This type would be either defined in the source system or in the SAP LT Replication Server and must be entered in the Target Table Type field. If the target structure (database table, table type or structure) is defined locally in the SAP LT Replication Server, the checkbox Local Target Type must be selected. The second way for changing the target structure is to define deviations in IUUC_REPL_TAB_DV. This settings table can be accessed by using the Edit Table Structure pushbutton). The Deviation checkbox will be set automatically if entries exist. Note that both methods for changing a table structure can be used at the same time. If a different ABAP Dictionary data type is defined, this type will be used as starting point for later modifications in IUUC_REPL_TAB_DV. You can change the table name in the Target Table Name field. The new table structure can be reviewed by double-clicking an entry in the Target Table Type field. All modifications, that is, the ABAP Dictionary type and entries in table IUUC_REPL_TAB_DV, will be evaluated and the system displays the new structure (see Figure 38). The option No Drop prevents the recreation of the target table when a source table is added to a configuration. By default, the target table will be dropped if it exists, and created again from the new configuration. This behavior has advantages regarding data and structural consistency but also has its limitations if more than one source table is replicated into a target table. For each of the source tables, the target table would be dropped and a new one created thereby losing all data that had already been loaded. In order to avoid the data loss that can result from this default behavior, select the No Drop checkbox. The option Row Store controls how the data is stored in the HANA database. In contrast to many other databases, HANA groups the data in columns and not by lines. Select this option if you want the data to be stored in rows instead of columns.

November 2012

35

Customizing the Replication Settings Table Settings

The size of read portions is the number of entries in one portion during the initial load for the default reading type DB_SETGET. It has no effect for other reading types, for example access plan, or for delta replication. For the latter, up to 5000 entries are selected in one portion. The last field in table IUUC_REPL_TABSTG is the partition command. It is a line of native (HANA) SQL code that is executed during the creation of the table in the target system. The partition command can be used to split the target table into several smaller packages. For example, PARTITION BY HASH (MANDT, CARRID) PARTITIONS 4 would create the table with four hash partitions selected by the fields Client (mandt) and carrid. Table IUUC_REPL_TABSTG contains the following fields: Field Mass transfer ID [not shown in UI] Table Name [not an input field] Target Table Type Description Mass transfer identifier of the configuration. Name of the source table in the source system, unique key field; is filled automatically from the active source table when adding a new line. ABAP Dictionary type of the target table if different from source table; Could be structure (note that a structure does not define any key fields), table type, or database table. Target table type is defined on the replication server (X) or source system ( ). Name of the table in the target system. Whenever a new table is added to a replication configuration, the target table is deleted from the target system (if it exists) and created again. Select this option in order to avoid dropping the target table, for example if several source tables are replicated into one target. Data will be stored in rows instead of columns (default for HANA are columns). Number of records read in one package during the initial load when reading type is 3 (db setget), default is 10000. Has no effect during the delta replay phase or for different reading types. Indicates that the structure of target table deviates from the source table, the deviations are defined in the table IUUC_REPL_TAB_DV. Partition command when creating the target table in the target system.

Local Target Type Target Table Name No Drop

Row Store Size of Read Portions

Deviations from Table Structure [not an input field] Partition command

Figure 37 There are two options for changing the table structure. Either a different ABAP Dictionary type (database table, table type or structure) can be defined either on the source system or on the replication server. Or the current structure can be modified through IUUC_REPL_TAB_DV, which can be accessed through the Edit Table Structure pushbutton.

36

November 2012

5 Customizing the Replication Settings 5.3 Table Settings

Figure 38 Review of the used table structure. By double-clicking an entry in the Target Table Type field in the tab page IUUC_REPL_TASTG, the used table structure in the target system will be displayed. If a different ABAP Dictionary type is used it will be displayed here, together with any changes defined in table IUUC_REPL_TAB_DV.

5.3.2 Table IUUC_REPL_TAB_DV


IUUC_REPL_TAB_DV provides a way to modify the table structure in the target system without creating a new ABAP Dictionary type in either the source system or on the replication server. This settings table can be accessed from the Edit Table Structure pushbutton in the

November 2012

37

Customizing the Replication Settings Table Settings

IUUC_REPL_TABSTG tab page (see

Figure 36). The system displays a dialog box (see Figure 39) where you can modify or delete the fields of the original structure. In the upper part, you can view the original table structure. For each field, you can select whether you want to keep it, change the data type, or delete it, that is, remove it from the target table. In the lower part, you can insert new fields by specifying their name, position, and data type. Note that if you want to create a new key field, you must position the new key field to the position either after the last key field, or in between any two key fields.

38

November 2012

5 Customizing the Replication Settings 5.3 Table Settings

Figure 39 The screen for changing the table structure. The upper part shows the current table fields and allows you to modify or delete individual fields. In the lower part, you can add new fields and specify their position in the new table structure. All modifications are saved in table IUUC_REPL_TAB_DV.

November 2012

39

Customizing the Replication Settings Table Settings

Figure 40 Changing the data type of a field.

5.3.3 Table IUUC_ASS_RUL_MAP


You can use table IUUC_ASS_RUL_MAP to specify mapping rules. These rules are realized through custom ABAP coding that will be executed during processing. The code can be defined either in an ABAP Dictionary include or directly as a line of code in the table (see Figure 43). Two different mapping schemes are supported - event-based rules, and parameter rules. For event-based rules, custom coding can be inserted at eight predefined points of processing. All fields of source and target tables can be accessed. Whereas the latter are used to calculate a target field from up to three source fields. Parameter rules are easier to use, but offer less flexibility than event-based rules. Both are described in more detail below. In either case, you can use the macro SKIP_RECORD to prevent a record from being replicated. A skipped entry will be not be replicated.

Figure 41 IUUC_ASS_RUL_MAP

5.3.3.1

Includes, and Lines of Code

Figure 42 The two possibilities for specifying the custom coding. An ABAP Dictionary include must be defined locally on the SAP LT Replication Server, whereas a line of code is stored directly in the settings table IUUC_ASS_RUL_MAP. A line of code will be stored directly in the settings table IUUC_ASS_RUL_MAP. No ABAP Dictionary objects must be created. A serious limitation is the restriction to 72 characters for each line of code; this means that only simple mapping rules can be realized. In contrast, ABAP Dictionary includes do not have any size limitations and can therefore be used to implement complex mapping rules. In order to review or modify the code, double-click the name of the include. If the include does not exist, the system calls transaction SE38 instead.

40

November 2012

5 Customizing the Replication Settings 5.3 Table Settings

Figure 43 The settings for IUUC_ASS_RUL_MAP. The first input field, Event, determines which type of mapping rule is used. If the field Event is empty, parameter rules will be used, otherwise event-based rules are used. The next four fields are only relevant for parameter rules. The last two fields define the code either through an ABAP Dictionary include or directly in the settings table. Field Mass transfer ID [not shown in UI] Table Name [not an input field] SAP Basis Release [not an input field] Event Export Field Name Description The mass transfer ID of the configuration. The name of the source table in the source system, this is a unique key field, and is filled automatically from the active source table when adding a new line. The Basis release of the SAP source system. This field will be filled automatically from the source system and also updated when importing settings from file. Event at which the provided mapping rules will be executed for eventbased rules. For parameter rules, this field must be empty. The receiving field for parameter rules; this field is not relevant for eventbased rules. Accessed as e_<fieldname> in the code. Import field for parameter rules; this field is not relevant for event-based rules. Accessed as i_<fieldname>_1 in the code. Import field for parameter rules; this field is not relevant for event-based rules. Accessed as i_<fieldname>_2 in the code. Import field for parameter rules; this field is not relevant for event-based rules. Accessed as i_<fieldname>_3 in the code. The name of the ABAP include that will be executed. The line of code that will be executed

Import Parameter 1

Import Parameter 2

Import Parameter 3

Insert Include Name Insert Line of Code

Table 2 Fields of the settings table IUUC_ASS_RUL_MAP.

November 2012

41

Customizing the Replication Settings Table Settings

5.3.3.2 Parameter Rules


Parameter rules are used for simple value mappings. Their main advantage is their easy definition, whereby the target and source fields are specified directly in table IUUC_ASS_RUL_MAP. However, they offer less flexibility than event-based rules. The Event field in IUUC_ASS_RUL_MAP (see Table 2) must be left blank for parameter rules and the target field name must be entered in the Export Field Name field. Up to three fields of the source table can be specified as input parameters for the ABAP code in the corresponding fields (Import Parameter 1, Import Parameter 2, and Input Parameter 3). If no input parameter is used, the first import field must contain the value Dummy (including the quotation marks). The export parameter of the code has the format 'e_<fieldname>', where <fieldname> is the name of the field entered as the export field in table IUUC_ASS_RUL_MAP. The three import parameters have the format 'i_<fieldname_1>_1', 'i_<fieldname_2>_2', and 'i_<fieldname_3>_3' where <fieldname_1>, <fieldname_2>, and <fieldname_3> are the names of the fields entered as import parameters in table IUUC_ASS_RUL_MAP. Two examples for parameter rules are given in Table 3Table 4. Field name Table Name SAP Basis Release Event Export Field Name Import Parameter 1 Import Parameter 2 Import Parameter 3 Insert Include Name Insert Line of Code E_CITYTO = HONOLULU. CITYTO DUMMY Value SPFLI 700

Table 3 Example for an entry of IUUC_ASS_RUL_MAP. In this example, the field CITYTO of the table SPFLI will be changed to Honolulu regardless of the original entry of the field CITYTO.

Field name Table Name SAP Basis Release Event Export Field Name Import Parameter 1 Import Parameter 2 Import Parameter 3 Insert Include Name Insert Line of Code

Value SPFLI 700

CITYTO CITYTO

IF I_CITYTO_1 = HONOLULU. E_CITYTO = HANA. ENDIF.

42

November 2012

5 Customizing the Replication Settings 5.3 Table Settings

Table 4 Example for an entry of IUUC_ASS_RUL_MAP. All flights sent to Honolulu in the previous example will be rerouted to Hana Airport on Maui instead. Other import parameters could be used as well and it would not be necessary to include the target field.

November 2012

43

Customizing the Replication Settings Table Settings

5.3.3.3 Event-based Rules


You can use event-based rules to execute custom ABAP coding at specific points of processing (see Table 5). A schematic listing of the replication process is shown in Table 5 with the events highlighted in green. The individual field mapping performed for parameter rules is printed in red italics. Note that the begin of block (BOT) and begin of loop (BOL) events as well as the end of loop (BOL) and end of block (BOT) events would be executed directly one after another for simple structures like transparent tables. For more complex structures, such as cluster tables, the block events BOT and EOT are triggered before looping over the clusters, whereas the loop events BOL and EOL are executed before looping over the entries of the logical tables in a cluster. Similarly, begin of record (BOR) and end of record (EOR) would do the same if no parameter rules are defined. The data of source and target work areas can be accessed through field symbols in begin of record (BOR) and end of record (EOR) events. The field symbols follow a generic name scheme <wa_s_tablename> for source and <wa_r_tablename> for target work areas, where tablename denotes the source table name. For instance, the work areas for the table SPFLI would be <wa_s_spfli> and <wa_r_spfli>. BOP Begin of processing DO Get next portion from source system BOT Begin of block LOOP AT source structures BOL Begin of loop LOOP AT source table MOVE-CORRESPONDING source work area TO target work area BOR Begin of record Individual field mapping (parameter rules) EOR End of record Insert target work area into target table ENDLOOP EOLEnd of loop ENDLOOP EOT End of block Write to target system ENDDO EOP End of processing Table 5 A schematic representation of the replication process. The data is loaded in blocks. For each block, the system loops through the entries of the source tables and performs the ABAP command MOVE-CORRESPONDING from the source table work area to the target structure. The target structure is then inserted into the target table. The events for event-based rules are highlighted in green. The individual field mapping of the parameter rules is in red italics. Field name Table Name SAP Basis Release Event Export Field Name Import Parameter 1 Value SPFLI 700 BOR

44

November 2012

5 Customizing the Replication Settings 5.3 Table Settings

Import Parameter 2 Import Parameter 3 Insert Include Name Insert Line of Code <WA_R_SPFLI>-SPFLI = HONOLULU.

Table 6 Example of event-based rules. The same mapping as in Table 3 is performed but now linked to the Begin of Record event. Field name Table Name SAP Basis Release Event Export Field Name Import Parameter 1 Import Parameter 2 Import Parameter 3 Insert Include Name Insert Line of Code Table 7 Example of event-based rules. Instead of a line of code, an ABAP include will be inserted. The code is listed in Table 8. * INCLUDE Z_SPFLI_MAP redirect all Honolulu flights to Hana IF <wa_s_spfli>-cityto = HONOLULU OR <wa_s_spfli>-airpfrom = HNL. <wa_r_spfli>-cityto = HANA. <wa_r_spfli>-airpto = HNM. <wa_r_spfli>-countryto = US. ELSE. skip all other records SKIP_RECORD. ENDIF. Table 8 Example of an ABAP include for event-based rules. All table fields can be accessed through field symbols. Instead of one event-based rule, three parameter rules must be defined to achieve the same goal. Z_SPFLI_MAP Value SPFLI 700 BOR

November 2012

45

Customizing the Replication Settings Table Settings

5.3.4 Table IUUC_SPC_PROCOPT


In the third tab page, you can use the settings table IUUC_SPC_PROCOPT to customize the code for the triggers that record the changes in the source tables. Note that this option is intended for expert users only. We strongly recommend that you contact SAP for support before using this feature, as incorrect use can result in serious data inconsistencies. Note that you can also use the settings table IUUC_ASS_MAP_RULE to define rules for the database triggers. Any rules that you define here only applicable for the replication process, they do not affect the initial load.

Figure 44 The trigger options for recording changes can be customized in table IUUC_SPC_PROCOPT.

5.3.5 Table IUUC_PERF_OPTION


You can use table IUUC_PERF_OPTION to optimize the performance of the initial load of the individual tables.

Figure 45 For each table, several parameters can be used to optimize performance. Field Mass transfer ID [not shown in UI] Table Name [no input field in UI] No of Parallel Jobs Field Name for Parallelization Seq. No. Description The mass transfer ID of the configuration The name of the source table in the source system. This is a unique key field that is filled automatically from the active source table when adding a new line The maximum number of jobs that will be used for loading the table The field name used for parallelization The sequence number for processing the source tables. Tables with low numbers will be loaded first

46

November 2012

5 Customizing the Replication Settings 5.3 Table Settings

Reading Type

The reading type for the table

Table 9 Relevant fields of the table IUUC_PERF_OPTION.

Reading type 1 Access Plan Calculation 2 Pool tables 3 DB setget (Cluster tables)

Description An access plan is used for reading the table; the data will be split into portions which are then loaded into the target system. Similar to the access plan reading type but the entire table will be read as one portion. Default option. Uses the function module DB_SETGET to fetch a predefined number of entries from the source table. These entries are ordered by their primary keys. Opens a database cursor in the source system and copies the data from the source table into an INDX table on the source system. The entries of the INDX table are then replicated ordered by their indices. Similar to the former type 4 but forces a full table scan. The INDX table is filled from an external report. Note that this reading type is not used for HANA replication. This reading type is not used for HANA replication.

4 INDX CLUSTER (IMPORT FROM DB)

5 INDX CLUSTER with FULL TABLE SCAN 6 INDX CLUSTER filled from external 7 INDX CLUSTER child table FTS

Table 10 Different reading types; the default option is DB setget.

November 2012

47