Many blogs are available on data replication from Non-SAP to HANA. But none of the blogs explain the data replication from SAP to Non-HANA.
The combination of non-ABAP on source and non-ABAP on target side is only officially supported if the non-ABAP target is SAP HANA Database. SAP generally supports if the source system is an SAP system connected via RFC, then connect to any receiver Database system that is supported by SLT (SAP Note 1768805). Plus replication from ABAP-based and non ABAP-based sources into non-ABAP targets is also available on project basis (SAP Note 1768805) please connect with SLT Dev first.
Thus I thought of explaining the configuration via this blog. This blog explains the data replication from SAP R3 system to MS SQL Azure on cloud. The below picture is self explanatory.
Please read the note “1768805 – SAP LT Replication Server: Collective Note – non-SAP Sources” for supported DB releases. Ensure to have the proper license from SAP for SLT for non-hana replication.
Enable SLT Target system dropdown for Non-HANA Target
Follow the note to enable non-hana target in SLT system.
“2285078 – SLT target system dropdown disabled when creating new Configuration”
Prepare SLT system
Please ensure that the SLT system is installed and configured to run the data replication.
For example, HTTP port(SMICM), Roles and below SICF services should be activated.
Please implement all the relevant notes in replication server and source system mentioned in the release note for DMIS component. In my case, implemented all the relevant note as per the note “2016511 – Installation/Upgrade SLT – DMIS 2011 SP7”
Setup RFC and DBCO connection
RFC connection to Source — SLT system to R3
DB Connection to Target — SLT system to MS SQL
For DBCO, please prepare you SAP instance to connect to remote SQL Server. In my case, I followed the note ” 1774329 – Preparing your SAP instance to connect to remote SQL server” to establish DBCO connection.
Enable SLT to push data to Non-HANA
Create a new LTR configuration
Launch configuration and monitoring dashboard through T-code “LTR”
Click on NEW and provide the details.
Press Next, choose the RFC connection to SAP source and put a check mark for “multiple usage” for 1:N scenarios otherwise not required to put a check mark.
Press Next and provide the target system SQL details
I had issues when I used the custom schema name instead of default schema “dbo” and was getting return code 3(writing error on target). The table was getting created with the structure but the data was not flowing. Hence changed the schema to default “dbo” and the data started populating successfully to target SQL.
Press Next and then set the required number of jobs for data transfer. This can be changed dynamically later.
Review and create the configuration in the next step.
Replicate the data to Non-Hana
Go to T-code LTRC –> Choose the Mass Transfer ID created in the previous step.
Navigate to tab “Table Overview” and click on Data Provisioning, provide the table/s and start Initial Load or Replication according to the need.
Once the data flow starts you can check the status in Data Transfer Monitor and for the progress, you can navigate to Load Statistics tab.
Now the data will be transferred to the target MS SQL. Login to the target server and execute few queries to check if everything looks fine.