Troubleshooting Position Management

When implementing the position management integration between SAP Fieldglass and SAP SuccessFactors Employee Central, some frequent errors can occur which you can resolve with some simple troubleshooting.

Employee Central API not Responding for Position ID XXXXXXXXX

This is the most common error that occurs post-implementation and configuration of the integration solution. Normally, this error is associated to something tied to the end point credentials, username, and password elements that are loaded in SAP Fieldglass for the SAP SuccessFactors Employee Central tenant.

First, ensure that all of the credentials are operational and that the API URL provided in the SAP Fieldglass system can be reached via an external system, like POSTMAN, to ensure that the configuration is correct and operational outside the SAP Fieldglass system.

Confirm that the user elements between SAP SuccessFactors Employee Central and SAP Fieldglass are in synchronization. If a user is logged into the SAP SuccessFactors Employee Central tenant with a username that isn't present in the SAP Fieldglass buyer, or possibly a username tied to a different SAP Fieldglass buyer, this error occurs as the SSO into SAP Fieldglass may not be operational, or the systems may not communicate properly against the previously mentioned loaded API values.

SAP Fieldglass API not Responding

This error occurs when there's a required element that's not configured properly in one or more of the following:
  • SAP SuccessFactors Employee Central Position Business Rules

  • SAP Fieldglass configure column transform of the Job Posting Upload (Requisition Upload EC)

  • SAP Fieldglass master data

In order for the SAP Fieldglass system to properly map the SAP SuccessFactors Employee Central position into a job posting object in SAP Fieldglass, it's imperative that the naming convention of the fields coming from the position API match to the names managed on the column transform template for the job posting upload (level, title, employeeclass, and so forth).

In addition, SAP Fieldglass requires key values like the cost center to determine the proper template name and currency are associated to the position. If the value in the API results doesn't match the master data in SAP Fieldglass, this error can occur. Clients need to ensure that the API data provided from Employee Central is available in SAP Fieldglass for mapping and that the naming conventions align.