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.
Unlike the classic point-to-point interfaces like e.g. IDocs, Web Services or RFCs, when talking about monitoring for cloud services, you always also have to consider the integration component of the scenario. For most cloud services, Advanced Integration Monitoring for the cloud service itself concentrates on monitoring 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 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 categories that are available for this specific cloud service type. For information on how to set up the monitoring categories for the other technical system and cloud service types, please refer to the setup documentation of the respective interface type.
After setting up the monitoring for the single components and interface types, you can use the scenario configuration to group all relevant messages and exceptions of the cloud integration scenario in one Advanced Integration Monitoring scenario. Information how to create scenarios can be found here.
For SAP IBP the following integration scenarios are possible:
The different scenarios contain the following exceptions and point-to-point connections:
|Scenario Component||Monitored Content||Monitoring Category|
|1||Systems: ABAP on-premise system||Logs written in the ABAP Application Log for the integration via SAP CPI-SDI||ABAP Application Log|
|2||Cloud Services: SAP Cloud Platform Integration for data services||Exceptions in SAP CPI-DS||SAP Cloud Platform Integration for data services|
|3||Cloud Services: SAP Integrated Business Planning||Exceptions in SAP IBP||SAP Integrated Business Planning|
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 Focused Run does not apply to cloud services.
However, to be able to monitor exceptions and performance in cloud services they need to be connected to Focused Run. This connection is created using the customer and cloud service specific root URL and an end-point definition, which allows Focused Run to receive information from the cloud service.
The first step is to import the SSL certificate into Focused Run. This is valid for all cloud services.
Import Cloud SSL certificate into STRUST
Export Certificate from Browser:
Import Certificate into Focused Run:
Additionally you have to perform certain preparations in the cloud service to enable Focused Run to connect to the cloud service.
Preparations in SAP Integrated Business Planning
After gathering all necessary information and creating the necessary connection point or users in the cloud service, you can now create the cloud service in Focused Run.
Input Values for Integrated Business Planning
The second step is to create the end-point for the cloud service. The end-point is used to actually connect to the cloud service with user and password. Most cloud services use HTTP end-points.
Input Values for SAP Integrated Business Planning
To be able to monitor interfaces of an on-premise system you first have to add it to Interface & Cloud Monitoring and select the monitoring categories you want to monitor for the system.
In the next step, you see all monitoring categories which are available for the system, depending on the system type and the installed software components. Some recommended standard monitoring categories are preselected.
Select the monitoring categories in scope.
Available Monitoring Categories
For SAP Integrated Business Planning the following monitoring category ist available:
For monitoring of errors and warning happening during the integration on the on-premise side, please use:
After selecting your monitoring categories you have to maintain filters to define what exactly you want to monitor. Some monitoring categories come with standard filters that usually just select all items of this monitoring category. Focused Run can handle this high amount of monitoring data, so you can stick to this standard filters. Or you can set up filters of your own. You can create more than one filter for a monitoring category.
Available Filter Options
SAP Integrated Business Planning
For SAP Integrated Business Planning you can either collect all exceptions or you can restrict the exceptions by the following parameters:
Please use the following filter parameters to collect the correct log areas:
|IBP Order-Based Planning Integration||/IBP/RM_INTEGRATION|
|IBP Order-Based Planning||/IBP/RM|
|IBP Inventory Optimization||/IBP/IO|
|IBP Process Management||/IBP/PROCESS_MGMT|
|IBP Sales and Operations Planning||/IBP/SOP|
SAP IBP integration via SAP CPI-SDI writes errors in the ABAP Application Log. To use the monitoring category 'ABAP Application Log' on the on-premise system you have to provide the object and the sub-object. Use the following filter values:
The setup of the filters for the monitoring categories only makes sure that the data is collected, however, alerts are not created automatically. To create alerts and notifications you have to create an alert individually. If you didn't use specific filters in the setup before, but rather opted to collect all data, you have to create filters for the alerts.
In the next sub-step, you have to maintain the filter. The filter values are the same as described above. For some metrics, you have to maintain metric parameters. Find details below in the overview of the available metrics.
In the last sub-step you have to activate the alert:
For single exceptions, the threshold type is always 'Already Rated'. This means depending on the calculation frequency the number of exceptions is checked and an alert is created if this number is bigger than 0. If you want to reduce the number of alert for these metrics, you could increase the value for the calculation frequency to increase the time between checks.
For SAP Integrated Business Planning the following metrics are collected:
SAP Integrated Business Planning
Error for the replication on the on-premise systems can be collected with the metric 'ABAP Application Log exceptions' for 'ABAP Application Log'.