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 DM Development News – Product Status - Use Cases - Roadmap
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
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
• 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
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 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
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 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
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 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
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)
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!