Skip to Content
Author's profile photo Astrid Tschense

Replacing Extractors with SAP LT Replication Server – part I

A lot of customers run data replication out of source tables into SAP BW with SAP LT Replication Server, and they want to use the delta functionality of SAP LT Replication Server to streamline the data transfer also for extractors – may it be generic extractors they have built themselves on tables that are not delta enabled, or on complex SAP extractors which take a lot of time to be processed.

By default, SAP LT Replication Server is capable of replicating transparent tables, pool- and cluster tables as well as views which are assigned to a leading table. The replication of extractors is not supported. But to meet the customer expectation and help to solve the issue of long running extractors, we want to offer a solution with SAP LT Replication Server technology. Therefore we are in the process of analyzing the SAP extractors that are used most by the customers and classify them according to their complexity, with the goal to replace the extractor logic with SLT functionality or replicate the delta data into SAP BW and perform the required logical steps there.

Already evaluated areas are

ERP Extractors:

  • Flexible Real Estate Management (0REFX)
  • Corporate Finance Management (CFM)
  • Cost Center Accounting (CO-OM-CCA)
  • Financial Accounting: Master Data (FI-IO), Asset Accounting (FI-AA), Accounts Receivable (FI-AR)
  • Material Management (MM-IO)
  • Plant Maintenance (PM-IO)
  • Treasury Management (TR-CM-IO)

CRM Extractors:

  • CRM Cross Component Master Data (0CRM-IO)
  • CRM Interaction Center (0CRM-CIC)
  • CRM Marketing (0CRM_MKT)
  • CRM Sales (0CRM_SALES)
  • CRM Services (0CRM_SERVICE)
  • CRM Survey (0CRM_SURVEY)
  • CRM Workforce Management (0CRM_WFM)

FI Extractors:

  • Policy Management (FS-PM)
  • Claims Management (FS-CM)
  • Reinsurance Management Risk Manager (FS-RI-RMN)
  • Life Reasurance Module (FS-RI-LRM)

The easiest type of extractors are those that can be replaced by a database view. For this type we offer a How-to Guide to enable customers to replace the extractor on their own.

For the more complex extractors we have identified different levels of complexity and figured out how much time it would take to replace the extractor by an SAP expert on project basis:

Complexity Level


Development Effort

Medium (Mid-complex 1)

Hierarchical objects

5-10 days

Medium (Mid-complex 2)

Hierarchical objects with add. lookups (or similar)

10-20 days


complex structures with joins, lookups, includes…

30-40 days

The extractor replacement can be ordered as an Engineering Service “SAP ESRV LT Repl Server Based Support (product ID: 9503240)”, customers can approach their Account Executive or TQM and request support.

You can check the detailed list of evaluated extractors attached to this blog. Evaluation of further extractors can be requested.

Best Regards


Assigned Tags

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

      Is this comprehensive list ?

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


      yes, the lists contain all extractors we have analyzed up to now.



      Author's profile photo Former Member
      Former Member

      Hi Astrid

      I think I have a good case for replacement. A simple standard extractor that has been tunned and still is taking long running times. It extracts from only one table that has a lot of records (really a lot) and a daily 12million delta.

      In % of time saving, how you compare replication vs extraction? 

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

      Hi Gerardo,

      the extraction with the standard extractor runs with only one job while you can configure the replication with SLT to run in parallelized mode with several jobs (given that we can replace the extractor with SLT technology). So depending on the amount of jobs you are using the replication can be x times faster. And if you replicate the data in real-time (not scheduled once per day), the amount of the transferred data is distributed over the  day which reduces the peaks.



      Author's profile photo Jaydeepsinh Rathore
      Jaydeepsinh Rathore

      Hi Astrid

      We have perfect use case  for Replacing Extractors with SAP LT Replication Server.

      We have 2 environments. 1 Native HANA environment and  2. BW on Non HANA.

      In BW we are using all the standard extractors from CRM and HANA.

      We want to replicate ECC extractor data on to HANA using SLT.

      Can you please share updated link for How to replace the extractor with SLT.

      The link you provided for How to Guid in your blog is not working.


      Author's profile photo Gijsbert Karens
      Gijsbert Karens

      Provided link to HOW-TO-GUIDE doesn't work