Skip to Content
Author's profile photo Astrid Tschense

SAP LT Replication Server integration with Operational Data Provisioning

Dear All,

with this Blog I want to give you an insight in “new scenarios” for SLT, beyond the HANA scenario you are already familiar with.

Since its SP5, SAP LT Replication Server is integrated with Operational Data Provisioning (ODP). ODP is a framework for extraction and replication scenarios that is part of SAPNetWeaver as of release NW 7.30. It is a unified infrastructure that can be used by several data providers transferring data out of source systems into a central storage. The data is stored in so-called Delta Queues (ODQ). The data can then be consumed by subscribers, that is, SAP applications that subscribe to this delta queue can read the data out of LT Replication Server is already a standard for the replication scenario for SAP HANA, but there are more scenarios SLT supports. One scenario is the integration  this queue. The data is kept there until the last subscriber has called the data or until a defined time has passed.

Benefits of ODP 

  • Operational Data Provisioning takes a lot of load from source systems because data is extracted exactly once and then distributed over ODP as needed, may it be in real-time or in certain time intervalls.
  • Operational Data Provisioning offers a recovery mechanism with configurable data retention periods, that means you can define how long the data should be stored in the ODQ after it has been read by all subscribing applications.
  • Highly efficient compression enables data compression rates up to 90 percent in ODQ

Integration with SAP LT Replication Server

ODP itself stores the data whenever it is delivered by the connected data sources, may it be by processes of via extractors. The integration of SAP LT Replication Server (DMIS2011 SP5) enhances the ODP concept with real-time replication using the known trigger technology. Now with SP6 available, SLT supports in this scenario also non-ABAP systems and pool- and cluster tables.

The main SAP applications using the SLT/ODP scenario are SAP Business Warehouse and SAP Data Services.

SAP Business Warehouse

You can use operational data provisioning for replicating data with SLT into SAP BW. This scenario has some advantages compared to using the WebService Interface and writing into a Web Service Data Source in the PSA layer, because you can load data directly into the InfoProviders (bypassing the PSA layer). You can perform the replication from ODQ either scheduled by using a DTP (Data Transfer Process)(as of SAP BW 7.30 SP8) or in real-time by using DTP with RDA (as of SAP BW 7.40 SP5). The setup and management of data replication is managed from SAP BW and in the Operational Delta Queue Monitor.


SAP Data Services

Before SAP Data Services was integrated with SLT, the Change Data Capturing feature was depending on the delta-capability of the data source itself and only covered SAP releases NW 7.00 or higher.

Now SAP Data Services 4.2 SP1 has been enhanced to integrate with SAP LT Replication Server by leveraging the new version of ODP API.

SLT supports the Change-Data-Capturing (CDC) scenario of SAP Data Services with real-time data provisioning and delta capabilities for all data sources, including source tables from all SAP system releases (4.6 C or higher) and non-SAP systems.


Documents and Info

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Thanks Astrid, very good blog explaining the capabilities! Reading the note and installation guide it seems there is a limitiation with respect to the initial load: only the first subscriber will receive this data, the other ones only the deltas. The 'extract once, deploy many' then only applies to the deltas unfortunately... What would you recommend as workaround to make the full dataset available to all subscribers? Would it work like a delta init without data transfer like in BW? Can the other subscribers trigger a full load (bypassing the ODQ?). Thanks in advance for your reply!

      Author's profile photo Astrid Tschense
      Astrid Tschense
      Blog Post Author

      Hi Marco,

      thanks for your feedback. Development is working to overcome this limitation of initial load only for the first subscriber with SP7. A workaround could be to create a second configuration for the second subscriber. This of course conflicts with the idea of ODP to have a single connect to the source system, but as a workaround it at least works. You could have up to 4 SLT configurations reading from the same data source (no matter if being registered over ODP or directly).



      Author's profile photo Stefan Koster
      Stefan Koster

      Hi Astrid,

      I'm wondering how the Operational Data Provisioning with it's ODQ interacts with the 'normal SLT replication' that we have been using to replicating data from source systems to HANA. It would be nice to hear that the source systems are only bothered once by the samen SLT system, which both sends the data directly to HANA and stores the data in the ODQ for BW and Data Services. However, I don't find anything about running the two options together in the documentation.

      Could you clarify if it is indeed possible to replicatie both to the ODQ and HANA at the same time, without bothering the source systems twice? Or should we see HANA as a subscriber to the ODQ?

      Best regards,


      Author's profile photo Former Member
      Former Member

      hi, that's exactly what we are struggling around with as well. Maybe DataServices is the option to go for distributing the data? Would be great if Astrid could comment on this.

      Author's profile photo Former Member
      Former Member

      Hi Astrid

      Some questions regarding ODP. Does the data in ODQ can be consumed by non-SAP solution? I saw that the data provision to BO Data service is using Web service interface. So does this can be a way to provide data to non-sap system? Thanks a lot.



      Author's profile photo Former Member
      Former Member

      Hi Astrid ,

      Currently standard FI data sources ( 0FI_GL_04 ) use global BWOM_SETTINGS . Minimum setting is 60 minutes . Will these settings be in effect for  ODP/ODQ ? If so  , then we cannot get real time extraction for FI GL extractors ? correct?

      Author's profile photo Astrid Tschense
      Astrid Tschense
      Blog Post Author

      Hi Lala,

      there is an SAP Note 991429 which allows for minute based extraction of data in 0FI_GL_4.

      The extractor 0FI_GL_4 is ODP enabled (check Note 2232584), so you could also use it with ODP without SLT.



      Author's profile photo Shankar Chintada
      Shankar Chintada

      May I know how to access the speeddemos, it says "Expired".

      Author's profile photo Ankit Sinha
      Ankit Sinha

      Hi Astrid Tschense ,

      In our scenario, We are moving data from S4Hana to AWS S3 in real time, So we are connecting with S4Hana as source system to SAP SLT and as target SAP Data Service using ODP context, and final Target for Data Service will be AWS S3.

      We are not able to visualize S4HANA tables & ODP objects in SAP Data Service Data Store which is connected to SAP SLT via ODP context. Can you please suggest some work around here.

      I tried to open SAP Data Service Demo link but its not working. Speeddemo:

      It will be great help if you can share another demo link.