SAP LT Replication Server for SAP HANA SPS04 SLT Core Features – Updates and Enhancements

1. SAP LT Replication Server for SAP HANA SPS04SLT Core Features – Updates and Enhancements • SAP internal only! • Find here link to recording Tobias Koebler / Jochen Merkel AGS SLO 05/2012

2. Multiple System SupportCore Features in Detail  New features in LTR UI • Consolidated UI for Replication Content Transformation Content • Load from archives • Maintenance Events in Source Systems Summary / Additional Information AGENDA

3. Multiple HANA System Support1:N Replication for SAP source systems System A SAP Source systems SAP HANA systems SAP source systems are connected to separate HANA systems. Schema name can be equal or different Schema 1 Schema 2 If one source system is connected to several target schema (currently 1:4 supported), the relevant target schema can be selected in the data provisioning UI

4. Connect Multiple Source System to Same HANA Schema 1/2Enhanced N:1 replication RS_ORDER is enhanced to support N:1 replication. Interims solution RS_ORDER_EXT gets obsolete. Adaption of table structure is done by monitor job automatically SAP HANA system Source systems are connected to same HANA system and also the same schema Source systems System A Schema 1 System B

5. Connect Multiple Source System to Same HANA Schema 2/2Ensure data separation Source systems SAP HANA system • Check if replicated data remains unique: • as no table will receive data from multiple source systems (unique table lists) • as data is already separated by the existing key (e.g. all source systems have unique client numbers) • If data doesn’t remain unique it might lead do data inconsistencies Source systems SAP HANA system • Enhance target table with a new system specific field (e.g. System ID) and set a unique value for each system: • Add additional key field (e.g. System ID) • Define a transformation rule to set a unique value

6. Multiple System SupportCore Features in Detail • New features in LTR UI • Consolidated UI for Replication Content • Load from archives • Maintenance Events in Source Systems Summary / Additional Information AGENDA

7. Configuration and Monitoring Dashboard 1/3New settings for a configuration Only one table space can be defined for the logging tables (as additional table spaces make no sense). If more than one table space were already defined, they will still be displayed. Flag to allow usage of source system in different configurations (1:N replication) Flag for client specific load and replication. Read will be only from the client which is specified in RFC connection.

8. Configuration and Monitoring Dashboard 2/3Master Job settings The “Master Job” can now easily be stopped and restarted via a button for the relevant configuration

9. Configuration and Monitoring Dashboard 3/3Enhanced Statistics Additional statistic data can be displayed in the “Statistic” tab. The statistic shows how many records have been replicated separated by the operation (Insert, Update, Delete)

10. System Demo

11. Multiple System SupportCore Features in Detail  New features in LTR UI • Consolidated UI for Replication Content • Load from archives • Maintenance Events in Source Systems Summary / Additional Information AGENDA

12. New UI to Specify Transformation Content General features: New UI to specify: • Structure changes of tables & partitioning of tables • Transformation rules to change and/or filter data • Performance optimization to use parallel read

13. New UI to Specify Transformation Content Combined Transaction for all Table Settings Transaction IUUC_REPL_CONTENT Select table 2 Select Configuration / Schema 1 Transport settings / transformation content via upload / download to other SLT system. 3 Define table settings

14. New UI to specify transformation content Define Table Settings • Chooseappropiatetabpage: • IUUC_REPL_TABSTGDefine table deviation and partitioning • IUUC_ASS_RUL_MAPTransformation rules to change and/or filter data • IUUC_SPC_PROCOPTTrigger specific adaption • IUUC_PERF_OPTIONPerformance optimization to use parallel read 2 Enter table name 1 Ability to import or export settings from / to file (only SLT table settings from new UI) Click on to specify table settings 3

15. New UI to Specify Transformation Content Define Table Deviation A different target structure can be defined - without having to create the structure in the DDIC. The table deviation can be defined in table IUUC_REPL_TAB_DV. In this case, only the deviation must be defined (ignore, change, or add certain fields). All other fields are derived from the source system. The table deviation can be defined in the replication content UI. There is no extra option to set the key flag of a new table field. If the new field should become a key field, you have to set the position of the new field so that the field in the following line is also a key field.

16. New UI to Specify Transformation Content Define Table Deviation Edit Table Structure

17. New UI to Specify Transformation Content Enhanced Table Settings - Partition There is an additional field (PARTITION_CMD) in table IUUC_REPL_TABSTG where a partitioning command can be defined for certain tables. The partition command will be added to the create statement of the table on the HANA System. The partition command has to be entered in the same way as it would be defined in the SQL editor of the HANA studio, for example: PARTITION BY HASH (a, b) PARTITIONS 4 SLT will add the partition command when generating the SQL command to create the table. For example: CREATE COLUMN TABLE mytab (a INT, b INT, c INT, PRIMARY KEY (a,b))PARTITION BY HASH (a, b) PARTITIONS 4 HANA WIKI - https://wiki.wdf.sap.corp/wiki/display/ngdb/Partitioning Note that instead of the partitioning command, each SQL parameter (e.g. for localization) is possible

18. New UI to Specify Transformation Content Transformation Rules • Instead of an ABAP routine, which contains the transformation rules, it is possible to enter one line of coding (max 72 characters) directly. • If the line of coding is defined, no ABAP include will be performed. • This option is suitable for implementing simple parameter rules to fill table fields, such as the source system ID.

19. Reading TypesAccelerated Load Procedures

20. New UI to specify transformation content Performance Optimization • Default setting for initial load: Reading Type 3 • The default setting is 3 jobs for each table for parallel read • If more parallel jobs are defined for parallel read than are available for loading, the tables will be processed successively • To determine the order of table processing the sequence number (Seq. No.) can be used.

21. New UI to specify transformation content Export/Import Settings Choose Import Option 3 Possibility to compare and load settings selectively for each table Import Settings intoTarget SLT Server 2 • For the export / import options, only the settings of Customizing tables will be uploaded and downloaded.  No objects (for example ABAP includes of rules) are exported or imported. • If you import settings, the mass transfer ID of the relevant SLT configuration must be entered. Save Settings in Dev. System 1

22. Special Considerations • For key fields, see slide 15 • Insteadofthepartitioningcommand, eachSQL parameter (forexampleforlocalization) canbeapplied • Use the Import Settings feature carefully to avoid unintentionally deleting or overriding existing settings. • Note that importing or exporting means that the Customizing of the SLT Server will be transferred. No include routines will be transported within this step.

23. System Demo • Partitioning • Table Deviation • Upload / Download

24. Multiple System SupportCore Features in Detail  New features in LTR UI • Consolidated UI for Replication Content • Load from archives • Maintenance Events in Source Systems Summary / Additional Information AGENDA

25. Load from SAP Archive 1/2Architecture and Key Building Blocks The ILM API must be available in the source system. The API can be installed by means of SAP Note 1652039 (46C – 731). SAP Source system SAP LT Replication Server SAP HANA system Read Module Structure Mapping & Transformation Write Module ADK Archive Access API DBConnection RFCConnection ADK Archive Archived data can be selected by the date of the archiving session. Application Table This presentation and SAP‘s strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. This document is provided 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

26. Load from SAP Archive 2/2Define Load Object Report: IUUC_CREATE_ARCHIVE_OBJECTin SLT system Select replication configuration Select Archive Object Define Selection Criteria Select Relevant table within current archive object

27. System Demo

28. Multiple System SupportCore Features in Detail  New features in LTR UI • Consolidated UI for Replication Content • Load from archives • Maintenance Events in Source Systems Summary / Additional Information AGENDA

29. Maintenance Events in Source SystemsAvoid error because of active triggers Currentsituation: Table ABCis in replicationtriggerisactive in thesourcesystem Anysoftware maintenance event (e.g. applying a transportor SP) whichcause a structuralchangeoftableABC will failbecauseoftheactivetrigger. Howtoavoidthissituation: SAP Note 1655725 has to be installed in the source system (only for >=NW7.0) • After you implement the correction instructions, the dictionary tools also accept • structural changes to tables if the change only consists of adding new fields. The note should only be installed if DMIS 2010 SP07 is installed on the SLT system. Otherwise table structure can be changed and replication process might continue without getting aware of the table change.

30. Maintenance Events in Source SystemsChange of table structure in HANA system Current situation: • Table ABC was changed in source system (additional fields only). • Manual deletion of triggers • Manual adjustment of target table in HANA system • Manual recreation of replication objects and triggers Expert Function – usually use stop/start Automated procedure with DMIS SP7: • Table ABC was changed in source system (additional fields only). • Manual deletionoftriggers SAP Note 1655725 has to be installed (only for >=NW7.0) • Manual adjustmentoftargettable • Manual recreationofreplicationobjectsandtriggers •  With DMIS 2010 SP07, the SLT server checks the source table for structural changes. If additional fields are added, the replication process is paused and the table structure in HANA, and the replication object is adapted accordingly. Afterwards, replication for the relevant table continues.

31. Multiple System SupportCore Features in Detail • New features in LTR UI • Consolidated UI for Replication Content • Load from archives • Maintenance Events in Source Systems Summary / Additional Information AGENDA

32. Summary of Key Features and Special Considerations • Summaryof Key Features: • 1:N and improved N:1 replication • Stop button: “Master suspend/resume function“ • Client-specific replication (only): Easy to customize • Improved load performance: Multi-threading for default reading type • Throughput statistics for replication • Consolidated UI for (table-specific) replication settings and transformation rules • Table structure changes (non-key fields) in source system handled automatically • Load from SAP archives • Special Considerations: • Specificconsiderationsfor SAP sourcesystem(s): • Handling oftablestructurechanges (relevant forsourcesystems on SAP NW 7.00 orhigher): Apply SAP Note 1655725 • Using 1:N Replication: DMIS_2010 SP07 required • Using “Load from Archives”: DMIS_2010 SP07 required, plus SAP Note 1652039 • SLT and HANA “compatibility matrix”: see SAP Note 1709225

33. SLT and HANA “compatibility matrix” SAP Note 1709225 • SAP HANA can be upgrade from SPS3 to SPS4 without upgrading DMIS component • The DMIS component can be upgraded from SP5 to a higher support package level without the need to upgrade the HANA database or studio If not all system are installed on the newest support package, some new functionalities might not be available.

34. Technical Requirements and System Set-Up Information for LT Replication Server (HANA 1.0 SPS04) SAP Source system SAP HANA system LT Replication Server (*) RFCConnection DBConnection • Installation: • Addon DMIS 2010_1_700 • Minimum support pack level: SP07 • Installation: • HANA SPS04: includes LT replication functionality fully integrated into the UI of the HANA modeler • Installation: • respective DMIS 2010 version • Minimum support pack level: SP05(**) • Basic Configuration: • Optional: define separate table space for logging tables • Define RFC user with appropriate authorization • Basic Configuration: • Define RFC connection to source system- Define DB connection to HANA system- Define max. number of jobs to be used for data replication Basic Configuration: - Create a DB user (if required) • System Requirements: • SAP Basis 4.6C andhigher • All data bases • System Requirements: • SAP Basis: Netweaver 702, with Kernel 7.20EXT (64BIT Unicode) PL90 - see SAP note 1597627, => currently limited platform availability • - Filesystem: 100 GB- RAM: 16-32 GB • CPU: 2-4 cores • Recommended number of background jobs: 10 (*) LT replication server can run on any SAP system with SAP NetWeaver 7.02 ABAP stack (using SAP Kernel 7.20EXT), for example on Solution Manager 7.1 or the source system – it does not have to be a separate SAP system! (**) A few new SLT features available with HANA SPS04 may require DMIS_2010 SP07

35. Technical Requirements and System Set-Up Information for LT Replication Server (HANA 1.0 SPS04) Non-SAP Source system SAP HANA system LT Replication Server (*) DBConnection DBConnection • Installation: • Addon DMIS 2010_1_700 • Minimum support pack level: SP07 • Installation: • HANA SPS04: includes LT replication functionality fully integrated into the UI of the HANA modeler • Basic Configuration: • Create DB user for Secondary DB connection • Basic Configuration: • Define DB connection to source system- Define DB connection to HANA system- Define max. number of jobs to be used for data replication Basic Configuration: - Create a DB user (if required) • System Requirements: • the OS/DB restrictions of NetWeaver 7.02 apply (see at http://service.sap.com/pam) • System Requirements: • SAP Basis: Netweaver 702, with Kernel 7.20EXT (64BIT Unicode) PL90 - see SAP note 1597627, => currently limited platform availability • - Filesystem: 100 GB- RAM: 16-32 GB • CPU: 2-4 cores • Recommended number of background jobs: 10 (*) LT replication server can run on any SAP system with SAP NetWeaver 7.02 ABAP stack (using SAP Kernel 7.20EXT), for example on Solution Manager 7.1 or the source system – it does not have to be a separate SAP system!

36. DB Supportability Matrix (HANA 1.0 SPS04): Loading Data via SAP LT Replication Server for SAP HANA For non-SAP source systems, the customer database license needs to cover a permanent database connection with 3rd party products like LT replication server. (*) Since a DB connection from LT replication server to a non-SAP system is required, the OS/DB restrictions of NetWeaver 7.02 apply (see at http://service.sap.com/pam)

37. Next Stepsand Key Information Sources • Next Steps: • Complete info session (CW18/19) • Update key documents on the SLT community • Create new version of TroubleShooting Guide • Create How-To Guide for Replication Content UI • Incorporate SPS04 related information into other key information sources e.g. HANA training material • Key Information Sources • (http://service.sap.com/hana; http://help.sap.com/hana) • SLT content included in SAP HANA SPS04 – RKT material • Updated Installation Guide • Updated Security Guide • Operations Guide (update planned by end of May) • Central SLT Note 1605140 (to be updated!) • SLT for SAP HANA SPS04 - Release Information Note: 1709225

38. Register Now: Other Info Sessions • SLT Featuring Other SAP HANA Use Cases: • Target Group:HANA Presales, SLT beginnersandexperts • Date / Time: 7th of May (morningandafternoonsession)

39. Key Contacts Regional SLT Experts: Key contacts in HANA CSA Team: Matt Kangas; Serge Muts HANA Product Management: Joerg Hoffmeister; Prasad Illapani SLT Product Management: Tobias Koebler; Michael Erhardt; Roland Hamm • Leverage info sources in LT Rep Server community first before contacting us! • Post error messages at CSS component BC-HAN-LTR and not in the community!

40. Thank You! Contact information: Tobias Koebler / Michael Erhardt (AGS-SLO Product Management) Jochen Merkel (AGS-SLO Development)