Back to blogs
How to Set Up an Import Connection in SAP Analytics Cloud (SAC) from S/4HANA Cloud
SAP Analytics CloudSACSAP S/4HANA Public CloudImport Data ConnectionCommunication ArrangementSAP_COM_0087SAC ModelerData Integration

How to Set Up an Import Connection in SAP Analytics Cloud (SAC) from S/4HANA Cloud

Step-by-step guide to configure an Import Data Connection in SAP Analytics Cloud (SAC) from SAP S/4HANA Public Cloud using SAP_COM_0087 and SAC Modeler.

Mechnoob · · 12 min read

Introduction

Connecting SAP Analytics Cloud (SAC) to SAP S/4HANA Public Cloud is one of the most critical integration requirements for modern cloud enterprise reporting, financial planning, and cross-functional analytics.

In SAP Analytics Cloud, you typically have two primary connection strategies:

  • Live Data Connections: Data remains in the S/4HANA system and is queried in real time via the Information Access (InA) protocol (as demonstrated in our guide on exposing analytical queries as live data models).
  • Import Data Connections: Data is extracted and loaded directly into SAC's in-memory storage engine. This approach enables advanced data wrangling, data transformations, custom hierarchy enrichments, offline analysis, and native SAC Planning capabilities.

In this step-by-step tutorial, we will configure an Import Data Connection between SAP S/4HANA Public Cloud and SAP Analytics Cloud. We will cover the complete end-to-end configuration across both tenants:

  1. Setting up the Communication System in S/4HANA Cloud.
  2. Creating dedicated Inbound & Outbound Communication Users.
  3. Activating the Communication Arrangement (SAP_COM_0087).
  4. Configuring the Import Connection in SAP Analytics Cloud.
  5. Verifying and browsing OData services inside SAC Modeler.

Starting Point: SAC Connections Overview

Before configuring S/4HANA, let's take a look at the Connections screen in our SAP Analytics Cloud tenant.

SAP Analytics Cloud Connections screen showing no existing S/4HANA connection

At this stage, no SAP S/4HANA connection exists. To enable SAC to pull data from S/4HANA Public Cloud, we first need to configure the communication handshake in S/4HANA Cloud.


Prerequisites

Before starting, ensure you have the following access:

  • Administrator or Configurator access in SAP S/4HANA Public Cloud (Business Catalog SAP_CORE_BC_COM for Communication Management).
  • Scope Item 1YB (SAP Analytics Cloud for Planning Integration) active in your S/4HANA tenant.
  • Administrator or Modeler role in SAP Analytics Cloud to manage data connections.

Phase 1: Configure S/4HANA Public Cloud Tenant

All initial integration objects are configured via the SAP Fiori Launchpad on your S/4HANA Public Cloud tenant.

SAP S/4HANA Public Cloud Fiori Launchpad home screen


Step 1: Create a Communication System

A Communication System represents the external system (or communication host) with which your S/4HANA Cloud tenant exchanges data.

  1. In the Fiori Launchpad search bar, search for Communication Systems and open the app.

Searching for Communication Systems in SAP Fiori Launchpad

  1. The app displays all existing communication systems configured in your tenant. Click the New button in the upper-right corner of the table.

Communication Systems list report with New button

  1. In the creation dialog:
    • System ID: SAC_CONNECTION
    • System Name: SAC_CONNECTION
    • Click Create.

New Communication System dialog entering System ID and System Name

  1. Under the Technical Data section in the General tab:
    • Host Name: Enter SAC_CONNECTION (or your SAC tenant host domain).
    • Port: 443 (standard HTTPS port).

Configuring Host Name and Port in Communication System General tab


Step 2: Create Inbound and Outbound Communication Users

For secure API handshakes, S/4HANA Cloud uses dedicated Communication Users rather than human business users.

Important Distinction: A Communication User is a technical service user created exclusively for API integration, Communication Systems, and Communication Arrangements. It cannot log in to the Fiori Launchpad UI.

  1. In your newly created communication system, navigate to the Users for Inbound Communication tab and click the + (Add) button.

Navigating to Users for Inbound Communication tab and clicking add button

  1. In the dialog, set the Authentication Method to User Name and Password. If you haven't created the user yet, click New User.

New Inbound Communication User dialog with New User button

  1. In the Create Communication User screen:
    • User Name: SAC_IMPORT_USER
    • Description: Enter a clear identifier (e.g., SAC Import Integration User).
    • Click Propose Password to generate a secure random password.
    • Copy and securely save this password — you will need it when configuring SAC.
    • Click Create.

Creating technical Communication User SAC_IMPORT_USER with proposed password

  1. Back in the Communication System, select SAC_IMPORT_USER and click OK.

Assigning SAC_IMPORT_USER to Inbound Communication

  1. Scroll down to Users for Outbound Communication, click +, and assign the same SAC_IMPORT_USER credentials.

Maintaining same user credentials in Users for Outbound Communication

  1. Click Save in the bottom right corner to persist the Communication System.

Step 3: Activate Communication Arrangement (SAP_COM_0087)

A Communication Arrangement binds a specific integration scenario to a Communication System and activates the corresponding OData and SOAP service interfaces.

For importing transaction and master data into SAC, SAP provides pre-delivered scenario SAP_COM_0087 (SAP Analytics Cloud for Planning Integration).

  1. Search for Display Communication Scenarios in the Fiori Launchpad.

Searching for Display Communication Scenarios app

  1. Open the app to view all communication scenarios supported by your system.

Display Communication Scenarios list view

  1. In the Scenario ID filter, enter SAP_COM_0087 and click Go.

Filtering communication scenarios by ID SAP_COM_0087

Note on Scope Item 1YB: If scenario SAP_COM_0087 does not appear in your search results, verify in Central Business Configuration (CBC) or Manage Your Solution that Scope Item 1YB is activated in your S/4HANA Public Cloud tenant.

  1. Select SAP_COM_0087 to inspect its details, then click Create Communication Arrangement in the upper-right corner.

Scenario details for SAP_COM_0087 with Create Communication Arrangement action

  1. In the dialog:
    • Scenario: SAP_COM_0087
    • Arrangement Name: SAC_IMPORT_CONNECTION
    • Click Create.

New Communication Arrangement dialog specifying arrangement name

  1. On the arrangement configuration screen, locate the Common Data section and click the value help for Communication System.

Common Data section with Communication System input field

  1. Select the communication system we created in Step 1: SAC_CONNECTION.

Selecting Communication System SAC_CONNECTION from search help

  1. Notice how the system automatically fills:
    • Inbound Communication User: SAC_IMPORT_USER
    • API-URL endpoint (e.g. https://myXXXXXX-api.s4hana.cloud.sap)
    • Pre-activated Inbound OData V2 Services:
      • Journal Entry Item Basic View (I_JOURNALENTRYITEMBASIC_CDS)
      • Product Master (A2X) (API_PRODUCT_SRV)
      • Business Partner (A2X) (API_BUSINESS_PARTNER)
      • Company Code - Read (API_COMPANYCODE_SRV)
      • G/L Account - Read (API_GLACCOUNTINCHARTOFACCOUNTS_SRV)
      • Cost Center - Read (A2X) (API_COSTCENTER_SRV)

Click Save to activate the arrangement.

Reviewing inbound services and saving communication arrangement


Phase 2: Configure Import Connection in SAP Analytics Cloud

With the S/4HANA endpoints and technical user active, we can now configure the connection inside SAP Analytics Cloud.


Step 4: Add New SAP S/4HANA Connection in SAC

  1. Log in to your SAP Analytics Cloud tenant.
  2. In the left navigation menu, expand Utilities (or Data Integration) and click Connections.

Navigating to Connections in SAP Analytics Cloud side menu

  1. On the Connections page, click the + (Add Connection) icon.

Clicking Add Connection icon on SAC Connections page

  1. Under Acquire Data (Import), select SAP S/4HANA.

  2. In the New SAP S/4HANA Connection configuration modal, provide the connection details:

    • Connection Name: Import Connection
    • Description: Connection to Public Cloud
    • Connect to an On-Premise S/4HANA: Leave unchecked (we are connecting to Public Cloud).
    • Data Service URL: Enter your S/4HANA Public Cloud tenant URL with trailing slash:
      https://myXXXXXX.s4hana.cloud.sap/
      
    • Authentication Type: Select Basic Authentication.
    • User Name: SAC_IMPORT_USER
    • Password: Paste the secure password generated for SAC_IMPORT_USER in Step 2.
    • Share these credentials when sharing this connection: Check this option if other modelers in your organization need to reuse this connection without entering credentials.
    • Click Create.

Configuring New SAP S/4HANA Connection dialog with Data Service URL and Basic Auth

  1. SAC validates the connection with the S/4HANA tenant. Once verified, the new connection Import Connection appears in the table with type SAP S/4HANA.

SAC Connections table showing newly created Import Connection


Phase 3: Verify and Import Data in SAC Modeler

To ensure our connection is fully functional, let's create a new model in SAC Modeler and inspect the exposed datasets.


Step 5: Acquire Datasets via SAC Modeler

  1. From the SAC side navigation, select Modeler.
  2. Under Create New, click Model.

SAC Modeler landing page with Model creation option

  1. In the Create Model from SAP S/4HANA dialog, click the Connection dropdown and select our newly created Import Connection (Connection to Public Cloud).

  2. Click Next.

  3. In the New Query for SAP S/4HANA wizard, choose Build a Query. The system queries the S/4HANA catalog through SAP_COM_0087 and displays all available OData services ready for acquisition:

    • API Fin Unit Of Measure
    • API Fin WBS Element Hierarchy Node
    • API Financial Planning Entry Item
    • API Journal Entry Item
    • API Lean Service for Writing Plan Data to ACDOCP
    • API Opening Balance
    • API for Business Area
    • API for Chart of accounts
    • API for Company Code
    • API for Cost Center
    • API for Cost Center Activity Type

New Query for SAP S/4HANA dialog displaying all available OData services

You can now select any entity, drag and drop dimensions and measures into your query, apply filters, and schedule recurring imports into SAC!


Technical Comparison: Import Connection vs Live Connection

Feature Import Data Connection (SAP_COM_0087) Live Data Connection (InA - UI)
Data Storage Replicated to SAC In-Memory Engine Remains in S/4HANA Cloud (Zero replication)
Protocol OData V2 APIs (REST) SAP Information Access (InA)
Refresh Mode Scheduled batches / on-demand imports Real-time query execution on every interaction
Data Wrangling Full data wrangling, formula columns & transforms Limited to CDS view definition logic
Planning Capabilities Full SAC Planning support (ACDOCP write-back) Read-only analytics
Data Latency Depends on schedule frequency Immediate / Zero latency
Volume Handling Optimized for small-to-mid planning slices Optimized for large-scale analytical datasets

Troubleshooting Common Issues

1. HTTP 401 Unauthorized Error

  • Cause: Incorrect technical user password or whitespace in copy-paste.
  • Fix: In S/4HANA Cloud, navigate to Maintain Communication Users, select SAC_IMPORT_USER, click Propose Password, save, and update the password in the SAC Connection dialog.

2. Communication Scenario SAP_COM_0087 Not Found

  • Cause: Scope Item 1YB is not activated for your tenant bundle.
  • Fix: Check your tenant configuration in SAP Central Business Configuration (CBC) or request the SAP Cloud Operations team to activate Scope Item 1YB.

Summary

In this guide, we successfully set up an end-to-end Import Data Connection between SAP Analytics Cloud and SAP S/4HANA Public Cloud:

  1. Communication System (SAC_CONNECTION) was established with HTTPS port 443.
  2. Communication User (SAC_IMPORT_USER) was created for technical Basic Authentication.
  3. Communication Arrangement (SAP_COM_0087) bound the planning and master data OData services.
  4. SAC S/4HANA Connection was configured with the tenant API URL and authenticated.
  5. SAC Modeler successfully verified the catalog and exposed all standard finance and master data OData services for data import.

With your import connection active, you can build rich SAC models, schedule automated delta loads, and drive financial planning workflows.