1. SAP Support Portal Home
  2. Application Lifecycle Management
  3. SAP Solution Manager
  4. Expert Portal
  5. Public Cloud Operations

Integrated Business Planning

Integrated Business Planning

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. 

Integration Scenario

Please, select...

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:

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

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

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

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)

Technical Prerequisites

The following technical prerequisites have to be met in order to monitor this scenario:

  • Error log monitoring requires at least SAP Solution Manager 7.2 SP04
  • SAP IBP job monitoring requires at least SAP Solution Manager 7.2 SP05
 

Available Monitoring Content

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) 

 

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.

 Exceptions 7.2 SP04
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.

 Exceptions 7.2 SP04

Connect Cloud Service

Please, select...

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: 

  1. Open the cloud service URL in your web browser.
  2. Click on the padlock next to the Cloud Service URL (within the address input field).
  3. When using Firefox, click on ‘Show Connection details', ‘More Information', 'View Certificate' and select the ‘Details' tab.
  4. When using Microsoft IExplorer, click on ‘View Certificate' and select the 'Certificate Path' tab.
  5. When using Google Chrome, click on ‘Certificate' and select the 'Certificate Path' tab.
  6. In the displayed certificate hierarchy select the Certification Authority (CA) certificate you plan to trust.
  7. When using Firefox, press ‘Export…'.
  8. When using Microsoft IExplorer or Google Chrome, press ‘View Certificate' and in the displayed pop-up navigate to the ‘Details' tab, to press ‘Copy to File…'.
  9. Select an export format you would like to use and that is supported by STRUST transaction, and export the certificate.

Import Certificate into SAP Solution Manager:

  1. Now, log on to SAP Solution Manager ABAP and go to transaction STRUST.
  2. Switch to Edit.
  3. Double click on entry 'SSL client SSL Client (Anonymous)'.
  4. Import the previously exported CA certificate, by pressing – within section ‘Certificate' – the icon ‘Import Certificate'.
  5. Press ‘Add to Certificate List'.
  6. Finally ‘Save' this modification. 

Additionally you have to perform certain preparations in the cloud service to enable SAP Solution Manager to connect to the cloud service.   

 
 
 
 

Preparations in SAP Integrated Business Planning

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:

  1. Log as administrator onto the SAP Fiori Launchpad of your S/4 HANA Cloud tenant
  2. Select 'Communication Systems' under Communication Management
  3. Create a new communication system
    • System ID: SAP Solution Manager SID
    • System Name: SAP Solution Manager system name (e.g. SOLMANAGER)
    • Host Name: Enter any value into the mandatory field Host Name. Please note that since the actual value is not used in this communication scenario, it can be chosen freely.
  4. Choose '+' user under 'User for Inbound Communication' to add a user for inbound communication
  5. Choose 'New User'
  6. Enter the following entries in the 'Create Communication User' screen
    • User Name: Enter a user name
    • Description: Enter a short description
    • Password: Enter a password. Remember this password for later
  7. Choose 'Create'
  8. Choose 'User Name and Password' as authentication method
  9. Select OK and save the communications system.
  10. Return to the Fiori Launchpad and choose 'Communication Arrangements' under 'Communication Management'
  11. Create a new scenario of type 'SAP_COM_0068' (Planning - Monitoring Integration)
  12. On the next screen select the communication system you created before and verify that the user name is provided automatically
  13. Save the communications arrangement 
 

Connect Cloud Service to SAP Solution Manager

The Cloud Services configuration is now accessible from the SAP Solution Manager Configuration (SOLMAN_SETUP) → Managed Systems Configuration → Tab 'Cloud Services'.

Create Cloud Service:

  1. Select 'Cloud Service Operations' → Create Cloud Service
  2. Select Service Type: 'SAP Integrated Business Planning' from the drop-down list.
  3. Define Service:
    • Tenant. The SAP Integrated Business Planning tenant name
  4. Root URL:  Root URL for the OData API, the host name of the Root URL must end with “-api” (e.g. https://my401235-api.scmibp.ondemand.com)
    • You can also adjust the extended service ID (The ID used as SID in LMDB) here.
  5. Confirmation: Check your input values and click 'Finish'

The second step is to create the end-point for the cloud service.

Create the End-Point:

  1. Select your SAP IBP cloud service from the list and click 'Configure Cloud Service' 
  2. Configure Endpoints: Click the 'Add' button on the 'HTTP Endpoints' tab.
  3. Enter the following information:
    • Description: A meaningful description
    • User: Communication user created before
    • Password: Password for the user
    • If necessary add proxy information to connect to SAP IBP
 
 

Monitoring Configuration

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. 
 

IBP Log Area

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.

  1. Go to 'General Planner' → 'Application Logs'
  2. Select the log you want to monitor / alert on
  3. The area and sub-area are visible in the top on the log screen
  4. Make sure to use the technical names for area and sub-area!  
 

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.
 

Filter Values in Interface and Connection Monitoring

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:

  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.

 
 

Job Monitoring

Configure Job Monitoring

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:

  1. Select the scenario and click 'Next'
  2. In step Configure Job click the 'New' button.
    • Select as Job Type ‘NW Appl Job' and as Technical System the IBP tenant.
    • Chose to get the job identification option From Managed System.
    • To select the job using the Job Selection Criteria and click ‘Search'.
    • Select the relevant job.
  3. Click Next.
  4. Define the monitoring object:
    • Copy the job name into the Monitoring Object Name field (you can chose a different name though)
    • On the Schedule tab, you can accept the default (e.g. data collection every hour) or adjust to your needs.
    • Confirm to create a monitoring object.
  5. Maintain the Alert Configuration:
    • Select the relevant key figures / metrics
      1. Status and Application Log Status should be selected always
      2. For Duration and Start Delay you need to define thresholds
      3. For End Delay, Out of Time Window and Not Started on Time you need to define on top the expected times.
  6. Optionally do further configurations, e.g. maintain Incidents and Notifications.
  7. Generate and Activate via the Actions button on top of the list of job monitoring objects.