slt devnews sp09

8/19/2019 Slt Devnews Sp09

http://slidepdf.com/reader/full/slt-devnews-sp09 1/42

AGS SLO Product Management, SAP AG

Real-Time Data Replication with

SAP Landscape Transformation Replication Server DMDevelopment News – Product Status - Use Cases - Roadmap



© 2015 SAP AG or an SAP affiliate company. All rights reserved.

The information in this presentation is confidential and proprietary to SAP and may not be disclose

permission of SAP. This presentation is not subject to your license agreement or any other serviceagreement with SAP. SAP has no obligation to pursue any course of business outlined in this doc

presentation, or to develop or release any functionality mentioned therein. This document, or any

and SAP's strategy and possible future developments, products and or platforms directions and fu

subject to change and may be changed by SAP at any time for any reason without notice. The inf

document is not a commitment, promise or legal obligation to deliver any material, code or functio

document is provided without a warranty of any kind, either express or implied, including but not li

warranties of merchantability, fitness for a particular purpose, or non-infringement. This documen

purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors o

document, except if such damages were caused by SAP´s willful misconduct or gross negligence

All forward-looking statements are subject to various risks and uncertainties that could cause actu

materially from expectations. Readers are cautioned not to place undue reliance on these forward

which speak only as of their dates, and they should not be relied upon in making purchasing decis

Legal disclaimer




Agenda

General status update on positioning

and customer projects

Development News DMIS2011 SP9

Product Roadmap Update 2015

Technical Prerequisites & Sizing

Summary



Overview


http://slidepdf.com/reader/full/slt-devnews-sp09 5/42© 2015 SAP AG or an SAP affiliate company. All rights reserved.

Replication

Real-time or scheduled

Delta capturing to minimize transfer volume

Transformation

Filtering by using selective criteria

Adjustment of tables

Conversion of data, e.g. to make sensitivedata anonymous

Installation & operation Deeply integrated within SAP landscapes to

reuse existing installation and monitoring

capabilities

Monitoring with SAP Solution Manager 7.1

SP5 onwards

SAP LT Replication ServerProduct description

SAP LT Replication Server (SLT) is a standard software to move data in real-time between differen

same network, wide area networks, or into the cloud to have the information at the right place at the right

The software helps to feed analytical systems with up-to-date business information from the productiv

support the acceleration of large volume transactions executed in SAP HANA, enables real-time repo

transfer volume for SAP BW and enables the synchronization between different systems.



Big Data provisioning with SAP LT Replication Server

SAP HANAwith optimized capturing

SAP Business Suite

Sources

Native DB

Pool, Cluster, INDX *) (i.e. HCM payroll

and SAPScript tables) tables

Unicode & non-Unicode

Replication of Views

Support of NW 4.6c and higher

SAP ASE, Oracle

MS SQL, Max DB

IBM DB2, DB4, AS/400, Informix

Unrest r ic ted change data captur ing

wi th almos t zero impact

SAP LT

Replication Server

Transformation and filter capabilities

Integrated data type mapping

Scalable NetWeaver instance Replication staging for HA / DR

Option to load out of archives

Real-Time

Batch

Support o f LAN, WAN

and c loud deployments

Robust and p roven archi tecture

wi th m ore than 4500 custom er

instal lat ions*) available on a project basis

Standardtable-based

replication

New

application-based

replication



SAP LT Replication ServerProduct architectural concept

SAP LT Replication Server is used to load and replicate data in scheduled or real-time mo

non-ABAP based source system into SAP HANA, SAP Data Services, SAP BW or any sy

ABAP or a supported Database platform.

Supported Databases

MSFT SQL Server Enterprise Edition

Oracle Enterprise Edition

IBM DB2 LUW/ UDB (DB6)

IBM DB2 zSeries

IBM DB2 iSeries (former AS/400)

IBM Informix

SAP MaxDB

Sybase ASE

SAP HANA

SAP LT Replication Server is embedded as middleware in your landscape and can be deployed w

existing operations. You use the software to feed several target systems with real-time informatio

business scenarios and requirements.



Customer figures 2015/7

5,416 customer landscapes

26bnrechighest load (

>30k tableswith one SLT

>70with on

70+ ABAP systemsconnected with one SLT

45 non-ABAP systemsconnected with one SLT

>20miohighest change ra

© 2014 SAP SE or an SAP affiliate company. All rights reserved.

>95% data transfeIS-U /CRM to SAP BW via



Largest SLT Customer Installation

71 ERP geographically distributed systems (some non-SAP) with approx. 21000 tables

(financial and logistics) feeding one central HANA database

overall loaded HANA DB size: - 88 billion records

Delta Updates from peripheral systems each hour:

Inserts - 10M

Deletes - 5M

Update - 14M

Data transfer occurs for most applications – Finance, Logistics, Sales

BSEG with 2 billion records initial loads

No noticeable Network impact with current set up.

SLT Server Instance Hardware: 4 Application servers with 64 GB RAM

HANA database: 10 nodes 5 TB scale-out

Implementing new hardware which will reduce the landscape requirements to 4 nodes.

Live with data feed to HANA since 2013

Data feed change is transparent to end users using existing dashboards

>30kwith o

500-80with one co

70+ ABAP syconnected with on



SLT Customer EnBW

41 ERP systems connected to one SAP Business Warehouse (BW on Oracle)

using ODP scenario, managed with minimum effort (0.1 FTE)

Data transfer over SAProuter from SAP IS-U to SAP BW: 200 records per second

108 tables in replication

Company wide used SLT for data replication from SAP CRM to SAP BW on HANA and add. MSSQL Server

95% data transfer reduction from full loads (350 GB, more than 12 hours every night)

to delta loads

No noticeable Network impact with current set-up.

Replacement of CRM extractors with SLT functionality

Replacement of generic extractors with SLT (Database Views)

>95% redof nightly batch load with d

SLT lowers0.1 FTE to ma

company-wide data

41 ABAP sysconnected with one SLT



Development News

DMIS 2011 SP09




Development News DMIS 2011 SP9New Main Features

• General Availability for scenario data load/replication from SAP source systems to o

You can now load or replicate data from a connected SAP ABAP based source system to non-ABAP based target sy

database connection. This works for all target systems based on SAP released database platforms according to SAPMatrix (PAM) for the underlying SAP NW ABAP Server on which the SLT Server functionality is deployed on.

• Add filter and parallelization settings into LTRS UI

This UI replaces the formerly manual maintenance of table DMC_ACSPL_SELECT

• Real-time Preview Mode for SAP BW replication

New Data Preview in SAP BW for source tables for displaying a small number of records instead of full load for chec




Development News DMIS 2011 SP9 Replication to non-ABAP targets

Scenario

Load or replicate data from a connected SAP ABAP based source system*) to non-ABAP based

target systems via a direct database connection. This works for all target systems based on SAP

released database platforms according to SAP‘s Product Availability Matrix (PAM).

Value Proposition

● Offers data provisioning and delta load capability for all tables transferred to non-HANA and

non-ABAP based analytical or transactional applications

● Sync your business data in real-time, while minimizing the necessary data transfer volume

*)Data Replication from non-ABAP based source systems to non-ABAP based target systems is still available on project base only. To request a project engagement

open a ticket on message component HAN-DP-LTR.

Note: In order to configure

non-ABAP based target sys

definition of a direct databa

based source systems. The

help applies for this scenar

Authorization Aspects an

Source System:

To access a non- ABAP tar

connection, the relevant us

necessary authorizations in

Contact your system admin

relevant authorizations as d

The SLT Server (ABAP) sy

from the database. To perfo

a specific table from a give

have privileges for the follo• Selecting from the table

• Creating a table in the g

table)

• Deleting the target table

after a stop replication)

• Creating synonyms for th

• Deleting the synonyms

Depending on the specific e

process of granting privilegFor more database specific

Replication related SLT No




Development News DMIS 2011 SP9Improving the performance of the replication process (1/2)

Scenario and Value Proposition

Replication of tables with very high change rates by dividing the logging table content into ranges. Dividing the table intoperformance because multiple jobs can transfer the data for each range at the same time.

You can improve the performance of the replication process for the following

scenarios:

• Replication via ODP Framework (SAP BW and SAP DS)

• Replication into PSA storage (SAP BW)

• Replication into a SAP HANA DB schema

• Replication into a SAP ABAP-based system (table based)

• Replication into a SAP ABAP-based system into the Application layer is technically

possible, but may be limited by application logic (sequencing issue)

• basically all target scenarios are supported

The feature ‘Specify Ranges Manually’ is available for source systems on the

following database platforms:

• ORACLE 11.2 64-Bit

• DB6 (DB/2 10.1 LUW 64-Bit)

• DB4 (DB2/400 V7R1)

• MS/SQL (MS SQL Server 2008/X86_64 & 2012/X86_64)

• SAP HANA 1.00




There are two option to configure parallel replication on one table:

• Specify Ranges ManuallySLT will take care to build equally distributed portions according

the specified grouping field(s). Not available on all DB platforms (see previous slide).

• Specify Ranges Manually (Expert )You can explicitly define the number of ranges as well as the

range conditions for building the portions. This feature is available on all

supported DB platforms.

To identify which field can be used for range calculation, transaction DB05

can be used to analyze the distinct values of a table.

For huge tables the analyze should be started in a background task. The result

is stored in the spool of background job TABLE_ANALYSIS_<table name>.

Development News DMIS 2011 SP9Improving the performance of the replication process (2/2)




Development News DMIS 2011 SP9Create Filter for Initial Load

You can further improve the initial load by filtering the

data that is replicated to the target system, and by

dividing the initial load into ranges.

If you only require a subset of the data in your target system,

you can improve the performance of the initial load by only

transferring the data you need. To do this, you specify filter

conditions for the table.

Note that if you are using f ilters and ranges together, you

must ensure the data is valid.

For example if you use filters to exclude certain data, then

do not create ranges that refer to this data.

CautionThe ranges that you specify must not overlap. If they overlap,

the overlapping content will be replicated to the target system

more than once.




Development News DMIS 2011 SP9Realtime Preview Mode for SAP BW replication

New Data Preview in SAP BW for source tables:

After activation of a DataSource in SAP BW, a Data

Preview can be displayed.

Use a small number of records instead of full load for

checking

Check if the data is transferred correctly

Check if changes on the table structure performed in

SLT (LTRS) are working

Check if views are assigned correctly

No entry in LT Replication Server Cockpit

No entry in ODQMON

No creation of infopackage/DTP required for preview




Development News DMIS 2011 SP9some more Enhancements & Corrections

• Optimized Update Trigger for SAP HANA (Revision 91 required)

A special implementation of update triggers to increase performance on SAP HANA DB

• Support of SAP HANA multitenant database containers

(introduced with HANA 1.0 SPS9)

• LTRS: Additional Validation Checks

Additional checks added to the automatic syntax check when trying to set a transformation rule to ‘released’.




Development News DMIS 2011 SP9Support of SAP HANA multitenant database containers

Logical Port Number

• If you are replicating data to SAP HANA, and are using a standard SAP HANA deployment scenario (one HANA DBM

schema), then you must specify the value '15' in the field Logical Port Number .

• If you are replicating data to SAP HANA and are using several databases on one SAP HANA system (multitenant data

must specify the logical port number of the multitenant database container.

Note that you can determine the logical port number by logging on to the SAP HANA system, and running the followin

SAP HANA studio:

SELECT SUBSTRING(SQL_PORT,4,2) FROM "SYS"."M_SERVICES" WHERE SERVICE_NAME = 'indexserver'




New Features DMIS 2011 SP9 Advanced Replication Settings (LTRS): Enhanced Syntax Check for R

Added additional checks to the automatic syntax check when trying to set a rule to released.



Product Roadmap Overvie




This is the current state of planning an

Today Future DirectioPlanned Innovations

SAP Landscape Transformation Replication ServerProduct road map overview - key themes and capabilities

Strategic developments• Replication from ABAP to ABAP systems (covering

the complete SAP Business Suite)

• Data provisioning for SAP BW & SAP Data Services

New features

• Generic parallel replication for all scenarios available forSAP source systems on most DB platforms

• Templates to manage and reuse configuration settingsacross tables, configurations, and systems

• Integrated data consistency check with repair mode

• Replication logging capability to support point-in-timerecovery

• Support of DB views as source objects (ABAP and non- ABAP sources)

• Filtering option for records in source system

• Optimized delta recording for SAP HANA as a sourcedatabase

Continuous improvements

• Deeply integrated within SAP landscapes to reuseexisting administration and monitoring capabilities, i.e. ofSAP Solution Manager, SAP NW Application Server andSAP HANA Studio

Strategic developmen

• Consistent replication fo

(continued)

• Transactional consisten

• SAP BW scenario:

Framework to offer an a

complex objects to enab

the transfer volume for

• Replication to multiple t

capability without limitat

• Integration of Hadoop /

target

Release DMIS 2011 SP8

Strategic developments

• Exclusive middleware for application-based replication

within modern SAP Business Suite solutions (i.e. Central

Finance scenario that is part of SAP Simple Finance)

• Object-based replication of complex SAP Business Objects

• Release of standard scenarios for data replication into nativedatabases (DB platform support according to SAP NW PAM)

New features

• Integration in SAP HANA EIM (Smart Data Integration UI)

• SAP BW scenario: Alternative for extracting data for complex

objects to enable real-time replication and to reduce the

transfer volume for SAP BW

– Working on a prioritized list of classical BW extractor logic whichcan be replaced with SLT replication

Continuous improvements

• Tools and documentation for reconfiguration

of replication scenarios after operational events like upgrade,

OS/DB migration or system refresh/copy

• Improved performance when replicating from non-ABAP

based sources

• Managing different data retention times in source and target

systems

• Support of new SAP HANA technology features




SAP Landscape Transformation Replication Server Application-based replication

Scenario

Middleware for application-based replication within modern SAP Business Suite solutions.

Value Proposition

● With the new S/4HANA area, a lot of existing SAP solutions will change their complex data models to a simplified arch

complex, multi-ERP system landscapes and/or customers who are unable to upgrade to this new simplified solutions

transition, a side car like approach. Traditional table to table replication cannot be used due to the complex structural r

● To overcome this problem, SLT is used to harmonize business data from multiple sources into one central application.

replication will be done with SAP LT Replication Server. DB triggers will detect all update/insert/deletes and will send itServer, which will feed an application interface on the target system. The application interface on the target will ensure

One SAP application that is using this approach is the Central Finance scenario that is part of SAP Simple Finance





SAP Landscape Transformation Replication Server SAP Simple Finance

Scenario

SAP LT Replication Server is the key enabler for all customers that do not want to migrate their existing FI system directl

to get the benefits of SAP Simple Finance.

Value Proposition

● Customers with complex, multi-ERP system landscapes or a lot of merger & acquisition activities, or customers who a

upgrade can use SAP LT Replication Server to harmonize their FI data from multiple sources into one central journal


SAP L d T f ti R li ti S




SAP Landscape Transformation Replication Server Replication to non-ABAP targets

This is the current state of planning a

Scenario

Load or replicate data from a connected SAP ABAP based source system*) to non-ABAP based target systems via a dire

This works for all target systems based on SAP released database platforms according to SAP‘s Product Availability Mat

Value Proposition

● Offers data provisioning and delta load capability for all tables transferred to non-HANA and non-ABAP based analytic

applications

● Sync your business data in real-time, while minimizing the necessary data transfer volume

*)Data Replication from non-ABAP based source systems to non-ABAP based target systems is still available on project base only. To request a project engagement open a ticket on message component HAN

SAP L d T f ti R li ti S




SAP Landscape Transformation Replication Server Object consistent replication for complex SAP data objects

Scenario

To achieve outstanding performance, the replication only processes data on table level without taking any business conte

approach is sufficient for most applications that are available for SAP HANA. For the small number of applications with c

requirements, the upcoming solution will ensure consistent replication for complex SAP objects at any time.

Value Proposition

● SAP data objects representing business data may consist of many technical separate tables on database level. Some

real-time replication of SAP data objects preserves data object consistency for these objects


SAP LT R li ti S 2 0 N F t




SAP LT Replication Server 2.0 – New FeaturesIntegration in SAP HANA EIM (Smart Data Integration UI)

Scenario

SAP LT Replication Server is integrated into SAP HANA Smart Data

Integration UI.

Value Proposition

• SAP LT Replication Server continues to support data sourcing via SAP

HANA user centric UIs. Like with SAP HANA Studio build-in Data Provisioning

UI and Data Modeler, SAP LT Replication Server integrates into SAP HANA

Smart Data Integration UI to allow users in typical data consuming roles to

directly utilize real-time data replication with/without data transformation

capabilities on the fly

SAP HANA Smart Data Integration U


SAP LT R li ti S 2 0 N F t




SAP LT Replication Server 2.0 – New FeaturesSAP BW: Streamlined data extraction

Scenario

SAP LT Replication Server is drastically reducing the amount of data which is transferred to SAP BW:

• Delta-capability to minimize the transferred volume to only changed data

• Cross-client-setup for scenarios dealing with data from multiple clients

Value Proposition

• Reduce amount of data with SLT technology:

Only deltas are replicated from the source Shorter transfer time, only small amount of data,

no program in target necessary

•With SLT, all data from several clients can be writteninto one table, reducing the amount of DataSources,

DTPs, Process Chains… to one.

• Opportunity for replacing BW Extractors:For generic extractors, or simple SAP extractors,

they can be replaced with database views

by the customer.

In addition, SAP supports the replacement of complex

extractors on project basis.

Standard BW Extraction


SAP LT Replication Server 2 0




Tools and documentation for reconfiguration of replication scenarios after operation

upgrade, OS/DB migration or system refresh/copy

● Process simplification and better documentation of necessary steps to execute in order to continue/rescenarios after system maintenance events

Improved performance when replicating from non-ABAP based sources

● Generic parallel replication for non-ABAP based source systems, too

Managing different data retention times in source and target

● SAP LT Replication Server provides unique capabilities to identify and filter out data deletions in SAP A

systems during the process of SAP Data Archiving to allow independent data retention policies in souri.e. a SAP HANA-based data warehouse solution can keep application data even if the data has been

source system

Support of relevant actual HANA technology features

● Reserved development capacity to ensure, that SAP LT Replication Server can support new importan

features, i.e. extended table type & multi-tenant database containers (SAP HANA 1.0 SPS9)

SAP LT Replication Server 2.0Planned continuous improvements


SAP Landscape Transformation Replication Server




SAP Landscape Transformation Replication ServerFuture direction

Object consistent replication for complex SAP data objects (continued)

● Replication based on a business object, like sales orders, customers, or contracts

● Easier and object-driven way of building new applications that require real-time information from the productive environment

SAP BW scenario: Alternative for extracting data for almost all complex objects to enable real-tim

replication and to reduce the transfer volume for SAP BW (continued)

● Framework to offer an alternative for extracting data for complex objects to enable real-time replication and to reduce the transfer volume

(continued)

● Continue to work on recommendations and how-to guides for replacing complex BW extractors with SAP LT Replication Server technolog

Replication to multiple targets: Redesign of 1:N replication capability without limitation of target system● Connect multiple consumers to one single data source while reading the data only once and provide the data in near real-time via a queu

target systems.

Integration of Hadoop / Hive as data source / replication target

● There is a growing demand for reading from / writing to a Hadoop data infrastructure. As of today SLT connectivity to Hadoop works via th

SAP Data Services. In order to reduce complexity and TCO, it is planned to investigate and invest in to a direct connectivity capability into




Technical Prerequisites &

Sizing

SAP LT Replication Server





Installation optionsSAP LT Replication Server is technically an ABAP Add-on to the SAP NW ABAP Server. Therefore, several installation

possible:

On a SAP ABAP-based source system, i.e. a SAP Business Suite System (with SAP Basis 7.0.2 or higher)

On a separate SAP NW ABAP Stack (Release 7.0.2 or higher)

On a SAP ABAP-based target system, i.e. a SAP BW or SAP Business Suite System (with SAP Basis 7.0.2 or higher

SAP source

system

Non-SAP sourcesystem

SAP source

system

SAP HANA

SAP NW ABAP Stack

SAP sourcesystem

SAP HANA

SLTServer

SLT

Server

SAP NW ABAP Stac

SAP source

system

Non-SAP sourcesystem

SAP ABAP-based System(i.e. SAP BW, SAP Business Suite, etc.

SLTServer

SLT

Server

Recommendation: In order to separate workload a separate SLT Server system is the most preferable optio

Especially when expecting high data transfer rates and/or to keep independent patch/release cycles.

Technical Prerequisites and System Set-Up Information




SA

s

SAP LT Replication

Server *)

SAP / non-SAP

Source system

DB

Connection

RFC or DB

Connection

Installation

SAP: Respective DMIS 2010/2011

version (DMIS 2011 SP2-9 or equiv.) ***)

SAP: Minimum SP level requirements may exist **)

non-SAP: no software installation required

Basic Configuration

Optional: define separate table space

for logging tables

SAP: Define RFC user with appropriateauthorization

Non-SAP: Create DB user for Secondary DB

connection

System Requirements

SAP: All ABAP-based SAP Systems starting with

R/3 4.6C, all supported OS/DB’s platforms

SAP & Non-SAP: OS/DB restrictions of related

SAP NetWeaver stack may apply (see at

http://service.sap.com/pam)

Installation

Add-on DMIS 2011 ***)

(Latest support pack level: SP9)

Basic Configuration

SAP: Define RFC connection to source system

Non-SAP: Define DB connection to source system

Define DB connection to HANA system

Define max. number of jobs to be used for data replication

System Requirements

According to Quick Sizing

Ensure sufficient number of available background jobs!

Installation

HANA SPS3-10functionality fully

HANA modeler

Basic Configuratio

Create a DB use

*) SAP LT Replication Server can run on any SAP system with SAP NetWeaver 7.02 ABAP stack or

for example on Solution Manager 7.1 or the source system – it does not have to be a separate S**) A few new SLT features available since HANA SPS05 may require DMIS_2010 SP09 / DMIS_20***) SAP customers who run other DMIS-based applications can apply DMIS_2010 in the source and S

Technical Prerequisites and System Set-Up Information for SAP LT Replication Server (with SAP HANA 1.0 SPS05 or higher)


http://service.sap.com/pam

http://service.sap.com/sap/support/notes/2191214





SAP LT Replication ServerDB Supportability Matrix for Source Systems

Database

Technical availability

ABAP sources non-ABAP sources (*)

MSFT SQL Server Enterprise Edition OK OK

Oracle Enterprise Edition OK OK

IBM DB2 LUW/ UDB (DB6) OK OK

IBM DB/2 zSeries OK OK

IBM DB2 iSeries (former AS/400) OK Ok

IBM Informix OK OK

SAP MaxDB OK OK

Sybase ASE

OK

(with DB Version 15.7.0.11)

OK

(with DB Version 15.7.0.11)

SAP HANA OK OK

For non-ABAP source systems, the customer database license needs to cover a permanent database

connection with 3rd party products like SAP LT Replication Server.

(*) Since a DB connection from LT replication server to a non-ABAP system is required, the OS/DB restrictions of SAP NetWeaver 7.02 or h

apply (see at http://service.sap.com/pam)

N

SLT

con

und

Ser

Ava

utili

Ver

DB

a co






SAP LT Replication Server – Software Release Strategy

There are two versions of SAP LT Replication Server available to resolvepotential conflicts with other SAP SLO products shipped within the same DMISAdd-on (SAP LT and TDMS)

SAP LT Replication Server 1.0 (based on Software Component Version DMIS 2010)can be deployed on SAP R/3 4.6c up to SAP NW ABAP Server 7.02/7.1x

SAP LT Replication Server 2.0 (based on Software Component Version DMIS 2011)can be deployed on SAP NW ABAP Server 6.20 or higher

Technically, both DMIS versions offer SPs with the same coding level toreduce the need for upgrade.

DMIS_2011 SP04 and DMIS_2010 SP09 (see also SAP Note 1824710)

DMIS_2011 SP5 (see also SAP Note 1882433): No equivalent DMIS_2010 SPversion in parallel!

DMIS_2011 SP6 and DMIS_2010 SP10 (see also SAP Note 1958809)

Current status

Since DMIS_2011 is released, this is the recommended product version for all new installations (both SAP LT Rep

systems).

SAP customers who run other DMIS-based applications (that require DMIS_2010 in the SAP source system) can use and/or SLT system. See also SAP Note 1691975.

For HANA customers using SLT with DMIS_2010 the switch (“technically” an upgrade) to DMIS_2011 will be a non-dis

Since DMIS 2010 SP10 / 2011 SP6 there will be no further code-equal DMIS2010 after SP10 … only bug fixing!

SLT and HANA Compatibility:

9

Quick Sizing with SAP SLT Sizing Guide

https://service.sap.com/sap/support/notes/1824710













Quick Sizing with SAP SLT Sizing Guide

Required Information / Input Parameters

Numbers of configurations

Numbers of tables per configuration

Details about each table:

– Table type [transparent/cluster]

– Number of records [rowcount]

– Size of single record (<>1500 bytes/record)

– Numbers of columns (S: < 150, M: 151...250, L: > 250)

– Expected change rate [changes per hour]

– Complex data transformations required [y/n?]

Max. tolerable initial load time [hours]

Max tolerable replication latency [sec]

ODP/SLT Scenario?

Replication Logging active?

With these input parameters you can estimate the appropriate system resource requ

You find all details in the official Sizing Guide.

IUUC_SCHEDULE_TABLE_OPER_INFO is a report that can analyze the tables that will be relevant for your replication project, and provide sizin

plan your hardware requirements accordingly. This report It is shipped with DMIS 2011 SP8 (or higher), or can be implemented with SAP note 2061415





Summary and Outlook

SAP LT R li ti S B fit




SAP LT Replication Server - Benefits

Natively leverages SAP ABAP Data Objects for replication on application level: Data load, as well as real-time or scheduled replica

– Pool, Cluster, INDX (for example HCM payroll and SAPScript tables) *)

– Unicode & non-Unicode

– Replication of views

– Supports all SAP Systems releases starting from SAP R/3 4.6c

– Table-based and application-based replication

High volume change data capturing with almost zero impact and point-in-time recovery capability

Complex transformation capabilities, such as filtering, data structure adjustments, data conversion, anonymization of sensitive d

Deeply integrated within SAP landscapes to reuse existing administration and monitoring capabilities, i.e. of SAP Solution Mange

and SAP HANA Studio

Connects to SAP HANA data sources with optimized change capturing

Connects to native Databases as data sources (according to the SAP NW Product Availability Matrix)

Connects to native Databases as data targets (according to the SAP NW Product Availability Matrix) via project engagement

Real-time or scheduled data replication into SAP BW reduces the amount of overnight data uploads. Delta updates on BW DataS

mechanisms, for ABAP-based systems as well as non-ABAP based systems on all SAP supported DB versions (according to PAM).

SAP Landscape Transformation Replication Server (aka “SLT”) is a perfect choice for all customers who n

real-time or scheduled data replication from SAP and Non-SAP sources with the option to accomplish even co

transformations on the fly.

Information Sources




Information SourcesFor Customers and Partners

Web Sites

SLT @ SAP Service Marketplace: http://service.sap.com/hana

SLT @ SAP Help Portal: http://help.sap.com/hana

SLT @ SCN: http://scn.sap.com/community/replication-server

SAP LT – important Documents and Links New SLT – Introduction Video

SLT – Overview Presentation

Installation Guide

Security Guide

Operations Guide

HANA & SLT Sizing; SLT Sizing Guide

Important SLT Notes: see in SLT General Note 1605140

SAP Note 2191214 - Installation/Upgrade SLT - DMIS 2011 SP9.

Training SLT100: 3 day class

as e-learning HA350: SAP HANA

HA200 SAP HANA

Administration

HA300 SAP HANA

Modeling

Specific customized

available on deman

http://service.sap.com/hana

http://help.sap.com/hana

http://scn.sap.com/community/replication-server

http://www.sap.com/demos/videos/distribute/sap-it-replication-server-real-time-data-integration-for-sap-hana-12-ov-us.wmv



https://admin.sdn.sap.com/irj/scn/index?rid=/library/uuid/a0ead886-8a05-3010-daa7-9ace6bc7845f



http://service.sap.com/~sapidb/011000358700000829322013


http://service.sap.com/~sapidb/011000358700000829342013E

http://service.sap.com/sizing

https://service.sap.com/~sapidb/011000358700001373882012E/SAP_SLT_Sizing_Guide_V1_2.pdf





https://service.sap.com/~sapidb/011000358700001373882012E/SAP_SLT_Sizing_Guide_V1_2.pdf



http://service.sap.com/~sapidb/011000358700000829342013E














http://help.sap.com/hana

http://service.sap.com/hana




Thank You!

Astrid Tschense-Oesterle

AGS SLO Product Management

[email protected]

Roland Hamm

AGS SLO Product Management

[email protected]

Tobias Koebler

AGS SLO Produ

tobias.koebler@

Contact information:

© 2015 SAP AG or an SAP affiliate company All rights

mailto:[email protected]











© 2015 SAP AG or an SAP affiliate company. All rights

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.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation

SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services

in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SA

other countries.

Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

© 2015 SAP AG oder ein SAP-Konzernunternehmen.

http://www.sap.com/corporate-en/legal/copyright/index.epx







Alle Rechte vorbehalten.

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne d

Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert w

Einige der von der SAP AG und ihren Distributoren vermarkteten Softwareprodukte enthalten proprietäre Softwarekomponenten anderer Sof

Produkte können länderspezifische Unterschiede aufweisen.

Die vorliegenden Unterlagen werden von der SAP AG und ihren Konzernunternehmen („SAP-Konzern“) bereitgestellt und dienen ausschließ

Der SAP-Konzern übernimmt keinerlei Haftung oder Gewährleistung für Fehler oder Unvollständigkeiten in dieser Publikation. Der SAP-Konz

und Dienstleistungen nach der Maßgabe ein, die in der Vereinbarung über die jeweiligen Produkte und Dienstleistungen ausdrücklich gerege

enthaltenen Informationen ist als zusätzliche Garantie zu interpretieren.

SAP und andere in diesem Dokument erwähnte Produkte und Dienstleistungen von SAP sowie die dazugehörigen Logos sind Marken oder e

AG in Deutschland und verschiedenen anderen Ländern weltweit.

Weitere Hinweise und Informationen zum Markenrecht finden Sie unter http://www.sap.com/corporate-en/legal/copyright/index.epx#tradema



