SAP S/4HANA Cloud Public Edition

Integration Scenario

For SAP S/4HANA Cloud Public Edition, the following integration scenarios are possible: 

 

 

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

  1. Integrating SAP backend with SAP S/4HANA Cloud Public Edition mediated via SAP Integration Suite - Cloud Integration: 2, 5, 7
  2. Integrating SAP backend with SAP S/4HANA Cloud Public Edition mediated via SAP Process Integration: 1, 2, 3, 6, 7
  3. Integrating SAP backend with SAP S/4HANA Cloud Public Edition via Cloud Connector: 1, 4, 7, 8 

 

 
Scenario ComponentMonitored ContentInterface Channel Type
Since SP
1 Systems: ABAP on-premise systemIDocsIDoc7.1 SP12 
2 Systems: ABAP on-premise system Web Service errors and performance Web Service: Web Service ABAP (STAD) or Web Service ABAP (SOAP)7.1 SP05* 
3 Systems: ABAP on-premise system Messages in the ABAP proxy framework Process Integration: Process Integration (PI – ABAP only)7.1 SP12 
4 Systems: ABAP on-premise system RFC destination to the SAP S/4HANA Cloud Public Edition (Cloud connector) RFC7.1 SP05* 
5 Cloud Services: SAP Cloud Integration Exceptions in integration flows (iFlow) in SAP Cloud Integration Cloud: Cloud (SAP Cloud Integration)7.1 SP12* 
6 Systems: SAP PI on-premise system PI Messages and ChannelsProcess Integration7.1 SP12 
7 Cloud Services: SAP S/4HANA Cloud Public EditionExceptions in SAP S/4HANA Cloud Public EditionCloud: Cloud (S/4 CE)7.2 SP06 
8 On-premise: Cloud Connector Availability and Performance for Cloud Connector Available monitoring content in System Monitoring 7.2 SP06 

*) Monitoring content was extended with later support packages (see monitoring template page for details) 

 

Technical Prerequisites

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

  • Requires at least SAP Solution Manager 7.2 SP06
  • To monitor exceptions happening in Asset Central Foundation Integration you need at least SAP Solution Manager 7.2 SP09
 
 

Available Monitoring Content

For S/4HANA Cloud Public Edition the following exceptions are currently covered by public cloud operation with SAP Solution Manager:

  • Business-critical exceptions related to Application Interface Framework (AIF)
  • Business-critical exceptions related to Data Replication Framework (DRF)
  • Business-critical exceptions related to Asset Central Foundation Integration (as of SM 7.2 SP09)

The exceptions in S/4HANA Cloud Public Edition are collected using Exception Management in SAP Solution Manager. After they are collected in Exception Management they can be reused for monitoring in Interface & Exception Monitoring .


Monitoring Template: Cloud (S/4 CE) 

Metric Name Description MAI Category Since SP
Single exceptions in S/4 CE (deprecated)Single exceptions detected in Application Log of S/4 CE Exceptions 7.2 SP08 

Single exceptions in S/4HANA Asset Central Foundation Integration

Single exceptions detected in S/4HANA Asset Central Foundation IntegrationExceptions7.2 SP13
Single exceptions in S/4HANA Data Replication FrameworkSingle exceptions detected S/4HANA Data Replication FrameworkExceptions7.2 SP13

Number of Exceptions in Asset Central Foundation Integration

Number of exceptions since the last data collection (Delta)Exceptions7.2 SP13

Number of Exceptions in Asset Central Foundation Integration (Last 24h)

Number of exceptions in the last 24 hoursExceptions7.2 SP13

Number of Exceptions in Data Replication Framework

Number of exceptions since the last data collection (Delta)Exceptions7.2 SP13

Number of Exceptions in Data Replication Framework (Last 24h)

Number of exceptions in the last 24 hoursExceptions7.2 SP13

Connect Cloud Service

Preparations in SAP S/4HANA Cloud Public Edition

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 S/4HANA Cloud Public Edition for enabling the API used by SAP 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 SAP S/4HANA Cloud Public Edition 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
    • 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_0454' (Application 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 S/4HANA Cloud' from the drop-down list.
  3. Define Service:
    • Tenant. The tenant can be any kind of identifier (e.g. the SID of the system or the account ID)
  4. Root URL: Root URL ( e.g. https://myhost-api.s4hana.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 S/4HANA Cloud Public Edition service from the list and click 'Configure Cloud Service' 
    • Select your SAP S/4HANA Cloud Public Edition service from the list and click 'Configure Cloud Service' 
    • Configure Endpoints: Click the 'Add' button on the 'HTTP Endpoints' tab.
    • Enter the following information:
      • Description: A meaningful description
      • Authorization: BASIC
      • User: Connection user created before
      • Password: Password for the user
      • If necessary add proxy information to connect to Cloud Integration

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 Exceptions from SAP S/4HANA Cloud Public Edition

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 S/4HANA Cloud Public Edition service. 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 'SAP S/4HANA Cloud Data Replication' or 'SAP S/4HANA Cloud Asset Central Foundation Integration'.
  3. Select the fields for filtering for your log store. The field OBJECT and SUBOBJECT are always selected by default, for some metrics they are preselected and cannot be changed. The following filter fields are available:
    • OBJECT (mandatory): Choose one of the values from the drop-down box
    • SUBOBJECT (mandatory): Choose one of the values from the drop-down box
    • EXTNUMBER: External ID of the Log entry
    • MSGID: Message Class (e.g. E (Error))
    • MSGNO: Message Number
    • MSGTXT: Message Text
    • PROGRAM: Program triggering the log entry
    • TCODE: Transaction code triggering the log entry
    • USER: The user who triggered the log entry
  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. Once you are done with the Log Store setup click 'Next' to go to the alert configuration. The alert configuration is done in the 'Interface and Connection Monitoring' described in the next section.
  6. 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.

Area Object Sub-Object
Application Interface Framework (AIF)  /AIF/LOG 
  • See documentation below
Data Replication Framework (DRF)  DRF_OUTBOUND 
  • ADHOC
  • CHANGES
  • DIRECTLY
  • INIT
  • MANUAL
  • ONLINE
Asset Central Foundation Integration /SYCLO/ 
  • /SYCLO/INB_TRANS 
/AIF/LOG Sub-Object

For /AIF/LOG there are a lot of different sub-objects that also depend of what interfaces you run in SAP S/4HANA Cloud Public Edition. To find out which sub-object to use, you have to find the interface you want to monitor in the message monitoring of your SAP S/4HANA Cloud Public Edition tenant.

  1. In the Launch pad go to Message Monitoring → Message Dashboard
  2. Select the message you want to monitor in SAP Solution Manager
  3. On the right side you find the columns 'Namespace' and 'Interface Name'
  4. The concatenation of 'Namespace' and 'Interface Name' separated by space designates the sub-object in the AIF log. (e.g. Namespace='/CMDBP' and Interface Name='BP_OUT' → subobject = '/CMDBP BP_OUT' 

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). 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.

To access the Integration Monitoring setup please go to SAP Solution Manager Configuration (SOLMAN_SETUP) → Application Operations → Integration Monitoring → Interface and Connections.

Monitoring Template: Cloud (SAP S/4HANA Cloud Public Edition) 

Navigate to the step 'Define Scope'. You can create a new scenario for the SAP S/4HANA Cloud Public Edition monitoring or use an existing one. Make sure the on premise system for the SAP S/4HANA CE scenario and the Cloud Service created for SAP S/4HANA Cloud Public Edition 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 S/4HANA Cloud Public Edition)'
    • 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 S/4HANA Cloud Public Edition system please select 'External Service'
  6. Source: Select the on premise system resp. the SAP S/4HANA 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 S/4HANA Cloud system please select 'External Service'
  8. Target: Select the on premise system resp. the SAP S/4HANA Cloud Public Edition 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. The interface channel type does not have any configurable parameters on the 'Interfaces' tab

Select Metrics:

  1. On the tab 'Metrics' select the metrics you want to monitor
  2. Provide the following information:
    • Parameter Set Name: You can enter a name for the parameter set to distinguish it if you have more than one
    • Sub-object name: Enter the sub-object of the log
    • User name: The user that triggered the exception
    • Client (expert field): The source client for the exception
    • External ID (expert field): The external ID of the exception
    • Message ID (expert field): Message Class (e.g. E, Error)
    • Message no. (expert field): Message Number
    • Message text (expert field): Message Text
    • Transaction Code (expert field): Transaction code triggering the exceptions
  3. 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!  

 

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.