Exporting Transaction Data from SAP Analytics Cloud

Since the master data and actual transaction data were 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.

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

More information, go to: Data writeback from SAP Analytics Cloud to SAP BW4 HANA through Open Data Protocol (OData) Services

For the export job to be successful, you must set up SAP Business Warehouse 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 Business Warehouse.
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 must all 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.

In this course, we 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. For more information, go to: Realtime (delta) Data Replication from SAP Analytics Cloud to BW/4 HANA.

Using the built-in export solution, you must 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.

Some target dimensions are automatically mapped to the source dimension.

It is important to check all the target dimensions for accuracy. In the following example, you can see that the target dimension has not been mapped. Select a source dimension from the dropdown list of values.

If no source value exists in the source dimension, 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 does not 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 must replace it with a default value such as USD.

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

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

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