Setup Guide

This guide walks you through configuring SAP S/4HANA Cloud Communication Management to expose the API_CHARCATTRIBUTECATALOG_SRV service and obtaining the hostname and credentials the SAP Characteristic Attribute Catalog connector needs.

The connector uses Basic Authentication with an SAP S/4HANA Cloud communication user. SAP exposes each API through a communication scenario, so the user must be assigned to a communication arrangement for the Inspection Master Data Integration (SAP_COM_0110) scenario before the connector can call the service.

Prerequisites

• An SAP S/4HANA Cloud system.
• A business user with the SAP_BR_ADMINISTRATOR role (or equivalent) to create communication users, systems and arrangements.

All the apps used in this guide are in the Communication Management group of the SAP Fiori launchpad.

Step 1: Create a communication user

1. Open the Maintain Communication Users app and select New.
2. Enter a User Name and a Description.
3. Set a Password and confirm it.
4. Select Create.

Note the user name and password. These are the credentials the connector uses.

Step 2: Create a communication system

1. Open the Communication Systems app and select New.
2. Enter a System ID and a System Name, then select Create.

3. Under General > Technical Data, enter a Host Name and a Logical System (an uppercase ID of up to 10 characters, for example, INTEGRATOR). Some scenarios refuse to activate when the logical system is empty.
4. Under Users for Inbound Communication, add the communication user from Step 1 with the User Name and Password authentication method.

5. Select Save.

Step 3: Create a communication arrangement

1. Open the Communication Arrangements app and select New.
2. In the Scenario value help, search for Inspection Master Data Integration and select SAP_COM_0110. This is the scenario that exposes API_CHARCATTRIBUTECATALOG_SRV, the service this connector calls.

3. Enter a unique Arrangement Name and select Create.

4. Select the communication system from Step 2. The communication user from Step 1 is filled in as the inbound user. If the scenario lists outbound services that the integration does not need, clear their Active check boxes so that no outbound user is required.

5. Select Save.

Step 4: Note the hostname

Open the saved arrangement. The API-URL next to Own SAP Cloud System shows the hostname (<unique id>-api.s4hana.cloud.sap).

You now have everything the connector needs:

• hostname: the API hostname, for example, my123456-api.s4hana.cloud.sap
• username: the communication user name
• password: the communication user password

tip

Store the hostname, username and password securely. Bind them to configurable variables and supply the values in Config.toml at runtime instead of hardcoding them.

What's next

• Action Reference: available operations
• Example: build an integration with this connector