Explaining the Setup for SAP S/4HANA

An RFC destination that manages the HTTP connection to SAP BTP notification service should be created so that the notifications can flow from SAP S/4HANA to SAP BTP. The RFC destination will use the notification host obtained from the Site Settings in the previous lesson. 

To create the RFC destination, complete the following steps: 

1. Log in to SAP S/4HANA with an admin user.

2. Open transaction SM59 and create a new RFC destination.

3. Provide a name for the Destination (for example, the name of subaccount) and select the Connection Type G (HTTP connection to external server).

4. Provide a Description. In the Technical Settings, provide the Host from the notification credentials obtained from the Site Manager and add "/v2" as Path Prefix.

5. Go to Logon & Security, scroll down to the Status of Secure Protocol section, and set SSL to Active.

6. Go to the Special Options and select the HTTP 1.1 version in the HTTP Setting section.

7. Save the RFC destination.

   Follow this exercise, which shows how the RFC destination is created in more detail:

   ExerciseStart Exercise

1. Log in to SAP S/4HANA as an administrator and open the transaction STRUST. Find the SSL client SSL Client (Anonymous) node and select it:

   
   Note

   If the SSL client SSL Client (Anonymous) node is not yet active, (marked with a cross icon), go into change mode, right-click on it, and select Create.

2. Within the detail screen, scroll down to the Certificate section. Choose the Import Certificate button, upload the root certificate exported in the previous task, and choose Add to Certificate List. (You have to be in change mode).

   

3. Save. The certificate should now be available in the Certificate List.

   Note

   In case a proxy server is used, and the OAuth 2.0 token endpoint of the subaccount can only be reached from the ABAP system via this proxy server, you must configure the proxy in the ABAP system as follows:

   1. Go to transaction SICF and choose Execute (F8).
   2. In the Client menu, choose Proxy settings.
   3. On the Global Settings tab, mark Proxy Setting is Active.
   4. On the HTTPS Protocol tab, enter the proxy server information.

Next, the OAuth 2.0 client profile must be created. Complete the following steps:

1. Log in to SAP S/4HANA as an administrator and open the transaction SE80.

2. Select Local Objects from the dropdown, enter the user name under which you want to create the OAuth 2.0 client profile, and choose the Display button.

3. Right-click the root node and select Create → More/Other → OAuth 2.0 Client Profile.

4. Enter a name for the Client Profile, select the Type as DEFAULT, and choose Continue.

5. Select Local Object to create it or select a package if you want to include it in a transport request.

6. It is added to the Object List. Make sure that the Scopes tab is empty and in the Administration tab, check the "No authorization check".

   Note

   The authorization check could also be left active. In this case, the users that create notifications (for example, workflow runtime users) will need the relevant authorizations (S_OA2C_USE:PROFILE=*;ACTVT=*; )

7. Save your OAuth 2.0 client profile.

   The following exercise guides you through the process of creating an OAuth 2.0 client profile in more detail:

   ExerciseStart Exercise

The OAuth 2.0 client profile must be configured with the correct OAuth settings from the Site Manager notification credentials. 

1. Log in to SAP S/4HANA and open the transaction OA2C_CONFIG.

   A browser window for the OAuth 2.0 configuration opens.

2. Choose the Create button and enter the following values:

   • OAuth 2.0 Client Profile: Select the client profile created in the previous task
   • Configuration Name: Should prefill with the same name
   • OAuth 2.0 Client ID: Enter the value from the notification credentials from the Site Manager

   Confirm with OK.

3. Scroll down to the Details section. In the General Settings, provide the values obtained from the Site Manager for the following fields:

   • Client Secret
   • Authorization Endpoint
   • Token Endpoint

4. Scroll down to the Access Settings and select the following values:

   • Client Authentication: Basic (default)
   • Resource Access Authentication: Header Field (default)
   • Selected Grant Type: Client Credentials

5. Scroll back up and Save the OAuth 2.0 configuration.

   The following exercise guides you through the process of configuring the OAuth 2.0 client profile in more detail:

   ExerciseStart Exercise

This step is optional for nonproductive environments (for example, development, testing), but is recommended in a productive setup. The use of bgRFC queue ensures that the notifications are queued and processed in a sequential manner. If bgRFC queue is not used, notifications will be sent synchronously and will not be resent if there is an error.

1. Within the IMG, navigate to / expand the following fields: SAP NetWeaver/ABAP Platform → Notification Channel → Notification Channel Hub → Configuration → Connection Settings.

   

2. Execute Register bgRFC Destination for Cloud Service.

   

3. Switch to the Define Inbound Dest. tab and create a new Destination named IWNGW_NOTIF_CLOUD_BGRFC with a queue prefix (can be created via the New Prefix field after creating the destination). As an example, you can name it NGW_.

   

4. Save the destination. It should now show up in the list of destinations. Then, return to the IMG.

This is usually an optional step for the configuration of notifications within SAP S/4HANA. However, it is a mandatory step for sending the notifications to SAP BTP.

1. Within the IMG, navigate to / expand the fields: SAP NetWeaver/ABAP Platform → Notification Channel → Notification Channel Hub → Administration → General Settings.

   

   The first three entries here will be executed as described in the following steps. 

2. Execute Register Notification Store in SFF.

   Choose New Entries, select the Notification Channel Secure Store Encryption from the list, and Save.

   

   Keep all the default values and Save. It is added to the list of Application-Specific SFF Parameters.

   Return to the IMG section from step 1.

3. Execute Maintain Notification Store in SFF Settings.

   You are navigated to STRUST. Find the SFF Notification Channel Secure Store Encryption node.

   If it is not active yet (marked with a cross), you must create it. Right-click it and choose Create.

   

   Return to the IMG section from step 1.

4. Execute Enable Sensitive Data Cache on the Hub.

   Select the checkbox for Enable Sensitive Data Cache and choose Execute.

   

   Choose Yes in the popup to confirm the settings. After that, a success screen displays.