Analyzing the Key Features of SAP Batch Release Hub for Life Sciences

Objective

After completing this lesson, you will be able to familiarize yourself with the central features of SAP Batch Release Hub for Life Sciences.

Overview

The SAP Batch Release Hub for Life Sciences is a cockpit developed with two major pharmaceutical companies. It is suitable for pharmaceutical companies of all sizes and can be integrated into various process and system landscapes.

The SAP Batch Release Hub for Life Sciences is a public cloud solution built on the SAP Business Technology Platform.

The concept of the SAP Batch Release Hub is to gather information and data from different systems involved in the batch release process, such as a Laboratory Information Management System (LIMS) or a Manufacturing Execution System (MES). For example, the user can choose to retrieve data from these systems to ensure a smooth batch release process.

An infographic illustrating the integration of various systems and processes to enhance batch release cycles in life sciences. The diagram shows a central cloud application labeled SAP Batch Release Hub for Life Sciences connected to various components such as CTM, ERP, DMS, GMS, MES, and RIMS. These connections aim to achieve faster batch release cycle times, standardization across the organization, elimination of human errors, improved user experience, and scalability for smaller batch sizes. Additional features include easily trainable modules for new hires, supply chain data checks, quality data checks, and regulatory data checks. The bottom of the image consists of a legend explaining the abbreviations used, such as ATTP for Advanced Track and Trace for Pharmaceuticals and ERP for Enterprise Resource Planning.

The data from those systems will be pushed into the SAP Batch Release Hub for Life Sciences. The concept of how the data will be pushed into the SAP Batch Release Hub for Life Science will be described in the following Unit of this course. 

In this lesson, you learn the scope of SAP Batch Release Hub for Life Science. 

Home Screen of SAP Batch Release Hub for Life Sciences

The home screen of SAP Batch Release Hub for Life Sciences is divided based on your assigned roles into different sections: 

  1. Release Decision
  2. PCN Release Decision
  3. Juristricitional Control
  4. Data Monitoring
  5. Configuration and Responsibilities
  6. Tracking of Changes
Screenshot of a software interface with various management options. The top menu includes tabs like Release Decisions, Data Monitoring, Configuration and Responsibilities, and Tracking of Changes. Below, there are clickable sections such as Release Decision Overview, My Release Decisions with a count of 162 open items, Monitor Data Processing, Monitor Alerts, Manage Staging and Active Data, Manage Release Configurations, Manage Quality Departments with a count of 9, View User Responsibilities, Manage Business Rules, Manage Repositories, and View Change History. The interface is part of an SAP system, indicated by the SAP logo in the top left corner.

The section Release Decision contains the application My Release Decision. This app is the central working area for qualified persons, auditors, and other users involved in the batch release process. It contains all relevant release decision triggers. This app is described in detail in this lesson.

The section Data Monitoring three apps:

  • Monitor Data Processing
  • Monitor Alters
  • Manage Staging and Active Data

These apps are more for an administrative user, as they contain much technical data, such as how different data has been pushed into the SAP Batch Release Hub for Life Sciences.

The section Configuration and Responsibilities offer different apps, such as:

  • Manage Release Configuration
  • Manage Quality Departments
  • Manage Business Rules
  • Manage Repository

The section Tracking Changes combines the following apps:

  • Track Changes
  • View (PCN) Signature Log

These apps are described in detail in this lesson.

Apps

My Release Decision App

In the app My Release Decision, the qualified persons and other authorized users are able to see all the release decisions that are available for processing, and have been sent to the SAP Batch Release Hub for Life Sciences. Each line shows the following data per default.

The image is a screenshot of an SAP interface titled My Release Decisions. It displays a table with multiple columns, including Batch ID, Material ID, Material Description, Plant, Release Decision Trigger ID, Release Decision Trigger Type, Release Type, Quality Department, Deviations, Release Checks, Due Date, Assigned To, and Processing Status. The table lists 197 release decisions with various details filled in for each column. The interface also includes filter options at the top for searching and refining the displayed data. Some entries have color-coded indicators for deviations and release checks, and the Assigned To column lists different names. The Processing Status column shows statuses like In Progress, New, Obsolete, Confirmed, and Completed.
Batch ID
Batch number that has been assigned in the leading ERP system for example in ECC or SAP S/4HANA. 
Material ID
Material Number that has been created in the leading ERP system for example ECC or SAP S/4HANA.
Material Description
Detailed description of the material, it will be also transferred from the leading ERP system.
Plant
Indicates the plant in which the batch shall be released, it could be a different one from the manufacturing plant.
Release Decision Trigger
Release decision trigger is central identifier in SAP Batch Release Hub for Life Sciences. All incoming batches are assigned a release decision trigger. In case of an inspection lot, the number of the inspection lot is displayed, there is no separate number range for the release decision trigger.
Release Decision Trigger Type
The type can differ from where the batches were originally sent. In the case of SAP S/4HANA and ECC, the release decision type would be IL for Inspection Lot, but it could also be Goods Receipt (GR) or Goods Issue (GI) if the batches are transferred from non-SAP systems as leading systems, and the mapping in the API contains these release decision trigger types.
Release Type
SAP Batch Release Hub for Life Sciences offer in the standard configuration different release types like Technical Release internal production, Technical Release external production, Market Release and Distribution Release. The difference between the different release type will be explained in the following lesson of this unit.
Quality Department
The quality department is the central organizational unit in SAP Batch Release Hub for Life Sciences .The QA Department decides whether the person can see a release decision trigger or not. In lesson 2 of this unit, the concept of the QA departments will be explained. If a person is not assigned to the relevant QA department, he/she will not be able to work on the release decision trigger even if they have the right authorization. 
Deviations
This column would indicate whether a batch has open or closed deviations. By moving the mouse over the colored deviations, you will see a cumulated overview of closed deviations, open deviations and closed with restrictions deviations.
Release Checks
This column cumulates the status of the release checks based on the release type. The different release types could have different release checks. This will be explained in lesson 2 of this unit. The color coding indicates whether data is still pending (grey), have been received with correct details for the release check (green), have been received with errors (red) or in case it has been configured the release check received data with condition (yellow).
Due Date
The due date will be calculated based on the duration time that has been maintained in the configuration of the release types, it can be overwritten by prioritizing a release decision trigger.
Assigned to
Anyone with authorization can assign themselves to a release decision trigger, or someone else can be assigned to the release decision trigger. 
Process Status
The column indicates the working status of the release decision:
Process StatusDefinition of Process Status
NewNo one has worked on the release decision yet.
 In progressProcessing of the item has started.

For example, the item has been assigned to a responsible person.

ObsoleteThe item was invalidated due to changes in the configuration, or the item was canceled through a release decision trigger.

When an item is made obsolete due to configuration changes, a new item is created with the latest configuration settings.

ConfirmedSubsequent processing in the source system has been completed and the release decision has been confirmed.
CanceledThe transaction has been manually set to canceled by a responsible person.

Only new transactions and transactions in process can be set to canceled. Once an item has been set to canceled, it can no longer be changed.

Screenshot of an SAP software interface showing a list of release decisions. The main table displays columns such as Batch No., Material ID, Material Description, and Plant. On the right side, a settings menu is open with options to change display fields, highlighted by a red arrow pointing to the settings icon. The menu includes checkboxes for various fields like Batch Quantity, Comment, and Confirmation Received On.

It is possible to add or remove fields to the table view in the My Release Decision app.

For example: 

  • Batch Quantity 
  • Decision set on 
  • Decision set by
  • Manufacturing plant 
  • Release Decision
  • Quality Batch Status

You can also use these fields for sorting or grouping within the table view.

Screenshot of an SAP software interface displaying a My Release Decisions dashboard. The screen shows a table with columns for Release Decision ID, Material ID, Material Description, Plant, Release Decision Target, Release Decision Trigger, Quality Department, and several status indicators such as Release Checks and Processing Status. Each row represents a different material with details like ID, description, and status indicators shown in colors green, red, and yellow to denote different statuses. The top of the screen has a navigation bar and several filter options, and there is a highlighted section indicating a search bar.

The My Release Decision App also offers further features including the following:

Regenerate 

Make the selected item obsolete and create a new one. Regenerating an item is required, for example, if you want to change the release type. 

Here's how to regenerate an item: 

  • Select a release decision item that has the processing status New or In Progress. 
  • Choose Regenerate. 
  • The selected item is marked as obsolete and can no longer be changed. The app creates a new release decision item for the same combination of material, batch, plant, release type, and release decision trigger represented by the selected item. 
  • Any changes in configuration and business data are automatically applied to the new item. 
  • Start processing the new item. For example, change the release type. 
Reprocess

Create a copy of the selected item for reprocessing. It may be necessary to reprocess a completed release decision item, for example, if the initial release decision was a preliminary one or if new business information requires the original decision to be revised. 

Note

Whether you can reprocess a release decision item depends on how release types are configured in your system.

Here's how to reprocess an item: 

  • Select a release decision item that has the processing status Completed or Confirmed. 
  • If reprocessing is allowed, this button becomes available. 
  • Choose Reprocess. 
  • The app creates a new release decision item for the same combination of material, batch, plant, release type, and release decision trigger represented by the selected item. 
  • The following information is copied from the original item and remains unchanged: 
    • Key data, such as material, batch, location, release type, and release decision trigger 
    • Prioritized due date
    • Release check statuses that were set manually 
    • Comments
    • Attachments
     
  • Check the new item for updated information and start processing it. 

 The following information is not copied from the original item and requires checking: 

Information

InformationWhat Happens to the Information
Release check statuses that were set by the systemRelease check statuses are updated according to the latest changes in the source system.
Person responsible assigned to the itemThe assignment is reset.
Countries/regions suitable for releaseManual changes are reset.
Stock postingsManual changes are reset.
Confirmation from the source systemConfirmation data is cleared

Set Prioritized Due Date  

Set a new due date for urgent release decisions. 

Here's how: 

  • Choose this button to open a dialog. 
  • If you're in the worklist, you must have selected at least one entry. 
  • Enter a date and confirm your entry. Note that you can only enter a date in the future. 

To reset a prioritized due date, clear the date field and confirm your entry. 

Assign

Assign a person responsible for processing a worklist item. 

Here's how: 

  • Choose this button to open a dialog. 
  • If you're in the worklist, you must have selected at least one entry. 
  • Enter the name of the person that you want to assign. You can assign people who are in the same quality department and have the same responsibilities as you. 
  • If you want to assign the worklist item to yourself, leave the input field empty and choose Assign to Me. 

Note

Once a worklist item has been assigned for processing, you can change the assignment, but you can't unassign the item completely. 

In addition to the My Release Decision app, the app Release Decision Overview provides a graphical overview. This dashboard app helps you understand and manage your workload of release decisions.

You can identify and prioritize the release decision that needs your attention the most. You can then navigate directly to the y Release Decisions app to edit them. In the My Release Decisions app, your worklist is automatically filtered to show only the relevant items.

Screenshot of the SAP Release Decision Overview interface. The left side of the screen shows a summary titled My Release Decision Items with a breakdown by urgency: 2 urgent, 37 overdue, totaling 41 items. Below this is a pie chart with red indicating overdue items and a small green segment for urgent items. The right side of the screen displays sections titled Ready for Release with 1 item listed, and Critical Release Decision Items showing a list of items, all marked as overdue by 145 days, with due dates and product IDs. The interface has a clean layout with navigation and filter options at the top.

The dashboard shows all release items categorized according to the different urgency states.

How Is Urgency Calculated?

The urgency of your release decision items is calculated based on a due date (or prioritized due date) and lead time as follows:

  • On Time: The number of days to the die date (or prioritized due date) is greater than the lead time.
  • Urgent: The number of days to the due date (or prioritized due date) is less than or equal to the lead time.
  • Overdue: The due date (or prioritized due date) is in the past.

The leas time is configured in the Manage Release Configurations app.

What You Can See

  • A chart summarizing your release decision items by urgency
  • A chart summarizing the release decision items that have pending or non-compliant checks
  • A list of critical release decision items (items that are overdue or urgent)
  • A list of release decision items with release checks that require your manual intervention
  • The number of release decision items that have open deviations
  • The number of release decision items that are ready for release
  • A chart showing the number of release decisions completed in the past days

What You Can Do

  • Use filters to show the release decisions items that you're interested in.
  • Personalize the filters and create your own views.
  • Navigate to the My Release Decisions app from any of the cards.
  • In the My Release Decisions app, your worklist is automatically filtered to show the relevant items.

The chart Ready for Release indicates all release items. A release decisions item is considered to be ready for release when it has the following characteristics:

  • The processing status of the release decision item is New or In Progress.
  • The status is green for all the related release checks.

Screenshot of a SAP Release Decision Overview interface. The left side of the screen lists Items Requiring My Intervention with several entries marked as Overdue: 145 days and requiring 1 manual intervention. Each entry is categorized under types like Market Release (MR) and Release for Emergency Use (REU). The right side of the screen displays a pie chart titled Items with Pending or Non-Compliant Checks, showing a majority of items overdue, with a small segment marked urgent. Above the chart, a summary notes 33 Total items with 2 Urgent and 31 Overdue. The interface includes various tabs and dropdown menus for navigation and filtering.

The area where the items with pending or Non-Compliant checks are displayed shows a summary of any overdue and urgent release decision items that have pending or non-compliant release checks.

In the chart, the items are categorized by the number of days from the due date (or prioritized due date). These items have the following characteristics:

The processing status is New or In Progress.

The items are Overdue or Urgent as follows:

  • Urgent: The number of days to the due date (or prioritized due date) is less than or equal to the lead time.
  • Overdue: The due date (or prioritized due date) is in the past.

There is at least one release check wit the following status:

  • A red status.
  • A grey status, and the release check status determination is either System or System or User.

View Change History App

Within the View Change History App you can get detailed information about changed made in objects used for batch release processing.

This app gives you an overview of what was changed, who made the change, and when the change was done.

Screenshot of an SAP software interface displaying a View Change History page. The page lists various changes made to system objects, including details like Object ID, Object Type, Changed By, Changed On, Attribute, Cause, Status, and More Change Info. The interface includes search filters at the top and options to export data, reset layout, and apply filters. The table is populated with multiple entries, primarily involving quality department responsibilities and mission decision review status changes.

The View Change History app logs changes made in the following apps:

  • My Release Decisions
  • Manage Release Configurations
  • Manage Quality Departments
  • Manage Staging and Active Data

Note

Changes related to the electronic signature for release decisions are tracked separately in the View Signature Log app.

In the Manage Release Configurations app, you can open a change history for a single object. For example, you can view all of the changes made for release check or for a release type. You'll also find these changes in the View Change History app, identified wit the object type, ID, and description.

The displayed content of the app includes the following information:

Displayed Content of the App

Displayed ContentInformation
Object TypeIdentifies the type of object for which a changes was made.
Object IDShows the identifier or set of identifiers for an object that was changed. What's shown here depends on the object type. For example, if an attribute was changed in a quality department ID. For changes made in a release decisions item, the ID contains the key fields for the item (batch ID, plant ID, material ID, release decision trigger type and ID, and release type ID).
Object DescriptionShows the description of an object that was changed, For example, if an attribute was changed in a quality department, this field shows the quality department description.
Changed byIndicates the user who made the change. It could be also the system as changing the user.
Changed onIdentifies the time when the changed was made.
AttributeIndicates where the change was made, either in a location or a release check or a time stamp for a release check.
ContextProvides additional context information about where the changed attribute is located.
Before ChangeValue or field entry before the change.
After ChangeValue after the change.

View Signature Log App

This app enables you to check who signed or attempted to sign a release decision. Setting a release decision in the My Release Decisions app requires an electronic signature. Users must enter a password and confirm the accuracy and correctness of the information given before the release decision can be set. This app shows all events related to the electronic signature for release decisions. An event is logged whenever a user opens the Set Release Decision dialog. 

A screenshot of a digital log showing a list of logged events in a table format. The table includes columns for Event, User, Date, IP Address, Reason ID, Part, Maintenance, Review Decision, Review Decision Trigger ID, and Details. The events are primarily labeled as Signature Generated and Signature Successful, with various users and dates listed. The interface includes a search bar, filters, and pagination controls at the top.

Logged Events

Shows you when and by whom a release decision was signed, or an attempt to sign a release decision was made. 

The following events are possible: 

  • Incorrect Password: The user tried to sign a release decision but entered the wrong password. 
  • Signature Canceled: The user started setting a release decision but canceled the action.
  • System Error: Setting a release decision wasn't possible because of a technical error.
  • Signature Successful: The user signed a release decision and the release decision was set.
  • User Inactive: The user is inactive in your Identity Provider (IdP) or the user's email address is invalid. 
  • User Locked: The user tried to sign a release decision but repeatedly entered the wrong password. 

Release Decision

Shows the release decision that the user set, or attempted to set in the My Release Decisions app. 

Values are shown for the following events: 

  • Incorrect Password: The release decision that the user entered. The release decision was not set due to an incorrect password. 
  • Signature Successful: The release decision that the user entered and signed. The release decision was set successfully. 

Details 

Shows additional information logged for an event record, if relevant. 

Additional columns that can be added or removed are:  

  • User: Which user executed the signature.
  • Created on: When did the signature happen.
  • Batch ID: For which batch the signature has been taken
  • Plant: For which plant the signature has been taken  
  • Material: For which material the signature has been executed
  • Release Decision Trigger ID:  The relevant release decision trigger for which the signature has been executed.
  • Release Decision Trigger Type: This would identify whether the release decision trigger has been created based on an inspection lot or any other type like the goods receipt or a goods issue.

Screenshot of a SAP software interface showing the Release Decision tab with sub-options. Highlighted is the Release Decision Overview section displaying an icon of a clipboard with a checkmark and the number 41 labeled as 'Open' indicating open release decisions. The top menu also includes options for Data Monitoring, Configuration and Responsibilities, and Tracking of Changes. A search bar and user initials 'SG' are visible in the top right corner.

Integration of SAP Batch Release Hub for Life Sciences with Other Source Systems

Integration of SAP Batch Release Hub for Life Sciences with Other Source Systems

SAP Batch Release Hub for Life Sciences can be integrated with different Systems: 

  • CTM: Clinical trial management
  • LIMS: Laboratory information management system
  • DMS: Document management system
  • QMS: Quality management system
  • MES: Manufacturing execution system
  • GBT: SAP Global batch traceability
  • ATTP: Advanced track and trace for pharmaceuticals
  • RIMS: Regulatory information management system
  • ERP: Enterprise resource planning 
Diagram illustrating a cloud-based application for batch release in life sciences. The image shows various interconnected components: ERP, CTM, DMS, and GMS icons on the left represent supply chain data check and quality data check processes. In the center, a cloud application icon connects to SAP Batch Release Hub for Life Sciences. On the right, icons for RIMs, GBT, MES, and ATTP represent regulatory data check and manufacturing data check. The top of the image features a cockpit dashboard for overseeing batch release. Lines between icons indicate data flow and integration points.

In SAP Batch Release Hub you can connect SAP Global Batch Traceability and a Document Management System in the configuration.  The DMS can be used for uploading release-dependent documentation and the SAP Global Batch Traceability to enrich the Batch Genealogy Check with a link to the SSAP Global Batch Traceability.

This section describes how to set up the link into SAP Global Batch Traceability. The integration concept for other systems will be described in the second learning journey Configuring and Implementing SAP Batch Release Hub for Life Sciences in the second Unit Explaining Architecture and Integration with SAP and non-SAP Systems.

Batch Genelogy Check

Batch Genelogy Check

In the settings for release checks, it is possible to enable the batch genealogy check via SAP Global Batch Traceability.  

Screenshot of a software interface, specifically an SAP system configuration page titled Make General Settings. The interface includes a navigation menu on the left with various configuration options such as Configure Release Check Statuses and Configure Quality Decisions. The main panel on the right shows settings for Batch Genealogy Check with options to enable it and fields for Host, Port, Page ID, and Client. There is also a section for Administrative Data showing the last change date and the user who made the changes.

This feature activation indicates whether you want to include a batch genealogy check as one of your release checks. 

If you want to include a batch genealogy check in the release checks for your release decision items, you must configure a connection to the source system for your batch genealogy data. You must enter the connection parameters for your SAP Global Batch Traceability system. These parameters are used to generate a link, which is displayed on the details page for the genealogy check in the My Release Decisions app. When you click the link, the SAP Global Batch Traceability system opens and displays the genealogy information for the relevant batch. You can review the batch genealogy directly in SAP Global Batch Traceability before setting the status of the genealogy check. 

You configure the connection to SAP Global Batch Traceability as follows: 

  • Activate the toggle bar icon for Use Batch Genealogy Check. 
  • The fields for the connection parameters are displayed. These fields are all mandatory when Use Batch Genealogy Check is selected. 
  • Enter the following information: 
    • Host
    • Port
    • Page ID
    • Client ID
  • Save your changes. 

For more information about configuring a connection to SAP Global Batch Traceability, see Direct Access to User Interface Using URL Parameters.

Transport Configuration

In the configuration app, the transport functionality can be enabled. Before starting with the configuration of the transport option make sure that you have followed the steps in the order of this lesson with the activation of the transport via application configuration, followed by adding the necessary configuration settings.

Screenshot of an SAP software interface showing the 'Make General Settings' page. The left panel lists various configuration options such as 'Configure Release Checks', 'Quality Batch Statuses', and 'Configure Release Types'. The main panel displays 'Application Configuration' with a toggle for 'Configuration Editable', and 'Administrative Data' showing details like 'Changed On: 12 Nov 2022, 15:09:04' and 'Changed By: sb-tenant-onboarding14'. The top right corner has buttons for 'Edit' and 'View Change History'.

Configuration Editable 

Controls whether the configuration settings are editable in this tenant. If Configuration Editable is set to Yes, authorized users can make any changes to the configuration settings in this app. Instead, the configuration changes must be made through a transport from another tenant. 

Transport Node Name 

Specifies the name of the transport node configured for this tenant in the SAP Cloud Transport Management service. In SAP Cloud Transport Management, you must create a transport node for each tenant from which you want to transport configuration settings. The name you enter here must exactly match the name of the transport node configured for this tenant in SAP Cloud Transport Management.

Where Is This Setting Used? 

The transport node name is used in the Transport Configuration Settings app to transport configuration settings from one tenant to another. The transport node represents the source and the target tenant for the transport process. 

Hint

To avoid any accidental changes or disruption to your production environment, set Configuration Editable to No in your production tenant. Make your configuration changes in another tenant where you can thoroughly test the effect on your release decision processes. Then, you can use the Transport Configuration Settings app to transport configuration changes to production as required. 

Transport Configuration Settings

Transport configuration settings from this tenant to the configured target tenant. 

This app uses the SAP Cloud Transport Management service to transport configuration settings from one tenant to another. By transporting your configuration settings, you can avoid manually maintaining configuration changes in multiple tenants. 

Screenshot of an SAP software interface showing a navigation bar with options such as Home, Release Decisions, Data Monitoring, Configuration and Responsibilities, and Tracking of Changes. The main section titled 'Configuration and Responsibilities' includes icons for Manage Release Configurations, Manage Quality Departments, Manage Business Rules, Manage Repositories, and Transport Configuration Settings, with the last option highlighted in a red box.

Transport Configuration Settings - Content

Required Setup 

Before you can transport your configuration settings, you must do the following: 

  • Create a transport node in SAP Cloud Transport Management. 
  • The transport node represents the source tenant and the target tenant for the transport. You need to create a transport node for each source tenant from which you want to transport settings. 
  • In your source tenant, enter the transport node name in the Manage Release Configurations app under General Settings. 
  • The transport node name that you enter under General Settings must exactly match the transport node name as configured in SAP Cloud Transport Management. 
Screenshot of SAP software interface showing the Transport Configuration Settings page. The page displays a section titled General Data with fields for Transport Node Name filled as bh-cnaqry-easd (test-tenant-3) and Configuration Transport Description filled as test. There are navigation buttons at the top for Transport and View Transport History, and a search bar in the upper right corner.

What Settings Are Transported? 

The transport of configuration includes all the following settings: 

  • Release check statuses 
  • Release checks 
  • Release check messages 
  • Quality batch statuses 
  • Usage decisions 
  • Release decisions 
  • Stock posting types 
  • Release types 
  • Combined release types 
  • Inspection types 
  • Business roles 
  • Material types 
  • Location types 
  • Organizational areas 

Need More Information? 

For more information about the SAP Cloud Transport Management service, see What Is Cloud Transport Management. 

Languages

When you are working in SAP Batch Release Hub for Life Sciences, you can choose your preferred language.

Screenshot of an SAP software interface displaying various management options. The top menu includes tabs for Home, Release Decision, Data Monitoring, Configuration and Responsibilities, and Tracking of Changes. The main area shows different sections like Release Decision Overview, My Release Decisions, Data Monitoring, Manage Staging and Active Data, and more. Each section is represented with icons and brief descriptions. The user profile and settings options are accessible in the top right corner.

The apps are available in the following languages:

  • English
  • German
  • Spanish
  • French
  • Japanese
  • Portuguese
  • Chinese
  • Russian

In the Settings panel, you can choose from different languages and confirm your selection by choosing Save.

Screenshot of an SAP software interface showing various settings options. The main focus is on the Language & Region settings window, which is open and displaying options for setting browser language, date format, and time format. The languages available in the dropdown menu include English, French, German, Japanese, Portuguese, Russian, Simplified Chinese, and Spanish. Other visible sections in the interface include Release Decision, Data Monitoring, and Configuration and Responsibilities.

German Language

This screenshot shows you the start screen after choosing the language, German.

New Features in Integration Hub for Life Sciences

The following new features are available in Integration Hub for Life Sciences:

  • Integrated Batch Release Hub Adapter:

    The Batch Release Hub Adapter is now included in SAP Batch Release Hub for Life Sciences by default. The original standalone version of the adapter is deprecated; however, it is still available and can be used if required.

  • Clinical Trial Data:

    The replication of batches that are part of clinical trials has been enhanced to include the related clinical trial and clinical study data.

  • Clinical Trial Release Check:

    The clinical trial release check data is based on regulatory data, especially country-related shelf-life data. The integration with SAP Intelligent Clinical Supply Management enables the automatic transfer of that data upon regulatory data changes.

  • Handling of Canceled Process Orders:

    Canceled process orders and goods movements are sent to SAP Batch Release Hub for Life Sciences with their component relationship status set to Inactive and are not included in the component details in the My Release Decisions app.

For more information, see (Optional) Set Up Integration Hub for Life Sciences.

Screenshot of a SAP software interface showing the Quality Department details for clinical trials. The screen is divided into several sections including Quality Department Details, Assigned Users, and Administrative Data. The Quality Department is labeled as active with various user IDs listed under Assigned Users. Administrative data shows creation and change dates. The interface has a navigation bar at the top and options for editing and viewing change history.

API to Extract Batch Genealogy Data

A new outbound API allows you to extract the genealogy data of a batch. This feature gives you access to the batch genealogy data, so that you can use the data in other tools and systems as required.

For more information, see: SAP Business Accelerator Hub.

Here you can find the link to the API information: Overview | Genealogy Data | SAP Business Accelerator Hub

Screenshot of the SAP Business Accelerator Hub interface for the Genealogy Data section. The page includes navigation tabs such as Overview, API Reference, and Try Out. There are sections for Introduction, API Resources, and Configuration Details. The interface shows options for viewing API reference, checking schema view, and a try-out feature. The status of the system is active, last modified on 18 Oct 2023, with a version number 3.0. The page layout is clean with text and selectable options clearly displayed, and there are two people visible in the background in an office setting.

Batch API Enhanced to Include the Batch Record Review Relevancy Indicator

The batch API version 4.0.0 has been enhanced to incorporate a new attribute called "isExcludedForBRR_ID."

This attribute indicates whether a batch can be excluded from the Batch Record Review Check.

Screenshot of a software interface for SAP Business Accelerator, showing the Batch Record Reviews module. The interface includes navigation tabs such as Explore, Resources, and Discover Integrations at the top. The main area displays an introduction to the Batch Record Reviews with options to view API Reference, Check Schema View, and Try Out. Below, there is a table listing API resources like API Specification and Authentication Methods. On the right side, there is a panel titled 'BatchStructure V1' listing various data fields such as plant_ID, material_ID, and qualityStatus_code, each with a type indicator and a visibility status.

The new attribute is visible in the Manage Staging and Active Data app for inbound batches.

If a batch is flagged as not relevant for the Batch Record Review, it will not be considered as a component in the Enhanced Batch Record Review Check. 

For more information, see: SAP Business Accelerator Hub.

For more information, see: Overview | Batch Record Reviews | SAP Business Accelerator Hub

Here you can find the link to the API information: Overview | Genealogy Data | SAP Business Accelerator Hub

Integration Hub

If you are using Integration Hub for Life Sciences, you must ensure that your system is configured to use the integrated Batch Release Hub Adapter. As of release 2306, the original standalone version of the Batch Release Hub Adapter is deprecated, and therefore, use of the integrated adapter is mandatory.

Diagram illustrating the integration architecture between SAP S/4HANA and SAP BTP for the Industry Solution for Life Sciences. The left side of the diagram shows the on-premise components including DRF Integration, OData Service, and SAP Cloud ALM Integration, all connected via REST over HTTPS. The right side shows SAP BTP components including Integration Core Service, Enterprise Messaging, and SAP Cloud ALM with API and Integration Monitoring features. Connections between these components are depicted with arrows indicating data flow, primarily using REST over HTTPS and OData over Cloud Connector. The center features a Batch Release Hub Adapter for Life Sciences, detailing inbound and outbound data flows.

For more information, see: Overview of Integration Hub for Life Sciences.

SAP Cloud ALM Real User Monitoring

Both SAP Batch Release Hub for Life Sciences and Integration Hub for Life Sciences support SAP Cloud ALM Real User Monitoring (performance monitoring).

SAP Cloud ALM Real User Monitoring works "out of the box" and allows you to see performance metrics in your SAP Cloud ALM tenant. The prerequisites are that you have enabled your SAP Cloud ALM subscription and turned on data collection for Real User Monitoring.

For more information, see Using SAP Cloud ALM and Real User Monitoring Setup & Configuration.

User Experience Improvement

The user experience improvements are delivered with the November 2023 release.

The following SAP Fiori themes are deprecated and have been removed:

  • SAP Belize
  • SAP Belize Deep
  • SAP High Contrast Black
  • SAP High Contrast White

The default SAP Fiori theme is now SAP Morning Horizon.

Screenshot of a software interface with a navigation bar on the left showing options such as Release Decisions, Data Monitoring, Configuration and Responsibilities, and Tracking of Changes. The main area displays a settings menu titled Appearance with theme options including SAP Evening Horizon, SAP High Contrast Black, SAP High Contrast White, SAP Morning Horizon, SAP Quartz Dark, and SAP Quartz Light. The SAP Morning Horizon theme is selected.

Features and Fixes in the November Regular Change

The following issues have been fixed in the November regular change:

  • Unable to extend user interface in SAP Batch Release Hub for Life Sciences
  • Issue during release check configuration
  • Error transporting application content via the cloud Transport Management Service (cTMS)

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn