Exporting Transaction Data from SAP Analytics Cloud

After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • Export transaction data to SAP Business Warehouse

Transaction Data Export Process

The Project: Exporting Transaction Data from SAP Analytics Cloud to SAP Business Warehouse

Since the master data and Actual transaction data was exported from SAP Business Warehouse to SAP Analytics Cloud, the team has been busy preparing the Forecast. They copied the data to a public plan version and finalized their plan values. Now, with the Forecast ready, they are ready to export the plan data from SAP Analytics Cloud back to SAP Business Warehouse.

Watch this short video to take a close look at the next phase of your integration project for creating a hybrid planning solution.

Setting Up Transaction Data Exports

In the model, there are a few key things you need to set up before you can export transaction data. Typically, you only use a single connection for importing and exporting data. However, when exporting to SAP Business Warehouse, you need to create a second connection to export data from SAP Analytics Cloud.

OData Connection

As a user responsible for planning data administration, you want to write back to SAP Business Warehouse from SAP Analytics Cloud. To do this, an OData (or Open Data Protocol) services connection must be created by your IT administrator. This will allow the export job to write back to SAP Business Warehouse write interface enabled ADSOs.

More information can be found in Data writeback from SAP Analytics Cloud to SAP BW4 HANA through Open Data Protocol (OData) Services

SAP Business Warehouse

For the export job to be successful, SAP Business Warehouse must also be set up to receive the exported data:

  1. Create an export job in SAP Business Warehouse.
  2. Create a standard ADSO with the Write Interface-Enabled setting activated. The Write Change Log setting is optional. This option is selected if a log in SAP Business Warehouse is needed or if the data is loaded into a subsequent data target in SAP BW.
  3. Include Calendar Year/Month as the time characteristic in the ADSO. The export to SAP Business Warehouse does not support fiscal calendar time characteristics. Fiscal period data in SAP Analytics Cloud is converted to calendar month data during the export. As every characteristic is a key field, they will all need to be transferred from SAP Analytics Cloud to SAP Business Warehouse during the export.
  4. For the export process to be successful, there must be master data members in SAP Business Warehouse.

SAP Analytics Cloud

API Subscriptions

In this course, we will focus on using the built-in export solution in SAP Analytics Cloud, however, it is also possible to use API Subscriptions to pull full or delta data into SAP Business Warehouse from SAP Analytics Cloud using the Data Export Service. More information can be found by going to Realtime (delta) Data Replication from SAP Analytics Cloud to BW/4 HANA.

Import/Export Jobs

Using the built-in export solution, you will have to configure the model preferences. In the Data and Performances section of the preferences, toggle on Enable Legacy Export. This is required for exports to systems such as SAP BPC, SAP S/4 HANA, and SAP Business Warehouse.

Export Transaction Data

Once the connection has been set up and the necessary configurations are complete, it is possible to create the export job in SAP Analytics Cloud. Some of the steps are the same as importing data in that you select the connection, select the target data, and map the data. However, there are a few additional points to keep in mind, which are covered below.

Mapping Dimensions

Some target dimensions are automatically mapped to the source dimension.

It's important to check all of the target dimensions for accuracy. In the following example, you can see that the target dimension has not been mapped. You will need to select a source dimension from the dropdown list of values.

If no source value exists in the source dimension, then you select Not Mapped and select a constant in the Default Value field. In the example below, you can see that the constant value of YCOA is used because ZCOA doesn’t exist in SAP Analytics Cloud.

Map the source version to the target SAP Business Warehouse version. However, remember that the export only supports public versions.

If the Currency Key is blank in the Target Dimension, you will need to replace it with a default value such as USD.

Mapping Measures

Only one measure can be exported per export job. In the following example, you can see the target measure ZAMOUNT is mapped to source dimension SignedData.


There is no special handling for compounding characteristics in an SAP BW ADSO, so all the superior characteristics (along with the compounding characteristic) should be mapped in SAP Analytics Cloud.

Export Method

The Clean and Replace selections control the data region that is overwritten in the target ADSO.

In the project scenario used in this course, there is another group who is writing to the same ADSO by calendar month and profit center. Therefore, you will select calendar month and profit center so that your export doesn't affect their data.

Export Transaction Data to SAP Business Warehouse

Business Scenario

As part of the integration project, once Forecast data is ready, you have to export the transaction data from SAP Analytics Cloud back to Business Warehouse.

What skills will you develop in this practice exercise?

In this practice exercise, you will:

  • Create an export job to export data to OData Services
  • Target and map the source data
  • Run the export
  • View the exported data in the ADSO in SAP HANA Studio

Log in to track your progress & complete quizzes