In continuing with the previous blog on implementing Total Workforce Management where we discussed the key identifiers in each of the involved systems (SAP Fieldglass, SAP SuccessFactors and SAP S/4 HANA HCM), let us now examine the key prerequisites to be enabled in SAP SuccessFactors solution followed by user provisioning and a comparison of standard vs. customer integration.
SAP SuccessFactors Configuration
1. SAP SuccessFactors mandatory attributes not captured in SAP Fieldglass are changed to “optional” in the base data model. SAP SuccessFactors API imports use the base data model to determine mandatory fields.
2. PositionID is set as “optional” in the base data model as it is not a mandatory attribute for SAP Fieldglass workers like Services Procurement or Profile workers
3. “Concurrent Employment for Contingent Worker” in SAP SuccessFactors is enabled or the customer does not have the requirement to have an SAP Fieldglass worker on multiple active work orders.
4. The standard mapping of SAP Fieldglass Identifiers is handled which is - SAP Fieldglass Work Order ID -> User ID and SAP Fieldglass Security ID or Master Worker ID - > Person ID External) in integrations downstream from SuccessFactors.
5. Job Information to Position Sync is enabled.
User Provisioning
SAP's recommended approach is to use Identity Services (IAS/IPS)-based integration for user provisioning. It’s an easy, centrally administered user management and identity provisioning system. Customers will benefit from the central user management thus maintaining users in multiple systems across a heterogeneous landscape will be obsolete. I invite you to look at the IDP (Section 6.2.1 on page 19) for a detailed approach on carrying out user provisioning.
Standard Integration vs. Custom Integration
The standard integration supports general use cases but does not offer any flexibility for custom mapping or specific scenario management with customers. Hence, a solution to this is to have a custom integration instead which is to copy the SAP Standard Package to a custom-specific one. It is important to understand various business scenarios and use cases that a company may come across, to ensure their varied needs are covered with a custom integration for holistic solution coverage. Hence, there is a prior need to identity these use cases.
Section 5.5 and Section 6.5 of the IDP provides detailed guidance on how one has the option to create logical checks on the data input from Fieldglass and create unique routes of updating data, adding custom fields and logic on what entities should be updated to ensure correct and stable data uploads.
Do let us know some of the tips and tricks you have used in your implementation of SAP Fieldglass integration to Employee Central. It will be great to hear from you!
Additional resources:
Blog - Part 1
Implementation Design Principle
Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee Central
Integrating Employee Central with SAP Fieldglass
Integrating SAP SuccessFactors Employee Central with SAP Master Data Integration
Replicating Master Data Using SAP Master Data Integration Service
Administration Fundamentals
Master Data Integration
