Monitoring Capabilities in SAP Batch Release Hub for Life Sciences
SAP Batch Release Hub for Life Sciences offers in In-App monitoring capabilities to review data that is coming in the SAP Batch Release Hub for Life Sciences. Three different tiles are available:
Beside those In-App capabilities, it is recommended to set up the monitoring in SAP Cloud ALM.
Monitor Data Processing
The App monitor data process displays all data records that have been sent to SAP Batch Release Hub for Life Sciences. As shown in the screenshot, different types of records, such as Inspection Lots and Batches, have been sent to the Batch Release Hub.
In the selection criteria, it is possible to filter for the following:
- Record
- A detailed record identification so that it can be linked to the right release decision item, like the inspection lot number includes the Material ID and the batch ID.
Example
Record Type Key Fields Batches Batch ID / Material ID / Plant ID Batch Release Countries Batch ID / Material ID / Plant ID / Country Code Quality Deviations Quality Deviation ID / Deviation Type / Batch ID / Material ID / Plant ID Release Decision Triggers Release Decision Trigger ID / Trigger Type / Batch ID / Material ID / Plant ID Inspection Lots Inspection Lot ID / Batch ID / Material ID / Plant ID - Record Types
Record Types are, as in the example, Inspection Lots, and Batches, but also Batch Review, Components, or Inspection Lot Characteristics can be selected.
- Event Type
- Indicates the type of event triggered. The following types of event are monitored:
- Business Rule Executed (BRE)
- Outbound Message Generated (OMG)
- Record Activated (RA)
- Record in Staging (RS)
- Release Decision Confirmed (RDC)
- Release Decision Item Created (ICR)
- Monitoring ID
- Enables to identify all events that have taken place for a single record.
Business Rules Executed
The incoming data is processed by the business rule framework. Once the data has been sent to BRH, the business rule is also executed, like in this example for the Record Type components and component relations.
To get more information for the record, just select one line.
Detailed Information for a Record
All the relevant data can be accessed in the detailed view, like the context of the payload or the inbound and outbound payload. It is always good to check why the business rules will not be executed as expected and why data in specific fields in the UI are missing.
In the end of the Event Record the alert is displayed, Alerts can be verified in the next app.
Monitor Alerts
Lists of the alerts that have been logged. Each entry represents an alert created when a particular event has been triggered for a data record. Alerts are logged when events occur successfully and when warnings and errors occur.
- Alert Type
Indicates the severity of the alert.
The following types of alert types can occur:
- Information: The event was successful.
- Error: The event failed and processing is halted.
- Warning: The event has a warning but processing continued.
To avoid any data loss or processing disruptions, follow-up, and resolve all alerts of type Error and Warning.
Monitor Staging and Active Data
Inbound data is initially stored in the staging area and is not available for use in the release decision processes. Before the inbound data can be used in the release decision processes, it must be activated, which moves the data from the staging area to the active area.
In this app, all the data that are used for fields in the UI can be checked. Like in our example, the batch data in the BRH App view and the table view can be adapted. For detailed information, select one line.
The detailed data also gives the link from which system the data came for, if it was an SAP ERP System or an external system.
