SAP HANA ETL-Based Replication


The Extraction-Transformation-Load (ETL) based data replication uses SAP BusinessObjects Data Services (hereafter referred to as Data Services) to load the relevant business data from the source system, SAP ERP, and replicate it to the target, SAP In-Memory Database (IMDB).
This method allows you to read the required business data on the level of the application layer.
You deploy this method by defining data flows in Data Services and scheduling the replication jobs.
Since this method uses batch processing, it allows also for data checks, transformations, synchronizing
with additional data providers, and the merging of data streams.
The data replication is operated by Data Services. Its main components are the Data Services Designer, where you model the data flow, and the Data Services Job Server for the execution of the replication jobs. An additional repository is used to store the meta data and the job definitions.

Data Flow
As for any replication scenario you have to define a series of parameters for the two systems involved.
Utilizing Data Services you have to set up Datastores to define such parameters. You use the Designer to set up Datastores.

Datastore Setup
Setting up a Datastore for the source system SAP ERP, choose SAP Applications for the type of Datastore, and specify the address of the system, the User name and Password allowing Data Services to access the system. Additional settings depend on the type of SAP ERP objects to be read.
For the target system of the replication, the IMDB, you have to set up a separate Datastore as done for the source system.

Data Flow Modeling
Once datastores are set up, Data Services can connect to the source system by RFC. Based on the metadata imported from the ABAP Data Dictionary to Data Services, you can determine the business data to be replicated. Data Services offers replication functions for a variety of data source types.
However, for the replication of SAP ERP data to IMDB, we recommend to use extractors.

Note:
• You must apply SAP Note 1522554 to fully benefit from the extractor support.
• In the source system, the extractors must be released for the replication access by Data Services.
In addition, you have to indicate the primary key, such as the GUID, to enable the correct replication.
• The extractors must support delta handling.

Choose the extractors that are relevant for the replication job.
Model the data flow for each extractor you have selected: Indicate the source for the data flow, which
is the extractor. For the target of the replication, choose a template table, which is then used in the
IMDB to store the replaced data.

Data Flow for Initial Load and Update
Both the initial load of business data from the source system into IMDB as well as updating the replicated
data (delta handling) is done using SAP BusinessObjects Data Services.
The initial load can be set up modeling a simple data flow from source to target. For the update, in most cases, the data flow is enhanced by a delta handling element, such as Map_CDC_Operation or Table_Comparison Transform.
It depends on the environment and the requested setup of the target tables which data flow design
serves your requirements best.
Although we recommend to use delta supporting extractors, you can also use SAP ABAP tables.

Replication Job Schedule
Since you can schedule the replication jobs when using Data Services, this method is suited where the
source system must be saved from additional load during the main business hours. Thereby you can
shift the replication work load, for example, to night-time.
As a result, the data that is available for reporting always represents the state reached by the time when the latest replication job was started.
Use the Management Console, which comes with Data Services, to schedule replication jobs. You can
choose from different tools and methods for the scheduling. You can use the Management Console
also to monitor the replication process.

Required Software Components
This replication method requires the following main components:
• SAP In-Memory Database
• SAP BusinessObjects Enterprise
• BusinessObjects Enterprise Central Management Server (CMS), which is a part of SAP
BusinessObjects Enterprise
• SAP BusinessObjects Data Services XI 4.0

 Read about related subjects:

 SAP HANA REPLICATION DATA

SAP HANA Trigger-Based Replication
SAP HANA Log-Based Replication

Comments

Post a Comment

Popular posts from this blog

SAP Dashboard Error - Cannot find the BusinessObjects Enterprise report source. (LO 26608)

<!-- Google tag (gtag.js) --> <script async src="https://www.googletagmanager.com/gtag/js?id=G-NL0CYP13VZ"></script> <script>   window.dataLayer = window.dataLayer || [];   function gtag(){dataLayer.push(arguments);}   gtag('js', new Date());   gtag('config', 'G-NL0CYP13VZ'); </script> Cannot find the BusinessObjects Enterprise report source. (LO 26608) Environment SAP BO XI 4.1 SP 5 two nodes Cluster Windows Server 2012 While refreshing dashboard (based on Live Office connection) from BI Launchpad with a no administrator user the above exception was erased. SAP says: Cause The document is not available; for example it does not exist, or it has been removed. Action Check the report path from CMS and use SetLocation in Live Office to re-define the report source. Otherwise, check if the user has sufficient rights to view the object. Solution In our case  we fixed this problem was to remo
Read more

SAP HANA Introduction

Image
SAP HANA:The future of database technology The capacity of main memory in servers has continuously increased over the years, whereas prices have dramatically dropped. Today, a single enterprise class server can hold several  terabytes of main memory. At the same time, prices for server main memory dramatically  dropped over the last few decades. This increase in capacity and reduction in cost makes it a  viable approach to keep huge amounts of business data in memory. This section discusses  the benefits and challenges. In few words you can understand SAP HANA plus  analyzing this evaluation: Typical access speeds Disk     4,000,000 ns Memory         0.4 ns Speed   10,000,000 Falling prices move processing from Disk/SSD to In-Memory In-Memory Computing The elements of In-Memory computing are not new. However, dramatically improved hardware economics and  technology innovations in software has now made it possible for SAP to deliver on its vision of the
Read more

SAP BusinessObjects 4.0 - Suite Presentation

Image
The latest Business Objects Suite, B.O. 4.0,  is suitable for every kind of user from top managers to simple clerk. It has a new  styling and unified look and feel in every tool of the suite. It garantees common query design experience across all data sources. It allows interactivity with shared charting, alerting, and search options. B.O. 4.0  has a new information design tool for heterogeneous access over all sources that represents  abstraction layer for multi-dimensional data sources. Beside it allows: A simplified, Right-Scale Deployment Enhanced scalability with virtualization and native 64-bit support Comprehensive system diagnosis and monitoring New auditing for compliance and usage analysis. New User Experience SAP BusinessObjects Mobile BI  Interactive Reports & Dashboards Allows to: Make informed decisions with instant access to personalized information Leverage existing BI investments & skills to quickly reach mobile users E
Read more