If any of these scenarios seem familiar or useful to you then please read on to understand how SLT works and your options around implementing it. Over the years, SLT has evolved into a middleware solution that supports change data capture and real-time replication scenarios for SAP Business Warehouse, SAP Data Services, SAP Simple Finance and native DB targets, with the latest version being SLT 3.0 SP03 (DMIS 2018).ġ Real-time provisioning of data for operational reporting and dashboardsĢ Batch loading of Enterprise data warehousesģ Reduce admin effort for high frequent master data updatesĤ Replicate financial data from SAP and non-SAP ERP systems to SAP Simple Financeĥ Synchronising data between two or more SAP ERP systemsĦ Replacing an existing solution with SLT in order to get real-time data replication SLT is a long-standing product and has its roots as the real-time data replication tool for SAP HANA since 2010 (DMIS – Data Migration Server 2010). There are other tools such as SAP Data Services or HANA Smart Data Integration (SDI) and these need to be evaluated along with the requirements, but SLT (usually) doesn’t carry any extra licencing cost and is reasonably simple to implement and support. Using SLT replication will ensure you provide the business with the right information at the right time whenever or wherever they need it.
It is a good solution for all HANA customers who need real-time or schedule based replication sourcing from both SAP and non-SAP sources, whether on premise or in the cloud. This is where SAP Landscape Transformation Replication Server (SLT) comes into its own.
Often you have data coming from a variety of different sources – both SAP and non-SAP – and you need to balance the needs of the business to get up-to-date data, alongside the impact that data replication can have on your source systems. SLT PositioningĪ common requirement for businesses using HANA as a reporting database is the need to replicate data into HANA as quickly and as easily as possible to facilitate reporting and decision-making. The requirement was for simple replication and, as an SLT runtime Licence is included with the HANA Enterprise Licence, this was the recommended choice.
Managing slt from sap hana studio full#
This meant they required an Enterprise licence for the full ECC instance at a significant cost.īy deciding to stop reporting directly against the main ECC system and using a “sidecar” HANA Enterprise instance with replicated data, it was possible to reduce the overall cost. On this particular project, the customer had previously been reporting directly against their HANA ECC database using Calculation Views using SAP and non-SAP reporting tools. However, from my experience, I think it should still be one you should consider if you want an established and straightforward way of replicating data into HANA – whether for real-time or batch replication. I have just completed a project using a SAP product, which perhaps is not discussed much any more – SAP Landscape Transformation Replication Server (SLT). SAP Landscape Transformation Replication Server (SLT) – A Cost Saving Use CaseĪuthor – Rashi Singal, Analytics Consultant, NTT DATA Business Solutions UK. Selective Data Transition to SAP S/4HANA.SAP BPC (Business Planning and Consolidation).SAP Change Assurance and Training Services.