For SAP Integrated Business Planning for Supply Chain the following integration scenarios are possible: 

Which integration scenario to choose depends on the object type of the data that you want to integrate:

• Time series (mandatory for time series based planning): Use SAP Cloud Integration for data services (SAP CI-DS)
• Orders etc. (mandatory for order based planning): Use SAP Cloud Integration Smart Data Integration (SAP CI-SDI)

The different scenarios contain the following exceptions and point-to-point connections:

1. Integrating ABAP backend with SAP IBP mediated via SAP Cloud Integration for data services: 2, 3, 4
2. Integrating ABAP backend with SAP IBP mediated via SAP Cloud Integration with Smart Data Integration: 1, 3, 4 

The following monitoring objects can be monitored for SAP IBP: 

• SAP IBP writes errors in the IBP error log, which can be collected and monitored by SAP Solution Manager.
• On the business application side, SAP IBP processes data and creates forecasts using data from any backend system (typically a SAP ERP system), i.e. there are important inbound and outbound data processes as well as forecast runs. Important jobs therefore are the Data Integration*, Forecast* jobs.​ These application jobs should be also monitored as part of the Job Monitoring in SAP Solution Manager.

This portal page explains how to set up the monitoring for the SAP IBP error log.

Monitoring Template: Cloud (SAP IBP) 

Step 1: Configure Exception Management

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 

1. In the step 'Define Scope' select the tab 'Cloud Services' and your SAP IBP system. If you didn't configure the system before make sure to select 'All Cloud Services' in the view drop-down. Click on 'Configure' or click 'Next' two times. You will enter the step 'Exception Configuration'.
2. Click 'Add / Configure Log Store'. Select 'IBP Logs'.
3. Select the fields for filtering for your log store. The following filter fields are available:
   • Area: Application Log Area (see info box below)
   • FreeText: Message Text
   • Severity: Error or Warning
   • SubArea: Application Log Sub Area
   • UserName: User creating the log entry
   • MsgID: Message Class
   • MsgNo: Message Number
4. Maintain the filter values for the fields in the Filter Definition panel under the log stores table. You can also add, remove or change filter fields and values later on in the area. You can use different operators for your filter value. You can add more than one filter filed combination per log store. To add an additional filter field combination click on the button 'Add Filter' in the 'Configured Log Stores' panel.
5. You should not set up the monitoring for the exceptions in the Exception Management. If you activate the monitoring here, you will receive an alert (and if set up this way an email) for every single exception in the application log. Instead we will use Interface and Connection Monitoring to monitor the central exceptions store for exceptions. 

Step 2: Configure Interface and Connection Monitoring

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:

1. Select the scenario and click 'Next'
2. In step 'Preparation' perform all relevant manual activities and run all automatic activities.
3. In step 'Configuration' click the 'Add' button.
   • Channel Name: Enter a meaning full name (max. 30 characters)
   • Type: Select 'Cloud'
   • Monitoring Template: Select 'Cloud (SAP IBP)'
   • Description: Enter a description for the channel
4. Click Next.
5. Source type:
   • If the source system is the on premise system, please select 'Technical System'
   • If the source system is the SAP IBP system please select 'External Service'
6. Source: Select the on premise system resp. the SAP IBP Cloud Service from the drop-down list
7. Target Type:
   • If the target system is the on premise system, please select 'Technical System'
   • If the target system is the SAP IBP system please select 'External Service'
8. Target: Select the on premise system resp. the SAP IBP Cloud Service from the drop-down list
9. The measuring point is selected automatically
10. If more than one client are connected for the on premise system please select the correct client for the monitoring
11. Click Next.
12. Click Finish.

Maintain the Interface:

1. Select the interface channel you created
2. On the 'Interfaces' tab click the 'Add' button.
3. Provide the following information:
   • Area (mandatory): Application Log Area
   • Subarea: Application Log Sub Area
   • Message ID: Message Class
   • Message number: Message Number

   • User: User creating the log entry

Select Metrics:

1. On the tab 'Metrics' select the metrics you want to monitor
2. Save your interface channel by clicking on the 'Save' button.

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:

1. Select the Alert for the interface channel (the alert is the line with the red flash icon next to it)
   • On alert level you can maintain notification and incident message creation
   • Do not remove the flag for 'Do not Group Individual Occurrences' as this flag ensures that an alert each time new exceptions are found during a data collection interval
2. Select the Metrics
   • Do not change the data collector type or data collector name on the tab 'Data Collection' as the monitor will not work anymore if this is changed.
   • Do not change the threshold if it is set to 'Already Rated'.
3. Click 'Apply and Activate' → <Choose one option> to activate the monitoring

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.