Integrating with SAP S/4HANA Systems

The above architectural diagram ( taken from the help SAP Batch Release Hub for Life Sciences > Administration Guide for SAP Batch Release Hub for Life Sciences > About SAP Batch Release Hub for Life Sciences ) provides the overarching functional and system architecture of SAP Batch Release Hub for Life Sciences as provided before release 2411 and with the changes introduced in release 2411 that are of concern of this chapter.

Specifically, the complexity in configuring and using the Integration Hub for Life Sciences (hereafter simply called Integration Hub) has been simplified, and the rest of this tutorial focuses on the changes and this new approach.

With Release 2411 of SAP Batch Release Hub for Life Sciences, the Integration Hub has been simplified, and the previous integration approach has been Deprecated, but not yet decommissioned.

The above figure, taken from the Administration Guide > Required Setup Activities > (Optional) Set Up Integration Hub for Life Sciences > Overview of Integration Hub for Life Sciences , shows both thenew version available (for non-production ) with release 2411 of SAP Batch Release Hub for Life Sciences, and the deprecated version.

The new integration approach removes the needs of

• custom managed SAP Event Mesh instance with related configuration tasks
• Integration Hub service deployed in the customer space

These simplifications do not reduce the functionality:

• The resilience that was provided by the custom managed SAP Event Mesh is now delivered directly by SAP S/4HANA Inbound that is part of SAP Batch Release Hub for Life Sciencse
• The monitoring of the integration is still accessible through SAP Cloud ALM

As per this figure the architecture for Batch Release Hub has been drastically reduced. The service Integration Core and Integration Hub for Life Sciences from the previous release will be no longer needed. The next pictures are describing the set up of this simplified way.

To use the new SAP S/4HANA integration the following tasks are now required:

1. Onboarding: For new customers.
2. Support: Request Integration for existing and new customer is required.
   1. Go to SAP Support Portal at http://support.sap.com/incident and create a ticket under component IS-LS-BRH-APP to request a subscription to Integration Hub for Life Sciences. Please include the following details:
      1. Tenant ID
      2. Subaccount ID
      3. Subdomain
   2. The support team will perform the onboarding activities and then reassign the ticket to you.
      Note

      Please wait until the ticket is reassigned to you, before proceeding to the next step.
3. SAP BTP: Create the brh-integration service. As soon as the support team has performed step 2/B. (Support) then
4. SAP S/4HANA: Change/ Create RFC destination.
5. SAP S/4HANA: Recreate or Create the OAUTH Configuration

For BRH only those two subscription are relevant for setting up the integration with SAP S/4HANA. Please create once the feedback is back from the SAP Support an instance for those applications.

1. In the SAP BTP cockpit, go to Services  Instances and create a new instance of brh-integration.
2. Create a service key for the new instance.
3. Choose View Credentials to see the URL and client credentials for the S/4 inbound service.
4. If you have extended Integration Hub for Life Sciences, you need to push the extensions to the URL for the new service.

For the outbound flow of batch release hub a S4HANA destination is needed. The URL for the destination will be created via the cloud connector. Add the BRH technical user from S/4 and the valid password. The user must have the following role /LSCH/PROCESS_RELEASE_DECISION this includes the access and process release decisions using the oData service /LSCH/RELEASE_DECISION_SRV..

As additional property add the SAP client as well. If more then one SAP S/4HANA system should be connected please add the logical system identifier (SID) to the name.

The OAUTH configuration will be created based on the service key from the BRH integration instance. Client ID and client secret can be taken from the service key. For both endpoints /oauth/token needs to be added and the http:/ needs to be removed. The client authorization is basic and the selected grant type is client credentials.

In the old approach using the event mesh and the integration core for life sciences subscription the host could be found in the service key of the integration core for life sciences instance. This must be now exchanged against the services key date from the batch release hub instance.

For existing customer, the OAUTH configuration also needs to be recreated, which is the next step. For new customer the OAUTH configuration must be created based on the next step as well.

Please assign the created OAUTH Profile and Configuration to the RFC.

To enable the content of integration hub for life sciences the business function /LSCH/BF_BRH must be activate to be able to see and maintain the IMG content for the integration hub for life sciences. This step is valid for new customers and customer that are upgrading from LSCH to ISLS. Customer that are upgrading from one ISLS version to another have already executed this step.

The configuration of the integration will be visible once the business function have been activated. In this IMG also the new scenarios clinical batch release with a tight integration from ICSM and the new features for Jurisdiction Control. Settings that have been made in the previous addon version, are still valid.