SAP Analytics Cloud, Data and Analytics, SAP API Business Hub, Data Export Service

Use Data Export Service to Replicate Data Between SAP Analytics Cloud Tenants


This blog describes how to replicate model data between two SAP Analytics Cloud systems using Data Export Service within an OData connection. This workflow is very suitable for the movement of data from production to development environments or vice versa, and for models that contain large volumes of data. Note that a pre-existing model must exist on the target system.


The steps to replicate data from one tenant to another can be broken down into 6 easy to follow steps:

  1. Configure OAuth Client.
  2. Locate the source tenant URL.
  3. Locate the source model ID.
  4. Create a remote connection.
  5. Set up import data.
  6. Map and import data.

Let’s take a closer look at each individual step.

1. Configure OAuth Client.

In order to send requests to the Data Export Service, you must first set up an OAuth client on the SAP Analytics Cloud source system. This requires administrator access.

  • Go to System > Administration in your SAP Analytics Cloud source system and select the App Integration tab.
Figure 1: App Integration on the Source System
  • Observe the list of URLs in the OAuth Clients section and make a copy of the access token URL under Token URL, as this will be needed in a future step.
  • Select Configured Clients within the OAuth Clients section.
  • Click Add New OAuth Client.
Figure 2: Add New OAuth Client Dialog
  • Complete the required fields by first entering a client name.
  • Under Purpose, select Interactive Usage and API Access.
  • Under Access, select Data Export Service.
  • Once the OAuth client has been created, note down the OAuth Client ID and the Client Secret. These values will be used to send requests to the Data Export Service.
Figure 3: OAuth Client ID and Secret
  • After configuring the OAuth client, you should have access to the following values, to allow you to send a sample request in Postman, custom applications or any other system that supports OAuth flow.
    • Access token URL
    • OAuth Client ID
    • (Client) Secret

2. Locate the source tenant URL.

  • Go to System > Administration in your SAP Analytics Cloud source system and select the System Configuration
  • Scroll down to Link My Tenants and make a note of the SAP Analytics Cloud URL, as this information will also be required later.

3. Locate the source model ID.

Each model has a unique identifier (ID). This can be obtained directly from the SAP Analytics Cloud URL on the source system. When you access a model, the model ID is referenced at the end of the URL after the last backslash “/”.

Figure 4: Obtain Model ID from URL

Make a note of this model ID as this is required in future steps.

4. Create a remote connection.

Create a remote connection on the target system, to connect the source and target SAP Analytics Cloud systems.

Note that a new connection is required for each model as every connection is specific to a model on the source system.

  • On the target SAP Analytics Cloud system, go to Connections and click on the +
Figure 5: Add a Remote Connection on the Target System
  • In the Select a Data Source dialog, select OData Services, under Acquire Data.
Figure 6: Acquire Data Using OData Services

In the New OData Services Connection dialog, specify:

  1. Connection name
  2. Description (optional)
  3. Use the source tenant URL, along with the Model ID, obtained in the previous sections, as part of the Data Service URL using the following format: https://<<TenantURL>>/api/v1/dataexport/providers/sac/<<modelID>>
  4. Ensure that there is no backslash “/” at the end of the Data Service URL
  5. Set Authentication Type to OAuth 2.0 Client Credentials.
  6. The OAuth Client ID from Section A OAuth Client Setup
  7. The Secret from Section A OAuth Client Setup
  8. The Token URL from Section A OAuth Client Setup
  • Click Create.
  • For errors, check that all required fields are correct and ensure that the URL follows the format mentioned above.

5. Set up import data

  • On the target system, open a pre-existing model and select Data Management.
Figure 7: Data Management Import from Data Source
  • Click Import Data > Data source.
  • Select OData Services.
Figure 8: OData Services
  • The Connection name that was created in Section 4 should be seen in the drop down.
Figure 9: Import Data from OData Services
  • Add a name to the query and select the data you wish to import. For example, Fact Data.
Figure 10: Import Fact Data into Target Model
  • Drag and drop required fields within the Build OData Services Query Dialog.
  • Apply filters to restrict the data that is imported. Note that filters must contain a value and should not include quotes.
Figure 11: Build OData Services Query
  • In case filters have been configured incorrectly or results are empty, you will receive a warning message similar to the following:
Figure 12: Empty Dataset Warning Message
  • A toast message confirms the successful job creation
Figure 13: Successful Job Creation
  • Select Set Up Import and see the fact data preparation screen.
Figure 14: Sample Prepare Fact Data Screen

6. Map and Import Data

  • Within the Fact Data Preparation screen, choose Next to open the Map to Facts.
  • Mapping of source and target data is automatically applied.
Figure 15: Map to Facts Screen
  • Click Next and Run Import once mapping has been applied.
  • The import settings can be changed, if required, from Update to Append, Clean and replace selected version data, Clean and replace subset of data.
Figure 16: Change Import Settings Option
Figure 17: Import Job Settings Dialog
  • Click Finish to import the data.
  • A success toast appears, confirming data has been imported successfully.
Figure 18: Import Success Toast Message
  • A Rejection Summary can be exported as csv to allow for further analysis.
Figure 19: Rejection Summary

This concludes the steps required to export fact data using the Data Export Service from a source SAP Analytics Cloud system to a target SAP Analytics Cloud system.