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

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 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 Monitoring Category
Systems: ABAP on-premise system Web Service errors and exceptions Web Service Messages (ABAP), Web Service (Performance)
Systems: ABAP on-premise system Messages in the ABAP proxy framework ABAP: PI Messages
Cloud Services: SAP Cloud Platform Integration Integration flows (iFlow) in SAP CPI SAP Cloud Platform Integration
Systems: PI on-premise system PI messages send via SAP PI

Java: PI Communication Channels, PI Messages

Cloud Services: SAP Fieldglass Exceptions that occur in the SAP Fieldglass SAP Fieldglass Integration, SAP Fieldglass Subscription

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: https://api.sap.com/package/SAPS4HANAintegrationwithSAPFieldglass?section=Overview

More information and business process models can be found here: https://rapid.sap.com/bp/#/BP_S4H_FG

SAP Fieldglass scenarios covered by Focused Run

SAP Fieldglass integration happens via two major areas, 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, invoiced etc.

The following SAP Fieldglass scenarios are currently covered Focused Run:

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

Configure 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 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: 

  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 Focused Run:

  1. Now, log on to Focused Run 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 Focused Run to connect to the cloud service.   

 
 
 
 

Preparations for 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 web service API. This is usually already done during the Fieldglass Implementation. You can use this same partner key for the Focused Run integration.

If you didn't integrate via a web service 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 Focused Run Integration you can either create a ticket with the SAP Fieldglass Service Desk or contact your Account Service Representative.

Please, select...

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.

  1. Call transaction FRUN
  2. Select 'Advanced Integration Monitoring' → Cloud Service Management
  3. Click the 'Add' button
  4. Select the Cloud Service Type.
  5. The other input fields in the section 'Definition' depend on the cloud service type, see the details below
  6. In the section 'Identification' you have to enter the following:
    • Customer Network: the isolated network for which this cloud service should be visible
    • Extended Service ID: the extended SID uniquely identifies the cloud service in LMDB and can be between 3 and 8 characters long
 

Input Values for SAP Fieldglass

  • Customer ID: Your customer ID
  • Fieldglass API Root URL: Your Fieldglass tenant URL (e.g. https://xxx.fgvms.com)
  • Description (optional) 
 

Please, select...

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.

  1. Click on the extended service ID of the cloud service 
  2. Click the 'Add' button on the 'HTTP ENDPOINTS' tab.
  3. Enter the following information:
    • Section 'Global':
      • Description: A meaningful description
    • Section 'Authentication':
      • The information needed here depends on the cloud service type, please refer to the details below
    • Section 'Proxy':
      • If necessary add proxy information to connect to the cloud service
 

Input Values for SAP Fieldglass 

  • Endpoint Type: HTTP
  • Authentication Type: OAUTH
  • 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

Advanced Integration Monitoring Setup

Please, select...

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. 

  1. Open the Advanced Integration Monitoring Application by clicking on the 'Integration & Cloud Monitoring' tile in transaction FRUN
  2. Click on the pinwheel in the upper right corner of the 'Integration & Cloud Monitoring' application
  3. In the configuration panel expand the 'Cloud Services' tray and click on the pen icon in the upper right corner. This will open the 'Configuration for Cloud Services' view.
  4. If your system is not on the list yet, click the 'Add' button to add it. If it is on the list, click on the system ID of 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 Fieldglass different monitoring categories are available.

  • SAP Fieldglass Integration: Collect exceptions from the Integration Audit Trail and real-time
  • SAP Fieldglass Subscription: Collects errors happening during the data exchange (Subscription activity) 
 

Please, select...

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

For both categories, you can either collect all exceptions happening in SAP Fieldglass for your customer ID or you can filter them using the following criteria:

SAP Fieldglass Integration

  • Status (mandatory): Choose from Error, N/A, Not Updated, Upload Data Error
  • Message: Filter on the error message
  • Activity: Upload or Download

SAP Fieldglass Subscription

  • Status (mandatory): Choose from Error, N/A, Not Updated, Upload Data Error
  • Message: Filter on the error message
  • Activity: Upload or Download 
 

Please, select...

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.

  1. Click on the 'New Alert' button in the upper right corner of the alerts table. A new panel will appear below the table for you to enter the alert information
  2. Select the monitoring category
  3. Select the metric name. The available metrics depend on the monitoring category.
  4. Enter a name for the alert
  5. Enter a name for the filter

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:

  1. Check the checkbox next to 'Active'
  2. You can adjust the calculation frequency and the severity
  3. Available threshold types depend on the metric selected. If the threshold type allows it you can adjust the threshold value which triggers the alert.
  4. Select the notification variant and the outbound connector variant from the drop-down list.

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.

Available Metrics

For SAP Fieldglass the following metrics are collected:

SAP Fieldglass Integration

  • SAP Fieldglass Integration exceptions: Indicates that new exceptions were collected during the last data collection interval

SAP Fieldglass Subscription

  • SAP Fieldglass Subscription exceptions: Indicates that new exceptions were collected during the last data collection interval