Explaining the Integration Between Cloud and SAP S/4HANA

Configuration of principal propagation required inclusive creation of technical user for basic authentication.

1. Scenarion end-to-end SSL encryption (termination of SSL at back end)
   • Exchange of certificate is mandatory
   • SAP Intelligent Clinical Supply Management Portal to Cloud Connector (SSL termination) from Cloud Connector to back end HTTP
   • Certificate is not required
2. Cloud-based LDAP service provide (for example, Microsoft, Google, Oracle)

   Exchange of certificate is mandatory

• Go to transaction code RZ10.
• Select Default Profile and Latest Activated Version.
• Choose Extended Maintenance.
• Choose Create New Parameter and add the following entries:
  • Parameter Name: login/certificate_mapping_rulebased Parameter Value: 1
  • Parameter Name: icm/HTTPS/trust_client_with_subject Parameter Value: *
  • Parameter Name: icm/HTTPS/trust_client_with_issuer Parameter Value: CN=SCC, OU=ICSM, O=SAP SE, C=DE
  • Parameter Name: icm/HTTPS/verify_client Parameter Value: 1

• In transaction code SM59, on the Logon & Security tab, check that SSL is set to active.
• Check which SSL certificate is selected. It should be <DFAULT SSL Client (Standard)>.
• Download the missing browser certificates from the front-end URL or Cloud Connector on SAP BTP and import them in transaction code STRUST into <SSL client SSL Client (Standard)>.
• Within this view, choose <Add to Certificate List> and save the settings.

• Go to transaction code SMICM
• In the toolbar, select Administration → ICM → Exit Soft → Global.
• Confirm to restart all ICM processes.

Check the federation of IDP setup principle propagation within SAP S/4HANA (B1S).

Enable connection to all SAP S/4HANA services accessed by end users and by technical users.

Workflow destination for the mail server has been set up

Add the following standard workflow roles as part of ICSM PoC:

• WorkflowInitiator (global role)
• WorkflowParticipant (global role)
• WorkflowAdmin (global role)

Check if the related ICSM standard roles are part of the ICSM role collection:

• WorkflowSettingEditor
• WorkflowSettingViewer Role

1. Set Up Cloud Integration to enable synchronization of study data.
2. Create Your OAuth 2.0 Client Profile.
3. Configure connection parameters.

1. RFC Connection (transaction code SM59)

   Make sure that the host URL is maintained correctly.

   Make sure that the RFC connection name is not longer than 14 characters.

   On the Logon & Security tab, select the following options:

   • Do not use user
   • Do not send logo ticket
   • SSL - active
   • SSL Certificate: SSL Anonymous
2. OAuth Profile Maintenance (transaction code OA2C_CONFIG)
   • Maintain OAuth profile for standard integration service plan.
   • Client ID and secret are retrieved from service keys (provided by BTP subaccount admin)
   • Make sure that when you maintain the authorization and token endpoint to only copy and paste the URL without https://
   • Change Selected Grant Type to Client Credentials.
   • Select SSL Anonymous in the field SSL Client PSE.
3. Configuration Connection Parameters (transaction code SM59)

   Perform Customizing according to 3296156 - ICSM : Study sync issue due to CONTACTS key field

   +++TR required+++

4. Transaction code to verify:/N/CTCO/SYNC_STUDY

1. Set Up SAP Event Mesh
2. Create a queue and a queue subscription for the following events Manage Queues.
   • Study change (creation or change to a study)
   • Status configuration change
   • Type configuration change
   • Phase configuration change
   • Study status change
3. Create a webhook for each of the events​ Manage Webhooks.

SICF Service activation for default/host → sap → bc → icsm_event_wb.

1. Creating, Configuring and Managing Channels
2. Maintain Outbound Event Topics
3. Queue Subscriptions

• /IWXBE/EVENT_MONITOR - Event Montior (Only available in SAP S/4HANA 2022; Transaction - /IWXBE/EEE_SUPPORT - EEE can be used in 2021 release)
• SWEQADM - Event Queue Administration
• SWEQADM_1 - Maintain Event Queue Administrator
• SWU3 - Automatic Workflow Customizing
• /IWXBE/EEE_SUPPORT - EEE - Support Reports
• SMDAEMON - ABAP Daemon Table
• /IWXBE/CONFIG - Configure Enterprise Event Channel
• SWUE - Trigger an event
• SWE2 - Display/Maint. Event Type Linkages
• SWEL - Display Event Trace

Before using this procedure, make sure that Cloud Connector, SSO, and principal propagation are set up.​

​Subscribing to the SAP Launchpad Service enables users to access all of the applications that they need to fulfill their tasks from a central point of entry.

1. Synchronize with principal propagation
2. Subscribe to SAP Launchpad Service
3. Configure 2 destinations to connect to the SAP S/4HANA system
4. Design-time destination
5. Runtime destination
6. Add Content Provider to SAP Launchpad Service
7. Create SAP Launchpad
8. Activate SAP Companion Content and enable it on app level (Enable In-App Help for a Launchpad with Federated Apps)
9. Enable the notification service (Integrate the Notification Service)
10. Add the SAP Launchpad Service to the HTTP whitelist
11. Set the user role
12. When you subscribed to the SAP Launchpad Service, 2 role collections were added: Lanchpad_Admin and Launchpad_External_User. To configure the SAP Launchpad Service, you need the Launchpad_Admin role. Map this role collection in Role Collection Mappings to access the SAP Launchpad Service as an admin. In your subaccount, go to Trust Configuration, select the IAS you use, choose Role Collection Mappings, and add the required mapping.
13. Expose respective roles by the SAP S/4HANA backend system
14. Set user roles for SAP S/4HANA apps
15. Add BTP Content Provider and Content Manager role

Before using this procedure, make sure that the business function xxxx is active.​

You use this procedure to xxxx.​

Settings are used by ICSM-specific BAdI Implementation xxxx to trigger the corresponding xxxx.​

Default settings are delivered to support xxxxx.

1. In the SAP Customizing Implementation Guide of Intelligent Clinical Supply Management, go to Master Data → ATTP Integration → Assign ATTP Business Functions by Goods Movement Type​.
2. Establish a mapping between ATTP events and postings of goods movement document types.​
3. ​ BAdIs​