Although it may not sound so at first, the SLT replication procedure can be quite tricky to get on with. However, that’s what we are going to decipher in this article. So, let’s not make any further ado and get started with our guide right away!
Installation Option For An ABAP And A Non-ABAP Source
When it comes to performing the SLT replication procedure, you can do it through more than one source. Here’s what you need to know about them.
For ABAP Source System
In this case, you can perform the installation procedure through two different options. Please keep reading to learn more about this aspect –
Option – A: The Replication Server Is An Entirely Separate System.
To begin with, you can establish the connection between the SAP Source and the SAP SLT as an RFC connection. If you are not comfortable with that, you may also do the same by using the DB connecting procedure. Once you are done with the table replication procedure, you might try creating a logging table within the source system. Conversely, the read module is going to be created automatically within the SAP Source System.
Option – B: The Replication Server Has Been Installed Within The Source.
In this case, the SAP LT replication server has to be installed at the beginning of the process. Once it’s done, you’ll need to integrate the required SAP NetWeaver and SAP kernel with the same too. The system architecture, then, must be simplified into a two-tier system.
For A Non-ABAP Source System
In this aspect, your job will be a little more intricate and complicated if you haven’t done this task before. Here’s what you have to do here.
- In the beginning, you will need to install the SAP LT server into a separate structure. And, once you’re done, you’ll have to only create the read modules in this case. And the connection between the non-ABAP source to the SAP LT server will be prompted or established through a database connection.
- In the second case, you should begin by checking if your non-ABAP source system is fulfilling all the usage-related prerequisites or not. After all, database connectivity from the non-ABAP system to the SAP LT server will be required in this aspect. Thus if the connection hasn’t been secured, the replication procedure might get crashed.
The Steps Of SLT Replication
Usually, the SLT replication procedure is completed in five minor yet important steps. It may include the following ones for you –
Step – 1: Installing The Replication Server.
The SAP LT replication server will be shipped in a DMIS-based add-on call. So, if you want to begin the replication procedure, you’ll need to install the server in your system first. The installation should be done within your ABAP source system and in the server too.
Note: If the source system is based on an on-premise SAP S/4HANA structure, then there’s no need to install the add-on DMIS. Just check if your system’s release configuration is 1610 or higher or not. In that case, you are good to go.
Step – 2: Configure The Source Data System.
Now, you’ll need to create an RFC ABAP connection to the Source data system from the SLT system. In this case, you will need to fill up the following slots in a drop-down display menu known as RFC destination –
- The RFC destination.
- The connection type.
- The Description 1 section.
- The Target Host.
… and the IP address.
The final option will probably be collected by the system automatically. But, if it doesn’t work for some reason, you will need to provide the same manually.
Step – 3: Begin Your SLT Configuration From The LTR Transaction.
Now, you will need to launch the LTR code you received from the system and start with your guided configuration. It, in turn, will help create the database connection to target the HANA database. Here is some additional information that you need to know in this regard –
- Initial Load Mode: It’s possible to define an Initial Load Mode in case you want to opt for a specifically-different reading type. The “resource optimised” note will define the “default” mode of the system. It will utilise reading type 3 for all the tables. In any case, the “performance optimised” will use a reading type 4 or 5.
- The Number Of Initial Load Jobs: This term defines a job that’s used in the initial load process within the SAP LT replication server.
- The Number Of Calculation Jobs: This value will specify the number of access plan-related calculation jobs. All of these will be allocated by the provided config.
- The Number Of Data Transfer Jobs: Unlike the former, this value will define the overall number of DTJs in your system.
Step – 4: Start From The Source System.
At first, you will need to create a database view or a table. And once you are done, you have to start the replication procedure with the same DB.
Please keep in mind that the process of initial load will begin in this aspect. And it may take quite a bit of time to load the data at the initial phase.
Anyway, once the replication process is active, you will need to perform the following steps to complete the procedure –
- If the target system and the source are different, you have to create the rule assignment within the LTRS transaction code.
- Also, don’t forget to verify the current schema mapping. If you feel like it, don’t forget to create a brand new mapping for your purpose.
Step – 5: The Post-Installation Viewpoint.
Once the procedure is complete, please check if the system has replicated everything as you needed it to. If everything looks alright, don’t forget to activate your SAP HANA. Here’s how you can do the same –
- Go to the CAR system and start with transaction SE38.
- Enter the term “/CAR/ACTIVATE_HTA” and click on Execute.
- Select each and every applicable business scenario, source master data system, and scenario options as a whole.
The Final Say
So, what do you think? Could we convey the information you were looking for? Well, if you still are confused about something, please comment below. We’ll try to answer you as soon as we can. Thanks for reading!
Discover how our end-to-end solutions can help your business thrive. Read more about SLO and explore our success stories to see how we have delivered customised solutions that drive results.
