VENKAT SAP HANA

Direct Extractor Connection data replication reuses existing extraction, transformation, and load mechanism built into SAP Business Suite systems via a simple HTTP(S) connection to SAP HANA. It is a batch-driven data replication technique. It is considered as method for extraction, transformation, and load with limited capabilities for data extraction.

DXC is a batch driven process and data extraction using DXC at certain interval is enough in many cases. You can set an interval when batch job executes example: every 20 minutes and in most of cases it is sufficient to extract data using these batch jobs at certain time intervals.

Advantages of DXC Data Replication

This method requires no additional server or application in the SAP HANA system landscape.
DXC method reduces complexity of data modeling in SAP HANA as data sends to HANA after applying all business extractor logics in Source System.
It speeds up the time lines for SAP HANA implementation project
It provides semantically rich data from SAP Business Suite 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.

Limitations of DXC Data Replication

Data Source must have a predefined mechanism for extraction, transformation and load and if not we need to define one.
It requires a Business Suite System based on Net Weaver 7.0 or higher with at least below SP: Release 700 SAPKW70021 (SP stack 19, from Nov 2008).

Configuring DXC Data Replication

Enabling XS Engine service in Configuration tab in HANA Studio − Go to Administrator tab in HANA studio of system. Go to Configuration → xsengine.ini and set instance value to 1.

Enabling ICM Web Dispatcher service in HANA Studio − Go to Configuration → webdispatcher.ini and set instance value to 1.

It enables ICM Web Dispatcher service in HANA system. Web dispatcher uses ICM method for data read and loading in HANA system.

Setup SAP HANA Direct Extractor Connection − Download the DXC delivery unit into SAP HANA. You can import the unit in the location /usr/sap/HDB/SYS/global/hdb/content.

Import the unit using Import Dialog in SAP HANA Content Node → Configure XS Application server to utilize the DXC → Change the application_container value to libxsdxc

Creating a HTTP connection in SAP BW − Now we need to create http connection in SAP BW using transaction code SM59.

Input Parameters − Enter Name of RFC Connection, HANA Host Name and <Instance Number>

In Log on Security Tab, enter the DXC user created in HANA studio using basic Authentication method −

Setting up BW Parameters for HANA − Need to Setup the Following Parameters in BW Using transaction SE 38. Parameters List −

PSA_TO_HDB_DESTINATION − we need to mention where we need to move the Incoming data (Connection Name created using SM 59)
PSA_TO_HDB_SCHEMA − To which Schema the replicated data need to assign
PSA_TO_HDB − GLOBAL To Replicate All data source to HANA. SYSTEM – Specified clients to Use DXC. DATASOURCE – Only Specified Data Source are used for
PSA_TO_HDB_DATASOURCETABLE − Need to Give the Table name having the List of data sources which are used for DXC.

Data Source Replication

Install data source in ECC using RSA5.

Replicate the metadata using specified application component (data source version Need to 7.0, if we have 3.5 version data source we need to migrate that. Active the data Source in SAP BW. Once data source is activated in SAP BW it will create the following Table in Defined schema −

/BIC/A<data source>00 – IMDSO Active Table
/BIC/A<data source>40 –IMDSO Activation Queue
/BIC/A<data source>70 – Record Mode Handling Table
/BIC/A<data source>80 – Request and Packet ID information Table
/BIC/A<data source>A0 – Request Timestamp Table
RSODSO_IMOLOG - IMDSO related table. Stores information about all data sources related to DXC.

Now data is successfully loaded into Table /BIC/A0FI_AA_2000 once it is activated.

This is also known as Sybase Replication in HANA system. The main components of this replication method are the Sybase Replication Agent, which is part of the SAP source application system, Replication agent and the Sybase Replication Server that is to be implemented in SAP HANA system.

Initial Load in Sybase Replication method is initiated by Load Controller and triggered by the administrator, in SAP HANA. It informs R3 Load to transfer initial load to HANA database. The R3 load on source system exports data for selected tables in source system and transfer this data to R3 load components in HANA system. R3 load on target system imports data into SAP HANA database.

SAP Host agent manages the authentication between the source system and target system, which is part of the source system. The Sybase Replication agent detects any data changes at time of initial load and ensures every single change is completed. When th ere is a change, update, and delete in entries of a table in source system, a table log is created. This table log moves data from source system to HANA database.

Delta Replication after Initial Load

The delta replication captures the data changes in source system in real time once the initial load and replication is completed. All further changes in source system are captured and replicated from source system to HANA database using above-mentioned method.

This method was part of initial offering for SAP HANA replication, but not positioned/supported anymore due to licensing issues and complexity and also SLT provides the same features.

Note − This method only supports SAP ERP system as data source and DB2 as database.

SAP HANA ETL based replication uses SAP Data Services to migrate data from SAP or non-SAP source system to target HANA database. BODS system is an ETL tool used to extract, transform and load data from source system to target system.

It enables to read the business data at Application layer. You need to define data flows in Data Services, scheduling a replication job and defining source and target system in data store in Data Services designer.

How to use SAP HANA Data Services ETL based Replication?

For SAP ECC system, choose database as SAP Applications, enter ECC server name, user name and password for ECC system, Advanced tab choose details as instance number, client number, etc. and apply.

This data store will come under local object library, if you expand this there is no table inside it.

Right click on Table → Import by name → Enter ECC table to import from ECC system (MARA is default table in ECC system) → Import → Now expand Table → MARA → Right Click View Data. If data is displayed, Data store connection is fine.

Now, to choose target system as HANA database, create a new data store. Create Data store → Name of data store SAP_HANA_TEST → Data store type (database) → Database type SAP HANA → Database version HANA 1.x.

Enter HANA server name, user name and password for HANA system and OK.

This data store will be added to Local Object Library. You can add table if you want to move data from source table to some specific table in HANA database. Note that target table should be of similar datatype as source table.

Creating a Replication Job

Create a new Project → Enter Project Name → Right Click on Project name → New Batch Job → Enter job name.

From right side tab, choose work flow → Enter work flow name → Double click to add it under batch job → Enter data flow → Enter data flow name → Double click to add it under batch job in Project area Save all option at top.

Drag table from First Data Store ECC (MARA) to work area. Select it and right click → Add new → Template table to create new table with similar data types in HANA DB → Enter table name, Data store ECC_HANA_TEST2 → Owner name (schema name) → OK

Drag table to front and connect both the table → save all. Now go to batch job → Right Click → Execute → Yes → OK

Once you execute the Replication job, you will get a confirmation that job has been completed successfully.

Go to HANA studio → Expand Schema → Tables → Verify data. This is manual execution of a batch job.

Scheduling of Batch Job

You can also schedule a batch job by going to Data Services Management console. Login to Data Services Management Console.

Choose the repository from left side → Navigate to 'Batch Job Configuration' tab, where you will see the list of jobs → Against the job you want to schedule → click on add schedule → Enter the 'schedule name' and set the parameters like (time, date, reoccurring etc.) as appropriate and click on 'Apply'.

SAP HANA Replication allows migration of data from source systems to SAP HANA database. Simple way to move data from existing SAP system to HANA is by using various data replication techniques.

System replication can be set up on the console via command line or by using HANA studio. The primary ECC or transaction systems can stay online during this process. We have three types of data replication methods in HANA system −

SAP LT Replication method
ETL tool SAP Business Object Data Service (BODS) method
Direct Extractor connection method (DXC)

SAP LT Replication Method

SAP Landscape Transformation Replication is a trigger based data replication method in HANA system. It is a perfect solution for replicating real time data or schedule based replication from SAP and non-SAP sources. It has SAP LT Replication server, which takes care of all trigger requests. Replication server can be installed as standalone server or can run on any SAP system with SAP NW 7.02 or above.

There is a Trusted RFC connection between HANA DB and ECC transaction system, which enables trigger based data replication in HANA system environment.

Advantages of SLT Replication

SLT Replication method allows data replication from multiple source systems to one HANA system and also from one source system to multiple HANA systems.
SAP LT uses trigger based approach. It has no measureable performance impact in source system.
It also provides data transformation and filtering capability before loading to HANA database.
It allows real-time data replication, replicating only relevant data into HANA from SAP and non-SAP source systems.
It is fully integrated with HANA System and HANA studio.

Creating a Trusted RFC Connection in ECC system

On your source SAP system AA1 you want to setup a trusted RFC towards target system BB1. When it is done, it would mean that when you are logged onto AA1 and your user has enough authorization in BB1, you can use the RFC connection and logon to BB1 without having to re-enter user and password.

Using RFC trusted/trusting relationship between two SAP systems, RFC from a trusted system to a trusting system, password is no required for logging on to the trusting system.

Open SAP ECC system using SAP logon. Enter transaction number sm59 → this is transaction number to create a new Trusted RFC connection → Click on 3^rdicon to open a new connection wizard → click on Create and new window will open.

RFC Destination ECCHANA (enter name of RFC destination) Connection Type − 3 (for ABAP system)

Go to Technical Setting

Enter Target host − ECC system name, IP and enter System number.

Go to Logon & Security tab, Enter Language, Client, ECC system user name and password.

Click on the Save option at the top.

Click on Test Connection and it will successfully test the connection.

To Configure RFC connection

Run transaction − ltr (to configure RFC connection) → New browser will open → enter ECC system user name and password and logon.

Click on New → New Window will open → Enter configuration name → Click Next → Enter RFC Destination (connection name created earlier), Use search option, choose name and click next.

In Specify Target system, Enter HANA system admin user name & password, host name, Instance number and click next. Enter No of Data transfer jobs like 007(it cannot be 000) → Next → Create Configuration.

Now go to HANA Studio to use this connection −

Go to HANA Studio → Click on Data Provisioning → choose HANA system

Select source system (name of trusted RFC connection) and target schema name where you want to load tables from ECC system. Select tables you want to move to HANA database → ADD → Finish.

Selected tables will move to chosen schema under HANA database.

SAP HANA audit policy tells the actions to be audited and also the condition under which the action must be performed to be relevant for auditing. Audit Policy defines what activities have been performed in HANA system and who has performed those activities at what time.

SAP HANA database auditing feature allows monitoring action performed in HANA system. SAP HANA audit policy must be activated on HANA system to use it. When an action is performed, the policy triggers an audit event to write to audit trail. You can also delete audit entries in Audit trail.

In a distributed environment, where you have multiple database, Audit policy can be enabled on each individual system. For the system database, audit policy is defined in nameserver.ini file and for tenant database, it is defined in global.ini file.

Activating an Audit Policy

To define Audit policy in HANA system, you should have system privilege − Audit Admin.

Go to Security option in HANA system → Auditing

Under Global Settings → set Auditing status as enabled.

You can also choose Audit trail targets. The following audit trail targets are possible −

Syslog (default) − Logging system of Linux Operating System.
Database Table − Internal database table, user who has Audit admin or Audit operator system privilege he can only run select operation on this table.
CSV text − This type of audit trail is only used for test purpose in a non-production environment.

You can also create a new Audit policy in the Audit Policies area → choose Create New Policy. Enter Policy name and actions to be audited.

Save the new policy using the Deploy button. A new policy is enabled automatically, when an action condition is met, an audit entry is created in Audit trail table. You can disable a policy by changing status to disable or you can also delete the policy.

SAP HANA License management and keys are required to use HANA database. You can install or delete HANA License keys using HANA studio.

Types of License keys

SAP HANA system supports two types of License keys −

Temporary License Key − Temporary License keys are automatically installed when you install the HANA database. These keys are valid only for 90 days and you should request permanent license keys from SAP market place before expiry of this 90 days period after installation.
Permanent License Key − Permanent License keys are valid only till the predefine expiration date. License keys specify amount of memory licensed to target HANA installation. They can installed from SAP Market place under Keys and Requests tab. When a permanent License key is expired, a temporary license key is issued, which is valid for only 28 days. During this period, you have to install a permanent License key again.

There are two types of permanent License keys for HANA system −

Unenforced − If unenforced license key is installed and consumption of HANA system exceeds the license amount of memory, operation of SAP HANA is not affected in this case.
Enforced − If Enforced license key is installed and consumption of HANA system exceeds the license amount of memory, HANA system gets locked. If this situation occurs, HANA system has to be restarted or a new license key should be requested and installed.

There is different License scenarios that can be used in HANA system depending on the landscape of the system (Standalone, HANA Cloud, BW on HANA, etc.) and not all of these models are based on memory of HANA system installation.

How to Check License Properties of HANA

Right Click on HANA system → Properties → License

It tells about License type, Start Date and Expiration Date, Memory Allocation and the information (Hardware Key, System Id) that is required to request a new license through SAP Market Place.

Install License key → Browse → Enter Path, is used to install a new License key and delete option is used to delete any old expiration key.

All Licenses tab under License tells about Product name, description, Hardware key, First installation time, etc.