Skip to Content
Technical Articles
Author's profile photo Zili Zhou

Realtime (delta) Data Replication from SAP Analytics Cloud to BW/4 HANA


As planning data in SAC is often changed by business users, these changes need to be replicated to the target systems like BW/BPC, S/4 HANA or Data Warehouse Cloud. This is a feature highly demanded by many customers.

The Data Export Service API is already GA in Q2.2022 with full data. With SAC QRC4 2022 the Data Export Service Delta feature will also be generally available without any delta toggle. Currently, if you are on a fast-track tenant, you can request the feature to be toggled on in your system. For further information please have a look at the help document for the delta feature in this API.

This blog will focus on how to use BW/4 HANA (as target) integrated features (Smart Data Integration) to pull the delta data from SAC (source) using the Data Export Service. Please be aware that this in contrast to a live connection or an import connection where SAC is the target and BW is the source.


Architecture and Prerequisites


Step Actions Purpose
1 Install DP Agent and connect BW/4 to SAC Prepare for the connections

Using SAC Planning model as BW source

–        Verification at HANA side

–        Create BW source system

–        Create Data Source

–        Understand the logic of changing data

–        Understand the logic of deleting data

Understand the delta logic from SAC to the replicated table at BW source

Setup BW data flow

–        Create an ADSO Z1DETADSO with  change log.

–        Create a DTP and simple mapping from data source to the ADSO

–        How changes at SAC side are reflected the ADSO Inbound Table, change log and Active Data

Understand the delta logic from replicated table to BW ADSO.


Further Links

Call for actions

Architecture and Prerequisites:

Below is the architecture we are going to use. Compared to the way to use ABAP and the API to write to a specific table, the advantages are here 1) best to utilize the HANA artifacts and memory for the real-time replication with SDI technology; 2) No programing is required.



Please remember that the toggle for the delta handling must be set explicitly in SAC (when this blog is written in Nov. 2022).  Delta API is planned to release in QRC4 2022 according to the current roadmap.

A DP Agent of version 2.5.3 or higher is necessary.

The target systems can be a BW/4HANA, DWC, or HANA on premise system (at time of publication of this article). Please check the latest PAM HANA SDI to check the latest status if more target systems are supported.


SDI CloudDataIntegrationAdapter PAM

Steps 1: Install DP Agent and connect BW/4 to SAC

There is already blog introducing this. Please refer to this help about the details how to install DP Agent and connect to the HANA system under BW/4: Leverage the SAP Analytics Cloud Data Export Service to extract your planning data to SAP HANA, SAP Business Warehouse and SAP S/4HANA

Step 2: Using SAC Planning model as BW source

Verification at HANA side

Before start doing anything in BW, you can verify in HANA side –>Provision –> Remote sources, it looks like below. The planning modes are under SAC folder. In case it is empty and also you do not get error, it is many cases due to the result was blocked by firewall in your local network.


Verificate the connection in HANA Studio

Create BW source system in BW Modeling Tool (BWMT)

Now we change to BW modeling Tool to create a Smart Data Access type source system. We call it SACDES here. Attention: All the SDA and SDI connection type is under this Smart Data Access. We are in fact using SDI here, however it is still called SDA in the UI.


BW Source System Type: Smart Data Access


Create Data Source in BWMT

Now we create a Data Source under SACDES. All the planning transaction data are delta enabled. Master data does not support delta. Thus, we search “FactData” here, which is transaction data. Attention: This is going to take a while to retrieve all the metadata from SAC. And you need to check in your SAC modeling URL to find the models.

My model is https://<mySACURL>sap/fpa/ui/app.html#/modeler&/m/model/C9ZOQZN2GI2L4HV6S4MK8ULFK


Choose the SAC model from BW


Here we created the data source called “Z1DELTAS”


Create a new datasource

Go to extraction Tab. Make changes as below for the delta enabled transaction data. The real-time replication type Upsert is like after image and insert is similar to before/after image in BW context.  We will use UPSERT here and will see how delta are reflected later.

Here are more information about the difference of UPSERT and INSERT.


Delta enabled extractions


Activate your data source first. Then click “Manage“ button, which is behind “Remote Subscription Type UPSERT”.  You should see status Initial here. By this step, BW will generate a virtual table, replication table and subscription, which we are going to check in details later.


Manage HANA Remote Subscription


Now you execute the delta initialization in the background.


Execute the delta initialization

After the jobs are done successfully, you can check how many records are replicated into the replication table.

Here is the way to find out what the virtual table, replication table and subscription. Click Overview and you will see all the subscription generated by BW in the system.  BW delta enabled data source generate VT (/BIC/CMV<Datasourcename>0000X000001) , Replicated Table (/BIC/CMT <Datasourcename>0000X000001) and subscription (/BIC/ CMU<Datasourcename>0000X000001) )


Overview of HANA Remote Subscriptions created by BW

In our case, the generated replication table is /BIC/CMTZ1DELTA00001000001 and our BW/4 is in SAPHANADB, thus you can run SQL in the HANA directly. We have replicated 508 records.


Check number of records at replicated table

Understand the logic of changing data

We will change a record (GLAccount  =“Cost of Goods Sold”, products “city” and Date “Jan (2022)”) from 9.000k to 6.500k

First, we check it in the replicated table it looks like below. SignedData is 9.000k.


How the record looks like at replication table


Now we are going to modify a record in SAC story: change this SignedData from 9.000k to 6.500K . and click publish.  IMPT: only public version can be pulled via the API.


Publish changed data in SAC

The virtual table points to SAC and it will be changed immediately. Verify by below

select  *  from "SAPHANADB"."/BIC/CMVZ1DELTA00001000001"  where "GLAccount"='Cost of Goods Sold' and "Products"='City'


Check the virtual Table pointing to SAC planning model


Depending on the volume, after some seconds or maybe several minutes, you can see the replicated table is also changed. SDI_CHANGE_TYPE” A” (as in Autocorrect) is for inserted or updated records.

select  *  from "SAPHANADB"."/BIC/CMTZ1DELTA00001000001"  where "GLAccount"='Cost of Goods Sold' and "Products"='City'


SAC changed data is automatically replicated to BW

Understand the logic of deleting data

Now I delete this record (GLAccount  =“Cost of Goods Sold”, products “city” and Date “Jan (2022)”) from SAC and publish.


Publish data after deletion

Here is the result from the virtual table, nothing could be found now.


Record is deleted at SAC


Here you will see the record is SDI_CHANGE_TYPE has value “D” for deleted in the replicated table.


SDI marks record as D and clean up the transaction data

Similarly, you can test the remote subscriptions of type INSERT, it returns the complete delta history in the target table of the replication.

Maybe you are already thinking about after some time, how to clean up the replicated table. The good news is BW has also implemented the house-keeping for the delta tables as below. Here is the LINK.


House keeping of replicated table

Step 3: Setup BW data flow


Create an ADSO Z1DETADSO with change log.Create%20BW%20ADSO%20with%20Changelog


Create a DTP and simple mapping from data source to the ADSO


Create DTP in BW


How changes at SAC side are reflected the ADSO Inbound Table, change log and Active Data

Here are 3 tables generated behind this ADSO.


Inbound Table, change log and Active Data of ADSO

We are looking at the Inbound table /BIC/A<ADSO>01 as below


Check the Inbound Table

Here is the active data table after the request is activated. The delete 1 record is not active and only 507 are there.

select * from "SAPHANADB"."/BIC/AZ1DETADSO2"


Check active table after deletion in SAC

After this, I changed one record in SAC, you will see from ADSO request only 1 record is loaded and 1 is activate.


Loaded Request and Activate Request

Here is the change log for this ADSO.


Changelog in ADSO


  1. Does the delta API support Classis Account Model?

    A: Yes, it supports both SAC Classis Account Model and new model.  It also supports both  Analytic models and Planning models. All transaction data has delta. Master data does not support delta.

  2. Do I need to filter out private version while using the API?

    A: No, only published data is exposed by API.

  3. How to trouble shooting subscription at HANA side?

    A: Download the SQL statements from Note 1969700 – SQL statement collection for SAP HANA.Search the keywords “SmartDataIntegration”. There will be around 9 SQL statements. For example , “HANA_SmartDataIntegration_Agents”  is to check the DP Agent status connected to your HANA. “HANA_SmartDataIntegration_RemoteSubscriptions” is to check the remote subscriptions.

  4. How to check the trace at the DP Agent side?

    A: SAP Note 3102531 – Where is dpagent framework trace located? – SDI

  5. How to check if my SAC Odata API works correctly?

    A: You can test your  SAC Odata API in Postman or below link Try Out | Data Export Service | SAP API Business Hub

  6. I have Dev/QA/Production landscape for my on premise systems, can they share the same DP Agent?

    A: No, DP Agent can only have one target system. Thus, you have to install DP Agent for each of your BW,/4 HANA, S/4HANA or HANA system.

  7. Can I create more than one subscription to one SAC planning model.

    A: yes, one consumer(BW, HANA and so on) could create several subscriptions to the same model.

Further Links

Further Blogs/links on the usage of SAC Data Export Service API:

Call for actions:

This method is a seamless combination from SAC Data Export Service Odata API to BW/4 and utilized SDI technology. There are still a few things we can tune the performance in case of huge data volume.   For example, parameter “Pagesize” of the data source in HANA is 10.000 by default and you could increase much 10 times large or even more. Parameter “Poll Period” (in mins) is by default 5 minutes, this could be reduced if you want to try to check the poll more frequently.


SDI Parameters for tuning


Be free to share your test result or any other comments here.

In case there is a need for guidance on how to use this architecture for HANA on primes or Data Warehouse Cloud, please also let me know.


Assigned Tags

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

      Master piece Zili! Thank you so much!

      Author's profile photo Carlos Jara Muñoz
      Carlos Jara Muñoz

      Amazing post, thank you very much for sharing Zili Zhou!!!

      Author's profile photo Santosh Hiremath
      Santosh Hiremath

      much needed feature for real time reporting for planning community!! Thanks Zili !!

      Author's profile photo Cemal Aslan
      Cemal Aslan

      Great blog, thank you Zili. I am curious, how this would work with DWC?

      Author's profile photo Zili Zhou
      Zili Zhou
      Blog Post Author

      Hi Cemal Aslan ,

      In DWC, you can either do it via data builder (setup can refer to or data flow.

      In data builder, in data intergration moninor --> Remote table monitor--> select the corresponding FactData from SAC and change it to "Enable realtime Access".

      In Data Flow,  you can use the Upsert for the target table. However the delta part is calculated at DWC side. There might be some workaround for this.





      Author's profile photo Xin Lu
      Xin Lu

      Thank you for sharing, Zili.

      We have BW 7.5 SP25 as backend, I try to create a new datasource point to SAC in BWMT, in the extraction tab, there is no "Overwritten delta with deletion" option. There are 3 options, "Delta only via Full upload", "Delta with After image", "Delta with Before image".

      Is it needed to setup Delta process in SAC ?



      Author's profile photo Zili Zhou
      Zili Zhou
      Blog Post Author

      Hi Xin Lu

      I did not try in BW on HANA. You can try with "Delta with After image", it should be similar.  The activation of the data source will take care of the createion the subscription (for delta).  You do not need to create a delta process from SAC side explictly. But you need to ask your SAC contact person from SAP to turn on the toggle before QRC4 release is there.




      Author's profile photo Shivaram Kashyap
      Shivaram Kashyap

      Hello Xin,

      We are on BW 7.5 SP19 and I was told that I cant create a Source System of type HANA SDA. How are you going about creating a Source System and a Data Source. Pls point me to a blog or help docs that have this information.

      Thank You,


      Author's profile photo Zili Zhou
      Zili Zhou
      Blog Post Author

      Hi Shivaram,

      this is how BW on HANA system SDA system creation





      Author's profile photo Harsha JALAKAM
      Harsha JALAKAM

      Hi Zili,

      Thanks for sharing the blog.

      Is there any way where we can filter the data coming into BW. At the moment, when we do initial load ( create subscription ), the SDA-->DP agent pulls all the data from SAC model into the virtual table. This causes a huge time delay in pulling data into BW and memory issues in the DP agent. So , to mitigate this is there any way where we can pull only the required data by filtering the data from the SAC model ,to pull only the required data rather than pulling all the data.

      Just to add, since all the data from the SAC model is being pulled into the Virtual Table in the first stage, the filter defined at the DTP level will not have any impact on the data that is being pulled into the system


      Author's profile photo Zili Zhou
      Zili Zhou
      Blog Post Author

      Hi Harsha,

      you can add filter at Hana source.

      adding filter at data source is not possible. So you need to create several HANA source system if you want to add different filters.







      Author's profile photo Harsha JALAKAM
      Harsha JALAKAM

      Hi Zili,

      Many thanks for your response.

      So you need to create several HANA source system if you want to add different filters. --> would this mean that we can 't add multiple conditions like  BPCVERSION = 'ACTUAL' & BPCENTITY = 'GLOBAL'?

      And if only single condition is supported is this format supported BPCVERSION IN ('ACTUAL','BUDGET')?


      is there any procedure or syntax in specifying the filters And where in BW we can specify?


      Author's profile photo Zhenhong Jiao
      Zhenhong Jiao

      Hello Zili,

      This is really a excellent blog. I followed your steps to enable SAC->BW data exporting successfully.

      But I still have one question that you might share some lights. I'm not able to enable the real-time data extraction.

      Pls find my testing SAC DS below, with AIMD delta mode. I upload couple of records in SAC side, and it won't replaicate to BW side automatically. I manually execute the delta DTP in BW side and successfully load the data into ADSO.

      Is there any additonal steps I need to do in SAC or BW side to make the changed data load/activate in ADSO by real-time?

      Our SAC version is 2023.2.6, and BW on HANA version is 2022/03 SP23.



      Author's profile photo Zili Zhou
      Zili Zhou
      Blog Post Author

      Hi Zhenhong,

      if you execute delta DTP the data is in ADSO, it means your data is already in /BIC/CMT <Datasourcename>0000X000001. you can first check if the delta is already there.

      The DTP is not triggerred automatically. But you can try streaming process chain if you want the BW part data is triggerred.




      Author's profile photo sureshkumar sundaramurthy
      sureshkumar sundaramurthy

      Dear Zili Zhou,

      Thanks a lot for this blog. I have followed the same steps to implement but I stuck at one point where we cannot see any SAC model to select while creating Data source under SDA Source (Remote Resource) in BW system. Can you please help if we missed any access privileges or steps.

      But we could see those model information from under remote source in HANA Verification. we%20cannot%20see%20SAC%20model%20in%20Data%20source

      we cannot see SAC model in Data source




      Author's profile photo John Leggio
      John Leggio

      Hi sureshkumar sundaramurthy , did you follow the steps in the below blog?



      Author's profile photo Zili Zhou
      Zili Zhou
      Blog Post Author

      Hi Suresh,

      it looks like the BW ABAP user does not have select privilege for the tables, Please check with your basis team which user owns this data source. And try to grant privileges to the BW ABAP user.




      Author's profile photo sureshkumar sundaramurthy
      sureshkumar sundaramurthy

      Hi Zili,


      Thanks for your response.

      it is resolved now, but we are facing other problems as Delta records are not updating in Replication table after we do change in SAC so SAP suggested to upgrade the DP agent version (2.6+).



      Author's profile photo sureshkumar sundaramurthy
      sureshkumar sundaramurthy

      Hi John,


      it got resolved after we use Data source Path Prefix as "sac" instead "sap".