Integrating with SAP Batch Release Hub for Life Sciences

Objective

After completing this lesson, you will be able to describe the integration of SAP Intelligent Clinical Supply Management with SAP Batch Release Hub for Life Sciences

Integration of SAP Intelligent Clinical Supply Management with SAP Batch Release Hub for Life Sciences

Deploying SAP Batch Release Hub for Life Sciences with SAP Intelligent Clinical Supply Management for operations is optional. 

If you want to use this solution together with SAP Intelligent Clinical Supply Management, some configurations need to be done at different places in the system.

The subsequent sections provide you with an overview of these configurations.

Flowchart illustrating the relationship between SAP Intelligent Clinical Supply Management and SAP Batch Release Hub for Life Sciences. The diagram shows an arrow from the blue box labeled SAP Batch Release Hub for Life Sciences to a white box labeled Customize, and another arrow from Customize to SAP Intelligent Clinical Supply Management.

SAP Intelligent Clinical Supply Management Configuration

To integrate SAP Batch Release Hub for Life Sciences with SAP Intelligent Clinical Supply Management, one configuration has to be made in the SAP Intelligent Clinical Supply Management Customizing.

Illustration of an industrial building connected by a dashed line to a software navigation path. The software menu hierarchy shown includes: - SAP Intelligent Clinical Supply Management - Master Data - Batch Release Hub Integration - Define Activation Settings for BRH Integration (highlighted in red)

Define Activation Settings for SAP Batch Release Hub for Life Sciences Integration

Description

You use this procedure to define the following activation settings for SAP Batch Release Hub for Life Sciences integration:

  • BRH Integration Is Active 

    If you select this option, the system enables SAP Batch Release Hub for Life Sciences integration-relevant functionalities (triggering of replication of batch data to the BRH cloud component).

  • BGRFC Destination for Batch Replication

    This option specifies the inbound destination for the background RFC used to trigger replication to the BRH cloud component for batch data affected by changes made in the Manage Shelf Life Data application or by changes resulting from RIMS record processing.

Procedure

  1. In the SAP Customizing Implementation Guide, go to SAP Intelligent Clinical Supply Management → Master Data → Batch Release Hub Integration →  Define Activation Settings for BRH Integration.
  2. Enter a BGRF Destination for Batch Replication and activate the BRH-ICSM Integration by selecting the checkbox.

RFC Configuration

To integrate SAP Batch Release Hub for Life Sciences with SAP Intelligent Clinical Supply Management, a valid bgRFC connection has to exist.

This connection is needed from SAP Intelligent Clinical Supply Management to replicate batch data to the SAP Batch Release Hub for Life Sciences cloud.

Illustration of a blue wrench icon connected by a dashed line to a screenshot of the bgRFC Configuration settings in a software interface. The configuration screen includes multiple tabs such as Scheduler: System, Scheduler: App. Server, Scheduler: Destination, Define Inbound Dest., and Define Supervisor Dest. The general system settings include: - Number of Log Messages: 10,000 - Log Lifetime (h): 120 - Supervisor Srv. Grp Outbound and Inbound sections include compression options and unit delete time settings (s). The last changed section includes fields for username, client ID, current date, and time for both outbound and inbound settings.

The following instructions should guide you through the creation of a bgRFC connection.

Background RFC Configurations

Prerequisites

To configure background remote function calls, you need to assign the authorization object S_BGRFC.

Procedure

  1. Go to transaction SBGRFCCONF.
  2. Create a supervisor destination.

    Note

    A supervisor destination is used to retrieve the configuration settings for the background remote function call (bgRFC) scheduler. It starts or stops the schedulers as required on each application server.
    1. Choose Create on the Define Supervisor Dest. tab.
    2. Enter the name of the destination to be created.
    3. Enter the supervisor's user name and a password.
    4. Choose Copy.

    Note

    The user maintained for this destination is the user with whom the scheduler will run. The user must be assigned the role SAP_BC_BGRFC_SUPERVISOR (available only for SAP_BASIS 740 and above) and the role SAP_BC_WEBSERVICE_CONFIGURATOR.
  3. Define the inbound destination.

    Note

    The inbound destination and queue prefixes help to keep different applications separate from each other and to avoid conflicts when applications use the same queue name in the same system.
    1. Choose Create on the Define Inbound Dest. tab.
    2. Enter the name of the inbound destination to be created.
    3. Select a logon/server group.
    4. Add a queue prefix.
    5. Choose Save.
  4. Enter the schedule destination.

    Note

    In this step, you configure scheduler settings for each destination by inserting a new entry with the respective destination name.
    1. Choose Create on the Scheduler: Destination tab.
    2. Enter the name of the inbound destination created earlier.
    3. Keep the default setting values.
    4. Choose Save.

For more information on transaction SBGRFCCONF, see the recommendations in SAP Note 2309399 - How to use SBGRFCCONF effectively?

Log in to track your progress & complete quizzes