SLT (SAP Landscape Transformation Replication Server) in SAP HANA

What is SLT (SAP Landscape Transformation Replication)?

SLT is the SAP first ETL tool that allows you to load and replicate data in real-time or schedule data from the
source system and Non-Source System into SAP HANA Database.

SAP SLT server uses a trigger-based replication approach to pass data from source system to target system.

SLT server can be installed on the separate system or on SAP ECC System.

Benefit of SLT system is as below-

 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.
 This support automatically non-Unicode and Unicode conversion during load/replication. (Unicode is
a character encoding system similar to ASCII. Non-Unicode is encoding system covers more character
than ASCII).
 This is fully integrated with SAP HANA Studio.
 SLT have table setting and transformation capabilities.
 SLT have monitoring capabilities with SAP HANA Solution Manager.

Architecture Overview of SAP SLT server with SAP / Non-SAP System is as below-

SAP SLT Connection Architecture overview between SAP System and SAP HANA

SAP SLT Replication Server transforms all metadata table definitions from the ABAP source system to SAP
HANA.

For SAP source, the SLT connection has the following features -

 When a table is replicated, SAP SLT Replication server create logging tables in the source system.
 Read engine is created in the SAP Source System.
 The connection between SAP SLT and SAP Source is established as RFC connection.
 The connection between SAP SLT and SAP HANA is established as a DB connection.

A database user with the same authorization as user "SYSTEM" can create a connection between SAP SLT and
SAP HANA Database.
 SAP SLT Connection between SAP System and SAP HANA DATABASE

SAP SLT Server automatically create DB connection for SAP HANA database (when we create a new
configuration via transaction LTR). There is no need to create it manually.

Configure SAP SLT Server for SAP Source System

First we need to configure SAP SLT replication server for connection between SAP Source and SAP HANA
database. T-code, LTR is used for creating a connection between SAP Source and SAP SLT.

Step 1) Login to SAP SLT server, and Call transaction "LTR" from SAP SLT replication server.

A Web-dynpro pop-up screen will appear for login to SAP SLT server.

1. Enter Client / User id / password

2. Click on logon tab
 A pop-up screen for Configuration will appear as below-

Click on "New" Button for the new configuration.

Step 2) In this step,

1. Enter Configuration name and description.

2. Select SAP System as the source system.
3. Enter RFC connection for SAP System.
4. Enter Username / Password / Host Name and Instance number.
5. Enter Job options detail –

 No. of data Transfer Jobs.

 No. Of calculation jobs.

6. Select Replication option as Real Time.

7. Once all the settings are maintained click on 'OK' to create a new schema in SLT.
A Configuration Name "SLTECC" will be added and active.

After configuration SAP SLT server successfully, SAP SLT Server automatically create DB connection for SAP
HANA database (when we create a new configuration via transaction LTR). There is no need to create it
manually.

In next step, we import data to SAP HANA from SAP Source.

Import SAP Source Data to SAP HANA through SLT

Once we have successfully configured SAP SLT server, a SCHEMA as configuration name above in SAP SLT is
created in SAP HANA Database.
This Schema contains following objects-

1. 1 Schema - SLTECC.
2. 1 User – SLTECC.
3. 1 Privileges
4. 8 Tables –

 DD02L (SAP Tables Name )

 DD02T (SAP Table Texts)
 RS_LOG_FILES
 RS_MESSAGE
 RS_ORDER
 RS_ORDER_TEXT
 RS_SCHEMA_MAP
 RS_STATUS.

5. 4 Role -

 SLTECC_DATA_PROV
 SLTECC_DATA_POWER_USER
 SLTECC_DATA_USER_ADMIN
 SLTECC_DATA_SELECT

6. 2 Procedures

 RS_GRANT_ACCESS
 RS_REVOKE_ACCESS

All configuration is completed, now we load a table from SAP ECC (ERP Central Component).

Step 1) To load tables from SAP ECC to SAP HANA database, follow below steps-

1. Go to Data provisioning from Quick View.

2. Select SAP HANA System.
3. Click on Finish Button.
Step 2) A screen for SLT Based Table Data Provisioning will be displayed. There are 5 options for data
provisioning as below-

Provision Option Detail

Load (Full Load) This is a one-time event, which starts an initial load of data from source system.

Replicate(Full Load + It start initial load (if not done earlier), and also consider delta change. Database trigger and related l
Delta Load) each table.

Stop Replication It stops the current replication process for a table. It removes database trigger and logging table com

Suspend It pause a running replication process of a table. The database trigger will not be deleted from the so
changes will continue. Related Information is stored in the related logging table in the source system

Resume Resume restarts the replication for a suspended table. After resume, the suspended replication proc

We use the first option from the table "Load option" for initial load of the table (LFBK) data from source to
SAP HANA table.

Step-by-step is as below-

1. Source and Target system details are selected according to SAP SLT configuration.
2. Click on Load Button and select the table (LFBK) which we need to load/replicate in SAP Hana.
3. Table (LFBK) will be added to Data Load Management Section with Action "Load" and Status
"Scheduled."
After data load, Status will be changed to "Executed". The table will be created in "SLTECC" schema with data.

Step 3) Check Data in the table (LFBK) by Data Preview from Schema "SLTECC" as below -.

1. Login in SAP HANA Database through SAP HANA Studio and select SAP HANA System HDB
(HANAUSER).

2. Select Table (LFBK) under Table node.

3. Right click on Table (LFBK) and click on Open data preview option.
4. Loaded Data through SLT process will be displayed in Data preview screen.
Now we have successfully loaded data in table "LFBK". We will use this table future in Modelling.

SAP SLT Connection between non-SAP System and SAP HANA

SAP SLT Replication Server transforms all metadata table definitions from the non-ABAP source system to SAP
HANA.

For Non-SAP source, the SLT connection has following features -

 When a table is replicated, SAP SLT Replication server create logging tables in the source system.
 Read engine is created in the SAP SLT Replication server.
 The connection between SAP SLT and SAP Source / SAP HANA is established as a DB connection.
 SAP SLT Connection between Non - SAP SLT Connection and SAP HANA System/DATABASE

SAP SLT can only do simplest transformations, so for complex transformations, we need another ETL
tool such as SAP Data services.

SAP HANA Calculation View Tutorial

What is Calculation View?

SAP HANA Calculation view is a powerful information view.

SAP HANA Analytic view measure can be selected from only one fact table. When there is need of More Fact
table in information view then calculation view come in the picture. Calculation view supports complex
calculation.

The data foundation of the calculation view can include tables, column views, analytic views and calculation
views.

We can create Joins, Unions, Aggregation, and Projections on data sources.

Calculation View can contain multiple measures and can be used for multidimensional reporting or no
measure which is used in list type reporting.

Characteristic of SAP HANA Calculation View as below –

 Support Complex Calculation.

 Support OLTP and OLAP models.
 Support Client handling, language, currency conversion.
 Support Union, Projection, Aggregation, Rank, etc.

SAP HANA Calculation View are of two types –

1. SAP HANA Graphical Calculation View (Created by SAP HANA Studio Graphical editor).
2. SAP HANA Script-based calculations Views (Created by SQL Scripts by SAP HANA Studio).

SAP HANA Graphical Calculation View

In SAP HANA Analytic view, we can select a measure from one table only.

So when there is a requirement for a view which contains measure from the different table then it cannot
achieve by analytic view but by calculation view.

So in this case, we can use two different analytic view for each table and join them in calculation view.

We are going to create a graphical Calculation View "CA_FI_LEDGER" by joining two Analytic View
"AN_PURCHASE_ORDER" And "AN_FI_DOCUMENT".

CA_FI_LEDGER will display finance document detail related to a purchase order.

STEP 1) In this step,

1. Go to package (Here Modelling) and right click.

2. Select New Option.
3. Select Calculation View.
A Calculation View Editor will be displayed, in which Scenario Panel display as below –

Detail of Scenario panel is as below –

 Palette: This section contains below nodes that can be used as a source to build our calculation views.

We have 5 different types of nodes, they are

1. Join: This node is used to join two source objects and pass the result to the next node. The join types
can be inner, left outer, right outer and text join.Note: We can only add two source objects to a join
node.
2. Union: This is used to perform union all operation between multiple sources. The source can be n
number of objects.
3. Projection: This is used to select columns, filter the data and create additional columns before we use
it in next nodes like a union, aggregation and rank.

Note: We can only add one source objects in a Projection node.

4. Aggregation: This is used to perform aggregation on specific columns based on the selected
attributes.
5. Rank: This is the exact replacement for RANK function in SQL. We can define the partition and order
by clause based on the requirement.
STEP 2)

1. Click Projection node from palette and drag and drop to scenario area from Purchase order analytic
view. Renamed it to "Projection_PO".
2. Click Projection node from palette and drag and drop to scenario area for FI Document analytic view.
Renamed it to "Projection_FI".
3. Drag and drop analytic View "AN_PUCHASE_ORDER" "AN_FI_DOCUMENT" and from Content folder to
Projection node and "Projection_FI" respectively.
4. Click Join Node from Palette and drag and drop to scenario area.
5. Join Projection_PO node to Join_1 node.
6. Join Projection_FI node to Join_1 node.
7. Click Aggregation node from palette and drag and drop to scenario area.
8. Join Join_1 node to Aggregation node.

We have added two analytic views, for creating a calculation view.

STEP 3) Click on Join_1 node under aggregation and you can see the detail section is displayed.

1. Select all column from Projection_PO Node for output.

2. Select all column from Projection_FI node for output.
3. Join Projection_PO Node to Projection_FI node on column

Projection_PO. PO_Number = Projection_FI.PO_NO.

STEP 4) In this step,

1. Click on Aggregation node and Detail will be displayed on right side of the pane.
2. Select Column for output from the Join_1 displayed on the right side in the detail window.

STEP 5) Now, click on Semantics Node.

Detail screen will be displayed as below. Define attribute and measure type for the column and also, mark key
for this output.

1. Define attribute and measure.

2. Mark PO_Number and COMPANY as Key.
 3. Mark ACC_DOC_NO as key.

STEP 6) Validate and Activate calculation View, from the top bar of the window.

1. Click on Validate Icon.

2. Click on Activate Icon.

Calculation View will be activated and will display under Modelling Package as below –

Select calculation view and right click ->Data preview

We have added two analytic views and select measure (TAX_AMOUNT, GROSS_AMOUNT) from both analytic
view.
Data Preview screen will be displayed as below –

CE Functions also known as Calculation Engine Plan Operator (CE Operators) are alternative to SQL
Statements.

CE function is two types –

Data Source Access Function

This function binds a column table or a column view to a table variable.

Below is some data Source Access Function list –

 CE_COLUMN_TABLE
 CE_JOIN_VIEW
 CE_OLAP_VIEW
 CE_CALC_VIEW

Relational Operator Function

By Using Relational Operator, the user can bypass the SQL processor during the evaluation and communicate
with calculation engine directly.

Below is some Relational Operator Function list –

 CE_JOIN (It is used to perform inner join between two sources and

Read the required columns/data.)

 CE_RIGHT_OUTER_JOIN(It is used to perform right outer join between the two sources

and display the queried columns to the output.)

 CE_LEFT_OUTER_JOIN (It is used to perform left outer join between the sources and

display the queried columns to the output).

 CE_PROJECTION (This function display the specific columns from the source and apply

filters to restrict the data. It provides column name aliase features also.)

 CE_CALC (It is used to calculate additional columns based on the business requirement.
 This is same as calculated column in graphical models.)

Below is a list of SQL with CE function with some Example-

Query Name SQL Query CE-Build in Function

Select Query On Column SELECT C, D From "COLUMN_TABLE". CE_COLUMN_TABLE("COLUMN_TABLE",[C,D])

Table

Select Query On Attribute SELECT C, D From "ATTRIBUTE_VIEW" CE_JOIN_VIEW("ATTRIBUTE_VIEW",[C,D])

View

Select Query on Analytic SELECT C, D, SUM(E) From "ANALYTIC_VIEW" CE_OLAP_VIEW("ANALYTIC_VIEW",[C,D])

View Group By C,D

Select Query on SELECT C, D, SUM(E) From "CALCULATION_VIEW" CE_CALC_VIEW("CALCULATION_VIEW",[C,D])

Calculation View Group By C,D

Where Having SELECT C, D, SUM(E) From "ANALYTIC_VIEW" Var1= CE_COLUMN_TABLE("COLUMN_TABLE");

Where C = 'value' CE_PROJECTION(:var1,[C,D],"C" ="value"/