Data provisioning in SAP HANA involves importing data from multiple SAP and non-SAP systems using either in-built tools like flat file upload and smart data access, or external tools. Flat file upload allows loading data from CSV or Excel files directly into HANA tables, while smart data access enables querying remote data sources using virtual tables. External tools for data provisioning include SAP Replication Server for real-time replication, SAP Data Services for batch ETL, and SAP Landscape Transformation for migrating data to HANA format.

1. DATA PROVISIONING IN SAP
HANA

2. AGENDA
Introduction
Data Provisioning Techniques
DATA PROVISIONING

3. DATA PROVISIONING
Data provisioning involves importing data from multiple SAP and non-SAP system into SAP
HANA.
data provisioning options available into two categories, they are
◦ SAP HANA in-built tools
◦ External Tools

4. DATA PROVISIONING TECHNIQUES
Flat File
Upload
Smart Data
Streaming
Smart Data
Access
External Tools For Data Provisioning
SLT
SAP Landscape
Transformation
SRS
SAP Replication
Server
DXC
Direct Extractor
Connection
SAP Data
Services
Source Systems
SAP ECC SAP BW Hadoop
Non-SAP Data
Sources
Social
Network
Sensors
In-Built Tools

5. FLAT FILE UPLOAD
Flat files are data files which are stored locally and not coming in from a live server.
One of the advantages we have with SAP HANA studio is, we have an option to load data from
either .csv or excel files to SAP HANA database directly without using any of the ETL tools.
Create the Table
Get the file containing
data in local system
Import file using
HANA studio
Manage the mappings Load the data
Sequential Steps in a Process

6. IMPORTANT FACTS ABOUT UPLOADING DATA FROM
FLAT FILES
If the required table for loading the data does not exist in SAP HANA database, it’s necessary to
create a table structure that is based on the flat files
The application suggests the column names and data types for the new tables and it’s possible to edit
them
The new table always has a 1:1 mapping between the file and table columns
When loading new data in the table, it gets appended to the existing data
The application does not allow to overwrite any column or change the data type of existing data
The supported file types are: .csv, .xls, and .xlsx

7. SMART DATAACCESS
SAP HANA Smart Data Access (SDA), enables remote data to be accessed via SQL queries as if
they are local tables in HANA, without copying the data into SAP HANA.
 With the help of SDA, SAP HANA can create so-called “virtual table” mapping to tables located in
remote data sources, and then SAP HANA can access the data directly by accessing the “virtual
table”.

8. Continue..
“virtual table” can be manipulated by SAP HANA just like an ordinary table, which means the
operations, such as select, update, insert, delete, and so on, are all available for “virtual table”.
Besides, join operation between local table and “virtual table” is supported.
When such join operation taken, optimizer of SAP HANA sends the relevant operations to
remote data source for processing, and then the result set would be sent back to SAP HANA for
further processing.

9. BENEFITS
Enable access to remote data access just like
“local” table
Benefit from HANA functionality without
moving all data to HANA
No special syntax to access heterogeneous
data sources
Cost savings

10. SMART DATA STREAMING
Smart data streaming adds real-time streaming analytics to the SAP HANA platform, making it
easy for developers to incorporate smart stream capture and active event monitoring, alerting and
event-driven response to their HANA applications.
Analyze and act on data as it arrives. Whether its sensor data from smart devices, social media
feeds, market prices, or click streams from a web site, SAP HANA smart data streaming can
extract insight from that raw data, allowing you to respond as fast as things happen.
This option is available from SAP HANA SPS 9 revision.

11. Streaming Data sources becoming ubiquitous
Sensors
Click Streams
Social Media
Transactions
Market Feeds

12. SAP HANA SMART DATA STREAMING
DEPLOYMENTS

13. Continued…
Data flows into the SAP HANA smart data streaming server from external sources through built-in or
custom adapters, which translate incoming messages into a format that is accepted by the SAP HANA
smart data streaming server.
This figure shows a typical smart data streaming deployment. Continuous queries, developed and
tested as projects using the SAP HANA smart data streaming plugin for SAP HANA studio, are
deployed to an SAP HANA smart data streaming server.
Output adapters translate rows processed by the server into message formats that are compatible with
external destinations, such as SAP HANA, and send those messages downstream.
SAP HANA cockpit provides an operations console for configuring smart data streaming.

14. EXTERNAL DATA PROVISIONING
TOOLS

15. SAP Replication Server (SRS)?
SAP Replication Server (SRS) also known SAP Sybase Replication Server is a real-time data
integration and movement software.
SAP Replication Server (SRS) moves and synchronizes transactional data including DML and
DDL across the enterprise, providing low impact, guaranteed data delivery, real-time business
intelligence, and zero operational downtime.

16. SRS Architecture

17. Why Sap Replication Server?
Because you can move, manage, and integrate data from the most popular SAP and non-SAP data
sources in real time – feeding your IT investments with high quality data that’s always where you need
it to be. With our data replication software, you can:
Ensure your distributed IT landscape is reliable, stable, and always available
Maintain business continuity with “zero downtime” disaster recovery solutions
Move up-to-the-second production data into SAP HANA for real-time reporting
Keep data synchronised across diverse database environments to maintain local performance
Perform database migrations without interrupting operations

18. SAP Sybase Replication Server -High
availability/disaster recovery
Minimize/eliminate user impact Protect against unplanned outages
Software, hardware, application failure
Unforeseen circumstances like data corruption
Protect against planned outages
Software, hardware, application upgrades
Enable ops to perform maintenance activities
Recover from natural disaster
Without geographic restrictions

19. SAP DATA SERVICES
SAP Data Services (DS) is suited for Data Integration (Batch), with HANA optimized
capabilities for Transforming, Cleansing* and Integrating (bulk or delta) structured and
unstructured* data from many different Sources (SAP and non-SAP) to the Target (SAP HANA).
SAP Data Services is a data integration and transformation software application.

20. What is ETL (Extraction, Transformation and Loading)?
It refers to a process in database usage and especially in
data warehousing that:
Extracts data from homogeneous or heterogeneous
data sources
Transforms the data for storing it in proper format or
structure for querying and analysis purpose
Loads it into the final target (database or data
warehouse)

21. SAP Data Services is the solution to overcome all the
problems
SAP Data Services is the first and only, all-in-one solution for:
Data Integration (ETL),
Data Quality Management,
Information Stewardship (Data Profiling And Metadata Management), And
Text Analytics.

22. What is SLT?
SAP Landscape Transformation Replication Server (“SLT”) is for all SAP HANA customers
who need real-time or scheduled data replication, sourcing from SAP and NON-SAP sources
Uses trigger-based technology to transfer the data from any source to SAP HANA in real-time.
SLT server can be installed on the separate system or on SAP ECC System.

23. SLTArchitecture overview
1. SLT Architecture overview between SAP System and SAP HANA
2. SLT Architecture overview between Non-SAP System and SAP
HANA

24. Benefit of SLT system
Allows real-time or schedule time data replication.
During replicating data in real-time, we can migrate data in SAP HANA Format.
SLT handles Cluster and Pool tables.
Automatically non-Unicode to Unicode conversion during load/replication
This is fully integrated with SAP HANA Studio.
SLT have table setting and transformation capabilities.
Replication from multiple source systems to one HANA system is allowed, also from one source system to multiple
HANA systems.

25. SAP HANA DXC
SAP HANA DXC is batch driven data replication technique i.e. it can execute after a time interval.
SAP HANA Direct Extractor Connection (DXC) is available as a simple option in batch mode for
data replication from existing SAP Data Source extractors (SAP Business Suite) to Target (SAP
HANA) for stand alone data mart scenarios.
In SAP Business suite application content Data Source Extractors have been available for data
modelling and data acquisition for SAP Business Warehouse.
SAP DXC use these Data Source Extractor to deliver data directly to SAP HANA.
DXC extraction processing bypasses the normal dataflow and sends data to SAP HANA instead.

26. DXC ARCHITECTURE
PSA- Persistent staging area:
It is the inbound storage area for data from the source
systems in the SAP Business Information Warehouse. The
requested data is saved, unchanged from the source
system.
Activation of DSO means calculating the delta and
updating the current data snapshot into Active table and
writing the history of changes made into change log table.
The active data table of the IMDSO can be used as a basis
for building data models in SAP HANA (attribute views,
analytical views, and calculation views)

27. Advantages of SAP DXC
SAP DXC requires no additional server or application in the system landscape.
It reduces the complexity of data Modelling in SAP HANA, as it sends the data to SAP HANA
after applying all business extractor logic in the source system.
It speeds up SAP HANA Implementation time lines.
It extract semantic rich data from SAP Business site and provide to SAP HANA.
It reuses existing proprietary extraction, transformation, and load mechanism built into SAP
business Suite systems over a simple HTTP(S) connection to SAP HANA.

28. Limitations of SAP DXC
Data Source must have pre-define ETL method, if not then we need to define them.
SAP DXC requires a Business Suite System on Net Weaver 7.0 or higher (e.g. ECC) equal or
below SP level: Release 700 SAPKW70021 (SP stack 19, from Nov 2008).
A procedure with a key field defined must exist in Data Source .

29. THANK YOU….
For more Details visit: kabilsapworld.blogspot.in