-
Technical Assistance
Request product support from SAP
-
Non-Technical Assistance
Request non-product support or provide feedback on SAP Support Portal site
Technical Assistance
Request product support from SAP
Non-Technical Assistance
Request non-product support or provide feedback on SAP Support Portal site
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 Integration Suite - Cloud Integration.
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) | 7.1 SP12 |
3 | Cloud Services: SAP Integration Suite - Cloud Integration | Exceptions in integration flows (IFlow) in SAP Integration Suite - Cloud Integration | Cloud: Cloud (SAP Cloud Integration) | 7.1 SP12* |
4 | Systems: SAP PI on-premise system | PI Messages and Channels | Process Integration | 7.1 SP12 |
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 Integration Suite - Cloud Integration 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
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 SAP Solution Manager Monitoring API from SAP Fieldglass into central Exception Management in SAP Solution Manager. | Exceptions | 7.2 SP08 |
Number of Exceptions in Fieldglass | Number of exceptions since the last data collection (Delta) | Exceptions | 7.2 SP13 |
Number of Exceptions in Fieldglass (last 24h) | Number of exceptions in the last 24 hours | Exceptions | 7.2 SP13 |
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.
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 Integration Suite - Cloud Integration this cloud service should be added as well.
Create the Interface Channel:
Maintain the Interface:
Select Metrics:
If you activate a metric please make sure:
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.
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.
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.