hana slt config en

7/16/2019 Hana Slt Config En

http://slidepdf.com/reader/full/hana-slt-config-en 1/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



© Copyright 2012 SAP AG. All rights reserved.

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.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used

under license for technology invented and implemented by Netscape.

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.

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.

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.

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.

SAP AGDietmar-Hopp-Allee 1669190 Walldorf Germany

T +49/18 05/34 34 24F +49/18 05/34 34 20www.sap.com



3

Any Java™ Source Code delivered with this product is

only to be used by SAP’s 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

Terms for Included Open

Source SoftwareThis 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

A) SAP grants Customer a non-exclusive, non-transferrable, royalty-

free 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.


its documentation for any purpose is hereby granted without fee,



supporting documentation. Silicon Graphics makes no representations

about the suitability of this software for any purpose. It is provided “asis” without express or implied warranty.







4

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.





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.



5

Typographic Conventions

Type Style Descrip tion

Example Text Words or characters quoted fromthe screen. These include fieldnames, screen titles,pushbuttons labels, menunames, menu paths, and menuoptions.

Cross-references to otherdocumentation

Example text Emphasized words or phrases inbody text, graphic titles, andtable titles

EXAMPLE TEXT Technical names of systemobjects. These include reportnames, program names,transaction codes, table names,and key concepts of aprogramming language whenthey are surrounded by bodytext, for example, SELECT andINCLUDE.

Exampl e t ext Output on the screen. Thisincludes file and directory namesand their paths, messages,names of variables andparameters, source text, andnames of installation, upgradeand database tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly as

they appear in thedocumentation.

<Example text> Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, forexample, F2 or ENTER.

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Librarydocumentation to help you identify differenttypes of information at a glance. For moreinformation, see Help on Help → GeneralInformation Classes and Information Classesfor Business Information Warehouse on thefirst page of any version of SAP Library.



Advanced Repl ication Sett ings

6 November 2012

Contents

1 Gett ing Started ............................................................................ 7 1.1 Global Defini tions ........................................................................ 7

1.2 Important SAP Notes ................................................................... 9

1.3 History of Changes ...................................................................... 9

2 Introduct ion ............................................................................... 10

3 Conf iguration Overview ........................................................... 11

3.1 Configuration List ...................................................................... 11

3.2 Configuration Details and Selection ........................................ 12

3.3 Remote Maintenance ................................................................. 13

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

4.1 Replication Settings for Source Tables ................................... 16

4.2 Add Source Table ....................................................................... 18

4.3 Managing Files ........................................................................... 19

4.3.1 Export to File ................................................................................. 19

4.3.2 Import from File ............................................................................. 20

4.3.2.1 Load All, Discard Original Settings ....................................................................... 20 4.3.2.2 Load All, Update Original Settings ........................................................................ 21 4.3.2.3 Load Selected Settings ......................................................................................... 23

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

4.4.1 Update Repl ication Status ............................................................ 28

4.4.2 Add Tables f rom Target System .................................................. 28

5 Customizing the Replication Sett ings ..................................... 29

5.1 Overview ..................................................................................... 29

5.2 Source Table Management ........................................................ 29

5.2.1 Acti ve Source Table ...................................................................... 30

5.2.2 Source Table Overview ................................................................. 30

5.2.2.1 Displaying Tables in the Tables for Replication Settings...................................... 31 5.2.2.2 Adding and Deleting Tables .................................................................................. 32 5.2.2.3 Copying Settings ................................................................................................... 32

5.3 Table Sett ings ............................................................................. 33

5.3.1 Table IUUC_REPL_TABSTG ......................................................... 34

5.3.2 Table IUUC_REPL_TAB_DV ......................................................... 37

5.3.3 Table IUUC_ASS_RUL_MAP ......................................................... 40

5.3.3.1 Includes, and Lines of Code ................................................................................. 40

5.3.4 Table IUUC_SPC_PROCOPT ........................................................ 46

5.3.5 Table IUUC_PERF_OPTION .......................................................... 46



1 Getting Started

1.1 Global Definitions

November 2012 7

•

1 Getting Started

This guide does not replace the daily operations handbook that we recommendcustomers 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 Definit ions The following table contains key terms related to the SAP LT Replication Server:

Term Definition

Advanced Replication Settings A transaction that runs on the SAP LTReplication Server that you can use to specifyadvanced replication settings. For example, youcan:• Modify target table structures

• Specify performance optimization settings• Define transformation rules

Configuration The definition of the parameters that the SAP LTReplication Server uses to replicate data fromone or more source systems to one or moretarget systems. The configuration specifies thesource system, the target system, and therelevant connections.

Configuration and Monitoring Dashboard An application that runs on the SAP LTReplication Server that you use to specifyconfiguration information (such as the sourceand target systems, and relevant connections)so that data can be replicated. You can also useit to monitor the replication status.

Database trigger A piece of code that updates a databaseautomatically in response to a certain event.

Data transfer J ob A job that is used for the data transfer processin the SAP LT Replication Server.

Initial load A step within the trigger-based replicationprocess that loads data from the source systemto target system.

Initial load J ob A job that is used for the initial load process in



Getting Started

Global Definitions

8 November 2012

the SAP LT Replication Server.

Latency The length of time to replicate data (a tableentry) from the source system to the targetsystem.

Logging table A table in the source system that records anychanges to a table that is being replicated. Thisensures that the SAP LT Replication Server canreplicate these changes to the target system.

Master job A job that exists for each configuration that callsthe initial load jobs and the data transfer jobs inthe SAP LT Replication Server.

Maximum latency The maximum time taken to replicate data (atable entry) from the source to target system.

Median latency The median time taken to replicate data (a tableentry) from the source to target system.

Minimum latency The minimum time taken to replicate data (atable entry) from the source to target system.

Reading type A technique for reading data from tables in thetarget system during the initial load process.

Replication phase A phase in the trigger-based replication processwhereby only changes to the source database(recorded by databases triggers) are replicatedto the target database, thereby facilitating real-time data replication.

SAP LT Replication Server An SAP system that facilitates the replication of

data from one or more source systems to one ormore target systems. The source systems canbe SAP or non-SAP systems.

Tables for replication settings The set of tables in the SAP LT ReplicationServer that contain the replication settings for aspecific configuration.

Trigger-based replication A technique for replicating data where an initialload is first performed that loads data from thesource to the target system, and a replicationphase begins whereby only changes to thesource database (recorded by databasestriggers) are replicated to the target database,

thereby facilitating data replication in real-time.

Transformation rules A rule that you can specify in the AdvancedReplication Settings transaction for sourcetables such that data is transformed during thereplication process. The transformed data willthen be present in the target table. For example,you can specify a rule to:• Convert fields• Fill empty fields

• Skip records



1 Getting Started

1.2 Important SAP Notes

November 2012 9

1.2 Important SAP Notes

Important SAP Notes

SAP NoteNumber

Title Comment

1.3 History of Changes The following table provides an overview of the most important changes in prior versions.

Version Important Changes

1.0 First version of the guide

1.1 Revised by information development



Introduction

History of Changes

10 November 2012

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 Serverconnected 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 processingsteps. In particular, after adding a table to a configuration for replication, a logging table anddatabase triggers must be set up in the source system in order to keep track of data changes forreal-time replication. In the target HANA system, a new database table must be created for the dataread 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 targetsystem. The table entries are first retrieved from the source table, and then processed in the SAPLT Replication Server before they are sent to the target HANA database. After the initial load isfinished, 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 processingoccurs 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 betransferred to the target system

The replication settings are stored in five tables in the SAP LT Replication Server. In theReplication 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 Description

IUUC_REPL_TABSTG Contains the settings that specify how changes of table structure fromsource to target system, for example the table name, different line typedefined in the ABAP Dictionary

IUUC_REPL_TAB_DV You can change the structure of the table at field level without defining anew line type in the ABAP Dictionary in the sender system or in the SAPLT Replication Server.

IUUC_ASS_RUL_MAP You can specify mapping rules that are executed during the replicationprocess.

IUUC_SPC_PROCOPT You can apply Customizing settings for database triggers in order torecord changes to the source table.

IUUC_PERF_OPTION Contains settings regarding the performance of the replication, forexample you can define settings for the reading type and portion sizes.

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



3 Configuration Overview

3.1 Configuration L ist

November 2012 11

3 Configuration OverviewWhen you execute transaction IUUC_REPL_CONTENT, the system displays an overview of allavailable 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 aconfiguration, choose the Display Details pushbutton.

You can also specify replication settings for a configuration that exists in a remote system (aremote SAP LT Replication Server).

Figure 1 The initial screen of the Replication Settings screen.

3.1 Configuration ListIn the initial screen, the system displays a summary of all the configurations that exist in the currentSAP LT Replication Server, see

Figure 2. In addition to the configuration name, you can view information about the source andtarget systems. In general, the schema name does not uniquely identify a configuration. Forinstance, a HANA database schema could be filled from different source systems. The name of theconfiguration and the target system would be the same, so the configurations could only bedistinguished by their source system information. You can use the SAP LT Replication Server toreplicate database tables from SAP and non-SAP sources into a HANA system. For non-SAPsystems, the underlying database is accessed directly by SQL statements.



Configuration Overview

Configuration Details and Selection

12 November 2012

Figure 2 A highlighted schema, and pushbuttons.

The following table details the fields from the Available Schemas table:

Field Description

Schema Name The name of the target database schema

Target Type Type of the target system

Source Type Type of the source system (either an SAP system or a non-SAP

system)

Target System This field contains a concatenation of the host and instance number forthe target system

Source System This field contains a concatenation of the system ID, host number andinstance 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 SAPrelease 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.




3.3 Remote Maintenance

November 2012 13

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

3.3 Remote MaintenanceIn complex system landscapes, it might be necessary to use more than one SAP LT ReplicationServer, and each server has its own configurations. Instead of logging onto each of these systemsin order to specify the replication settings, you can specify the settings remotely. You can specifyan RFC connection, and read and write the replication settings to the relevant database tables inthe remote SAP LT Replication Server. Note that the RFC user must have sufficient authorizationsto 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 cancreate 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 remoteschemas, you can change back to the local system schemas by selecting the empty RFCconnection 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 thedropdown list.



Configuration Overview

Remote Maintenance

14 November 2012

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

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




3.3 Remote Maintenance

November 2012 15

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



Replication Settings Overview

Replication Settings for Source Tables

16 November 2012

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 theschema name, mass transfer ID, and the SAP LT Replication Server as well as information aboutthe 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 processedfrom the SAP LT Replication Server. On the right-hand side, you can view all the tables, togetherwith their custom replication settings that have been added either manually or from the replicationserver. In addition, you can view the replication status. Checkboxes indicate which of the tables forthe replication settings have entries for each source table.

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

4.1 Replication Settings for Source Tables The system displays the source tables in table Replication Settings for Source Tables. The tablecontains the following fields:

Field Description

Source Table Name The name of the table in the source system

Replication Status Current replication status of the table

REPL_TABSTG This table contains custom table settings such as a changed table namesor structures. A selected checkbox indicates that this table contains entriesfor the relevant source table.




4.1 Replication Settings fo r Source Tables

November 2012 17

ASS_RUL_MAP This table contains the settings for mapping rules that are used during thereplication process. A selected checkbox indicates that this table containsentries for the relevant source table.

SPC_PROCOPT This table contains the settings for database triggers. A selected checkboxindicates that this table contains entries for the relevant source table.

PERF_OPTION This table contains the performance settings, such as the reading type. Aselected checkbox indicates that this table contains entries for the relevantsource table.

You can change the Source Table Name field. If you change this field, all the settings that exist forthe table are copied to this new source table. The Replication Status field indicates whether a tableis already being replicated or not. Changes made to the settings of tables that are being replicatedwill 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 restartthe replication.

Below the table, there are standard pushbuttons for managing tables. You can use thesepushbuttons to select or deselect all entries, add a line before the currently selected line, delete themarked lines, or sort the entries. If you delete a table name from this list, all settings for this tablewill also be deleted. To edit the replication settings for selected tables, choose the Edit Settings for Selected Tables pushbutton.




Add Source Table

18 November 2012

Figure 9 Overview of all tables together with their custom replication settings. The first columncontains the source table names. The replication status for any of the tables has not been set yetmeaning that they are either not in replication or their status has not been updated yet. Thecheckboxes indicate whether a source tables has entries in the corresponding settings tables. Forinstance, 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 caneither add a line, and change its name, (see Figure 9), or, you can use the input field on the left-hand side of the screen. If you use the input field, the system checks whether the table alreadyexists in the list or not.




4.3 Managing Files

November 2012 19

Figure 10 Adding a table manually.

4.3 Managing FilesExporting replication settings to a file is a convenient way of saving replication settings for later usein a different replication. The entries of the replication settings tables (see Table 1) and also thecode for the includes specified as mapping rules in table IUUC_ASS_RUL_MAP (see section 5.3.3for 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 thenew configuration runs on the same server, these includes would already be there, if a differentserver is used, they must be created manually. In addition, during the upload, the mass transfer IDand 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 FileWhen you export the replication settings to a file, (pushbutton Save Settings to File), the systemdisplays 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 besaved in the file.

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




Managing Files

20 November 2012

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 uploadingsettings:

• 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.




4.3 Managing Files

November 2012 21

You can discard the existing settings, and use new settings for all tables. All the entries in thesettings tables are deleted and the uploaded entries are used. If a table has Customizing settings inthe original configuration but none in the new one, it will not have any settings afterwards. Forexample, if the tables ‘SAIRPORT’ and ‘SPFLI’ have customized settings, but the template containsonly entries for ‘SPFLI’ and ‘SFLIGHT’, the new configuration after the upload would only containsettings 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 thetemplate file (see Figure 16). For example, if tables ‘SAIRPORT’ and ‘SPFLI’ have customizedsettings but the template has entries for the tables ‘SPFLI’ and ‘SFLIGHT’, the new configurationwould include all three tables. This option is particularly useful if settings are uploaded from severalfiles.




Managing Files

22 November 2012

Figure 16 Originally, the tables in the section highlighted on the top of the screen, and some of thetables 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 thetables in the bottom section, tables from the both sections will have custom settings. In the firstcase, (see Figure 14), the settings for the tables in the top section would be deleted.




4.3 Managing Files

November 2012 23

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 cancompare the settings for each table, and you can choose which one will be used or whether thesettings for this table should be deleted (see Figure 18). The default behavior is to keep the originalsettings if they exist, and use the template if they do not (the opposite behavior of the previousoption (see Figure 15). In addition, you can compare the original and uploaded settings for eachtable, see Figure 19, and decide which should be used. It is also possible to use neither and omitthe settings for a table, that is, to use neither the original nor the uploaded configuration for thattable, (see Figure 20 andFigure 21 as an example).




Managing Files

24 November 2012

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




4.3 Managing Files

November 2012 25

Figure 19 Comparison of original settings and those imported from file (template). Here, the onlydifference is the target table name. Choose the pushbutton Keep Current Settings to use thecurrent setting (‘Z_SCOUNTER’), the pushbuttonUse Template to use the uploaded(‘ZFLIGHTS_SCOUNTER’), or use the pushbutton Omit Table to omit both settings and use the

original name (‘SCOUNTER’).




Managing Files

26 November 2012

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




4.4 Tables in Target System

November 2012 27

Figure 21 Overview of the replication settings for the tables from Figure 20 for the upload. Theomitted tables ‘SCOUNTER’, ‘SCPLANE’, ‘SCURR’, ‘SCURX’, and ‘SCUSTOM’ do not appear anymore.

4.4 Tables in Target SystemBefore customizing the replication settings for a table, it is generally advantageous to check thereplication status. If a table is already in replication, it usually must be reloaded for the changedsettings 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 AddTables from Target System to add all tables to the list which are already processed.

Figure 22 Section Tables in Target System.




Tables in Target System

28 November 2012

4.4.1 Update Replication Status

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

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

4.4.2 Add Tables from Target SystemIf 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 thereplication 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.



5 Customizing the Replication Settings

5.1 Overview

November 2012 29


5.1 Overview To customize the replication settings, choose the Edit Settings for Selected Tables pushbutton. Itconsists 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 whichlines 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 cannotbe changed in the settings tables.

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

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



Customizing the Replication Settings

Source Table Management

30 November 2012

5.2.1 Act ive Source TableIn order to add new settings for a source table, you must make the table active (see Figure 27). Todo this, either double-click an entry in the Replication Settings for Tables table, or enter the name inthe 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 tothe Replication Settings for Tables table automatically after you add a new line to any of the tablesfor replication settings. For instance, the overview does not contain the table ‘SPFLI’ (see Figure28). If you want to customize the replication settings for that table, enter the name in the AddSetting 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 systemcopies the name to the Add Settings for Table field and you can then change the replicationsettings.

5.2.2 Source Table OverviewIn 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 arecustomized for that table (see Figure 21). If the Display flag is set for a source table, thecorresponding entries for the settings tables are shown. Besides changing which tables aredisplayed, you can add tables to the configuration, copy the settings for one table to another, or setthe 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




5.2 Source Table Management

November 2012 31

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 ReplicationSettings

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

Figure 29 Change whether a table will be displayed or not by selecting the Display checkbox. Thesettings for table ‘SAIRPORT’ are not displayed and those for ‘SBOOK’ are shown. If you select theDisplay 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 selectand display the settings for several tables at once. You can use the pushbuttons on the left forselecting or deselecting all tables, and the Display Selection pushbutton to display the markedtables.




Source Table Management

32 November 2012

5.2.2.2 Adding and Deleting TablesApart 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 requiredsource 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, thosetables will not have any custom replication settings. Note that the active table name will not bereset. If you delete the active table from the overview list, you can add settings for that table rightaway 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 theoverview list. If you add a line (left hand side), a blank line is added, where you can manually addthe table name. When removing entries (right hand side), the replication settings for the tables willbe deleted. In this example, the entries in IUUC_REPL_TABSTG (the other tables do not havecustom settings for this source table - the relevant checkboxes are not selected) for table‘SBOOK_2’ would be removed.

5.2.2.3 Copying SettingsIn the Replication Settings for Tables table, you can change the source table names. Thereplication settings for the old table would then be applied to the new source table. After enteringthe new name in the Table Name field (see Figure 32), the system displays a dialog box that asksyou how you want to proceed. The options are to either rename the table name, or to copy thesettings. If you copy the settings, the table name in the Replication Settings for Tables table and allassociated entries in the settings tables will be changed to the new name. There will be noreplication settings for the old source table any more. Whereas in the latter case, all entries will becopied to the new name such that old and new source table will have identical settings apart fromthe table name.




5.3 Table Settings

November 2012 33

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 bothtables will have the same replication settings afterwards.

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

5.3 Table SettingsOn the right-hand side of the settings screen, there are the actual settings tables. Four of the fivesettings 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 beadded, 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 rightwithout having to navigate back to the previous screen.




Table Settings

34 November 2012

Figure 35 Screen for editing the table settings. This screen consists of four tab pages, one for eachof the four main settings tables. The first two buttons can be used to select or deselect all tableentries. The next two buttons are for adding and deleting lines followed by buttons for sorting theentries by their table names in ascending or descending order. In addition, you can import allsettings 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 tablename and structure, in the target system.




5.3 Table Settings

November 2012 35

Figure 36 IUUC_REPL_TABSTG describes the changes of the target table properties with respectto the source system.

By default, the table created in the target system will have the same name and structure as thesource table. However, it might be necessary to change the name or alter the table structuredepending on your requirements. For instance, tables from different sources could be replicated toone target system, some table fields might have become obsolete, or several fields could becombined into one field.

A new table name can be entered in the Target Table Name field. Modifications to the tablestructure can be achieved in two different ways (see Figure 37). Firstly, a different ABAP Dictionarydata type can be used. This type would be either defined in the source system or in the SAP LTReplication 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, thecheckbox Local Target Type must be selected. The second way for changing the target structure isto define deviations in IUUC_REPL_TAB_DV. This settings table can be accessed by using theEdit 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 differentABAP Dictionary data type is defined, this type will be used as starting point for later modificationsin 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, willbe 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 aconfiguration. By default, the target table will be dropped if it exists, and created again from the newconfiguration. This behavior has advantages regarding data and structural consistency but also hasits limitations if more than one source table is replicated into a target table. For each of the sourcetables, the target table would be dropped and a new one created thereby losing all data that hadalready 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 manyother 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.




Table Settings

36 November 2012

The size of read portions is the number of entries in one portion during the initial load for the defaultreading type DB_SETGET. It has no effect for other reading types, for example access plan, or fordelta 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 partitioncommand 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 hashpartitions selected by the fields Client (mandt) and carrid.

Table IUUC_REPL_TABSTG contains the following fields:

Field Description

Mass transfer ID

[not shown in UI]Mass transfer identifier of the configuration.

Table Name

[not an input field]

Name of the source table in the source system, unique key field; is

filled automatically from the active source table when adding a newline.

Target Table Type ABAP Dictionary type of the target table if different from source table;Could be structure (note that a structure does not define any keyfields), table type, or database table.

Local Target Type Target table type is defined on the replication server (‘X’) or sourcesystem (‘ ‘).

Target Table Name Name of the table in the target system.

No Drop Whenever a new table is added to a replication configuration, thetarget table is deleted from the target system (if it exists) and createdagain. Select this option in order to avoid dropping the target table, for

example if several source tables are replicated into one target.

Row Store Data will be stored in rows instead of columns (default for HANA arecolumns).

Size of Read Portions Number of records read in one package during the initial load whenreading type is 3 (db setget), default is 10000. Has no effect during thedelta replay phase or for different reading types.

Deviations f rom TableStructure[not an input field]

Indicates that the structure of target table deviates from the sourcetable, the deviations are defined in the table IUUC_REPL_TAB_DV.

Partition command Partition command when creating the target table in the target system.

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




5.3 Table Settings

November 2012 37

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 bedisplayed. If a different ABAP Dictionary type is used it will be displayed here, together with anychanges defined in table IUUC_REPL_TAB_DV.

5.3.2 Table IUUC_REPL_TAB_DVIUUC_REPL_TAB_DV provides a way to modify the table structure in the target system withoutcreating a new ABAP Dictionary type in either the source system or on the replication server. Thissettings table can be accessed from the Edit Table Structure pushbutton in the




Table Settings

38 November 2012

IUUC_REPL_TABSTG tab page (see

Figure 36).

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




5.3 Table Settings

November 2012 39

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




Table Settings

40 November 2012

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 realizedthrough custom ABAP coding that will be executed during processing. The code can be definedeither 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. Forevent-based rules, custom coding can be inserted at eight predefined points of processing. Allfields of source and target tables can be accessed. Whereas the latter are used to calculate atarget field from up to three source fields. Parameter rules are easier to use, but offer less flexibilitythan 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. Askipped 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 mustbe defined locally on the SAP LT Replication Server, whereas a line of code is stored directly in thesettings table IUUC_ASS_RUL_MAP.

A line of code will be stored directly in the settings table IUUC_ASS_RUL_MAP. No ABAPDictionary objects must be created. A serious limitation is the restriction to 72 characters for eachline of code; this means that only simple mapping rules can be realized. In contrast, ABAPDictionary includes do not have any size limitations and can therefore be used to implementcomplex 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.




5.3 Table Settings

November 2012 41

Figure 43 The settings for IUUC_ASS_RUL_MAP. The first input field, Event, determines whichtype of mapping rule is used. If the field Event is empty, parameter rules will be used, otherwiseevent-based rules are used. The next four fields are only relevant for parameter rules. The last twofields define the code either through an ABAP Dictionary include or directly in the settings table.

Field Description

Mass transfer ID

[not shown in UI] The mass transfer ID of the configuration.

Table Name

[not an input field]

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 addinga new line.

SAP Basis Release[not an input field]

The Basis release of the SAP source system. This field will be filledautomatically from the source system and also updated when importingsettings from file.

Event Event at which the provided mapping rules will be executed for event-based rules. For parameter rules, this field must be empty.

Export Field Name The receiving field for parameter rules; this field is not relevant for event-based rules.Accessed as e_ <fieldname> in the code.

Import Parameter 1 Import field for parameter rules; this field is not relevant for event-based

rules.Accessed as i_ <fieldname> _1 in the code.

Import Parameter 2 Import field for parameter rules; this field is not relevant for event-basedrules.Accessed as i_ <fieldname> _2 in the code.

Import Parameter 3 Import field for parameter rules; this field is not relevant for event-basedrules.Accessed as i_ <fieldname> _3 in the code.

Insert Include Name The name of the ABAP include that will be executed.

Insert Line of Code The line of code that will be executed

Table 2 Fields of the settings table IUUC_ASS_RUL_MAP.




Table Settings

42 November 2012

5.3.3.2 Parameter RulesParameter 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 andthe target field name must be entered in the Export Field Name field. Up to three fields of thesource 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 nameof the field entered as the export field in table IUUC_ASS_RUL_MAP. The three import parametershave 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 importparameters in table IUUC_ASS_RUL_MAP.

Two examples for parameter rules are given in Table 3Table 4.

Field name Value

Table Name SPFLI

SAP Basis Release 700

Event

Export Field Name CITYTO

Import Parameter 1 ‘DUMMY’

Import Parameter 2

Import Parameter 3

Insert Include

Name

Insert Line of Code E_CI TYTO = ‘ HONOLULU’ .

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

Field name Value

Table Name SPFLI


Event

Export Field Name CITYTO

Import Parameter 1 CITYTO

Import Parameter 2

Import Parameter 3

Insert IncludeName

Insert Line of Code I F I _CI TYTO_1 = ‘ HONOLULU’ . E_CI TYTO = ‘ HANA’ . ENDI F.




5.3 Table Settings

November 2012 43

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




Table Settings

44 November 2012

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 reditalics.

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 structureslike transparent tables. For more complex structures, such as cluster tables, the block events BOTand EOT are triggered before looping over the clusters, whereas the loop events BOL and EOL areexecuted 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 recordInsert target work area into target table

ENDLOOP

EOL—End 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 ABAPcommand MOVE-CORRESPONDING from the source table work area to the target structure. Thetarget structure is then inserted into the target table. The events for event-based rules arehighlighted in green. The individual field mapping of the parameter rules is in red italics.

Field name Value

Table Name SPFLI


Event BOR

Export Field Name

Import Parameter 1




5.3 Table Settings

November 2012 45

Import Parameter 2

Import Parameter 3

Insert Include

NameInsert 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 nowlinked to the Begin of Record event.

Field name Value

Table Name SPFLI


Event BOR

Export Field Name

Import Parameter 1

Import Parameter 2

Import Parameter 3

Insert IncludeName

Z_SPFLI _MAP

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.

* I NCLUDE Z_SPFLI _MAP

“ r edi r ect al l Honol ul u f l i ght s t o Hana

I F <wa_s_spf l i >- ci t yt o = ‘ HONOLULU’

OR <wa_s_spf l i >- ai r pf r om = ‘ HNL’ .

<wa_r _spf l i >- ci t yt o = ‘ HANA’ .

<wa_r _spf l i >- ai r pt o = ‘ HNM’ .

<wa_r _spf l i >- count r yto = ‘ US’ .

ELSE.

“ ski p al l ot her r ecor ds

SKI P_RECORD.

ENDI F.

Table 8 Example of an ABAP include for event-based rules. All table fields can be accessedthrough field symbols. Instead of one event-based rule, three parameter rules must be defined toachieve the same goal.




Table Settings

46 November 2012

5.3.4 Table IUUC_SPC_PROCOPTIn the third tab page, you can use the settings table IUUC_SPC_PROCOPT to customize the codefor the triggers that record the changes in the source tables. Note that this option is intended forexpert 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 thedatabase triggers.

Any rules that you define here only applicable for the replication process, they do not affect theinitial load.

Figure 44 The trigger options for recording changes can be customized in tableIUUC_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 Description

Mass transfer ID

[not shown in UI] The mass transfer ID of the configuration

Table Name

[no input field in UI] The name of the source table in the source system. This is a uniquekey field that is filled automatically from the active source table whenadding a new line

No of Parallel Jobs The maximum number of jobs that will be used for loading the table

Field Name for Parallelization

The field name used for parallelization

Seq. No. The sequence number for processing the source tables. Tables withlow numbers will be loaded first




5.3 Table Settings

Reading Type The reading type for the table

Table 9 Relevant fields of the table IUUC_PERF_OPTION.

Reading type Descrip tion

1 – Access Plan Calculation An access plan is used for reading the table; the data will besplit into portions which are then loaded into the target system.

2 – Pool tables Similar to the access plan reading type but the entire table willbe read as one portion.

3 – DB setget (Cluster tables) Default option. Uses the function module DB_SETGET to fetcha predefined number of entries from the source table. Theseentries are ordered by their primary keys.

4 – INDX CLUSTER (IMPORTFROM DB)

Opens a database cursor in the source system and copies thedata from the source table into an INDX table on the source

system. The entries of the INDX table are then replicatedordered by their indices.

5 – INDX CLUSTER with FULLTABLE SCAN

Similar to the former type 4 but forces a full table scan.

6 – INDX CLUSTER fil led f romexternal

The INDX table is filled from an external report. Note that thisreading type is not used for HANA replication.

7 – INDX CLUSTER chi ld tableFTS

This reading type is not used for HANA replication.

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

hana slt config en

Documents