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.
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:
|Scenario Component||Monitored Content||Interface Channel Type||Since SP|
|1||Systems: ABAP on-premise system||Web Service errors and performance||Web Service: Web Service ABAP (STAD) or Web Service ABAP (SOAP)||7.1 SP05*|
|2||Systems: ABAP on-premise system||Messages in the ABAP proxy framework||
Process Integration: Process Integration (PI – ABAP only)
|3||Cloud Services: SAP Cloud Platform Integration||Exceptions in integration flows (iFlow) in SAP CPI||Cloud: Cloud (SAP Cloud Platform Integration)||7.1 SP12*|
|4||Systems: SAP PI on-premise system||PI Messages and Channels||
|5||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: 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
The following technical prerequisites have to be met in order to monitor this scenario:
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:
|Metric Name||Description||MAI Category||Since SP|
|Single exceptions in SAP Fieldglass||
Single exceptions detected in SAP Fieldglass.
Exceptions are retrieved via the Solution Manager Monitoring API from SAP Fieldglass into central Exception Management in SAP Solution Manager.
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:
Import Certificate into SAP Solution Manager:
Additionally you have to perform certain preparations in the cloud service to enable SAP Solution Manager to connect to the cloud service.
The Cloud Services configuration is now accessible from the SAP Solution Manager Configuration (SOLMAN_SETUP) → Managed Systems Configuration → Tab 'Cloud Services'.
Create Cloud Service:
The second step is to create the end-point for the cloud service.
Create the End-Point:
For SAP Fieldglass you have to set up the exception store for the exceptions occurring 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
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:
Maintain the Interface:
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:
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.