Introducing SAP Ariba Direct Materials Sourcing for Automotive and Industrial Manufacturing in SAP S/4HANA
Explaining Key Direct Material Sourcing Processes
Setting Up SAP Ariba Direct Materials Sourcing for Automotive and Industrial Manufacturing in SAP S/4HANA
Setting Up SAP Business Technology Platform

Creating an HTTP Destination

Objective

After completing this lesson, you will be able to create an HTTP destination and a technical user.

Technical User in SAP S/4HANA

In the architectural setup between an SAP S/4HANA system and SAP Business Technology Platform, data is not directly sent to SAP Ariba supplier quotation management. After publishing a project, the system sends only the minimum information to SAP Event Mesh. An API call will be triggered from SAP Ariba supplier quotation management to read the data via Cloud Connector from SAP S/4HANA.

To read and post additional data, a technical user is required.

SAP BTP Applications integration process, depicting event flow between SAP Event Mesh, SAP Ariba supplier quotation management, SAP S/4HANA, and Cloud Connector for API data retrieval.

How to Create a Technical User in the SAP S/4HANA Back End

Destinations

Creating a destination ensures the security of data exchanged between systems. In your SAP BTP account, choose Destinations (in the Connectivity tab) and create new destination. As a prerequisite, you need Cloud Connector to access the SAP S/4HANA system from the cloud. In the URL section, provide the virtual host from the Cloud Connector. If you use several cloud connectors, you can use a location ID to distinguish between them. In the Authentication section, choose Basic Authentication and provide details for the technical user.

How to Create a Destination

Summary

  • Create a technical user in SAP S/4HANA to securely enable system integration.
  • Use the Cloud Connector to allow SAP Ariba to read data from SAP S/4HANA.
  • Configure a destination in SAP Business Technology Platform with basic authentication for data exchange.
  • Ensure each destination uses a unique Location ID to distinguish between cloud connectors.