1. SAP HANA – Data Provisioning for Replication with SAP and Non-SAP Applications

2. Disclaimer
This presentation outlines our general product direction and should not be relied on in making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. 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. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.

3. Content SAP HANA Data Provisioning - Positioning
SAP HANA Data Provisioning - Options
SAP LT Replication Server (SLT)
SAP Data Services (DS)
SAP Direct Extractor Connection (DXC)
SAP HANA Data Provisioning – What’s new in SAP HANA SPS05?

4. SAP HANA SPS04: Data Provisioning Positioning
SAP LT Replication Server
SAP LT Replication Server (SLT) is positioned for real-time data replication from SAP and non-SAP sources (SAP supported data bases only)
-> Mainly recommended for real time data replication business scenario
SAP Data Services
SAP Data Services (DS) is positioned for batch load-based data replication from non-SAP sources and SAP sources (with complex ETL requirements)
-> Mainly recommended for batch type data replication business scenarios
SAP HANA Direct Extractor Connection (DXC)
DXC is available as a simple option in batch mode for data replication from existing SAP Data Source extractors (ERP) into SAP HANA.
-> Mainly recommended for batch type data replication for stand alone HANA business scenarios
Other Data Provisioning Options
Sybase Event Stream Processor (ESP) * : will be available for replicating real time event streams from Sybase ESP (CEP) into SAP HANA
* Planned to be available as part of SAP HANA SPS05 and Sybase ESP 5.1-SP1

5. Data Provisioning with SAP HANA 1.0
SAP BusinessObjects tools
Other query tools
SAP Business
Suite
SAP LT Replication Server
Trigger Based, Real Time
DB Connection
SQL
BICS
SQL
MDX
SAP In-Memory Computing Studio
ETL, Batch
SAP BW
ODBC
Log Based,
Real Time
SAP Data Services
SAP In-Memory Database
ECDA/ODBC
Calculation and Planning Engine
Row & Column Storage
Sybase Replication Server
Non-SAP
Data Sources
Extractor
Batch
SAP HANA Direct Extractor Connection**
Http/Https
ECDA – Enterprise Connect Data Access
Activation Queue
In memory DSO
Trading & Order
Management Systems
Sybase Event Stream Processor *
ODBC
Event Streams
Real Time
XS Engine
SAP HANA
Data Sources
* Sybase ESP 5.1-SP1, Q4-2012
** SAP ERP & BW Extractors

6. SAP HANA Data Provisioning Options: 1. SAP LT Replication Server
SAP LT Replication Server does not have to be a separate SAP system and can run on any SAP system with SAP NetWeaver ABAP stack 7.02 or higher with SAP Kernel 7.20 (or higher)
SAP source system
SAP LT Replication Server
SAP HANA system
HANA Studio
Application Table
Replication Configuration
Application Table
Trigger Based Delta Recording
RFC Connection
Replication Engine
DB Connection
Connection(s) between source system and SAP HANA system are defined as “Configuration” on the SAP LT Replication Server
Data load and replication are triggered via SAP HANA Studio

7. SAP LT Replication Server
LT Replication Concept: Trigger-Based Approach Architecture and key building blocks
SAP source system
SAP LT Replication Server
SAP HANA system
Read module
RFC Connection
Structure mapping & Transformation
Application table
Logging table
Application table
Write module
DB Connection
DB trigger
Efficient initialization of data replication based on DB trigger and delta logging concept (as with near zero-downtime approach)
Flexible and reliable replication process, incl. data migration (as used for TDMS and SAP LT)
Fast data replication via DB connection LT replication functionality is fully integrated with HANA Modeler UI

8. SAP LT Replication Server
LT Replication Concept: Trigger-Based Approach Replication from non-SAP sources
Non SAP source system
SAP LT Replication Server
SAP HANA system
DB Connection
Read module
Application table
Logging table
Structure mapping & Transformation
Application table
DB Connection
Write module
DB trigger
SAP LT replication server transfers in a first step all metadata table definitions from the non-SAP source system to the SAP HANA system into the tables DD02L and DD02T. Read module now has to reside on LT replication server as it requires an ABAP stack. NOTE: For non-SAP source systems, the customer database license needs to cover a permanent database connection with 3rd party products like LT replication server.

9. SAP HANA Data Provisioning Options: 2. SAP Data Services 4.1
High Performance
Highly-scalable engine to move large volumes of data into HANA
Integrated with HANA’s bulk-load interfaces
Wide Connectivity
Data and Metadata connectivity to all major enterprise data sources
Native, fast connectivity to Applications, RDBMS, Files, Text
Powerful Transformations
Built-in transformations for data quality (*)
Support for non-relational data formats including text and XML
SAP HANA Appliance
SAP HANA DB
In-Memory
SAP Business Suite
SAP HANA Studio
SAP BW *1
SAP
Data Services 4.1
Structured/Text Data Sources
(*) = Requires additional licenses

10. NEW in SAP Data Services 4. 1
NEW in SAP Data Services 4.1* Data Services Workbench for data loading into SAP HANA
New, Eclipse-based user interface design for Data Services
A simple wizard to replicate data and metadata (table definitions) from 3rd party databases into SAP HANA.
In 3 easy simple steps, you can replicate large data sets from any source to your SAP HANA target:
Set up connections to source and target system
Select the required tables from the source (or simply select all tables)
Generate and execute the job to move all data with one mouse click
Once the wizard exits, more additional features can be added:
Filters, complex data mappings (expressions and functions)
Load options, delta loading strategy, etc.
*SAP Data Services RTC in June 2012

11. SAP Data Services 4.1 – Workbench Design Replication job
HANA (8 selected tables)
Step 3: Deploy your Data Services job and execute.
Step 1: Select source and target connections (database or SAP application).
Step 2: Select tables for replication, target tables will be generated automatically.

12. SAP Data Services 4.1 – Workbench Monitor job run
Built-in capabilities to monitor the data loading
Compare historic load times
See load progress in real-time

13. Activation Processing
SAP HANA Data Provisioning Options: 3. SAP HANA Direct Extractor Connection (DXC)
Leverage pre-existing foundational data models of SAP Business Suite entities for use in SAP HANA data mart scenarios
Significantly reduces complexity of data modeling tasks in SAP HANA
Speeds up timelines for SAP HANA implementation projects
Provides Semantically Rich Data from SAP Business Suite to SAP HANA
Ensures data appropriately represents the state of business documents from ERP
Application logic to “make sense of the data” already built into many extractors
Simplicity / Low TCO
Re-uses existing proprietary Extraction, Transformation, and Load mechanism built into SAP Business Suite systems, over a simple http(s) connection to SAP HANA
No additional server or application needed in system landscape
Change Data Capture (delta handling)
Efficient data acquisition – only bring new or changed data into SAP HANA
DXC provides a mechanism to properly handle data from all delta processing types
SAP ERP
Extractor
DataSource (flat structure)
Embedded BW
DataSource
PSA
generic data transfer
InfoCubes
Data Store Objects
InfoObjects
SAP HANA
Activation Queue
Active version
In memory DSO
Status
Activation Processing
ERP data
http

14. SAP HANA Direct Extractor Connection: Details - 1 -
SAP HANA Direct Extractor Connection (DXC)
Utilizes the Data Source extractors that exist in SAP Business Suite systems 
Originally, those were developed for use with BW
DXC is for use in SAP HANA standalone scenarios (data mart); BW on SAP HANA is a separate topic.
DXC utilizes the embedded BW
Starting with NetWeaver 7.0, (embedded) BW has been part of NetWeaver ABAP
In typical SAP Business Suite systems, the embedded BW is not utilized
customers used to run separate BW systems
Most customers already have the Support Package level needed on source SAP Business Suite system, e.g. SAP NW 7.0 Support Package Stack 19 – first available Nov 2008
DXC uses the embedded BW system to enable extraction towards SAP HANA and monitoring
DXC mainly requires applying SAP note
Note: Modeling in the embedded BW is not part of the DXC solution. An architectural variation is available, which uses a “sidecar” BW instead of the embedded one.

15. SAP HANA Direct Extractor Connection: Details - 2 -
The extraction from the SAP Business Suite system is controlled by the Data Warehousing workbench inside the embedded BW
When data is extracted from, the SAP Business Suite system, it is not loaded into the PSA of the embedded BW - it is redirected instead and sent to SAP HANA
it gets loaded into in-memory DSO’s activation queue - and then gets activated into the active table of the in-memory
However, in the data load monitor of the embedded BW, the data load into the activation queue in the DSO in SAP HANA appears like data is loading into the PSA of the embedded BW
Delta processing (aka “change data capture”)
Works the same for DXC as it would if BW is the receiving system
If the DataSource is delta enabled, then delta-data is available with SAP HANA Direct Extractor Connection, too
DXC internally in HANA uses
The ICM (Internet Connectivity Manager) receives XML packages over the http(s) connection
A mechanism written on the XS Engine (special runtime component for SAP HANA)
receives data packages from ICM, converts format
inserts the records into the activation queue of the in-memory DSO
activation processing -> records go into the active table in proper sequence
Both the ICM and XS Engine components must be enabled in SAP HANA to utilize DXC

16. SAP Sybase Event Stream Processor ESP-5.1
SAP HANA Data Provisioning: What’s new in SAP HANA SPS05* Sybase ESP-5.1 Integration with SAP HANA 1.0
INPUT STREAMS
Studio (Authoring)
ODBC**
SAP Sybase Event Stream Processor ESP-5.1
Sensor data
Dashboard ?
Application
Transactions
Message Bus
Events
Database
High speed smart capture: SAP Sybase ESP can apply logic to transform, filter, aggregate, enrich incoming event streams and capture data in SAP HANA
SAP Sybase ESP can query SAP HANA database to provide context for processing incoming events
SAP HANA 1.0
SAP HANA
Studio
SAP HANA
Database
* SAP HANA SPS05, RTC Q4 2012
** Sybase ESP 5.1 SP1- ODBC Adapter, RTC Q4 2012
Note: This is the current state of planning and it may be changed by SAP at any time

17. SAP HANA Data Provisioning: What’s new in SAP HANA SPS05
SAP HANA Data Provisioning: What’s new in SAP HANA SPS05* with SAP LT Replication Server
Technical readiness for replication of SAP Business Suite on SAP HANA
SLT for SAP BW: ready for proof-of-concepts and prototyping projects
Integrated use of SLT by ERP and other SAP HANA Application Accelerators
Improved usability
Help Center with detailed context-related documentation
Advanced status tracking (when using Access Plan / Range Calculation)
Improved stability
Eliminate manual steps on SLT system after implementing a note or support package
Support related expert functions streamlined
New and improved performance options
Data load using ROW ID approach with reading type 4
Optimized job management: free-up background jobs and resources for tables with low change rates
* SAP HANA SPS05, RTC Q4 2012
Note:
This is the current state of planning and it may be changed by SAP at any time

18. Further Information SAP Public Web
saphana.com
SAP Education and Certification Opportunities