SAP LT Replication Server integration with Operational Data Provisioning
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
- Find here an Overview of the SLT integration with Operational Data Provisioning
- Documentation is available in the Application Help for SAP BW and SAP Data Services
- Central Note 1972175
- GMC courses covering the SLT Scenarios: HA350, BW362 (new version coming soon)