SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

download SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

If you can't read please download the document

Transcript of SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    1/44

    SAP Landscape Transformation (LT) Replication Server

    Overview and Development News for

    DMIS_2010 SP09 / DMIS_2011 SP4

    Michael Erhardt / Tobias Koebler / Roland HammAGS SLO Product Mgmt. March 2013

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    2/44

    2013 SAP AG. All rights reserved. 2

    Agenda

    Status and Roadmap

    Software Version and Shipment related News

    Development News

    Update: Replication into a BW Data Source

    Q&A

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    3/44

    Overview,

    Positioning, & Outlook

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    4/44

    2013 SAP AG. All rights reserved. 4

    SAP Landscape Transformation Replication Server (SLT)Status as of March 2013

    SAP Landscape Transformation Replication Server (SLT) is the most widespread real-time data

    replication and incremental data loading offering for SAP and non-SAP sources (for SAP HANA

    DataMart scenarios, HANA Content and Accelerators, SAP BW on HANA, etc.)

    Actual Market Situation:

    At least 80%of SAP HANA Datamart Scenario customers are using SLT, (not considered other use cases, such as

    BW on HANA, HANA Accelerators and B1 Analytics, )

    Real-timedata provisioning is still a key selling point for HANA customers

    BW customers see that an incrementaldata loading capability is a decisive advantage

    Approx. 200 different Customers actively using SLT (derived from CSN Message statistics)

    A lot of the HANA customers connect also non-SAP sources with SLT

    High customer satisfaction with robust SLT technology

    Build-in data transformation capabilities (Migration Workbench) are rated as a decisive advantage

    SAP internal & external SLT expert community is still growing fast

    Customers request guidance in operations aspects for the entire HANA stack (incl. SLT)

    Landscape design & sizing recommendations

    Maximize performance of initial data load

    Efficient monitoring and trouble shooting

    We receive a lot of external / internal requests to expand SLT technology to more use cases, for example

    to support other targets than SAP HANA,

    A heterogeneous warm standby solution for SAP Business Suite Systems, etc.

    http://upload.wikimedia.org/wikipedia/de/thumb/2/2b/Petrochina_logo.svg/38px-Petrochina_logo.svg.pnghttp://files.softicons.com/download/system-icons/apple-logo-icons-by-thvg/png/256/Apple%20logo%20icon%20-%20Aluminum.pnghttp://upload.wikimedia.org/wikipedia/de/thumb/2/2b/Petrochina_logo.svg/38px-Petrochina_logo.svg.pnghttp://upload.wikimedia.org/wikipedia/de/thumb/2/2b/Petrochina_logo.svg/38px-Petrochina_logo.svg.pnghttp://s.apsrv.de/images/logos_tm/30x30white/VW.gif?1344939801http://s.apsrv.de/images/logos_tm/30x30white/VW.gif?1344939801http://h50146.www5.hp.com/enterprise/casestudy/yodobashi3/images/yodobashi_logo.gifhttp://s.apsrv.de/images/logos_tm/30x30white/VW.gif?1344939801http://upload.wikimedia.org/wikipedia/de/thumb/2/2b/Petrochina_logo.svg/38px-Petrochina_logo.svg.pnghttp://www.conagrafoodservice.com/images/common/footer/conagra_logo.gifhttp://files.softicons.com/download/system-icons/apple-logo-icons-by-thvg/png/256/Apple%20logo%20icon%20-%20Aluminum.pnghttp://h50146.www5.hp.com/enterprise/casestudy/yodobashi3/images/yodobashi_logo.gif
  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    5/44

    2013 SAP AG. All rights reserved. 5This presentation and SAPsstrategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document isprovided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement

    SAP LT Replication Server for SAP HANARoad map at a glance (planned innovation & future direction)

    PLANNED INNOVATIONS, FUTURE DIRECTION

    SAP LT Replication ServerFeatures

    Current release

    (DMIS 2010 SP9 /

    DMIS 2011 SP4

    for SAP HANA SPS05)

    Delivered!

    New Scenario/Use Case: SLT for SAP BW:o general availability planned by end of march 2013

    New Features Improved usability & stabilityo LTR UI Improvements:

    o two new health checks (Job Analyzer and Table Health check)o SLT Configuration UI: Initial Load Mode "Resource Optimized" vs. Performance Optimized"o Redesign of the Statistics view: You can switch between the latency or the throughput view.o Display/change Settings for Statistical Datao You can define the language used to create the column texts on HANA sideo Job options: The number of data load , replication and access plans calculation jobs is

    customizableo New Authorization Roles

    o New Administration/Monitoring UI Transaction LTRC: LT Replication ServerCockpito LTRC: Data Provisioning UI supporting the SLT for BW scenario

    o Advanced Replication Settings (IUUC_REPL_CONTENT):o Improved UI for editing the table structureo Enabled for table deviation of non SAP source systemo New button to reset a load/replication object.

    o SAP Solution Manager monitoringintegration: Improved alerting with more details, will

    be integrated into SAP Solution Manager 7.1 SP9 (planned)

    This is the current state of planning and may be changed by SAP at any time.

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    6/44

    2013 SAP AG. All rights reserved. 6This presentation and SAPsstrategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document isprovided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement

    SAP LT Replication Server for SAP HANARoad map at a glance (planned innovation & future direction)

    PLANNED INNOVATIONS, FUTURE DIRECTION

    SAP LT Replication ServerFeature

    Planned:

    Upcoming Release

    (DMIS 2011 SP5)

    New Featureso ODQ - Operational Delta Queue

    Technical Readinesso HR Data Tables (HR Cluster tables)o Redesign: Handling of non-SAP data sources and targets

    Improved Usability & Stability

    in total a more than 50 person day Investment, i.e.:o LTR Configuration UI will be redesigned:

    Guided Procedure with build-in check after each input section (data source, target, configuration

    parameters)

    Planned:

    Future Release

    (DMIS 2011 SP6)

    New Scenario/Use Case:o 1:N data distribution scenario for non-SAP Data Sources, too

    o 'Heterogeneous warm Standbyo Replication to other target DBs (as project solution only!)

    Technical Readinesso Support of 'Point-in-Time Restore of Replication Landscape'Scenario

    This is the current state of planning and may be changed by SAP at any time.

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    7/44 2013 SAP AG. All rights reserved. 7This presentation and SAPsstrategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document isprovided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement

    SAP LT Replication Server for SAP HANARoad map at a glance (planned innovation & future direction)

    PLANNED INNOVATIONS, FUTURE DIRECTION

    SAP LT Replication ServerFeature

    Future Direction

    (Roadmap Outlook)

    New Features

    o Optimized near-Zero Downtime Support for OS-/DB-Migrations, i.e. use of MWB instead of

    R3Loado Improved ILM Support

    Technical Readiness

    o Several conceptual enhancements i.e. Transactional Consistence

    Improved Performance

    o Automated parallelization of Replication Process

    Investments in improved Usability & Stability

    o Functional and consistency checks for replicationo Selective Re-Load for tables with active transformation ruleso Further improvements in several operations aspects (i.e. more health checks)

    This is the current state of planning and may be changed by SAP at any time.

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    8/44

    Software Version and

    Shipment

    related News

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    9/44 2013 SAP AG. All rights reserved. 9

    DMIS_2010 SP09 / DMIS_2011 SP4

    Supportability Matrix

    Databa se SAP Source System Non-SAP Sources / Direct DB Connection

    MSFT SQL Server Enterprise Edition

    Oracle Enterprise Edition

    IBM DB2 LUW/ UDB (DB6)

    IBM DB/2 zSeries

    IBM DB2 iSeries (former AS/400)

    (on demand)

    IBM Informix

    SAP MaxDB

    Sybase ASE

    (with DB-Version 15.7.0.11) (with DB-Version 15.7.0.11)

    SAP HANA (Rev 38)

    SAP LT Replication Server 1.0: DMIS 2010 SP09

    Release to Customer: 20.02.2013

    available for SAP NetWeaver ABAP-based Systems on 4.6C -> 7.0x & 7.1x

    SAP LT Replication Server 2.0: DMIS 2011 SP04

    Release to Customer: 06.03.2013

    available for SAP NetWeaver ABAP-based Systems on 6.20 -> 7.x (incl. 7.3, 7.31, 7.4)

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    10/44 2013 SAP AG. All rights reserved. 10

    Related SLT Notes

    The most actual state of SLT Notes per SP can be found in the SLT Dev wiki:

    https://wiki.wdf.sap.corp/wiki/display/SLODev/SLT+Notes

    https://wiki.wdf.sap.corp/wiki/display/SLODev/SLT+Noteshttps://wiki.wdf.sap.corp/wiki/display/SLODev/SLT+Noteshttps://wiki.wdf.sap.corp/wiki/display/SLODev/SLT+Notes
  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    11/44 2013 SAP AG. All rights reserved. 11

    What DMIS Version to Use?DMIS 2010 vs. DMIS 2011

    With HANA SPS05, two versions of SAP LT Replication Server are now released:

    SAP LT Replication Server 1.0 (based on Software Component Version DMIS 2010)

    SAP LT Replication Server 2.0 (based on Software Component Version DMIS 2011)

    Technically both DMIS versions include the same coding level (no need for an upgrade):

    DMIS_2010 SP07 and DMIS_2011 SP02 (see also SAP Note 1709225)

    DMIS_2010 SP08 and DMIS_2011 SP03 (see also SAP Note 1759156)

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

    Current status

    With HANA SPS05, DMIS_2011 is released and recommended for all new installations (SAP LT Replication Server and

    SAP source systems).

    SAP customers who run other DMIS-based applications (that require DMIS_2010 in the SAP source system) can apply

    DMIS_2010 in the source and 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-

    disruptive event.

    The future SP release cycles of DMIS 2011 and DMIS_2010 will be different! DMIS_2010 SPs will only be available at

    every second DMIS_2011 SP Release. In midterm/longterm future maybe even less frequent than that

    Up to HANA SPS04 only DMIS_2010 was released for HANA customers,however SAP LT 2.0 and TDMS 4.0 are based on DMIS_2011

    http://service.sap.com/sap/support/notes/1709225http://service.sap.com/sap/support/notes/1759156https://service.sap.com/sap/support/notes/1824710http://service.sap.com/sap/support/notes/1691975http://service.sap.com/sap/support/notes/1691975https://service.sap.com/sap/support/notes/1824710http://service.sap.com/sap/support/notes/1759156http://service.sap.com/sap/support/notes/1709225
  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    12/44

    Development News

    DMIS_2010 SP09 / DMIS_2011 SP4

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    13/44 2013 SAP AG. All rights reserved. 13

    LTR UI Changes (1of 6)

    LTR UI: In the Helpcenter two new health checks are added:

    Job Analyze:This health check analyzes if all relevant jobs are running for the current configuration. This health check helps to find the

    root cause for an issue related to not running jobs

    Table Health Check:This health check analyze if all required steps are executed (e.g. create trigger) for all tables of the current configuration.

    This health check helps to find the root cause if a table sticks in a certain status as it indicates which steps are not

    successfully executed yet.

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    14/44 2013 SAP AG. All rights reserved. 14

    LTR UI Changes (2of 6)

    You can define an Initial Load Mode if you want to use a different default reading type.

    Initial Load Mode "Resource Optimized" is the default mode and uses reading type 3 for all tables

    Initial Load Mode "Performance Optimized" can be used if reading type 4/5 should be used for all

    tables. SLT will use reading type 4 for cluster tables and reading type 5 for the other tables.

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    15/44 2013 SAP AG. All rights reserved. 15

    LTR UI Changes (3of 6)

    Redesign of the Statistics view: Latency and throughput statistic are no longer display in two

    different tables on the same screen. There is now one table and you can switch between the

    latency or the throughput view.

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    16/44 2013 SAP AG. All rights reserved. 16

    LTR UI Changes (4 of 6): Display Settings for Statistical

    Data

    The statistic data (latency and throughput) which is deleted after 30 days in older version can be

    archived based on individually settings. There are 3 now configuration settings (which can beconfigured in the LTR UI):

    Condense on hourly base: Condense data that is older than the define timeframe (n days) will be

    condensed on hourly base. I.e. all portions replicated within one hour are condensed in one statistic

    record and saved in archive table. Default value: 10 days.

    Condense on daily base: Condense data that is older than the define timeframe (n days) will be

    condensed on daily base. I.e. all portions replicated within one day are condensed in one statistic record

    and saved in archive table. Default value: 30 days.

    Delete statistical data: Timeframe (n days) after which the statistic data is deleted. Default value: 365

    days.

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    17/44 2013 SAP AG. All rights reserved. 17

    LTR UI Changes (5 of 6)

    You can define the language used to create the column texts on HANA side.

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    18/44

    2013 SAP AG. All rights reserved. 18

    LTR UI Changes (6 of 6): Display & Change Settings

    Initial Load Mode:

    Initial Load Mode "Resource Optimized" is the default mode and uses reading type 3 for all tables Initial Load Mode "Performance Optimized" can be used if reading type 4/5 should be used for all tables. SLT will use

    reading type 4 for cluster tables and reading type 5 for the other tables.

    Job options:

    Number of Data Transfer Jobs and number of Initial Load Jobs

    The number of access plans calculation jobs is now customizable. The default will still be one, but you can define a

    higher number of access plan calculation jobs that can run in parallel.

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    19/44

    2013 SAP AG. All rights reserved. 19

    SLT Server: new authorization roles

    Two new roles for the user in the SLT System:

    Role SAP_IUUC_REPL_ADMINis required to create, change or display configurations.

    Role SAP_IUUC_REPL_DISPLAYcan be used if a user should be able to see the existing configuration

    and their status but is not allowed to change any settings or create a new configuration.

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    20/44

    2013 SAP AG. All rights reserved. 20

    N:1 Replication

    For N:1 replication SLT connects to an already existing schema and the user has to enter the password of

    the schema owner which is normally not known.If SLT connects to an existing schema, it now checks if there is already a DB connection defined pointing to

    this schema. If such a connection exist, the logon data will be copied and the user doesn't need to enter the

    password any longer (there will be just a confirmation popup, that the schema exist and it has to be

    confirmed to proceed).

    /nSM30

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    21/44

    2013 SAP AG. All rights reserved. 21

    LTRC: LT Replication Server - Cockpit

    New transaction code "LTRC" to enter IUUC_SYNC_MON. The old transaction remains

    active. LTRC is released to customer and is documented !

    Introducing a newclean Tab Pages

    Design

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    22/44

    2013 SAP AG. All rights reserved. 22

    LTRC: Data Provisioning UI

    CE1S_GO

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    23/44

    2013 SAP AG. All rights reserved. 23

    LTRC: runtime information on initial Load

    The runtime information of the initial load is no longer deleted when the object switches to the

    delta mode and can be displayed in the SAP LT Replication Cockpit (TA LTRC)

    A new GUI based program is available to display statistic data (latency and throughput) for a

    defined timeframe (program name: IUUC_REPL_CONFIG_ANALYSIS)

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    24/44

    2013 SAP AG. All rights reserved. 24

    IUUC_REPL_CONTENT(Advanced Replication Settings)

    Changed UI for editing the table structure (see screenshots on following slides)

    There is a new button in transaction IUUC_REPL_CONTENT to reset a certain load/replication object. This

    function is required if a rule definition is changed/corrected and the load object has to be recreated with the

    new settings

    IUUC_REPL_CONTENT enabled for table deviation of non SAP source system

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    25/44

    2013 SAP AG. All rights reserved. 25

    UI Changes in Transaction IUUC_REPL_CONTENT

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    26/44

    2013 SAP AG. All rights reserved. 26

    UI Changes in Transaction IUUC_REPL_CONTENT

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    27/44

    2013 SAP AG. All rights reserved. 27

    Summary of NON-SAP ReplicationDevNews

    Informix now also covered as source DB format (Version 11.5.2 onwards)

    Specific feature improvements:

    - Target table deviation in IUUC_REPL_CONTENT

    now also possible

    - Required adjustments in replication process now

    automated if source table structure changes

    Other technical improvements:

    Source table names in upper and lower case (case sensitive) now supported.

    Table names with > 30 characters now also supported.

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    28/44

    2013 SAP AG. All rights reserved. 28

    Stability Improvements

    A deviating type on the HANA side can now be also defined for a certain table field (e.g. field table-date

    should be created as DATE on HANA side). So you can either redefine the default mapping in general

    (e.g. DATS -> DATE instead of NVARCHAR) or for a individual field

    Correction for the suspend of cluster tables: If one logical cluster table is suspended, all other cluster

    tables are suspended too (as they use the same logging records). Now the status for all other cluster

    tables is also set to "SUSPENDED"

    In case of a move-corresponding error while mapping source to the target format, SLT will stop now with

    an according error message (in previous version there was just the error message). We also introduce

    variable move_error which can be reset in a rule if the move-corresponding error was solved by a rule

    In case of connection issues to the HANA DB, SLT catches the exception to avoid a dump and write a

    more precise error message.

    Correction for the replication of pool tables: The trigger is now adapted accordingly if new logical tablesof the same table pool are added for replication

    1:N Replication now also available for pool tables

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    29/44

    Replication into a SAP NW BW DataSource

    with SAP Landscape TransformationReplication Server (SLT)

    SLT

    SAP NetWeaver

    ECC

    AnyDB

    SAP NetWeaver BW

    AnyDB (or SAP HANA)

    DataSource

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    30/44

    2013 SAP AG. All rights reserved. 30This presentation and SAPsstrategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document isprovided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement

    Real-time Data Replication into SAP BWReplication into a BW DataSource

    Overview

    Data replication from SAP and non SAP systems into SAP NW BW 7.0 (onwards)

    possible with SAP Landscape Transformation Replication Server (SLT)

    Real-Time data processing via SAP BW Realtime Data Acquisition (RDA)

    Daemon into a DataStore Object (DSO) or master data tables (MD)

    SLT

    Structure

    mapping &

    Transfor-mation

    Write module

    SAP NetWeaver ECC

    AnyDB*

    Application table

    Logging tableDB trigger

    Read module

    RFC-BAPI

    SAP NetWeaver BW

    WebService

    DataSource

    RDA

    Daemon

    MDDSO

    AnyDB (or SAP HANA)

    * Including non-SAP sources replication for SAP supported DB versions as well!

    PSA

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    31/44

    2013 SAP AG. All rights reserved. 31This presentation and SAPsstrategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document isprovided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement

    Real-time Data Replication into SAP BWStatus and Positioning: PSA-Based Approach

    Status:

    Since almost 6 months real-time data replication into SAP BW is implemented as project solutionpiloted with several SAP BW customers

    Promising customer pipeline awaiting RTCof this functionality

    -> released for customers as of March 2013!

    Value Proposition:

    Delta recording and replication only

    Provide the data in real-time

    Recommended for simple tables (no join or transformation logic included)

    and data sources (extractors) without delta mechanism and complex business logic.

    Approaches with SLT replication for SAP BW:

    via Persistent Staging Area (PSA) / Web Service Data Source:-> all BW customers

    (but rather not preferred option for BW on HANA)

    via HANA DB schema / view

    Virtual Provider or Transient Provider:

    -> BW on HANA customers only!

    SLT

    SLT

    PSA

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    32/44

    2013 SAP AG. All rights reserved. 33This presentation and SAPsstrategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document isprovided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement

    Processing Steps in SLT: Define RFC connections

    Define a Configuration:Establishes theconnections between source system(s),

    SLT and BW system(s)

    Map logical system and MT ID: in table

    IUUC_BW_LOGSYS

    Start data load/replication for tables:Automatically creates logging tables and

    DB triggers in the source system and related

    Web Service Data Source in the BW system

    Processing Steps in BW: Define for each configuration a system of type Web

    Service

    Data is written in PSA via function module

    Data distribution via RDA: RDA can acquire data in

    real-time and load requests to DataStore Objects or

    master data tables

    Data can be queried in ~1 min. after data change insource

    Maintain

    tableIUUC_BW_LOG_

    SYS

    Real-time Data Replication into SAP BWDetails (1/4)Processing Steps

    Define

    Confi-

    guration

    Start

    Replica-

    tion

    Web ServiceData Source

    in PSA

    DSO Query

    MD

    SLT BW

    Log. table + DB trigger

    RDADaemon

    Source

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    33/44

    2013 SAP AG. All rights reserved. 34This presentation and SAPsstrategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document isprovided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement

    Real-time Data Replication into SAP BWDetails (2/4)Replication into a BW DataSource

    SLT / BW integration Steps:SAP LT Replication Server steps are now automated and integrated with SAP NetWeaver BW(as of DMIS 2011 SP4 / DMIS 2010 SP9)

    Create a configuration in the SLT system with connections

    to source system and SAP BW system

    RFC connection to SAP BW system

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    34/44

    2013 SAP AG. All rights reserved. 35This presentation and SAPsstrategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document isprovided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement

    Real-time Data Replication into SAP BWDetails (3/4)Replication into a BW DataSource

    Start data provisioning via t-code: LTRC

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    35/44

    2013 SAP AG. All rights reserved. 36This presentation and SAPsstrategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document isprovided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement

    Real-time Data Replication into SAP BWDetails (4/4)Integration of SLT and BW

    SLT will create BW DataSource automatically

    according to SLT naming conventions:SLT_ in target system

    no manual work necessary

    Field RECORDMODE is appended to each

    data source and automatically filled according

    to existing naming conventions Action RECORDMODE SLT operations modeInsert N 'I'

    Delete D 'D'

    Update ' ' 'U'

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    36/44

    2013 SAP AG. All rights reserved. 37This presentation and SAPsstrategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document isprovided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement

    Real-time data replication into SAP NW BWCommercial Aspects and Software Shipment

    Commercial AspectsIf SAP BW is not running on a SAP HANA Enterprise

    Edition, the following license for SAP Landscape

    Transformation Replication Server is required:

    SAP LT Basis (Material Number 7010685)

    SAP LT IT Consolidation (Material Number 7010688)

    SAP LT Value chain harmonization (Material Number 7010687)

    Software Version and Download

    SAP Landscape Transformation Replication Server 2.0(based on DMIS_2011) is the recommended version for

    the replication into SAP NW BW, find at

    http://service.sap.com/swdc.

    http://service.sap.com/swdchttp://service.sap.com/swdchttp://service.sap.com/swdc
  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    37/44

    2013 SAP AG. All rights reserved. 38This presentation and SAPsstrategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document isprovided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement

    Installation / Deployment Options

    As long as the technical prerequisites are met, there are 3 potential options to

    deploy SAP Landscape Transformation Replication Server

    For productive use - a separate SLT system is recommended to stay

    flexible for software maintenance and scale out scenarios and

    minimize impact on other applications

    Source System (if SAP) BW System Dedicated System

    Advantages Simplified landscape and

    administration

    Re-use of existingSAP ERP instance

    Simplified landscape and

    administration

    Re-use of existing

    NW instance

    No software maintenance

    dependencies

    Flexibility

    Disadvantages Performance impact

    Potential software

    maintenance dependencies

    Performance impact

    Potential software

    maintenance dependencies

    Investment and maintenance

    effort for separate server / NW

    instance

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    38/44

    2013 SAP AG. All rights reserved. 39This presentation and SAPsstrategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document isprovided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement

    Technical Prerequisites in Detail

    SAP BW systemSAP Landscape Transformation

    Replication ServerSource system

    System Requirements:

    SAP Basis: SAP Netweaver 7.02 or higher

    RFCConnection

    RFC or DBConnection

    System Requirements:

    SAP sources: SAP Basis 4.6C and higher

    non-SAP: all SAP supported DB versions

    (with respective SAP Kernel installed on

    LT Replication Server)

    Installation (if SAP source system!):

    Respective DMIS_2011 add-on version*

    Minimum DMIS_2011 SP level: SP02

    Installation:

    Add-on DMIS 2011_1_700 (or higher)**

    Minimum DMIS_2011 SP level: SP04

    Apply SAP Note 1810627

    Installation:

    Respective DMIS_2011 add-on version

    Minimum DMIS_2011 SP level: SP02

    Apply SAP Note 1808251(BW specifics!)

    Basic Configuration:

    Define RFC or DB connection to source system

    Define RFC connection to BW system

    Maintain table IUUC_BW_LOG_SYS (after creation

    of a configuration)

    Basic Configuration:

    Optional: define separate table space

    for logging tables

    Define user with appropriate authorization

    for remote connectionsee SLT Security

    Guide

    Basic Configuration:

    Define each affected source system as

    logical systemtype Web Service

    Define RFC user with appropriate

    authorization

    * For R/3 4.6C source systems or if other DMIS_2010 based applications are in use, install DMIS_2010 (part of SAP LT Replication Server 1.0)

    ** The use of SAP LT Replication Server 2.0 (DMIS_2011) is recommended, in case other DMIS_2010 based applications (such as TDMS 3.0) are in use,

    you may run LT Replication Server also with DMIS_2010_1_700 SP09 (or higher)

    System Requirements: SAP BW 7.0: min. SP levelSP17

    SAP BW 7.01 and 7.40: min. SP levelSP00

    SAP BW 7.027.31: min. SP levelSP01

    https://service.sap.com/sap/support/notes/1810627http://service.sap.com/sap/support/notes/1808251http://service.sap.com/sap/support/notes/1808251https://service.sap.com/sap/support/notes/1810627
  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    39/44

    2013 SAP AG. All rights reserved. 40This presentation and SAPsstrategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document isprovided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement

    Next Steps and Key Information Sources

    Next Steps: finalize documentation (expected by end of March)

    Functional completeness (with next support package), e.g. automate the

    creation and mapping of logical system with MT ID

    Establish regional multipliers and experts in SAP BW community

    Drive rollout and support upcoming customer / project requests

    Key Documents and Links

    Central Note: 1826585

    SLT for SAP BW on SCN (Blog): coming soon

    Installation Guide(in preparation)

    Security Guide(for SAP HANA)

    Operations Guide(for SAP HANA)

    How-To Guide Advanced Replication Settings(see SAP Note 1733714)

    SLT Sizing Guide

    Key Contacts

    BW CSA team: Marc Hartz

    BW Product Management: Rainer Uhle

    SLT Product Management: Astrid Tschense-Oesterle; Michael Erhardt

    http://service.sap.com/sap/support/notes/1826585http://service.sap.com/~sapidb/011000358700000604912011http://service.sap.com/~sapidb/011000358700000604912011https://community.wdf.sap.corp/sbs/docs/DOC-134829http://help.sap.com/hana/hana1_slt_repli_sec_en.pdfhttp://help.sap.com/hana/hana_slt_tom_en.pdfhttp://service.sap.com/sap/support/notes/1733714http://service.sap.com/sap/support/notes/1733714http://service.sap.com/sap/support/notes/1733714http://service.sap.com/~sapidb/011000358700001373882012Ehttp://service.sap.com/~sapidb/011000358700001373882012Ehttp://service.sap.com/~sapidb/011000358700001373882012Ehttp://service.sap.com/sap/support/notes/1733714http://service.sap.com/sap/support/notes/1733714http://service.sap.com/sap/support/notes/1733714http://service.sap.com/sap/support/notes/1733714http://help.sap.com/hana/hana_slt_tom_en.pdfhttp://help.sap.com/hana/hana1_slt_repli_sec_en.pdfhttp://help.sap.com/hana/hana1_slt_repli_sec_en.pdfhttps://community.wdf.sap.corp/sbs/docs/DOC-134829http://service.sap.com/~sapidb/011000358700000604912011http://service.sap.com/~sapidb/011000358700000604912011http://service.sap.com/sap/support/notes/1826585
  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    40/44

    Mid Term Strategy / Outlook

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    41/44

    2013 SAP AG. All rights reserved. 42This presentation and SAPsstrategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document isprovided without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement

    SLT Acting as Operational Delta Provider (ODP)

    Key Take Aways: The capturing of changed data (delta recording capabilities via trigger-based approach)

    is a highly demanded feature

    Leveraging the existing (open and flexible) Operational Delta Queue (ODQ) concepts

    allows SLT to become an Operational Delta Provider (ODP).

    This is a strategic enhancement of SLTs and the trigger-based replication portfolio to address the needs

    of other consumers - beyond the highly integrated but proprietary solutions for SAP HANA and SAP BW

    Technical readiness and expected availability is planned with DMIS_2011 SP05 by 08/2011

    Specifics of the ODP scenario

    SLT system will be the host of ODQ with a persistent /

    stage area (with very high compression rate > 98%!)

    No DMIS installation on target system required

    Each consumer has to integrated via enhanced

    ODP replication API Multiple suppliers and consumers can use

    same queue (real N:M replication)

    First committed consumers:

    - SAP NW BW 7.3 (onwards) starting in 08/2013

    - SAP Data Services 4.2: RTC expected in Q4/2013

    SLT

  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    42/44

    2013 SAP AG. All rights reserved. 43

    Key Information SourcesFor Customers and Partners (External)

    Web Pages:

    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(new!)

    Some assets linked @ HANA Experience Page

    SAP LT

    Key Documents and Links

    New SLT - Introduction Video

    SLT - Overview Presentation(located in SAP internal - SLT community)

    Installation and Configuration Guide

    Security Guide

    Operations Guide(SP08 related updates completed by 11/2012)

    How-To Guide Advanced Replication Settings(see SAP Note 1733714) Sizing Guide

    Important SLT Notes: see in SLT General Note 1605140

    http://service.sap.com/hanahttp://help.sap.com/hanahttp://scn.sap.com/community/replication-serverhttp://www.sap.com/demos/videos/distribute/sap-it-replication-server-real-time-data-integration-for-sap-hana-12-ov-us.wmvhttps://community.wdf.sap.corp/sbs/docs/DOC-134829http://service.sap.com/~sapidb/011000358700000604912011http://help.sap.com/hana/hana1_slt_repli_sec_en.pdfhttp://help.sap.com/hana/hana_slt_tom_en.pdfhttp://service.sap.com/sap/support/notes/1733714http://service.sap.com/sap/support/notes/1733714http://service.sap.com/sap/support/notes/1733714https://service.sap.com/~sapidb/011000358700001373882012E/SAP_SLT_Sizing_Guide.pdfhttp://service.sap.com/sap/support/notes/1605140http://service.sap.com/sap/support/notes/1605140https://service.sap.com/~sapidb/011000358700001373882012E/SAP_SLT_Sizing_Guide.pdfhttp://service.sap.com/sap/support/notes/1733714http://service.sap.com/sap/support/notes/1733714http://service.sap.com/sap/support/notes/1733714http://service.sap.com/sap/support/notes/1733714http://help.sap.com/hana/hana_slt_tom_en.pdfhttp://help.sap.com/hana/hana1_slt_repli_sec_en.pdfhttp://service.sap.com/~sapidb/011000358700000604912011https://community.wdf.sap.corp/sbs/docs/DOC-134829https://community.wdf.sap.corp/sbs/docs/DOC-134829https://community.wdf.sap.corp/sbs/docs/DOC-134829https://community.wdf.sap.corp/sbs/docs/DOC-134829http://www.sap.com/demos/videos/distribute/sap-it-replication-server-real-time-data-integration-for-sap-hana-12-ov-us.wmvhttp://www.sap.com/demos/videos/distribute/sap-it-replication-server-real-time-data-integration-for-sap-hana-12-ov-us.wmvhttp://www.sap.com/demos/videos/distribute/sap-it-replication-server-real-time-data-integration-for-sap-hana-12-ov-us.wmvhttp://www.sap.com/demos/videos/distribute/sap-it-replication-server-real-time-data-integration-for-sap-hana-12-ov-us.wmvhttp://scn.sap.com/community/replication-serverhttp://scn.sap.com/community/replication-serverhttp://scn.sap.com/community/replication-serverhttp://scn.sap.com/community/replication-serverhttp://help.sap.com/hanahttp://service.sap.com/hana
  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    43/44

    2013 SAP AG. All rights reserved. 44

    Key Information SourcesFor SLT Beginners and SLT Experts (SAP Internal ONLY!)

    Getting Started:

    SLT Recordings (based on SPS03)

    HANA training classes: HA200; HA300

    SLT Guides and Notes

    Preparation for initial installation & configuration: Pre-Arrival Checklist

    SLT

    Special Topics: Using new IUUC_SYNC_MON (SLT Cockpit):

    - User Guide

    - Short Introduction(SAPConnectRecording)

    Advanced Trouble Shooting information(Trouble Shooting Guide V3.4)

    Architectural Overview - Load / Replication Procedure

    How-To accelerate Initial Load

    How-To accelerate Replication Procedure Advanced load procedure for ORACLE using ROW ID(transparent tables only!)

    Visit the SLT Communityto stay up-to-date!

    https://community.wdf.sap.corp/sbs/docs/DOC-124851https://community.wdf.sap.corp/sbs/docs/DOC-167709https://sap.emea.pgiconnect.com/p80307806/https://community.wdf.sap.corp/sbs/docs/DOC-98062https://community.wdf.sap.corp/sbs/docs/DOC-163028https://community.wdf.sap.corp/sbs/docs/DOC-86189https://community.wdf.sap.corp/sbs/docs/DOC-128762https://community.wdf.sap.corp/sbs/docs/DOC-153317https://community.wdf.sap.corp/sbs/groups/lt-replication-for-hanahttps://community.wdf.sap.corp/sbs/groups/lt-replication-for-hanahttps://community.wdf.sap.corp/sbs/groups/lt-replication-for-hanahttps://community.wdf.sap.corp/sbs/docs/DOC-153317https://community.wdf.sap.corp/sbs/docs/DOC-128762https://community.wdf.sap.corp/sbs/docs/DOC-128762https://community.wdf.sap.corp/sbs/docs/DOC-128762https://community.wdf.sap.corp/sbs/docs/DOC-86189https://community.wdf.sap.corp/sbs/docs/DOC-86189https://community.wdf.sap.corp/sbs/docs/DOC-86189https://community.wdf.sap.corp/sbs/docs/DOC-163028https://community.wdf.sap.corp/sbs/docs/DOC-163028https://community.wdf.sap.corp/sbs/docs/DOC-163028https://community.wdf.sap.corp/sbs/docs/DOC-163028https://community.wdf.sap.corp/sbs/docs/DOC-98062https://sap.emea.pgiconnect.com/p80307806/https://community.wdf.sap.corp/sbs/docs/DOC-167709https://community.wdf.sap.corp/sbs/docs/DOC-124851https://community.wdf.sap.corp/sbs/docs/DOC-124851https://community.wdf.sap.corp/sbs/docs/DOC-124851
  • 7/26/2019 SAP LT Repl Server DevNews DMIS2011 SP4 MAR2013 Final

    44/44

    Thank You!

    Contact information:

    Tobias Koebler / Michael Erhardt / Roland Hamm (AGS-SLO Product Management)