PUBLIC

SAP Fieldglass
2024-02-21

Implementation Guide for SAP Fieldglass

Integration with SAP SuccessFactors Employee
© 2024 SAP SE or an SAP affiliate company. All rights reserved.

Central
Implementation Guide

THE BEST RUN

Content

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

2 About This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 Integration Credentials and Single Sign-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3.1 Create an Integration End Point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.2 Configure X.509 Certificate Authentication for Worker Data Integration. . . . . . . . . . . . . . . . . . . . . . . . . . 7

4 Master Data Integration and Identity Services Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4.1 Location Upload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

5 Position Management Integration and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

5.1 Custom Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
5.2 Job Posting Template Upload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
5.3 Job Posting Upload. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.4 Troubleshooting Position Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
5.5 Optional: Status Update Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

6 Worker Data Integration and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

6.1 Enable Features in SAP Fieldglass. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
6.2 Enable and Configure the Active Worker Delta Single Line Download. . . . . . . . . . . . . . . . . . . . . . . . . . . 38
SAP Fieldglass Provider Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Configure Standard and Custom Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
6.3 Optional: Download Worker After Acceptance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.4 Error Handling of Contingent Worker Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

7 Error Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

8 Restrictions Using SAP Fieldglass and SAP SuccessFactors Employee Central. . . . . . . . . . . . . . . .45

9 Additional Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
2 PUBLIC Content
1 Introduction

An overview of integrating SAP Fieldglass with SAP SuccessFactors Employee Central.

The SAP Fieldglass vendor management system (VMS) contains records for different types of workers, all of which
are supported within SAP SuccessFactors Employee Central, a cloud HR core system that manages total workforce
(employee and external workers).

Employee Central is a master system for employees and organizational data. SAP Fieldglass is a master system
for external workers. This integration allows you to view contingent worker records taken from SAP Fieldglass in
Employee Central.

There are three integration scenarios:

1. Replicating master data from Employee Central to SAP Fieldglass.

2. Creating the SAP Fieldglass Job Requisition from Employee Central Position Management.
• An optional configuration is available within SAP Fieldglass to send real-time Job Posting status updates to
the SAP SuccessFactors Employee Central position.
3. Replicating worker data from SAP Fieldglass to Employee Central.

The following diagram illustrates the integration scenarios.

• Replication of master data is prerequisite for scenarios 2 and 3.

• Scenarios 2 and 3 can be used separately or together as an end-to-end scenario, as indicated.

When an upload connector is enabled for the first time, the default upload record limit for API and API-A versions is
10,000 and is editable to a maximum limit of 1,000,000 for API and 10,000,00 for API-A. The default upload record
limit for Bulk Full and Bulk Delta versions is 10,000,000 and is noneditable (technically, there's no record limit for
Bulk uploads).

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Introduction PUBLIC 3
2 About This Guide

This guide is for SAP Fieldglass administrators and configuration managers who need to perform the technical
implementation and configuration of the SAP Fieldglass and SAP SuccessFactors Employee Central integration.

Some of the configuration tasks described in this guide require the assistance of an SAP Fieldglass representative.
In addition, tasks that require the assistance of a configuration manager include links to specific instructions that
are described in the SAP Fieldglass Configuration Manager Guide. Specific requirements are noted where they
apply.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
4 PUBLIC About This Guide
3 Integration Credentials and Single Sign-On

For initial configuration setup, exchange the following connectivity and Single Sign-On (SSO) configuration details
with the appropriate technical resources.

SAP Fieldglass Credentials

Property Value

Test Domain https://[environment].fgvms.com

Username

Password

Employee Central Single Sign-On Credentials

Property Value

Assertion Consumer Service https://[environment].fgvms.com/SF2FG

You can optionally specify the Buyer Code and use script
ssoid2user.id_comp_sf2fg, as follows:

• ACS URL is https://[environment].fgvms.com/SF2FG?

BuyerCode=[BuyerCode]
• Enable script ssoid2user.id_comp_sf2fg for the
buyer.
• If this is done, then usernames must also have the buyer
code appended.

Logout URL https://[environment].fgvms.com/login.jsp&ssoLog

Audience URL https://[environment].fgvms.com

SP Mapping Key fg

SAP Fieldglass Web Service Credentials

The SAP Fieldglass web service is for SAP Cloud Identity worker integration, if needed.
Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Integration Credentials and Single Sign-On PUBLIC 5
Property Value

End Point https://[environment].fgvms.com/ws2/services/connectorn

Username

Password/ Key [company_code]_licenscekey

Employee Central Access Credentials

Property Description

API Odata URL Used for API connectivity of job postings.

API Company Code Used for API connectivity of job postings.

API Username Used for API connectivity of job postings.

API Password Used for API connectivity of job postings.

Integration Center Host Used for subscription file imports of master data.

Integration Center Username Used for subscription file imports of master data.

Integration Center Password Used for subscription file imports of master data.

3.1 Create an Integration End Point

Create an integration end point based on the integrations credentials.

Based on the API credentials described in , the SAP Fieldglass configuration manager needs to create an end point
to define the credentials and pathway for the SAP Fieldglass client to call and connect to the SAP SuccessFactors
Employee Central OData API.

After a position is triggered for creation in SAP SuccessFactors Employee Central, the SAP Fieldglass requisition
process references this data to call back the SAP SuccessFactors Employee Central API, connect, and retrieve the
necessary position information to map into their job posting upload object.

 Note

Create the end point before configuring the job posting template and job posting integrations in SAP Fieldglass
as described in Position Management Integration and Configuration.

 Note

When creating the end point, you need to add an additional field for api_version and specify the value as
described in the table.

For information on creating an end point and adding an additional field in

Configuration Manager, see https://help.sap.com/viewer/73c0a1be6aaa46ef9b66b1c3f28a77f4/cloud/en-US/
6e39fc5329064264861caca66c3bcda0.html.
Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
6 PUBLIC Integration Credentials and Single Sign-On
 Property Value

ID [Buyer Code]_EC_INTEGRATION

Category odata

activity Active

URL* [API odata URL]

Username* [API Username]@[ API Company Code]

Password* password

api_version (create new additional field) v2

expand_key 2

select_key 1

 Note

Properties marked with * (asterisk) must be provided by the SAP SuccessFactors Employee Central client.
Define all other fields as described in the table.

 Note

All newly implemented clients are required to have the value v2 in the api_version field to properly connect
to the preferred position API. The value v2 reflects the updated API call to go against the standard position API
within SAP SuccessFactors Employee Central. The value v1 or no entry in the end point configuration directs
the API call to the legacy (business rules-based) API within SAP SuccessFactors Employee Central. Only legacy
clients and clients with the configured business rules setup in SAP SuccessFactors can use either v1 or omit the
entry from the end point.

3.2 Configure X.509 Certificate Authentication for Worker

Data Integration
Configure SAP Cloud Integration and SAP Fieldglass to use X.509 certificate authentication for position and worker
integration.

Context

To align with SAP security best practices and standards, clients are required to generate and maintain a client
certificate in SAP Cloud Integration for configuration in their associated iFlow that calls and connects to the SAP
Fieldglass application to retrieve an API Worker Download connector and its associated data.

 Note

For detailed information on configuring the following X.509 fields, see Create, Generate, and Activate Asset in
the SAP Fieldglass Configuration Manager guide.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Integration Credentials and Single Sign-On PUBLIC 7
Procedure

1. Obtain the public certificate to be used for authentication.

2. Log into SAP Fieldglass with the Configuration Manager role and then choose the Manage Crypto Assets
tile. For detailed information on managing crypto assets in Configuration Manager, see the SAP Fieldglass
Configuration Manager guide.

The Encryption Keys and Certificates page opens.

3. Choose New.

The Create Asset page opens.

4. In the Category list, choose X509.

5. Open the certificate in Notepad, select, and copy all text (including the Begin Certificate and End
Certificate lines), and then paste it into the Public Certificate box.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
8 PUBLIC Integration Credentials and Single Sign-On
 When you click outside of the box the Begin Certificate and End Certificate lines are no longer visible.
6. In the Notification Email ID field, enter the email contact to notify when the certificate is about to expire.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Integration Credentials and Single Sign-On PUBLIC 9
7. Choose the Auto-Activate option to make the certificate/asset immediately active and effective in the client’s
vault within the SAP Fieldglass application.

8. Under Extended Key Usage link an object to the certificate. There are a few options for this, however in this
case we're linking a user.
9. After all the relevant fields are populated, choose Create to save the certificate in SAP Fieldglass.

The certificate details display.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
10 PUBLIC Integration Credentials and Single Sign-On
Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Integration Credentials and Single Sign-On PUBLIC 11
4 Master Data Integration and Identity
Services Configuration

The integration of SAP Fieldglass master data with SAP SuccessFactors Employee Central data requires a
configuration manager to enable and configure the integration upload connectors.

Use the Connector Setup Wizard in Configuration Manager to enable and configure the following connectors in SAP
Fieldglass:

• Location Upload

Where SAP Master Data Integration (MDI) is used, enable and configure the following connectors for use with MDI:

• Job Code Upload

• Business Unit Upload
• Cost Center Upload (see Note)
• Legal Entity Upload (see Note)

 Note

Financial master data can only come from SAP S/4HANA for MDI-based Cost Center and Legal Entity.

For more information on enabling connectors for MDI, see Replicating Master Data Using SAP Master Data
Integration Service on the SAP Help Portal.

User Provisioning

For user provisioning, SAP's recommended approach is to use Identity Services(IAS/IPS)-based integration.

An easy, centrally administered user management and identity provisioning are key for an end-to-end integration.
Customers will profit from the simple configuration and the central user management. Maintaining users in
multiple systems across a heterogeneous landscape will be obsolete.

The user lifecycle management will be managed centrally using the central Identity Provisioning service (IPS) and
Identity Authentication Service ensures a consistent way of enabling Single Sign-On (SSO) throughout all SAP
products.

For more information on enabling and replicating users, see Configure Identity Authentication Service and Identity
Provisioning Service .

4.1 Location Upload

Create a variant of the Location Upload for Employee Central transmissions.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
12 PUBLIC Master Data Integration and Identity Services Configuration
 Official Connector Name Location Upload Comments/ Notes

Real Time vs. Batch Batch

Transfer Method SFTP

File Type CSV

Frequency Daily

Field Layout/ Data Mapping See Detail section below.

Bulk vs. API (Processing Framework – BULK Full

Upload only)

Record Inclusion Logic (Upload) All active locations. Effective dating not handled by SAP
Fieldglass. All active records are received.

Record Inclusion Logic (Download) N/A

Variant Name Upload Locations EC

Variant Code EC

Header
Header information defaults within the connector settings.

File Header required in the “Edit Batch Job” is unchecked.

Detail
Use Upload Column Transform to map defaults for the following fields and to map the SAP SuccessFactors fields
to the SAP Fieldglass fields as per the following table.

• Default Corporate Calendar = Default Corporate Calendar

• Currency = ALL

SAP Fieldglass SAP SuccessFac-

Field Header tors Mapping (En- Field Length/ Data Description/ Use/
Name tity) Type Required Value/ Format Field Rules

Code externalcode| Yes Location Code Code for the site.

The code must be
(FOLocation) unique for each
site.

Name name Yes, for Adds only Location Name Name for the site.

(FOLocation)

Description description No Optional text de-

scription of the site.
(FOLocation)

Address 1 addressAddress1 No Line 1 of the site’s

address.
(FOLocation)

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Master Data Integration and Identity Services Configuration PUBLIC 13
SAP Fieldglass SAP SuccessFac-
Field Header tors Mapping (En- Field Length/ Data Description/ Use/
Name tity) Type Required Value/ Format Field Rules

Address 2 addressAddress2 + No Line 2 of the site’s

address.
addressAddress3
 Note
(FOLocation)
Contact your
SAP Fieldglass
representative
for assistance
with this script
item.

City addressCity No City where the site

is located.
(FOLocation)

State/ Province addressState No Required in US. State/Province

where the site is lo-
(FOLocation) cated.

Country addressCountry Yes, for Adds only Valid values are: Country Code for
the country where
(FOLocation) USA the site is located.

CAN

Zip/ Postal Code addressZipCode Yes Required in US. Zip Code/Postal

Code of the site.
(FOLocation)

Hours per Week standardHours No Standard hours

worked per week at
(FOLocation) the Site.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
14 PUBLIC Master Data Integration and Identity Services Configuration
5 Position Management Integration and
Configuration

The following data flow diagram depicts the authentication methods used during a position request to SAP
Fieldglass. After the authorization is complete, SAP Fieldglass sends API requests to SAP SuccessFactors in order
to land directly on an SAP Fieldglass Job Posting Create page. Users can link back to view the requisition once it's
created.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Position Management Integration and Configuration PUBLIC 15
 Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
16 PUBLIC Position Management Integration and Configuration
5.1 Custom Fields

To capture details passed from SAP SuccessFactors Employee Central to SAP Fieldglass as part of the creation of a
Job Posting, the configuration manager can add the custom fields used within SAP Fieldglass.

Position ID

Position ID is mandatory. All other fields described below are optional or partly optional based on other
configuration choices.

Module Job Posting

Name Position ID

Data Type Text

Mandatory Value Yes

Linked To Work Order/ Worker

Job Code

Job Code is optional. This custom field is only required where the job code data created and held in SAP
SuccessFactors Employee Central isn't being prepopulated into SAP Fieldglass via SAP Master Data Integration
(MDI). It's used within SAP Fieldglass to store the job code captured against the position with SAP SuccessFactors
Employee Central.

Module Job Posting

Name Job Code

Data Type Text

Mandatory Value No

Linked To (Optional) Work Order/ Worker

Employee Class

Employee Class is optional.

Module Name Job Posting

Name Employee Class

Data Type Text

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Position Management Integration and Configuration PUBLIC 17
Mandatory Value No

Linked To (Optional) Work Order/ Worker

Job Level

Job Level is optional.

Module Job Posting

Name Job Level

Data Type Text

Mandatory Value No

Linked To (Optional) Work Order/ Worker

Pay Grade

Pay Grade is optional.

Module Job Posting

Name Pay Grade

Data Type Text

Mandatory Value No

Linked To (Optional) Work Order/ Worker

5.2 Job Posting Template Upload

Create a variant of the Job Posting Template Upload for SAP SuccessFactors Employee Central transmissions.

With a position integration, where the position in SAP SuccessFactors is uploaded via the native Job Posting
Template connector into SAP Fieldglass, the data are in synch at the time of creation. Master data mismatches will
make the integration fail, and corrections are required to continue the process.

Transmissions are loaded on an ad-hoc basis to preload templates. Extracts are in the Integration Center of SAP
SuccessFactors.

 Note

The detail section of the connector variant contains a field that requires a custom script. For assistance with
the custom script, contact your SAP Fieldglass representative.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
18 PUBLIC Position Management Integration and Configuration
For information on creating a variant, see https://help.sap.com/viewer/73c0a1be6aaa46ef9b66b1c3f28a77f4/
cloud/en-US/8a2506aa422f4f9198d1678a552f2751.html?q=variant.

For information on creating custom fields, see https://help.sap.com/docs/SAP_FIELDGLASS_INTEGRATION/

73c0a1be6aaa46ef9b66b1c3f28a77f4/bca21ff5494d4e6eb15ccbf1ada48390.html.

For information on configuring column transforms for

connector uploads, see https://help.sap.com/viewer/73c0a1be6aaa46ef9b66b1c3f28a77f4/cloud/en-US/
5cc0fc50a7b646de869906756ea12a76.html?q=%22transform%20column%22.

Connector Description

Official Connector Name Job Posting Template Comments/ Notes

Real Time vs. Batch Batch

Transfer Method Manual

File Type CSV

Frequency As needed.

Field Layout/ Data Mapping See Detail section below.

Bulk vs. API (Processing Framework – API

Upload only)

Record Inclusion Logic (Upload) Active Positions since Last Run

Variant Integration Name Job Posting Template EC

Variant Code EC

Header

Header information defaults within the connector settings.

File header required in the ‘Edit Batch Job’ is unchecked.

Detail

Use Upload Column Transform to map defaults for the following fields and to map the SAP SuccessFactors fields
to the SAP Fieldglass fields as per the following table.

• Number of Positions = 1
• Enable Simplified Workflow = No
• Associate All Business Units = Yes
• Labor Type = Defined by Customer
• Service Type = Temp
• Timesheet Type = Hourly
• Timesheet Frequency = Weekly
• Distribution Rule = Automatically distributed to Suppliers specified in the template after final approval
• Distribution List = ALL

The following fields are populated from SAP SuccessFactors and mapped using Upload Column Transform.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Position Management Integration and Configuration PUBLIC 19
SAP Fieldglass SAP SuccessFac-
Field Header tors Mapping (En- Field Length/Data Description/ Use/
Name tity) Type Required Value/ Format Field Rules

Title Title + ‘|’ + Job Text Yes Title of the position Title
Code Level
requested for this
 Note
job posting.
Contact your
SAP Fieldglass rec-
SAP Fieldglass
ommends that the
representative
value of the Title
for assistance
field is the same
with this script
as the template
item.
name to allow for
easy tracking and
reporting purposes
based throughout
SAP Fieldglass.

Job Code jobcode Text Yes Job Code associ- Job Code
ated to all job post-
(Position)
ing templates and
used in the filter-
ing of templates
for positions that
don't have an ex-
act match to a job
posting template.

[c] Job Code jobcode Text No [c] Job Code

(Position)  Note
Only required
where the na-
tive Job Code
isn't being
used.

[c] Job Level jobLevel Text No [c] Job Level

(Position)

[c] Pay Grade payGrade Text No [c] Pay Grade

(Position)

[c] Employee Class employeeClass Text No [c] Employee Class

(Position)

[c] Position ID Code Text Yes [c] Position ID

(Position)

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
20 PUBLIC Position Management Integration and Configuration
5.3 Job Posting Upload

Create a variant of the Job Posting Upload for Employee Central transmissions, which is used to map in the Position
API data received to the job posting template.

 Note

The detail section of the connector variant contains several fields that require custom scripts. For assistance
with the custom scripts, contact your SAP Fieldglass representative.

For information on creating a variant, see https://help.sap.com/viewer/73c0a1be6aaa46ef9b66b1c3f28a77f4/

cloud/en-US/8a2506aa422f4f9198d1678a552f2751.html?q=variant.

For information on working with column

transforms, see https://help.sap.com/viewer/73c0a1be6aaa46ef9b66b1c3f28a77f4/cloud/en-US/
5cc0fc50a7b646de869906756ea12a76.html?q=%22transform%20column%22.

To view the SAP SuccessFactors Employee Central Position Management API for employee position management,
go to https://api.sap.com/api/ECPositionManagement/schema .

Connector Description

Official Connector Name Job Posting Comments/ Notes

Real Time vs. Batch Real Time

Transfer Method API

File Type

Frequency Real Time

Field Layout/ Data Mapping See Detail section below.

Bulk vs. API (Processing Framework – API

Upload only)

Record Inclusion Logic (Upload) Per Position ID

Variant Integration Connector Name Job Posting EC Required variant connector name.

Variant Code EC

Header
Header information defaults within the connector settings.

Detail

• Add an entry for "General Ledger Account Name" if GLAs are enabled for the buyer.
• Owner transform could append the buyer code if usernames append the buyer code.

Use Upload Column Transform to map defaults for the following fields and to map the SAP SuccessFactors fields
to the SAP Fieldglass fields as per the following table.

• Number of Positions = 1
• Coordinator Username = [buyer]@FG_HELP
Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Position Management Integration and Configuration PUBLIC 21
• Creator Username = [buyer]@FG_HELP
• Job Seeker Rate can be increased = Yes
• Hours per Week = 40
• Hours per Day = 8

The logic for matching criteria is defined in the Template Match Criteria column in the following table. This is
comprised of the Job Code Name/ Job Code Level/ and Language.

SAP Fieldglass SAP SuccessFac-

Field Header tors Mapping (En- Description/ Use/ Template Match
Name tity) Required Value/ Format Field Rules Criteria

External Job Post- Code Yes 244003 Any unique identi-

ing Id fier of this job post-
(Position) ing (as it pertains
to this file). When
this file is uploaded,
SAP Fieldglass au-
tomatically assigns
each job posting
with the next ap-
plication-generated
identifier.

Template Name external- Yes Examples: Name of the job Language for tem-
posting template plate name is de-
Name_[language]
Administrative As- upon which this job rived off of the
(for example, exter- sistant | EntryAs- posting is based. job posting owner
nalName_en_US) sistant Administra- Job posting tem- user profile (owner
plate names are de- username). Direct
tif | Niveau
+'|'+ fined in the SAP Match lands on
Fieldglass applica- page 2 (augment)
jobLevel tion. of the job posting
(Position) submission page.
No match lands on
page to create a job
posting.

 Note
Contact your
SAP Fieldglass
representative
for assistance
with this script
item.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
22 PUBLIC Position Management Integration and Configuration
 SAP Fieldglass SAP SuccessFac-
Field Header tors Mapping (En- Description/ Use/ Template Match
Name tity) Required Value/ Format Field Rules Criteria

Title Same as SAP Field- Yes The title of the po-

glass template.
sition requested for
this job posting.

SAP Fieldglass rec-

ommends that the
value of the Title
field is the same as
the template name.
This allows for
easy tracking and
reporting purposes
based throughout
SAP Fieldglass.

Job Description description No Description of the

position requested
(Position)
on this job posting.

If this field is left

null, the job de-
scription from the
job posting tem-
plate becomes the
default description
for this job posting.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Position Management Integration and Configuration PUBLIC 23
SAP Fieldglass SAP SuccessFac-
Field Header tors Mapping (En- Description/ Use/ Template Match
Name tity) Required Value/ Format Field Rules Criteria

Business Unit Code businessUnit Yes ACE_CORP The business unit

in which this job
(Position)
posting belongs.
Business unit co-
des must be de-
fined in the SAP
Fieldglass applica-
tion, and the job
posting owner must
have access to this
business unit code.

 Note
When buyer is
using “Users
have access to
all Business
Unit/Cost Cen-
ters and Sites”
plug-in, the BU
is automati-
cally associ-
ated to JP
owner and all
those users
who can act as
coordinator on
upload.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
24 PUBLIC Position Management Integration and Configuration
 SAP Fieldglass SAP SuccessFac-
Field Header tors Mapping (En- Description/ Use/ Template Match
Name tity) Required Value/ Format Field Rules Criteria

Site Code location Yes AU_SYD The code of the

site in which this
(Position)
job posting is lo-
cated. The site
code aids suppliers
in knowing where
the work occurs,
so that appropriate
candidates within
that locale are sub-
mitted. This field
also assists suppli-
ers in determining
which supplier ac-
count manager ful-
fills the job posting.

Job posting owner

must have access
to this site in order
to create the job
posting.

Site names must

be defined in the
SAP Fieldglass ap-
plication.

 Note
When buyer is
using “Users
have access to
all Business
Unit/Cost Cen-
ters and Sites”
plug-in, the site
is automati-
cally associ-
ated to JP
owner and all
those users
who can act as
coordinator on
upload.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Position Management Integration and Configuration PUBLIC 25
SAP Fieldglass SAP SuccessFac-
Field Header tors Mapping (En- Description/ Use/ Template Match
Name tity) Required Value/ Format Field Rules Criteria

Location Code location Yes AU_SYD The code of the lo-

cation in which this
(Position)
job posting is lo-
cated. The location
code aids suppliers
in knowing where
the work occurs,
so that appropriate
candidates within
that locale are sub-
mitted.

Location name
must be defined in
the SAP Fieldglass
application.

Start Date effectiveStartDate Yes 2013-04-11T00:00 Date on which the

:00 contract begins.  Note
(Position)
Contact your
SAP Fieldglass
representative
for assistance
with this script
item.

End Date effectiveEndDate Yes 2013-05-11T00:00 Date on which the

:00 contract ends.  Note
(Position)
Contact your
SAP Fieldglass
representative
for assistance
with this script
item.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
26 PUBLIC Position Management Integration and Configuration
 SAP Fieldglass SAP SuccessFac-
Field Header tors Mapping (En- Description/ Use/ Template Match
Name tity) Required Value/ Format Field Rules Criteria

Owner Username Owner Yes SAP Fieldglass Match on SAP

username of the Fieldglass user.
(Position) person who owns Owners default
this specific job language drives
posting. The owner matching logic
receives notifica- against the job
tions and work posting template. A
items about the job separate template
posting. This user- is set up in SAP
name must be de- Fieldglass for each
fined in the SAP language.
Fieldglass applica-
tion.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Position Management Integration and Configuration PUBLIC 27
SAP Fieldglass SAP SuccessFac-
Field Header tors Mapping (En- Description/ Use/ Template Match
Name tity) Required Value/ Format Field Rules Criteria

Cost Center Code costCenter Yes 35106 Code of the cost

center this job
(Position)
posting is assigned
to. The cost center
code typically iden-
tifies to what cost
center (or total esti-
mated budget) this
job posting applies
and is used for ac-
counting purposes.

Cost center codes

must be defined in
the SAP Fieldglass
application. The job
posting owner must
have access to this
cost center in order
to create the job
posting.

The cost center

code isn't directly
related to the busi-
ness unit or the
site.

 Note
When buyer is
using “Users
have access to
all Business
Unit/Cost Cen-
ters and Sites”
plug-in, the CC
gets automati-
cally associ-
ated to JP
owner and all
those users
who can act as
coordinator, on
upload.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
28 PUBLIC Position Management Integration and Configuration
 SAP Fieldglass SAP SuccessFac-
Field Header tors Mapping (En- Description/ Use/ Template Match
Name tity) Required Value/ Format Field Rules Criteria

Hours per Week standardHours Yes Standard number

of hours per week
(Position)
for this position on
this job posting.

Yes, if some Hours

per Week value isn't
set on site or in
buyer’s company
configuration.

Comments comment No ACC-MGR

(Position)

Job Code jobcode Yes ACC-MGR

(Position)

[c] Job Code jobcode No Manager

 Note
(Position)
Only required
where the na-
tive Job Code
isn't being
used.

[c] Job Level jobLevel No Salary Grade 13

(Position)

[c] Pay Grade payGrade No Employee

(Position)

[c] Employee Class employeeClass No

(Position)

c] Position ID Code No Added for applica-

tion visibility. Also
(Position) stored in the Exter-
nal Position ID field
for integrations.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Position Management Integration and Configuration PUBLIC 29
5.4 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.

 Note

An additional debug error log can be enabled in SAP Fieldglass for troubleshooting integration details. Contact
your SAP Fieldglass representative for assistance with enabling this feature.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
30 PUBLIC Position Management Integration and Configuration
5.5 Optional: Status Update Configuration

Configure the status update integration in the Publish/Subscribe Framework section in Configuration Manager.

Using the Publish/Subscribe setup functionality in the Configuration Manager Self-Service Dashboard, enable
an optional status update integration payload and to deliver it to SAP SuccessFactors Employee Central for
maintaining real-time status for their position objects in the position org chart.

 Note

This configuration step is only required if the client wants to maintain status updates in the SAP
SuccessFactors Employee Central position object. This configuration is supported by SAP SuccessFactors
Employee Central (November 2021–2111) and allows for users to create new SAP Fieldglass job postings from
positions that have since closed in the SAP Fieldglass application. If a client doesn't enable or configure this
integration, the standard legacy behavior remains in place – reflecting a technical SUCCESS status from SAP
Fieldglass within SAP SuccessFactors Employee Central positions.

Configure the Status Update Integration

The following table summarizes the values required for the status update payload and end point. The values are
also included in the subsequent steps.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Position Management Integration and Configuration PUBLIC 31
Status Update Payload Properties
Publish/Subscribe Payload Name Activities End Point Elements

[Buyer Code]_SF_EC_STATUS UPDATE Add Ad Hoc Approver ID: [Buyer Code]_GET_SF_EC_STATUS

Approved
URL: [SuccessFactors Do-
Approver Edit main]/ODATA/v2/upsert

Assign Username:

Associate User Password:

Auto Distribute

Change Coordinator

Change Distributor

Change Job Posting Owner

Change Maximum Submissions

Change Project

Close

Compare

Complete Later

Decline

Distribute

Edit

Email Job Seekers Resume/CV

Halt

Pushed To Next Level

Redistribute

Reject

Remove Ad Hoc Approver

Remove Project

Reopen

Restart

Resume

Submit

Undecline

Withdraw

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
32 PUBLIC Position Management Integration and Configuration
  Note

For detailed information on using Configuration Manager, see https://help.sap.com/viewer/

73c0a1be6aaa46ef9b66b1c3f28a77f4/cloud/en-US/3e76ca93d2b6423ebbffd4e830ec59e5.html.

1. Sign in to SAP Fieldglass using your configuration manager user role.

2. Navigate to the Publish/Subscribe Framework section on the Self-Service Dashboard, and then choose
Setup.
The Publish Subscribe Setup Wizard opens on the Welcome page.
3. To define the payload and end point for the status updates, choose the Let's Get Started button.

The Payload creation page opens.

4. Select the Choose New button, and proceed as follows:

1. In the Payload Name field, enter an applicable payload name ([Buyer Code]_SF_EC_STATUS UPDATE).
2. In the Description field, enter a corresponding value.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Position Management Integration and Configuration PUBLIC 33
 3. In the Base Module list, choose Job Posting.
After selecting the base module, the Linked Modules options display.

5. Choose all linked modules to ensure all associated data is present in the payload deliverable being defined.
6. In the Format list, choose JSON.
7. Choose Next Step.
The Subscribe page opens.

8. In the Activities list, choose the options applicable to the subscription for the selected base module. SAP
Fieldglass recommends choosing all activities.

 Note

Don't configure the payload with any specific Supplier Codes – leave these options unselected to send the
status payloads for all requisitions and not specific to any supplier.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
34 PUBLIC Position Management Integration and Configuration
 9. In the Transporter Class list, choose SF/EC Transporter (this is the required value). This class selection
modifies the larger JSON payload into a consolidated format that Employee Central requires. Choosing any
other option results in creating and sending the larger JSON output to Employee Central, which fails in
processing.
10. In the Email and Notify at Retry fields, enter email addresses for notifications.
11. Choose Next Step.
The End Point page opens.

12. To create the end point for the delivery of the status update payload, select Choose New.
13. Enter the following details:
1. In the ID field, enter the applicable End Point ID to define where to deliver the data (for example, [Buyer
Code]_GET_SF_EC_STATUS).

 Note

The Category field autofills with Publish/Subscribe and is shaded.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Position Management Integration and Configuration PUBLIC 35
 2. In the URL field, enter the required API end point to send the status for the SAP SuccessFactors Employee
Central ODATA API, for example [SuccessFactors Domain]/ODATA/v2/upsert.
3. In the Username and Password fields, enter the credentials to authenticate to the SAP SuccessFactors
Employee Central OData API. Enter these values to match what the client has already configured in the
SAP Fieldglass database or in the position integration end point, as described in Create an Integration End
Point [page 6].
14. Choose Next Step.
The Finished page opens.

15. To complete the Publish/Subscribe configuration, choose Finish.

The Publish Subscribe payload begins to send data once the defined activities occur in the SAP Fieldglass
application for the Job Posting base module.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
36 PUBLIC Position Management Integration and Configuration
6 Worker Data Integration and Configuration

Worker data integration is a prepackaged integration that allows a client to replicate external worker’s data from
SAP Fieldglass into Employee Central using SAP Cloud Integration as middleware.

The integration uses Employee Central OData APIs and SAP Fieldglass SOAP web service.

SAP Fieldglass contains records of different types of workers (contingent workers, SOW workers, profile workers),
which are all supported with the integration to Employee Central. Clients can exclude particular worker types from
replication downstream using configurations in SAP Fieldglass.

The integration replicates only active workers and confirmed work orders.

 Note

Master data integration must be synchronized between Employee Central and SAP Fieldglass. For more
information on replicating master data from SAP SuccessFactors Employee Central to SAP Fieldglass, see
Using SAP Fieldglass with Employee Central on the SAP Help Portal.

 Note

SAP Cloud Integration supports creating and using X.509 Certificate Authentication when connecting with
other SAP platforms. Accordingly, X.509 Certification authentication is supported as part of the SAP Fieldglass
and SAP SuccessFactors Employee Central position and worker integration product solution. For configuration
information, see Configure X.509 Certificate Authentication for Worker Data Integration [page 7].

For more information about the architecture of how the integration works, see the data workflow diagrams in
the SAP Fieldglass and SAP SuccessFactors Employee Central Integration Business Synopsis, which provides an
overview of all integration points between SAP SuccessFactors Employee Central and SAP Fieldglass.

6.1 Enable Features in SAP Fieldglass

Describe how to enable specific features required for the integration.

Prerequisites

The following configuration tasks require the assistance of an SAP Fieldglass administrator.

Context

Configure SAP Fieldglass for integration with worker data.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Worker Data Integration and Configuration PUBLIC 37
Procedure

1. In the company configuration, enable the Integration option.

2. In the company configuration, enable the Enable Security Information option and enable include the
Security ID field for contingent workers.
3. Enable user role permissions. On the company's Admin Configuration menu under User, choose User Role.
1. Choose the applicable user role.
2. On the User Role Details page, locate the Configuration module, and then enable the options Download
Data and Upload Data.

6.2 Enable and Configure the Active Worker Delta Single Line
Download

The SAP Fieldglass Active Worker Delta Single Line Download connector is used to download worker data that have
had revisions since the last successful run date.

Prerequisites

The configuration manager needs to perform the following configuration tasks.

Context

The connector returns a single line per worker for temp workers, SOW workers, profile workers, and any new
contingent workers that have onboarded since the last run date.

For integration purposes, only the Active Worker Delta Single Line Download is used. In the initial load, the
connector executes using an old date from the past and returns all contingent workers hired after this date. For all
subsequent incremental loads, the connector executes with the last successful execution date and time.

Procedure

1. To enable the connector, in Configuration Manager, open the Active Worker Delta Single Line Download on the
Details page.
2. Choose More Actions > Enable Feature.
3. In the Name list, choose SuccessFactors - Standard Employee Central Worker Download, and then choose
Enable. This step automatically configures the required fields and sequences that are needed on the SAP
SuccessFactors Employee Central side. In addition, you need to manually add and configure a few custom
fields in the download. For information on this topic, see Configure Standard and Custom Fields [page 40].
Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
38 PUBLIC Worker Data Integration and Configuration
 4. To optionally exclude SAP Fieldglass worker types, ask your SAP Fieldglass representative to apply filter criteria
to the Active Worker Delta Single Line Download so only the desired worker types are sent to Employee Central.
(The integration supports all worker types by default: SOW workers, contingent workers, and profile workers.)

6.2.1 SAP Fieldglass Provider Settings

To support master data changes, the person_ID field from SAP SuccessFactors Employee Central and
security_id from SAP Fieldglass are used to send the modified information for contingent workers.

SAP Fieldglass Identifiers for Workers

The unique identifier for the Active Worker Delta Single Line Download connector can either be the Job Seeker
ID or the Worker ID field. Each record has a unique value in each of these fields.

Because of data privacy laws, employee person identifiers or any other employee information can't be stored
within the middleware. To solve this problem, an identifier coming from SAP Fieldglass is mapped with the
person_id_external field for a contingent worker in Employee Central. Currently there are four identifiers used
in SAP Fieldglass:

• Job Seeker ID
• Worker ID
• Person ID
• Security ID

Security_ID is unique and stays the same for a contingent worker even with different assignments and is
mapped to the person_id_external field in Employee Central.

Security_ID is a mandatory field to be configured and activated for use in SAP Fieldglass.

Types of Workers

SAP Fieldglass contains three types of workers:

• SOW Worker
• Contingent Worker
• Profile Worker

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Worker Data Integration and Configuration PUBLIC 39
6.2.2 Configure Standard and Custom Fields

Describes the standard fields and the custom fields required for integration with SAP SuccessFactors Employee
Central.

Prerequisites

The configuration manager needs to perform the following configuration tasks.

Context

The following steps explain how to edit fields and add custom fields to the Active Worker Delta Single Line
Download connector.

For information on how to work with custom fields in Configuration Manager, see https://help.sap.com/
viewer/73c0a1be6aaa46ef9b66b1c3f28a77f4/cloud/en-US/b188c2b8aa1549d48c8554c408e6f69c.htmlon the
SAP Help Portal.

Procedure

1. In SAP Fieldglass, sign into the company using a configuration manager profile.
2. Open the Active Worker Delta Single Line Download on the Details page, and choose the Enabled Fields tab.
The configured fields display.

3. Ensure that the connector is configured correctly with the following 37 fields in the sequence described.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
40 PUBLIC Worker Data Integration and Configuration
 Sequence Field Name Mandatory?

1 Job Seeker ID (used to create the User

fields in Employee Central)

2 Worker ID

3 Person ID

4 Security ID Yes

5 Status

6 First Name (API level) Yes

7 Last Name (API level) Yes

8 Worker E-Mail

9 Job Posting Title

10 Work Order ID

11 Work Order/ Work Order Revision

Owner

12 Work Order/ Work Order Revision

Owner Employee ID

13 Business Unit Code Yes

14 Business Unit Name

15 Vendor Number Yes

16 Vendor Name

17 Buyer Code

18 Remit To Address Code

19 Cost Center Name

20 Cost Center Code Yes

21 Billable Per Diem

22 Start Date

23 End Date

24 Currency

25 Site Code

26 Site Name

27 Location Code Yes

28 Work Location Name

29 Worker Supervisor

30 Work Order Status

31 Worker Start Date

32 Transaction Code

33 Last Revision Date

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Worker Data Integration and Configuration PUBLIC 41
 Sequence Field Name Mandatory?

34 Worker Type

35 Company Code (SAP Fieldglass Legal Yes

Entity Code)

36* Position ID*

37* Job Code*

 Note

Except for the fields marked with an asterisk (*), the enabled feature automatically configures all of the
fields in the sequence shown. The last two fields (sequences 36 and 37), which are the added custom
fields, must be enabled in the download connector in the following manner.

4. On the upper right side of the page, choose Edit.

The connector opens in the Connector Setup Wizard.

5. Add the Position ID and Job Code custom fields to the download. These fields can be defined to pull
specifically from the Job Posting module – you don't need to combine or link to other modules where these
custom fields may be linked. See the table below for field values.

Once these elements are configured, the full list of the required fields is complete.

If an Employee Central client requires any additional fields, data, or has changes to the standard mapping
schema, both native fields and custom fields can be added and modified in the same manner as described
above – they just need to match the receiving schema of the SAP SuccessFactors Employee Central system.
A user can navigate to the Enabled Fields tab of the active connector and select +Add Native Fields or
+Add Custom Fields, and then select accordingly. The sequence can also be modified manually through a
drag-and-drop function when editing that download’s configured fields.

Once the connector is enabled and configured, confirm that the naming convention reflects the Standard
Worker Download - Delta Single Line connector. This custom connector name is important, as the SAP Cloud
Integration configuration that the SAP SuccessFactors Employee Central client configures for the webservice
call focuses on this connector name for pickup and processing of the active connector. This download doesn't
typically require a configured subscription and delivery of the files to an endpoint, as the SAP SuccessFactors
Employee Central client should be calling directly to obtain the data from SAP Fieldglass through Cloud
Integration. Details on that middleware configuration are available in the SAP SuccessFactors Employee
Central guides that are referenced in the Additional Resources [page 46] section.

 Note

The Job Code custom field is only required where the job code data created and held in SAP
SuccessFactors Employee Central isn't being prepopulated into SAP Fieldglass via SAP Master Data
Integration (MDI). It's used within SAP Fieldglass to store the job code captured against the position with
SAP SuccessFactors Employee Central.

Where the native Job Code field is being used instead of the custom field, include the Job Code field into
the download, ensuring it's in the same position as defined for the Job Code custom field.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
42 PUBLIC Worker Data Integration and Configuration
6.3 Optional: Download Worker After Acceptance

Describes optional configuration that disallows downloading work orders based on status.

In addition to the SuccessFactors - Employee Central Worker Download connector that is used for configuration of
the worker download, an additional custom feature, Download Worker After Acceptance, can be enabled on
the Active Worker Delta Single Line Download in Configuration Manager. This feature disallows work orders in the
statuses of Pending Approval, Rejected, Created, and Declined to be included in the download.

For information on enabling custom features in Configuration Manager, see https://help.sap.com/viewer/

73c0a1be6aaa46ef9b66b1c3f28a77f4/cloud/en-US/bca21ff5494d4e6eb15ccbf1ada48390.html.

 Note

When using this optional feature, if the data coming from SAP Fieldglass contains either an inactive or
unconfirmed user, an error is logged in the SAP Fieldglass audit trail and you receive the following message:

No new/modified ACTIVE Contingent Workers found with CONFIRMED Work Order Status.

6.4 Error Handling of Contingent Worker Records

Describes how to troubleshoot errors with the Active Worker Delta Single Line Download connector.

The Active Worker Delta Single Line Download connector used to extract contingent workers from SAP Fieldglass
only extracts new workers and any that were extended since the last run date. If the error is because of missing
data from SAP Fieldglass, the failed contingent worker record is picked up in the next run of the connector.

If the SAP Fieldglass connector doesn't return any records (no change within SAP Fieldglass), the connector
throws the following SOAP fault exception:

Error = org.apache.cxf.binding.soap.SoapFault: download throwable

If the failure is because of misconfiguration or a network failure within Employee Central, contingent worker records
don't change within SAP Fieldglass. The next run of the Active Worker Delta Single Line Download doesn't fetch
the records. The middleware sends notifications to Execution Manager. Clients need to contact their SAP Fieldglass
representative to have the last date run reset within SAP Fieldglass.

If the date is reset within SAP Fieldglass, the Active Worker Delta Single Line Download connector picks up the
worker records that have changed since the last run date. These records are sent out to the middleware for
processing. If that batch contains workers’ previously successful processed information within Employee Central,
this data may be overwritten.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Worker Data Integration and Configuration PUBLIC 43
7 Error Reporting

What happens if the network goes down or if there are missing fields during the data integration? Errors are logged
in Execution Manager for different type of errors.

There are certain error types captured in error reporting:

• Hard Errors: Application errors such as connector failures.

• Soft Errors: Business errors such as missing fields or data.
• The attributes are captured in a .csv file attached within the Execution Manager

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
44 PUBLIC Error Reporting
8 Restrictions Using SAP Fieldglass and SAP
SuccessFactors Employee Central

Before you start integrating SAP Fieldglass contingent worker data with Employee Central for your company, there
are restrictions to consider.

Overlapping Assignments

To replicate worker data with overlapping assignments in SAP Fieldglass to Employee Central, you need to upgrade
your Employee Central instance to support Concurrent Employment for contingent workers.

For information about enabling Concurrent Employment for contingent workers in your
Employee Central instance, see https://help.sap.com/viewer/7b2dec4ed4d9459f893cce6f5920528d/2111/en-
US/3e6e4e76239449b39debb429e78ae549.html.

Effective Dating

Within Employee Central, worker has an effective date entity, but it's not supported by SAP Fieldglass. Since
Employee Central can’t identify the change within SAP Fieldglass, the middleware overwrites data only if the work
order dates are unchanged.

 Example

The contingent worker starts in business unit 10001 that has the work order start date of January 1, 2015 and
end date of March 31, 2015. In February 1, 2015, the business unit changes to 20002 for this worker. The new
business unit is valid from the original work order start date up until the original work order end date in SAP
Fieldglass.

Work Orders

You can't close a work order before the actual close due date, and changing work order dates isn't supported.

OData API Call Restrictions

OData APIs are executed in batches to avoid performance issues with redundant calls out to single entities.
Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Restrictions Using SAP Fieldglass and SAP SuccessFactors Employee Central PUBLIC 45
9 Additional Resources

Where you can find additional information on the integration of SAP Fieldglass and SAP SuccessFactors Employee
Central.

• View or download Integrating SAP Fieldglass with Employee Central on the SAP Help Portal.
• For best practice information on integrating SAP Fieldglass with SAP S/4HANA and SAP SuccessFactors
Employee Central, go to https://help.sap.com/viewer/b96229c257d74ce48b38a3f98e7c2270/cloud/en-US.
• For information on overviews and best practices related to SAP Fieldglass and SAP SuccessFactors Employee
Central worker integrations, go to SAP Fieldglass Integration with SAP SuccessFactors Employee Central on
the SAP Business Accelerator Hub.
• For general integration information related to SAP SuccessFactors Employee Central and SAP Fieldglass, go to
https://api.sap.com/products/SAPSuccessFactors/overview?target=SAPFieldglass .

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
46 PUBLIC Additional Resources
Important Disclaimers and Legal Information

Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:

• Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your agreements
with SAP) to this:

• The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.

• SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.

• Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering an SAP-hosted Web site. By using such links,
you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this information.

Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within the
control or responsibility of SAP.

Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use the
experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your feedback
(e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.

Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax and
phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of example
code unless damages have been caused by SAP's gross negligence or willful misconduct.

Bias-Free Language
SAP supports a culture of diversity and inclusion. Whenever possible, we use unbiased language in our documentation to refer to people of all cultures, ethnicities, genders,
and abilities.

Implementation Guide for SAP Fieldglass Integration with SAP SuccessFactors Employee
Central
Important Disclaimers and Legal Information PUBLIC 47
www.sap.com/contactsap

© 2024 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.

Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.

SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.

Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.

Material Number: 20221031

*20221031*

THE BEST RUN