Skip to main content

Accelerate Data Replication with SAP SLT: Real-time Made Easy!

SLT (SAP Landscape Transformation) is a powerful ETL (Extract, Transform, Load) tool designed to facilitate real-time or scheduled data replication from SAP source systems or non-SAP systems into SAP HANA Database. It employs a trigger-based replication approach, which means that database triggers are activated whenever data is populated in the logging table.

Here are some key details about SLT:

  1. Real-time and Scheduled Replication: SLT enables both real-time and scheduled data replication. It ensures that changes made in the source system are promptly replicated to the target system.

  2. Support for Cluster and Pool Tables: SLT can replicate data from both Cluster tables and Pool tables, allowing for a comprehensive data replication solution.

  3. Real-time Data Transformation: SLT not only replicates data but also provides transformation capabilities to convert the data into the appropriate format for SAP HANA. This ensures that data is readily usable in the target system.

  4. Integration with HANA Studio: SLT is seamlessly integrated with HANA Studio, providing a user-friendly interface for managing and monitoring the replication processes.

  5. Table and Rule Settings: SLT offers flexible table settings and rule settings, allowing for customizable data replication and transformation processes to meet specific business requirements.

  6. Monitoring Capabilities: SLT can be monitored using the SAP Solution Manager, providing comprehensive insights into the replication status and performance.

Architecture of SAP SLT server with SAP as Source System:



  • DB Triggers: SLT utilizes database triggers to monitor events such as inserts, deletes, modifications, and updates that occur in the application table of the source system.

  • Logging Tables: When a database trigger is activated, the modified data is stored in logging tables created on the source system. These logging tables serve as a temporary storage for replicated data.

  • Read Engine: The read engine reads the data from the logging tables and sends it to the SLT Replication server.

  • Mapping and Transformation Engine: This engine handles the structured transformation of data to match the target HANA DB format, ensuring compatibility and consistency.

  • Write Engine: The write engine is responsible for writing the transformed data into the HANA DB from the SLT Replication server.

The installation of SAP SLT Replication Server can be done in two scenarios:

  1. Source System is SAP System: In this case, the SLT Replication Server can be installed either as a standalone system or on the source system itself.

  2. Source System is Non-SAP System: When the source system is a non-SAP system, the SLT Replication Server can only be installed as a standalone system. Additionally, a DB connection is established between the non-SAP source system and the SLT Replication Server, while an RFC connection is used with an SAP source system.

How SLT Works:

The replication process between the SAP source system, SLT Replication server, and HANA DB involves the following steps:

  1. Establish RFC Connection: An RFC connection is set up between the SAP source system and the SLT Replication Server.

  2. Establish DB Connection: A DB connection is established between the SLT Replication server and the HANA DB.

  3. Initial Load: When the replication option is executed for a table for the first time, the system loads the entire data from the application table into the HANA DB.

  4. Replication: After the initial load, the status changes from "Load" to "Replicate." The DB trigger and logging table are created in the source system to store modified data as per the triggers.

  5. Data Read and Transformation: The read engine retrieves data from the logging table and sends it to the SLT Replication server via the RFC connection. The SLT Replication server then performs necessary transformations and formatting to match the HANA format.

  6. Data Writing: The write engine writes the transformed data into the HANA DB using the DB connection, ensuring that the replicated data is securely stored in the target system.

Note :

Replicating archive tables is supported since DMIS 2011 SP11. Supported Source systems for archiving are listed in the two following notes:

2325520 - Installation/Upgrade SLT - DMIS 2011 SP11 2415064 - Installation/Upgrade SLT - DMIS 2011 SP12


While reading about SLT I came across another blog which focuses on a real time use case,

We will focus on a specific use case of SAP Landscape Transformation Replication Server (SLT) that highlights its cost-saving benefits. The author shares their experience of working on a project where the customer was reporting directly against their HANA ECC database using Calculation Views with SAP and non-SAP reporting tools. This required an expensive Enterprise license for the full ECC instance.

To reduce costs, the author suggested an alternative approach. They recommended the customer to stop reporting directly against the main ECC system and instead use a "sidecar" HANA Enterprise instance with replicated data. This solution would help reduce overall costs. Since an SLT runtime license is included with the HANA Enterprise license, implementing SLT for simple replication was the recommended choice.

SLT is positioned as a solution for businesses using HANA as a reporting database. It addresses the need for quick and easy data replication into HANA to facilitate reporting and decision-making. SLT is a suitable option for real-time or schedule-based replication from both SAP and non-SAP sources, whether on-premise or in the cloud. The use cases for SLT mentioned in the blog post include:

  • Real-time provisioning of data for operational reporting and dashboards
  • Batch loading of enterprise data warehouses
  • Reducing administrative effort for high-frequency master data updates
  • Replicating financial data from SAP and non-SAP ERP systems to SAP Simple Finance
  • Synchronizing data between two or more SAP ERP systems
  • Replacing an existing solution with SLT to achieve real-time data replication
  • Handling of all native SAP table formats, including Cluster and Pool tables
  • Integration with HANA Studio for seamless management
  • Monitoring capabilities using SAP HANA Solution Manager
  • Support for non-Unicode and Unicode conversion during load/replication
  • Mobile capability through SLT Replication Manager for monitoring data replication process and system parameters from anywhere using a mobile device connected to the internet

Reference and Relevant Notes:-

Youtube Video : Explaining SLT in detail

Blog inspiration : Sudhir Kumar's Blog

Use Case of SLT in details : Rashi Singal' Blog

1605140 - SAP Landscape Transformation Replication Server (SLT)

3318703 - How to confirm if SLT replication is working properly?

2014562 - FAQ: SAP HANA LT Replication Server (SLT)

1768805 - SAP Landscape Transformation Replication Server (SLT): Non ABAP-based Sources

2372636 - Cannot replicate data when different trigger options exist - SLT

2796027 - How many times can a table be replicated using SLT?

2575237 - What does a Red Status in LTRC mean? - SLT





Comments

Post a Comment

You might find these interesting

Notes for Build Resilient Applications on SAP BTP with Amazon Web Services [ Week 1]

Welcome back to the next chapter in our ongoing series dedicated to unraveling the dynamic interplay between SAP Business Technology Platform (BTP) and Amazon Web Services (AWS). For those just joining us, this blog serves as an invaluable resource for individuals delving into the world of SAP BTP or seeking a comprehensive reference guide. SAP BTP, or SAP Business Technology Platform, is a comprehensive platform that brings together various essential capabilities for application development, automation, data management, analytics, planning, integration, and AI. These features are all integrated into a unified environment, making it user-friendly for both professional IT developers and citizen developers. Image Credit  Key Features of SAP BTP: Application Development: SAP BTP offers a range of tools for development. For instance, SAP Build enables low-code development, while the SAP Business Application Studio caters to core developers, providing services like document management a...
1 comment
Read more

8 Must-Know Questions About Object Store on SAP Business Technology Platform

What is the problem that Object Store solves ? Modern enterprise systems increasingly deal with massive volumes of unstructured data such as documents, logs, media files, and backups. Traditional relational databases are not optimized for such workloads. What is Object Store ? Object storage—commonly referred to as blob storage—addresses this gap by providing scalable, durable, and cost-efficient storage for unstructured data. Object storage is a storage architecture designed to manage unstructured data as discrete units called objects.  Each object consists of: Binary data (file content) : Image , File etc Metadata (descriptive attributes) : File size, Content type, Last modified timestamp, Storage class (hot, cool, archive) Unique identifier (key or URL) : unique path-like string used to locate a blob inside a bucket Unlike file systems or relational databases, object storage does not rely on hierarchical file structures or schemas. The SAP BTP Object Store service is a managed, ...
Post a Comment
Read more

Understanding SAP BTP Global Accounts, Directories, Subaccounts, and Entitlements

In SAP Business Technology Platform (BTP), organizing your resources effectively is crucial for efficient management and scalability. This blog provides a comprehensive overview of global accounts, directories, subaccounts, and entitlements within SAP BTP. What is a Global Account in SAP BTP? A global account in SAP BTP represents the contractual agreement you have with SAP. It serves as the top-level container for managing various resources, including directories, subaccounts, members, entitlements, and quotas. Within a global account, you receive entitlements and quotas for platform resources, which can be allocated to subaccounts for actual consumption. How Do Directories Function in SAP BTP? Directories in SAP BTP allow you to organize and manage your subaccounts based on your technical and business requirements. A directory can contain other directories and subaccounts, enabling you to create a hierarchical structure. This hierarchy can be up to 7 levels deep, with the global ac...
Post a Comment
Read more

How to properly Start/Stop SAP system through command line ?

Starting/stopping an SAP system is not a critical task, but the method that most of us follow to achieve this is sometimes wrong. A common mistake that most of the SAP admins do is, making use of the 'startsap' and 'stopsap' commands for starting/stopping the system.  These commands got deprecated in 2015 because the scripts were not being maintained anymore and SAP recommends not to use them as many people have faced errors while executing those scripts. For more info and the bugs in scripts, you can check the sap note 809477.  These scripts are not available in kernel version 7.73 and later. So if these are not the correct commands, then how to start/stop the sap system?  In this post, we will see how to do it in the correct way. SAP SYSTEM VS INSTANCE In SAP, an instance is a group of resources such as memory, work processes and so on, usually in support of a single application server or database server with...
25 comments
Read more

KPIs for Recovery in HANA Database Administration

Introduction: In the dynamic landscape of database administration, ensuring the robustness of a system is paramount. One crucial aspect that demands meticulous attention is the recovery process following a system failure. Two key performance indicators (KPIs) stand out in this realm – Recovery Point Objective (RPO) and Recovery Time Objective (RTO) . In this technical blog, we will delve into the significance of these KPIs for HANA database administrators and explore strategies to optimize them. Recovery Point Objective (RPO): RPO is a critical metric that defines the maximum acceptable data loss in the event of a system failure . For HANA database administrators, establishing an RPO involves a careful balance between data consistency and the overhead of continuous data replication. Continuous Data Backups: To meet stringent RPO requirements, implementing continuous data backups is imperative. Utilizing HANA's native backup capabilities and integrating them with a robust backup s...
Post a Comment
Read more

Huge Multiversion Concurrency Control (MVCC) Versions in HANA

What is MVCC? MVCC is a database concurrency control method that allows multiple transactions to occur concurrently without conflicting with each other. In a nutshell, it ensures that each transaction sees a snapshot of the database at a specific point in time, even if other transactions are making changes concurrently. MVCC in SAP HANA: SAP HANA uses MVCC to manage concurrent access to data. Each transaction in HANA sees a consistent snapshot of the data at the time the transaction began. This is achieved by maintaining multiple versions of a data row, each associated with a specific transaction or point in time. The Issue of Huge MVCC Versions: Now, the term "Huge MVCC Versions" indicates a situation where there is a significant number of these versions for a particular set of data. Here's why this might become a problem: Increased Memory Usage: Each version of a data row consumes memory. As the number of versions increases, the overall memory consumption by the databas...
Post a Comment
Read more

Execute HANASitter for hang situation analysis

The SAP HANAsitter is configured to perform default checks once every hour to ascertain the online and primary status of SAP HANA. Upon confirmation, it initiates tracking procedures, which involve regular responsiveness assessments (typically every minute). If SAP HANA becomes unresponsive, the HANAsitter commences recording activities, potentially capturing call stacks of active threads, run-time dumps, index server gstacks, and/or kernel profiler traces, although, by default, no recording occurs. When SAP HANA is responsive, the script scrutinizes critical features, including a standard check for more than 30 active threads. If this threshold is exceeded, the script triggers recording. Upon completing the recording process, the script exits, with an option to be configured for restart using the command line. Setup Steps Overview: Begin by creating an SAP HANA user with the desired name (e.g., HANASITTER) and assign the CATALOG READ privilege to it. Establish a user key in the hdbuse...
Post a Comment
Read more

Deploying SAP on Google Cloud : Part 1

 Connect to Google  Connection Method To be Used for Speed Explanation Example Uses Cloud VPN Proof of Concept Variable, up to 3 Gbps Connects on-premises network to Google Cloud securely over the internet using IPsec VPN tunnels. Creating a Cloud VPN tunnel between on-premises and Google Cloud. Encrypted IPsec tunnels Dedicated Interconnect For Enterprise level connect 10 Gbps to 100 Gbps Provides a dedicated, private connection between on-premises and Google Cloud through Google's network. Provisioning a dedicated interconnect connection. Direct physical connection between on-premises and Google Cloud network infrastructure Partner Connect If you have a data center which cannot be reached to Dedicated Google facility. Variable, up to 100 Gbps Allows connecting to Google Cloud through supported service providers. Establishing a connection with a supported service provider. Utilizes service provider's network infrastructure. Configure Tunnels with Google Cloud Platform IPsec
Post a Comment
Read more

Building the Foundation of the PO System: Architecture and some terminologies

1. Loosely Coupled and Tightly Coupled Services : Loosely Coupled Services : These services interact with each other with minimal dependencies. Changes in one service don't significantly impact others. Pros include flexibility, easier updates, and better scalability. A common example in PO is when a shipping service communicates with an inventory service. Changes in the inventory service won't necessarily disrupt shipping. Tightly Coupled Services : These services are interdependent, so changes in one service can affect others. While they might provide faster communication, they can be less flexible and harder to maintain. For example, tightly coupling an order processing service with a payment service means any change in payment could ripple to order processing. 2. SOA - Service-Oriented Architecture : SOA is an architectural approach where everything is treated as a service, encapsulating specific functionality. Service Orchestration Example (Banking Transaction) : Consider ...
2 comments
Read more

Work Process and Memory Management in SAP

Let’s talk about the entire concepts that are related to memory when we talk about SAP Application. Starting with few basic terminologies, Local Memory :  Local process memory, the operating system keeps the two allocation steps transparent. The operating system does the other tasks, such as reserving physical memory, loading and unloading virtual memory into and out of the main memory. Shared Memory :  If several processes are to access the same memory area, the two allocation steps are not transparent. One object is created that represents the physical memory and can be used by various processes. The processes can map the object fully or partially into the address space. The way this is done varies from platform to platform. Memory mapped files, unnamed mapped files, and shared memory are used.  Extended Memory : SAP extended memory is the core of the SAP memory management system. Each SAP work process has a part reserved in its virtual address space for extended memory...
7 comments
Read more