Configuring Data Ingestion

Objective

After completing this lesson, you will be able to explaining the technical integration options between SAP S/4HANA ERP and data ingestion and the respective pros and cons

Data Replication Options to Data Ingestion

Direct Connection vs. iFlow

The direct connection involves configuring SAP S/4HANA to send data directly to the open API of data ingestion. On the other hand, iFlow integration routes data from SAP S/4HANA through cloud integration to data ingestion, introducing an iFlow intermediary. Choosing between these options is crucial, and often, the preference leans towards iFlow for its flexibility, enhanced monitoring capabilities, and configurable settings.

There are 2 options to send data from SAP S/4Hana to data ingestion:

Direct connection: directly address the open APIs from SAP S/4Hana through HTTP
Through Cloud Integration: send data to an iFlow that connects to Data Ingestion

Diagram showing data replication model for S/4 S21, cloud integration, and CIC BTP with API connections.

Comparison Direct vs. Indirect Data Replication

Direct Replication

Easy setup with SAP S/4HANA configuration only.

Indirect Replication via Integration Flows

use configuration within the iFlow to maintain paths and connections
extensibility options through iFlow exits
Monitoring with Cloud Integration including option to trace payloads

Navigating SAP S/4HANA Tables: CIC Default Endpoints and CAC Endpoints CUST

In the realm of SAP S/4Hana two tables play a pivotal role in our journey – CIC Default Endpoints and CAC Endpoints CUST. These tables hold the key to endpoint paths, defining the links that direct data to specific entities within data ingestion. Understanding these tables becomes essential for a seamless configuration process, ensuring the accurate flow of information.

CIC_DEF_ENDPNTS
This table contains for each entity the default endpoint suffixes to which the data will be sent
CIC_ENDPNTS_CUST
If the default endpoint cannot be used or the customer chooses to create an own path, the destination suffix can be set in this table for the configured RFC destination

Tables showing endpoint definitions and custom endpoints with respective IDs, entities, and endpoint paths for SAP data replication.

Mastering OAuth Profile and RFC Destination

The technical intricacies of setting up a direct connection are shown. Mastering the OAUTH profile is a crucial step, involving the creation of a profile with a unique configuration name. This profile houses essential elements like client ID, client secret, and authorization endpoint for OAUTH token retrieval. Simultaneously, crafting the RFC destination involves linking the SAP S/4HANA system with data ingestion by entering the API endpoint. This streamlined approach eliminates the need for multiple RFC connections, enhancing efficiency and minimizing errors.

Maintain Security settings (OAUTH)
Maintain RFC destination

Setting Up a Direct Connection

Get security credentials from the Data Ingestion Instance.

SAP BTP Cockpit interface showing subscriptions for Data Ingestion for Industry Cloud highlighted in red.

Get security credentials from the Data Ingestion.

Screenshot of a cloud service interface showing credentials details in JSON format including client ID and authentication URL.

Maintain OAUTH profile with transaction OA2C_CONFIG.

Settings page displaying OAuth client configurations and service provider details, with sensitive information redacted.

Maintain OAUTH profile with transaction OA2C_CONFIG.

Screenshot of server authorization settings, including endpoints and access authentication options.

Maintain RFC destination via Transaction SM59.

Configuration window for connection test, showing settings for HTTP connection to external server including target system settings.

Maintain security settings in Logon & Security Tab.

SAP interface displaying connection settings for RFC Destination, focusing on logon and security options including OAuth settings.

Log in to track your progress & complete quizzes