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, provide a valid admin page (see the wiki for details)
Enter the preview mode to see the content - a reminder that the admin page should be activated separately.
For SAP Fieldglass the following integration scenarios are possible:
The different scenarios contain the following exceptions and point-to-point connections:
- Integrating ABAP backend with the SAP Fieldglass in a direct connectivity scenario: 1, 5
- Integrating ABAP backend with the SAP Fieldglass mediated via SAP Integration Suite - Cloud Integration: 1, 3, 5
- Integrating ABAP backend with the SAP Fieldglass mediated via SAP Process Integration (Web Service based): 1, 2, 4, 5
| Scenario Component | Monitored Content | Monitoring Category | |
|---|---|---|---|
| 1 | Systems: ABAP on-premise system | Web Service errors and exceptions | Web Service Messages (ABAP), Web Service (Performance) |
| 2 | Systems: ABAP on-premise system | Messages in the ABAP proxy framework | ABAP: PI Messages |
| 3 | Cloud Services: SAP Integration Suite - Cloud Integration | Integration flows (IFlow) in SAP Integration Suite - Cloud Integration | SAP Integration Suite |
| 4 | Systems: PI on-premise system | PI messages send via SAP PI | Java: PI Communication Channels, PI Messages |
| 5 | 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
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, provide a valid admin page (see the wiki for details)
Enter the preview mode to see the content - a reminder that the admin page should be activated separately.
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, provide a valid admin page (see the wiki for details)
Enter the preview mode to see the content - a reminder that the admin page should be activated separately.
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, provide a valid admin page (see the wiki for details)
Enter the preview mode to see the content - a reminder that the admin page should be activated separately.
Input Values for SAP Fieldglass
- 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, provide a valid admin page (see the wiki for details)
Enter the preview mode to see the content - a reminder that the admin page should be activated separately.
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, provide a valid admin page (see the wiki for details)
Enter the preview mode to see the content - a reminder that the admin page should be activated separately.
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, Upload Data Error
- Message: Filter on the error message
- Activity: Upload or Download
SAP Fieldglass Subscription
- Status (mandatory): Choose from Error, Upload Data Error
- Message: Filter on the error message
- Activity: Upload or Download
Please, provide a valid admin page (see the wiki for details)
Enter the preview mode to see the content - a reminder that the admin page should be activated separately.
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