SAP Fieldglass

SAP Fieldglass is a Software-as-a-Service solution that offers services for external workforce management and services procurement. SAP Fieldglass integrates seamlessly with SAP on-premise solutions via webservices, SAP PI or SAP Cloud Platform Integration.

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 Fieldglass the following integration scenarios are possible:  



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

  1. Integrating ABAP backend with the SAP Fieldglass in a direct connectivity scenario: 1, 5
  2. Integrating ABAP backend with the SAP Fieldglass mediated via SAP CPI: 1, 3, 5
  3. Integrating ABAP backend with the SAP Fieldglass mediated via SAP PI (Web Service based): 1, 2, 4, 5 

Scenario Component Monitored Content Interface Channel Type Since SP
Systems: ABAP on-premise system Web Service errors and performance Web Service: Web Service ABAP (STAD) or Web Service ABAP (SOAP) 7.1 SP05*
Systems: ABAP on-premise system Messages in the ABAP proxy framework

Process Integration: Process Integration (PI – ABAP only)

7.1 SP12
Cloud Services: SAP Cloud Platform Integration  Exceptions in integration flows (iFlow) in SAP CPI  Cloud: Cloud (SAP Cloud Platform Integration) 7.1 SP12*
Systems: SAP PI on-premise system PI Messages and Channels

Process Integration

7.1 SP12
Cloud Services: SAP Fieldglass  Exceptions is SAP Fieldglass  Cloud: Cloud (SAP Fieldglass)  7.2 SP08 

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

For setup information for the single monitoring templates other than Cloud (SAP Fieldglass) please refer to the detail pages for the respective template which you can reach from the Monitoring of Integration Scenarios start page.

When you set up the exception collection and monitoring you first need to know or identify with PI services, Web Services or SAP CPI iFlows are relevant for each scenario. You can find the setup information and also the relevant web service proxies here:



Technical Prerequisites

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

  • To collect single exceptions in the SAP Fieldglass you need at least SAP Solution Manager 7.2 SP08
  • To create alerts via Web Service Monitoring you need at least SAP Solution Manager 7.1 SP14

Available Monitoring Content

Fieldglass integration happens in two ways, batch integration and real-time integration. Batch integration is mainly used for master data like user data, organizational data and so on. Real-time event-driven integration is used for data that needs to be exchanged, based on workflows and in real-time like work orders, invoice etc.

The following SAP Fieldglass scenarios are currently covered in public cloud operations with SAP Solution Manager:

  • Subscription Activity: Errors that happen during the data exchange for the batch integration
  • Integration Audit Trail: Errors that happen after the delivery during the data consumption
  • Real-time Event-driven data: Errors that happen during the data exchange of workflow based information (planned)

Monitoring Template: Cloud (SAP Fieldglass)


Metric NameDescriptionMAI CategorySince SP
Single exceptions in SAP Fieldglass

Single exceptions detected in SAP Fieldglass.

Exceptions are retrieved via the SAP Solution Manager Monitoring API from SAP Fieldglass into central Exception Management in SAP Solution Manager.

Exceptions7.2 SP08 

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.

For a successful SSL handshake, please make sure the following parameter are set in the SAP Solution Manager system:

  • icm/HTTPS/client_sni_enabled = TRUE
  • ssl/client_sni_enabled = TRUE

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 Fieldglass

Maintain Fieldglass Partner

To connect to Fieldglass via any API you need to have a Fieldglass Partner Key. Usually you get this partner key as soon as you integrate with Fieldglass via any WebService API. In most cases this is already done during the Fieldglass Implementation. You can use this same partner key for the SAP Solution Manager integration.

If you didn't integrate via an WebService API with Fieldglass but instead e.g. use file integration, you might not have a Fieldglass partner key yet. To request a partner key for the SAP Solution Manager Integration you can either create a ticket with the SAP Fieldglass Service Desk or contact your Account Service Representative. 


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 Fieldglass' from the drop-down list.
  3. Define Service:
    • Customer ID: Enter your customer ID
  4. Define Root URL: Your Fieldglass tenant URL (e.g.
    • 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 Cloud Platform 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
  • OAuth URL: Extend your  Fieldglass  URL with '/api/oauth2/v2.0/token?grant_type=client_credentials&response_type=token'
  • Application Key: Fieldglass Partner Key
  • User: User for login
  • Password: Password for the user
  • If necessary add proxy information to connect to SAP Fieldglass 

Monitoring Configuration

Step 1: Configure Exception Management

For SAP Fieldglass you have to set up the exception store for the exceptions occurring in SAP Fieldglass.

Exceptions in SAP Fieldglass 

Please note that you need SAP Solution Manager 7.2 SP 08 to set up this exception store.

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 Fieldglass cloud 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 either 'SAP Fieldglass from FGSAPT (INTEGRATION)' or 'SAP Fieldglass from FGSAPT (SUBSCRIPTION)'. Select the correct end-point for SAP Fieldglass if you have more than one.
  3. Select the fields for filtering for your log store.  The following filter fields are available:
    • Activity: Upload or Download (select from the drop down box)
    • Message: Filter on the server message
  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 field 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 'Save'
  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. 

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

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

Please note that you can only set up this channel if you run at least SAP Solution Manager 7.2 SP 08. With this template you can monitor exceptions happening directly in SAP Fieldglass.

Navigate to the step 'Define Scope'. You can create a new scenario for the SAP Fieldglass monitoring or use an existing one. Make sure the on premise system for the SAP Fieldglass scenario and the Cloud Service created for SAP Fieldglass are part of the Interface and Connection Monitoring scenario. If you use the integration via SAP CPI this cloud service should be added as well.

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 Fieldglass)'
    • 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 Fieldglass cloud service please select 'External Service'
  6. Source: Select the on premise system resp. the SAP Fieldglass 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 Fieldglass cloud service please select 'External Service'
  8. Target: Select the on premise system resp. the SAP Fieldglass 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. 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. Enter Metric Parameters:
    • Parameter Set Name: Enter a name for the set of metric parameter
    • Activity (CP): Choose Upload or Download
    • Category (CP): Choose 'SAP Fieldglass Subscription' or 'SAP Fieldglass Integration'
    • Message: Filter in the server message
    • Type (CP): Filter on the transaction type (e.g. SAPBusinessPartnerPush)
  3. Save your interface channel by clicking on the 'Save' button.


If you activate a metric please make sure:

  • To create at least one Parameter Set
  • Enter a value or '*' in at least one of the filter parameter marked with (CP) above

The filter parameters marked with (CP) in the list above are used to create an extended context. This means that you can group your results using these parameters. The data collection will then count the exceptions based in these grouping criteria. 

  • For exceptions in SAP Fieldglass the filter parameter 'Category' is the best candidate for basic grouping

You can use one or several filter parameters to group. Please keep in mind the more filter parameters you use for the grouping the more fine granular your result set gets. E.g. If you use 'Category' and 'Type' you would get one entry for each Category and Type combination in your result set. 

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 SAP Fieldglass 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.