SAP Integrated Business Planning (IBP) is a planning application, that combines supply chain monitoring, sales and operations planning, demand management, inventory planning, and supply planning into a comprehensive solution, which also supports the integration of data from external systems (for example, SAP ERP or SAP Advanced Planning and Optimization).
The recommended integration solution between SAP IBP and on-premise systems is SAP Cloud Platform Integration for data services.
For most cloud services, SAP Solution Manager is able to collect and monitor exceptions happening in the cloud service. But to fully monitor a cloud service scenario it is also important to monitor the integration between the cloud service and the on-premise backend system. This integration consists of different point-to-point interfaces of different usually more traditional types.
The following section describes the different integration options for the cloud service. Please choose the integration option you are using and consider also setting up the monitoring for the relevant interface types that are part of the integration scenario for the cloud service.
On this page we describe the monitoring setup this specific cloud service type. For information on how to set up the monitoring for the interface types supporting the integration, please refer to the setup documentation of the respective interface type which you can here.
For SAP Integrated Business Planning the following integration scenarios are possible:
Which integration scenario to choose depends on the object type of the data that you want to integrate:
The different scenarios contain the following exceptions and point-to-point connections:
|Scenario Component||Monitored Content||Interface Channel Type||Since SP|
|1||Systems: ABAP on-premise system||Logs written in the ABAP Application Log for the integration via SAP CPI-SDI||RFC: RFC Number of AppLog Errors metric||7.1 SP05|
|2||Cloud Services: SAP Cloud Platform Integration for data services||Exceptions in SAP CPI-DS||Cloud (SAP HCI DS)||7.2 SP03|
|3||Cloud Services: SAP Integrated Business Planning||Exceptions in SAP IBP||Cloud (SAP IBP)||7.2 SP04|
|4||Cloud Services: SAP Integrated Business Planning||Application Jobs in SAP IBP||use Job Monitoring application||7.2 SP05 (check SAP Note 2669548)|
The following technical prerequisites have to be met in order to monitor this scenario:
The following monitoring objects can be monitored for SAP IBP:
This portal page explains how to set up the monitoring for the SAP IBP error log.
|Metric Name||Description||MAI Category||Since SP|
|Number of exceptions in SAP IBP||
Number of exceptions detected in SAP IBP.
Exception statistics is retrieved from central Exception Management in Solution Manager. Data Collection is executed in delta mode.
The statistics are based on single exceptions which are retrieved via an API from SAP IBP into central Exception Management in Solution Manager.
|Single exceptions in SAP IBP||
Single exceptions detected in SAP IBP.
Exceptions are retrieved via an API from SAP IBP into central Exception Management in Solution Manager. Data Collection is executed in delta mode.
Public cloud service offerings are usually Software-as-a-Service (SaaS) solutions. This means that customers only have access to the service but not to the underlying infrastructure. Hence, the usual way to connect on-premise managed systems to SAP Solution Manager does not apply to cloud services.
However, to be able to monitor exceptions and performance in cloud services they need to be connected to SAP Solution Manager. This connection is created using the customer and cloud service specific root URL and an end-point definition.
The first step is to import the SSL certificate into SAP Solution Manager. This is valid for all cloud services.
Import Cloud SSL certificate into STRUST
Export Certificate from Browser:
Import Certificate into SAP Solution Manager:
Additionally you have to perform certain preparations in the cloud service to enable SAP Solution Manager to connect to the cloud service.
Create Communication Agreement
The user that will be maintained in the RFC endpoint, must be a user declared in the relevant Communication Arrangement defined in SAP Cloud for Customer for enabling the API used by Solution Manager. To arrange a communications agreement and allow SAP Solution Manager access please proceed as following:
The Cloud Services configuration is now accessible from the SAP Solution Manager Configuration (SOLMAN_SETUP) → Managed Systems Configuration → Tab 'Cloud Services'.
Create Cloud Service:
The second step is to create the end-point for the cloud service.
Create the End-Point:
After the basic configuration you now have to configure Exception Management, as the exceptions collected via Exception Management and stored in the central exception store are the basis for the Integration Monitoring data collection.
Configuration for IBP Logs
To access the Exception Management setup please go to transaction SOLMAN_SETUP → Application Operations → Exception Management
To find out which log area and sub-area to use for the filter, you can check the available logs in your IBP tenant.
You need a user with the authorizations to see the "General Planner" group in the IBP Launchpad.
The last step is the configuration of Interface and Connection Monitoring. The Interface and Connection Monitoring setup can be accessed via SAP Solution Manager Configuration (SOLMAN_SETUP).
Configuration for Monitoring Template: Cloud (SAP IBP)
To access the Integration Monitoring setup please go to SAP Solution Manager Configuration (SOLMAN_SETUP) → Application Operations → Integration Monitoring → Interface and Connections.
Navigate to the step 'Define Scope'. You can create a new scenario for the SAP ByD monitoring or use an existing one. Make sure the on premise system for the SAP ByD scenario and the Cloud Service created for SAP ByD is part of the Interface and Connection Monitoring scenario.
Create the Interface Channel:
Maintain the Interface:
User: User creating the log entry
Since the data collection is based on the content of the global exceptions store, you can always check the collected exceptions in Exception Management. All filter parameters are part of the collection context of the exceptions. The filters applied in Interface and Connection Monitoring allow you to filter the exceptions collected by the Exception Management further. However if the filters in Exception Management do not collect an exception, it is not available in the central exception store and you will not be able to find it in Interface and Connection Monitoring!
You can maintain attributes as described in the Interface and Connection Monitoring Setup on the tab 'Attributes'.
Thresholds and the collection schedule are maintained in the next step of the guided procedure. Once you have maintained all your channels, click 'Next' in the main guided procedure to move to the step 'Activation'.
Maintain Thresholds and Schedule:
If not active you can also activate the reporting for the channels by checking the box in the column 'Reporting'. This way you can see a history of the number of exceptions that happened and also place the metric on the OCC Dashboard in Focused Insights.
In the following we describe the monitoring configuration for an individual cloud Application Job.
To access the Job Monitoring setup please go to SAP Solution Manager Configuration (SOLMAN_SETUP) → Application Operations → Job Monitoring
Note: You need to have configured the IBP system as cloud service in the Managed System Configuration as described above and you need to have done the steps described in note SAP Note 2669548, beside others apply the BCSet attached to the note.
Navigate to the step 'Define Scope'. You can create a new scenario for the monitoring or use an existing one. Add the IBP system/tenant as external service to the monitoring scenario.
Create the Job Monitoring Object: