Hi All,

This document will give a basic overview on monitoring SLT activities and will also highlight on basic checks that can be done to find the root cause for errors that might arise.

This is an ongoing document and is based on details given in SAP LT Application Operations Guide and on personal experience from SLT projects.

Hope this gives a good overview for beginners!

Regards,

Saritha K

Dear All,

with this Blog I want to give you an update o the SLT scenario for Operational Data Provisioning.

Most important:

With the new SP7, the SLT scenario for ODP is no longer limited in terms of parallel initial load! That is, now every subscriber (up to 4) gets the initial load of requested tables, no matter if it is the first or fourth subscription on the Delta Queue.

Since SP6 already, SLT supports in this scenario also non-ABAP systems and pool- and cluster tables.

Use Cases:

The most important benefits for Data Replication with SLT into SAP BW are:

- Replacing nightly batch loads with (near) real-time data transfer

- Reducing the amount of transferred data from full loads to delta-only

Can also be used to replace generic BW extractors:
combine the tables/fields of the extractor in a view and replicate only deltas with help of SLT. Make use of Advanced Replication Settings/ Transformation Rules.

- Management of multi client data extraction with SLT reduces management effort drastically

Customer example:

Image may be NSFW.
Clik here to view.

Customer could reduce the running data transfer processes and the number of DataSources to one, and the implementation of a new client means no effort for data replication.

SpeedDemo:

the newest SpeedDemo on DMIS2011 SP7 with BW 7.40 can be found here:

External link:http://demo.tdc.sap.com/SpeedDemo/b8a87ba2b128bb28

Image may be NSFW.
Clik here to view.

Scan the QR code to launch directly on iPad

Best Regards,

Astrid

SP09 was released on 28^th of July!

Pls. go to our page on the Support Portal to get an overview on our product SAP LT!

Here, you find in detail the Features for every solution included.

Heike Jensen

SAP SE, AGS SLO Product Management

Hi All,

at TechEd Las Vegas we are offering the following sessions around SAP LT Replication Server:

EXP27314     Meet the Expert: SAP Landscape Transformation Replication Server

                    Tue 03:30 PM - 04:00 PM Lounge 2, Show Floor

DMM806       Road Map Q&A: SAP Landscape Transformation Replication Server

                    Wed 02:00 PM - 03:00 PM Road Map Q&A 3, Show Floor Learn Zone – Hall C, Level 2

DMM806       Road Map Q&A: SAP Landscape Transformation Replication Server

                    Thu 12:00 PM - 01:00 PM Road Map Q&A 4, Show Floor Learn Zone – Hall C, Level 2

EXP27315     SAP Landscape Transformation Replication Server

                    Thu 02:30 PM - 03:00 PM Lounge 2, Show Floor

DMM164       SAP Landscape Transformation Replication Server: Real-Time Data Replication

                    Tue 11:15 AM - 01:15 PM Lando 4205

DMM164       SAP Landscape Transformation Replication Server: Real-Time Data Replication

                    Wed 10:30 AM - 12:30 PM Murano 3305

DMM107       SAP Landscape Transformation Replication Server: Real-Time Use Cases

                    Wed 09:15 AM - 10:15 AM Marcello 4401A

DMM107      SAP Landscape Transformation Replication Server: Real-Time Use Cases

                    Thu 09:15 AM - 10:15 AM San Polo 3406

DMM268       Streamline the Transfer of Data into SAP BW

                    Fri 08:00 AM - 10:00 AM Murano 3301B

DMM268      Streamline the Transfer of Data into SAP BW

                    Thu 04:30 PM - 06:30 PM Murano 3303

ITM230        Data Migration to SAP S/4HANA with SAP Landscape Transformation

                   Tue 11:00 AM - 12:00 PM Titian 2202 

ITM230        Data Migration to SAP S/4HANA with SAP Landscape Transformation
                   Wed 03:15 PM - 04:15 PM Palazzo Ballroom O 

EXP27014    Landscape Transformation Management Tools and Services

                    Tue 02:30 PM - 03:00 PM Lounge 5, Show Floor 

EXP27014    Landscape Transformation Management Tools and Services

                    Thu 02:30 PM - 03:00 PM Lounge 5, Show Floor

Visit us at POD S32 "Migration, Conversion, and Realtime Replication" at the Show Floor!

Hi,

as already announced at TechED this year, here is the new Performance Optimization Guide for SLT:

https://scn.sap.com/docs/DOC-68672

Feel free to post here any feedback.

Best, Tobias

Dear All,

SAP TechEd 2015 is over – thanks a lot to those who joined our sessions or stepped by at our pod in the show floor. Our sessions were nearly sold out, but they were also recorded.

Image may be NSFW.
Clik here to view.

You can find a replay on the TechEd homepage:

DMM164: SAP Landscape Transformation Replication Server: Real-Time Data Replication

SAP Landscape Transformation Replication Server is the cornerstone in landscapes requiring real-time data replication – such as landscapes with the SAP HANA platform; the SAP Business Warehouse (SAP BW) application; or SAP Simple Finance, central finance foundation. This session provides you with details about the new version, the functions, and the road map and gives you hands-on experience for different use cases.

http://events.sap.com/teched/en/session/26562 (22minutes introduction on SLT)

Find the slides on http://www.sapevents.edgesuite.net/TechEd/TechEd_Vegas2015/pdfs/DMM164.pdf

DMM268: Streamline the Transfer of Data into SAP BW

Experience how the power of SAP Landscape Transformation replication server combines with operational data provisioning (ODP) to transfer delta data in real time into SAP Business Warehouse (SAP BW). Learn how to transform and filter data in the source system to reduce data traffic, and benefit from real-time data for your reporting requirements.

http://events.sap.com/teched/en/session/26564 (17 minutes introduction on SLT for BW)

Find the slides under http://www.sapevents.edgesuite.net/TechEd/TechEd_Vegas2015/pdfs/DMM268.pdf

Regards

Astrid

Recently i got the chance to work very closely with SAP Basis for installing the SAP HANA Live Components of various applications i.e. SAP ECC, CRM , TM , EM , APO, EWM and also HANA Live Browser as well etc.

Initially i was not sure and was not aware of various Prerequisites (HANA , SAP Source systems , SAP SLT Server requirements) for installing the same and it took a lot of time to come up with the information so as to plan for installation.

I would like to summarize this so that the same can be used for others saving time for installation.

Note: SAP LT Replication server was installed as a separate SAP System.

Refer the mentioned SAP notes for the various Prerequisite Table for each of the above mentioned HANA Live Components.

Thanks for reading.Image may be NSFW.
Clik here to view.

Our production system is ECC 6.0 and we are not  planning to upgrade and migrate our system to HANA in a short period of time. On the other hand we want to use Hana live analitics and consume our real-time data with Lumira. For this requirement we decided to go with sidecar POC senario. With the DMIS addon capability we can make ABAP to ABAP replication for the specified tables. Our sidecar scenario requires standalone SLT and HANA license.

First of all we need to check our systems patch level and start for installing DMIS addon for SLT. On the ERP side we need to  install DMIS 2011_1_700 SP9 addon. In our case, SAP LT Replication Server is in the same system and we don’t need to check compatibility for support package level on both systems.

In the target system (Business Suite on Hana, ECC 6.07) also I have installed DMIS addon 2011_1_731 SP9. Main OSS note for DMIS addon is “2191214 - Installation/Upgrade SLT - DMIS 2011 SP9”. As an alternate you can use SAP Solution Manager system as an LT Replication server for non production usage. For productive usage SAP recommends dedicated SAP LT Replication server.

In the both side RFC connections were created and tested before creating configuration. For ABAP source system, we created a new user (do not use DDIC) and assigned the role IUUC_REPL_REMOTE  for RFC connection. With DMIS addon, two new roles have been created. In the replication system, roles SAP_IUUC_REPL_ADMIN and SAP_IUUC_REPL_DISPLAY are required to create, change or display configurations. Additionally i gave the roles related with NW Business Client which role names are including *NWBC*. You can follow the Application Operations Guide for SAP LT  at service.sap.com/instguides.

After preparation steps, we defined a connection between the source and target system. SAP defines this information as a configuration. In the replication server via transcation LTR we have created new config which name is ERP2HANA. In the configuration wizard, we specified source and target system and rfc names with the standard transfer settings. Now we were ready for the replication. In the transaction LTRC, gone through Data Provisioning button and selected the tables VBAK and VBAP then executed succesfully. You need to check the tables are exist in the both side exactly, because SLT couldnot create the target table structure.  Also if you have different client number between source and target; you need to specify transfer rules.  In my case, i am using Lumira and handling with the help of it without defining transfer rules.

Image may be NSFW.
Clik here to view.

In the LT Replication Server Cockpit (LTRC) i can check the transfer status for tables, view and analyze errors, change table write modes, reset load and replication in the expert mode. During replication you can get dublicate error short dump and use oss note 1972009 for solving and resetting status. Also MWBMON transaction can be used for monitoring mass data transfer.  Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

After sucessfully transferring data to HANA, I have validated data by running a simple SQL sentence in HANA studio.

Image may be NSFW.
Clik here to view.

SLT as we know is one of demanding middleware technlogies today which can be very useful, though normally roadmap for SLT is HANA but in our case it was decided to use Oracle as target system and SAP ECC as the source. From SLT SP009 - it started supporting Oracle as target as well. Here is quick overview on few learnings -

Data Flow :

SAP ECC ->SLT- >Oracle DB

1) Sizing of Oracle DB Target -Memory size of Oracle DB need to be estimated correctly else often the issue occured where oracle system memory was full becaue of volume of data flowing from SAP ECC.Hence we needed to increase the memory size of Oracle to fix this issue and hence in longer term need to estimate size growth and accrodingly take actions.

2) Stats for Initial Load in SLT-  For number of tables it was observed that initial loading stats information in LTRC T code was misisng and this was fixed when SAP suggested to apply SAP Notes but the same issue appeared again when we were loading other tables then SAP said this will be taken up in further release as this was major change.

3) Timestamp field Oracle requirement- There was requirement to add Timestamp field to tables in SLT, and send across data to Oracle in oracle time stamp format.This was acheived by passing hard coded value from SLT in Oracle time format and then script was written in Oracle which will overwrite this value with latest time stamp from Oracle.

So the timestamp generation in SLT was possible but while updating to Oracle data type changed to VarChar which was not required as user required it in TIMESTAMP data type of Oracle. Hence this was only posisble in Oracle system.

4)Language Text Issue- Certain Russian language characters were reported as question mark ? in Oracle as system could not recognize and hence to fix this Oracle was upgraded to have multi Lingual capability. Post that this was rectified.

Hope above helps.

thanks,

Nilesh

Dear All,

              With this blog I would like to share the learning I had with the SLT configuration with Single source and multiple controller systems

SLT Replication Server Version details:

          SLT NW 731 SP5 – DMIS 2011_731 SP5 on Oracle Database

          HANA Revision: 74.04

SAP LT Replication server - Conflicting Objects

    In certain scenario there can be a case where in the data is required from one particular source system in same or different HANA databases using different controller systems (SLT replication servers).

Due to multiple Replication servers and only one source system, conflict between objects such as triggers, logging tables, synonyms and run time objects created by two separate SLT servers can occur.

The only reason for these conflict is the number ranges defined in the SLT system, the number range for SLT replication server is defined in 3 sections; as follows

• DMC_FMID

          This is the number range used during the generation of the runtime objects (function modules) which are called or created during replication startup for          a particular application table

• IUUC_SHDW

          This Number range used during the generation of the Triggers and the logging tables

• IUUC_TABID

          This Number range used during the generation of the synonyms

    To avoid such situations we need to update the above mentioned number ranges to one of the Controller system so that the conflicts can be avoided.

These changes are required to be done before creating any new configuration.

Ensure that these changes are applied before initiating or executing any data transfer activities from the central system on the connected SAP source system(s) - otherwise previously generated objects in the source or target system might become corrupted.

To change the number ranges in each additional central system, proceed as follows:

• Enter transaction SNRO in each subsequent central system.
• Change the default number range intervals for the following objects:
  1. DMC_FMID (<15 digits>): Number used in name of generated runtime object (function module)
     For example starting with:
     - 000030000000000 in 2nd control system
     - 000050000000000 in 3rd control system, etc.
  2. IUUC_SHDW (<7 digits>): Number for trigger and logging table
     For example starting with:
     - 3000000 for 2nd control system
     - 5000000 for 3rd control system

          Note: the number range object IUUC_SHDW allows numbers with 8 digits. However, since some scenarios overwrite the first digit when creating object          identifiers, you must use only 7 digits when defining the number range intervals.

• Only relevant for SAP LT Replication Server:

1. IUUC_TABID (<11 digits>): Number of synonyms for 1:N replication - used by SAP LT replication server only!
         For example starting with:
         - 30000000000 for 2nd control system
         - 50000000000 for 3rd control system

References :

• 1892481 - Conflicting generated objects using DMIS-based Applications

Do share your feedback or questions in case any.

Thanks and Regards

Amar Ghuge.

Dear All,

With this blog I would like to share the learning which i had when i wanted to use the same source system for replication from different clients using the same controller SLT system.

SLT Replication Server Version details:

          SLT NW 731 SP5 – DMIS 2011_731 SP5 on Oracle Database

          HANA Revision: 74.04

SAP LT Replication server – Allow Multiple Usage

          In certain cases where any single client replication from a source system is not enough and we want to use the same source system again for the replication but this time from a different client.

          For any SLT system we can use the same source systems 4 times, only if the reuse of the system is marked as true.

          For making multiple source system connections using the same source system we have to make sure that the option “Allow Multiple Usage” option is checked during the first SLT replication configuration.

          If the option “Allow Multiple Usage” is not selected for a particular source system the only option available in that case would be to delete the configuration and create a new one with this check “Allow Multiple Usage” as true. For new configuration we don't need to create a new schema in HANA we can use the same schema for replication.

          Please Note: Checking the option “Allow Multiple Usage” doesn’t have any impact even if the source system is not configured again for replication. Thus it is always a best practice to check the option “Allow Multiple Usage”.

Please do let me know your feedback on same or let me know in case of any questions and concern.

Thanks and Regards,

Amar Ghuge

Dear All,

a lot of customers approached us asking if they can transfer their delta data with SLT to Hadoop. See here how the setup can look like to transfer data with SLT to SAP HANA and from SAP HANA further on to Hadoop and what the benefits are if you use SLT - like full coverage of table types: transparent, pool and cluster tables as well as INDX type tables, and full coverage of all ABAP source systems from 4.6c on...

E2E Scenario: SAP LT Replication Server and Hadoop using the Data Lifecycle Manager in SAP HANA Data Warehousing Foundation

Regards

Astrid

Hi,

I want to share with you some special considerations and settings that has to be defined for specific tables if you replicate from an ABAP source or into an ABAP target that is using HANA as a database. I copied the note text:

2319897 - SLT – Replicating data from tables with no primary key on DB level

You are replicating data from an ABAP-based SAP system running on SAP HANA, and you face the following issue: You want to replicate data from an SAP application table whose primary key is defined in the ABAP Dictionary, not in the database. You want to replicate data into an SAP application table whose primary key is defined in the ABAP Dictionary, not in the database. This SAP Note explains how to avoid inconsistencies when replicating data from such tables.

Reason and Prerequisites

You use SAP LT Replication Server with release DMIS 2011

Within an SAP HANA-based SAP system (i.e. SAP S/4HANA, SAP Business Suite on SAP HANA) there are SAP application tables whose primary key is defined in the ABAP Dictionary, not in the database. This has been designed in order to save memory space in the in-memory SAP HANA database. Application logic of the source system ensures that no duplicate records occur.

The list of currently known tables include:

ACDOCA

ACDOCP

FAAT_DOC_IT FAAT_PLAN_VALUES

FAAT_YDDA

MATDOC

MATDOC_EXTRACT

VER28179_NP

The replication of data can result in duplicate records in the target system if no primary key (including a unique constraint) has been defined in the database for the target table.

Solution

1.) If you are using an RFC connection to connect to the receiver system, SLT expects the table to exist already. In this scenario SLT won't create any primary key (including a unique constraint) on the

2.) If you are using an RFC connection to connect to the source system database (standard option for an ABAP-based SAP system), SAP LT Replication Server will create a primary key (including a unique constraint) for the target table in the database automatically. This setting should not be changed, because otherwise replication of data into that table may cause duplicate records and therefore inconsistencies.

3.) If you are using a direct database connection (connection type DBCON) to connect to the source system database, SAP LT Replication Server will not find a primary key in the source system database for the relevant table, and therefore cannot create a trigger. Data cannot be replicated to the target system.

Solution:

- For each table whose primary key is defined in the ABAP Dictionary, not in the database, you need to explicitly tell SLT which fields to use to track changes. You therefore have to create entries in the following SLT delivered table IUUC_DB_TAB_KEYS according to the SAP ABAP Dictionary key definition of the application table.

- You can now start the replication of the table (or tables). In the target system, the target structure will be created according to the database view that was created in the source system (including the primary key and related unique constraint).

When using SLT to replicate data from Oracle DB to HANA, you might see SQL error 932 occurred on a specific table and the initial load was failed.
The reason is that you have defined a long field in the table, e.g. VARCHAR(2000).
Following is an example of the problem and the workaround.

• We create table SLT_DEMO with 3 long fields - BBB, CCC and DDD, and insert 2 records into it as below.
  Image may be NSFW.
  Clik here to view.
• We start to load the table in SLT.
  Image may be NSFW.
  Clik here to view.
  However the load failed. We can see SQL error 932 below in tag "Application Log" or by clicking "View Errors" button.
  Image may be NSFW.
  Clik here to view.
  Image may be NSFW.
  Clik here to view.
  We also can see the following shortdump occurred in ST22.
  Image may be NSFW.
  Clik here to view.
• Now let's check the proxy table of SLT_DEMO.
  You can see the data type of CCC and DDD were converted to "STRING" which should be "CHAR".
  However BBB was converted to "CHAR" correctly.
  Image may be NSFW.
  Clik here to view.
  Data type "STRING" is for "LONG" and "CLOB", so when SLT tried to read data from SLT_DEMO on the source DB, it hoped field CCC and DDD should be "LONG" or "CLOB".
  However it found the data type of CCC and DDD were"VARCHAR", then error "inconsistent datatype" occurred.
• We can use table IUUC_DB_COL_TYPE to specify the data type of a field in SLT as below.
  We need to stop the load and add 2 records in table IUUC_DB_COL_TYPE for CCC and DDD in SE11.
  Image may be NSFW.
  Clik here to view.
  We need to specify the values as below.
  Image may be NSFW.
  Clik here to view.
  Field "DBCON NAME" and "DB SCHEMA" can be found in tag "Administration Data" in LTRC.
  Image may be NSFW.
  Clik here to view.
  Now we have 2 convert rules in table IUUC_DB_COL_TYPE.
  Image may be NSFW.
  Clik here to view.
• Let's start the load in LTRC again.
  You can see the data was loaded without any problem.
  Image may be NSFW.
  Clik here to view.
  Image may be NSFW.
  Clik here to view.

We do not have a plan to enhance this functionality at the moment and the design may change, so there is no Note or KBA to introduce the workaround.
If you have the same problem, you have to refer to this blog.

Hi All,

I was planning trying to write a Technical blog which couldn't happen in these many years but finally got chance today.

As this is my first blog on technical details please let me know if there are any missing screenshots or mistakes.

The blog contains the navigation and important points in SLT as I have came across.(major details are already mentioned in old blogs by scn experts).

I have already worked in SLT but never worked on advanced settings so this blog will have all those details which I came across recently.

1. Recently all replications were changed to inactive status due to some issue.

Image may be NSFW.
Clik here to view.

To activate it -

Click On related Configuration Name to go for detail screen. Then go to Administrative Data and click on Button Activate for Configuration Status.

Image may be NSFW.
Clik here to view.

Now if we have no issue then the Configuration Status will be Active

Image may be NSFW.
Clik here to view.

As in above screen shot data replication starts again.

Now we will look at the other Tabs :

      2. Checking created FM and all relevant objects of SLT.

  Goto Data Transfer Monitor and Double click on our Custom table as highlighted as in below screenshot.

Image may be NSFW.
Clik here to view.

It will take us to the new screen as below.

Image may be NSFW.
Clik here to view.

Click on Button Display.

Image may be NSFW.
Clik here to view.

_017 corresponds to Mass Transfer ID and in Description we can see our Ztable name ZEMPLOYEE_TEST.

Note : All SLT related names of jobs or any objects have *IUUC*.

Function Group has Function Modules and which have code related to SLT.

To check the Target Structure from SLT double click on the short text adjacent to No 3 as highlighted in below screenshot.

Currently Consistency overview is green or good.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

We can see the Final structure which is moving from SLT as in above screenshot.

Now go back and click on No 4 to see the source structure/ fields.

Initially we get the screen as below. Then click on drop down adjacent to S_LOGTAB to see source structure S_EMPLOYEE_TEST.

Image may be NSFW.
Clik here to view.

Double click on S_EMPLOYEE_TEST see the fields related to that structure

Image may be NSFW.
Clik here to view.

Go Back and Click on Conversion Logic to see the if any ABAP coding is available.

Image may be NSFW.
Clik here to view.

Then we can see the screen as below.

Image may be NSFW.
Clik here to view.

Processing-Related - Corresponds to the code written at field.

Event-Related          - Corresponds to event based code as its self explanatory.

For Testing purpose I gave both to check where this link will be available.

Double click on Processing Related Fields - TEST_FIELD.

Note : Please remember that this will be our Target field name we have used. For understanding purpose I am attaching Target structure once again as below.

Image may be NSFW.
Clik here to view.

      Click on button highlighted below as ABAP editor.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

The highlighted one in above screenshot is ABAP include where code is written.(As field symbol names are big it didnt fit in 72 char so need to create a new include and write the code in that. ex : <wa_s_zemployee_test>-new_field and other condition). When we write the code in include we need to use other fields as below instead of field symbol.

Image may be NSFW.
Clik here to view.

Go back and click on the parameters Tab and we can see the import and export parameters to be used.

Image may be NSFW.
Clik here to view.

Now Double click on BOR under Event-Related and the ABAP Editor as highlighted to see the ABAP program used.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

For our demo purpose I used both field and Event based. I have used only BOR event based to check the replication.

Now go back 4 times to get to the LTRC default screen.

  3. Goto Expert Functions and Settings for Notifications - to mention any email ids incase of any issue in SLT replication.

Image may be NSFW.
Clik here to view.

Double Click on Settings for Notifications.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Goto Expert Functions andcheck Job Health

Image may be NSFW.
Clik here to view.

Remaining all are self explanatory. Will add them once I come across any important point.

Hoping that this will be useful for all who are in SLT.

Please do share your valuable feedback.

In this blog, we will have a look on how to create the SLT configuration for BW PSA scenario.

Prerequisite:

• DMIS add-on on BW system.
• RFC connection work between SLT system and BW system

Landscape:

Image may be NSFW.
Clik here to view.

Steps :
1. Go to transaction LTRC , create configuration, input configuration name, and descritption
Image may be NSFW.
Clik here to view.

2. Choose Source System, here we are using the SAP source system.

Image may be NSFW.
Clik here to view.

3. As we will use BW as target system, so here we choose RFC connection and scenario of "Persistent Staging Area (PSA) for SAP BW" . And then input the created RFC connection to BW system. And for Logical System Name, we input the name we want. And note this Logical System name, we will use it later.

Image may be NSFW.
Clik here to view.

4. As we are just testing, so here we set the following parameter

Image may be NSFW.
Clik here to view.

5. Review your settings and create the configuration.

Image may be NSFW.
Clik here to view.

6. Go to BW system， transaction RSA1， click on "Source System" and right click on "Web Service" , and click on "Create".

Image may be NSFW.
Clik here to view.

7. Create the web Service Source System, For "Logical System Name", input the name that you defined in step 3.  And input your source system name.

Image may be NSFW.
Clik here to view.

8. Then all are prepared, we can start replication of tables.

Image may be NSFW.
Clik here to view.

10. SLT: transaction LTRC -> Table Overview -> Data Provisioning -> Start Load -> Table : ZKLAUS_TEST

Image may be NSFW.
Clik here to view.

11.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

12. BW side , when you double click on source system Z07, it will jump to the datasource "Unassigned Nodes" -> "test open sql from sum" . And you can find the datasouce "SLT_ZKLAUS_TEST", right click -> manage.

Image may be NSFW.
Clik here to view.

13. And you coud find that the table has already been transferred to PSA.
Image may be NSFW.
Clik here to view.Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

This is whole steps for creating the configuration for BW PSA scenario.

You want to replicate view in Oracle to HANA , while the view include two tables in different tablespace.

Preparation:

Table in oracle:

Table 1:  SLT_DEMO , SLT_DEMO is in tablespace TEST
Image may be NSFW.
Clik here to view.

Table 2 : SLT_DEMO1 , SLT_DEMO1 is in tablespace SLTORA

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

VIEW : VIEW_TEST

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Go to SE16 -> Table "IUUC_DB_TAB_KEYS" -> add entry like below.

DBCON NAME:  input your db connection

DB SCHEMA: your DB schema

INT TABNAME: The View that you want to replicate

INT FIELDNAME: The key of the view

IS KEY : X

KEY POSITION : The position of the KEY

Image may be NSFW.
Clik here to view.

P.S. If you you have several keys, you could add severy entries one by one.

e.g.

Image may be NSFW.
Clik here to view.

1. Go to transaction LTRS, then we need to define the advanced settings before we replicate the view.

•    Transaction LTRS -> Choose your Mass Transfer ID -> Right click on "Table Settings" -> Add table -> Here we add the base table "SLT_DEMO".
•    In "Structure Template", we input the view that we want to replicate
•    In "Deviating Table Name" , here we can define the name that you want in your target system. If you want the name in target system the same as your source system. Here you can input "VIEW_TEST" the same name as the view in your source Oracle system.
•    For "View for Initial Load" and "View for Replication", we input the same as "Structure Template"
•    Then click "Save" button to save the settings.

Image may be NSFW.
Clik here to view.

   Click on "Table Structure" tab, you will find that the structure has already been changed to the same as the view in Oracle.

Image may be NSFW.
Clik here to view.

   Right click on "Performance Options" -> Add table SLT_DEMO -> Change the "Reading Type" to "5 Sender Queue". And click on "Save" button.

Image may be NSFW.
Clik here to view.

2. Go to transaction LTRC -> Table overview -> Data Provisioning -> Start replication of table "SLT_DEMO" .

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

And you will find that the view VIEW_TEST has aleady been replicated to HANA.

Image may be NSFW.
Clik here to view.

After convert HANA to MCD (MultiTenant) some tasks must to be executed in SLT to connect with MCD Database.

In addition to Note 2101084 please check the SAP Note relevant for your DMIS version from the list below and ensure all corrections are applied to both source and SLT server where indicated in the note.

• 2016511 - Installation/Upgrade SLT - DMIS 2011 SP7
• 1958809 - Installation/Upgrade SLT - DMIS 2011 SP6 / DMIS 2010 SP10
• 1882433 - Installation/Upgrade SLT - DMIS 2011 SP5
• 1824710 - Installation/Upgrade SLT - DMIS 2011 SP4 / 2010 SP9
• 1759156 - Installation/Upgrade SLT - DMIS 2011 SP3 / 2010 SP8
• 1709225 - Installation/Upgrade SLT - DMIS 2010 SP7 / 2011 SP2
• 2191214 - Installation/Upgrade SLT - DMIS 2011 SP9 & SP10

All corrections are necessary in order for SLT to function as intended. Once all corretions are installed please follow the instructions below:

Now in SLT we create the IUUC_HOST_PORT table as shown below

   1.- Execute the SE11 transaction

Image may be NSFW.
Clik here to view.

   2.- Copy the table name and click on CREATE

Image may be NSFW.
Clik here to view.

   3.- Set the following configuration. At the end save and activate it

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

   4.- Create a entry from SE16 transaction

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

Image may be NSFW.
Clik here to view.

The IUCC HOST: Is the value you set in xsengine.ini -> public_urls

You need to add a virtual hostname in xsengine.ini -> public_urls   You can do it from SystemDB or TenantDB, but if SystemDB is used, when saving the value, please select the TenantDB

Image may be NSFW.
Clik here to view.

The IUUC PORT

Execute the following query in the tenanDB to get the internal port used by indexserver:

Image may be NSFW.
Clik here to view.

In my case 41

Save the entry

   5.- Execute LTRC transaction

Image may be NSFW.
Clik here to view.

   6.- Deactivate and Activate the replication