How to Expose SAP S/4HANA Cloud Custom Query to SAC as an Import Model

Introduction

In our previous tutorials on integrating SAP S/4HANA Public Cloud with SAP Analytics Cloud (SAC), we explored two core integration mechanisms:

1. Exposing Analytical Queries as Live Data Models: Real-time querying via the Information Access (InA) protocol using Developer Extensibility (ADT).
2. Setting Up an Import Data Connection using SAP_COM_0087: Extracting standard SAP transaction and master data into SAC's in-memory storage.

While standard communication scenarios like SAP_COM_0087 provide out-of-the-box OData services for journal entries, products, and cost centers, enterprise analytics often requires custom dimensions, specific calculated metrics, or joined transaction views created using Key User Extensibility.

When you create a Custom CDS View in S/4HANA Cloud and attempt to search for it inside an SAC Import Model, you quickly run into a roadblock: the custom CDS view does not appear in the catalog.

In this step-by-step tutorial, you will learn how to expose custom CDS views from SAP S/4HANA Public Cloud to SAP Analytics Cloud as an Import Data Model. We will cover:

1. Exposing a Custom CDS View as an External API.
2. Creating and publishing a Custom Communication Scenario.
3. Activating a Communication Arrangement linked to your existing SAC communication system.
4. Consuming the custom CDS view inside SAC Modeler.

The Starting Point: Why Custom CDS Views Are Not Visible by Default in SAC

In SAP Analytics Cloud, when you navigate to Modeler → Create New Model and select your S/4HANA Import Connection:

When you choose Build a Query and search for your custom CDS view (prefixed with YY1_), no results are found. Only standard pre-delivered SAP OData services appear in the list.

This is expected behavior. S/4HANA Cloud enforces strict API governance. For an external application like SAC to access a Custom CDS View via OData, three explicit building blocks are required:

1. The CDS view must be published with the scenario type set to External API.
2. The auto-generated CDS OData service must be registered inside a Custom Communication Scenario.
3. The scenario must be bound to your external Communication System through an active Communication Arrangement.

Let's walk through this process end-to-end.

Phase 1: Expose the Custom CDS View as an External API

Our first objective is to ensure that the custom CDS view is configured with the correct scenario type so that the platform generates an OData service endpoint.

Step 1: Open the Custom CDS Views App

1. Log in to the SAP Fiori Launchpad on your S/4HANA Public Cloud tenant.
2. In the search bar, search for Custom CDS Views and launch the app.

1. Locate and select your custom CDS view from the list report. Here, we select our existing billing document view YY1_BILLING_DOCUMENT_DATA.

Step 2: Set Scenario to External API

When defining a Custom CDS View in Key User Extensibility, the Scenario property dictates how the view can be consumed:

• Analytical Cube / Dimension: Used within S/4HANA embedded analytics and query designers.
• External API: Exposes the CDS view as an OData V2 service for external consumption (SAC, third-party middleware, or external apps).

1. In the CDS editor, navigate to the General section.
2. Ensure the Scenario dropdown is set to External API.

Important: If your CDS view was originally created under a different scenario (such as Analytical Cube), you cannot directly consume it through communication scenarios. You must use a CDS view configured with the External API scenario.

Step 3: Review Elements and Publish

1. Switch to the Elements tab to confirm all required dimensions, measure attributes, and associations are selected.
2. Click Publish in the bottom-right corner.

Wait until the status displays Published in green. Once published as an External API, S/4HANA auto-generates an OData V2 service with _CDS appended to your CDS technical name (for example: YY1_BILLING_DOCUMENT_DATA_CDS).

Phase 2: Create a Custom Communication Scenario

To expose our newly generated OData service to SAC's technical user, we must bundle it into a Custom Communication Scenario.

Step 4: Open Custom Communication Scenarios App

1. Return to the SAP Fiori Launchpad.
2. Search for Custom Communication Scenarios and open the app.

1. The app lists all user-defined integration scenarios in the tenant. Click the New button in the header toolbar.

Step 5: Define Scenario ID and Description

In the creation popup:

• Scenario ID: Enter a unique technical ID prefixed with YY1_ (for example, YY1_SAC_CUSTOM_IMPORT).
• Description: Provide a meaningful description (e.g., Custom CDS Import Scenario for SAC).
• Click New.

Step 6: Add Inbound Service (External API)

A communication scenario requires at least one inbound service interface to handle incoming API requests from external systems like SAC.

1. In the newly created scenario, select the Inbound Services tab.
2. Click the + (Add) button.

1. In the service search dialog, search for your custom CDS view name (YY1_BILLING_DOCUMENT_DATA).
2. Notice that S/4HANA Cloud automatically appends _CDS to the service name:

   YY1_BILLING_DOCUMENT_DATA_CDS
   

3. Select the service and confirm your selection.

1. The service is now listed under Inbound Services with protocol OData V2. Click Save.

Step 7: Publish the Communication Scenario

Before the scenario can be used in a Communication Arrangement, it must be published across the tenant.

1. Click the Publish button in the header bar.

1. The status indicator changes to Publishing.

Note: Publishing may take 1 to 2 minutes depending on tenant load and background generation queues. Do not navigate away while the status is in progress.

1. Once completed, the status updates to Published with a green checkmark.

Phase 3: Create and Activate the Communication Arrangement

Now that the scenario is published, we link it to our existing SAC communication infrastructure by creating a Communication Arrangement.

Step 8: Create Communication Arrangement from Scenario

1. Directly from the published scenario screen, click the Create Communication Arrangement button located in the upper-right corner.

1. In the creation dialog:
   • Scenario: Pre-filled with your scenario (e.g., YY1_SAC_CUSTOM_IMPORT).
   • Arrangement Name: Enter a descriptive name (or keep the default).
   • Click Create.

Step 9: Assign Existing Communication System (SAC_CONNECTION)

To allow SAC to reuse the same credentials and HTTPS endpoint we established previously, assign our pre-configured Communication System.

1. On the Communication Arrangement configuration page, locate the Common Data section.
2. Click the value help icon for Communication System.

1. Select the communication system we created in Blog 09: SAC_CONNECTION.

1. Once selected, the system automatically populates:
   • Inbound Communication User: SAC_IMPORT_USER
   • Authentication Method: Basic Authentication
   • Assigned Inbound Service: YY1_BILLING_DOCUMENT_DATA_CDS
2. Click Save in the bottom-right corner to activate the arrangement.

The arrangement is now active. The technical user SAC_IMPORT_USER has immediate authorization to query YY1_BILLING_DOCUMENT_DATA_CDS over HTTPS.

Phase 4: Import and Verify Custom CDS Data in SAC Modeler

With backend exposure and security configured, we can now verify the dataset inside SAP Analytics Cloud.

Step 10: Build Query in SAC Modeler

1. Log in to your SAP Analytics Cloud tenant.
2. In the side navigation bar, go to Modeler → Create New → Model.
3. Select Import Connection (Connection to Public Cloud) and click Next.
4. In the New Query for SAP S/4HANA dialog, click Build a Query.
5. In the service search bar, search for your custom CDS view:

   YY1_BILLING_DOCUMENT_DATA_CDS
   

6. The custom CDS view now appears in the catalog, ready for acquisition!

1. Select the entity, choose your fields, apply any required filters or time-range restrictions, and finish building your SAC Import Model.

Technical Comparison: Custom CDS Import vs. Standard SAP_COM_0087 vs. Live InA

Troubleshooting Common Issues

1. Custom CDS View Does Not Appear in Communication Scenario Value Help

• Cause: The CDS view scenario was not set to External API, or the view is still in draft state.
• Fix: Open the Custom CDS Views app, verify that the Scenario field is set to External API, and click Publish. Wait until the status turns green before adding it to the scenario.

2. Service Not Visible in SAC Modeler Search

• Cause 1: The Custom Communication Scenario was saved but not published.
• Fix 1: Verify in Custom Communication Scenarios that the scenario status is Published.
• Cause 2: The Communication Arrangement was not saved or linked to SAC_CONNECTION.
• Fix 2: Ensure the arrangement has status Active and that SAC_CONNECTION is assigned in Common Data.

3. HTTP 403 Forbidden When Querying Service from SAC

• Cause: The communication user configured in SAC (SAC_IMPORT_USER) is not assigned to the custom communication arrangement.
• Fix: Open the custom communication arrangement in S/4HANA Cloud and ensure SAC_IMPORT_USER is maintained under Inbound Users.

Summary

In this guide, we completed the end-to-end process of exposing custom business data from SAP S/4HANA Public Cloud to SAP Analytics Cloud as an Import Data Model:

1. Configured Custom CDS View: Set scenario to External API and published the view to generate the OData V2 service (YY1_BILLING_DOCUMENT_DATA_CDS).
2. Created Custom Communication Scenario: Bundled the custom inbound OData service and published the scenario.
3. Activated Communication Arrangement: Linked the scenario to our existing SAC_CONNECTION communication system and technical user.
4. Verified in SAC Modeler: Successfully browsed and imported the custom dataset into an SAC Import Model.

By combining Key User Extensibility with Custom Communication Scenarios, you can seamlessly bring any tailored business logic or calculated data into SAC for advanced transformations and enterprise planning.