SAP Fieldglass Integration Basics
In this blog post, I will share the basics related to SAP Fieldglass integration.
SAP Fieldglass is a Vendor management System to manage external workers. There can be 3 types of workers – Contingent workers (external consultants/independent contractors/ freelancers), statement of work (SOW) workers, and profile workers (security staff/cafeteria staff/cleaning staff).
Profile workers are created in SAP fieldglass only for tracking and compliance purposes.
A typical high level workflow of procuring contingent worker is like below:
- Buyer/Hiring Manager creates a Job posting in Fieldglass using existing job template
- Supplier submits list of Job seekers matching the requirement
- Buyer hires a job seeker after reviewing the list and creates work order
- Supplier accepts the WO
- Buyer activates the WO
- Worker registers in the Fieldglass system
- Worker submits time and expenses
- Buyer approves the timesheet
- If the auto-invoicing option is enabled in Fieldglass (recommended), approved time and expense sheets automatically generate an invoice and it is sent to buyer’s AP (Accounts Payable) system for further processing and payment
To fulfil the need for integrating with other systems, Fieldglass provides connectors of type – Download and Upload.
Download Connectors: Data is downloaded from SAP Fieldglass and then uploaded into client systems
Upload Connectors: Upload data from client system to SAP Fieldglass
The list of connectors API are available in SAP API Business Hub
Download Site Codes from Fieldglass
The Configuration Manager role is for a technical user to access integration tools on self-service dashboard in SAP Fieldglass Configuration Manager.
It is a series of preconfigured questions to help us with the selection of a connector that suits our needs.
If we already know the connector we need, we can select the ‘Connectors’ Tile and select the required connector from the list of available connectors.
It is used to enable and configure the connector.
Similarly, security can be defined based on the requirement.
If required, custom fields can be defined. The last step is to define the ‘Transfer Method’.
If we select ‘Subscription’, we have to select the endpoint from the list of available endpoints and select available subscription options.
For ‘SOAP Web Service’, a license key against username (technical user) is required. License Key is used as a password for web service requests.
End Points Tile:
It is used to create a new endpoint or edit an existing endpoint for any of the below categories.
Integration Subscriptions Tile:
Define schedule for run
API Application Keys Tile:
Used to create API application keys. The system auto-generates the application key, Client ID, and Client Secret. Also we can set up Web Services in this section.
Monitor Activity Tile:
It shows the audit trail for upload/download activity details.
The above gives a basic overview of available integration tiles.
Thank you for reading this blog post. Please feel free to share your feedback or thoughts or ask questions in the Q&A tag below.