|SAP Fieldglass Messages||Messages||Messages send from and to SAP Fieldglass which are recorded in the Subscription Audit Trail, the Integration Audit Trail and the Event Driven Audit Trail|
The following video demonstrates the setup steps to set up Integration & Exception Monitoring for SAP Fieldglass.
A textual step by step description for all setup steps is provided in the sections below the videos.
To connect to Fieldglass via the API you need two pieces of information to process data: an application key and an active web service (username/password).
Please do not use the Client ID and the Client Secret provided in the API Application Key application. They are not applicable for SAP Cloud ALM end-points.
If you already have an API Application Key for SAP Cloud ALM follow the SAP documentation to retrieve existing API Application Key information.
Remark: In rare cases no user on customer side has access to the API Application Key application. In these cases please open an incident with SAP on component BNS-FG-FAS.
Please note that with SAP Cloud ALM Release 2011 there might be an error if you perform a connection test. This doesn't influence the Interface Monitoring data collection and this error can be ignored.
Error message when clicking 'Ping Connection'
When clicking 'Check Connection' during the end-point creation you will see the following error message
In SAP Cloud ALM you can easily activate the standard monitoring content without any additional setup effort.
You can change which parts of the standard content are activated for each cloud service, activate and deactivate alerts or create own alerts with specific filters.
Adjust Monitoring Categories
Available Alerts for SAP Fieldglass
Available Filter Fields for SAP Fieldglass
The filter fields depend on the monitoring category the alert is created for and additional on the filter category, if there is more than one available.
Name: Message name (see Application Data tab for collected messages)