SAP SuccessFactors Work Zone Setup with SuccessFactors Sales4Demo Instance Part 2 of 2

January 30, 2023
Sara Sampaio
Technical Articles

In this blog post of Part 2 you will learn about setting up SAP Success Factor Work Zone with your SAP Success Factor tenant pre-requisites before running Work Zone Configurator.

The Work Zone Configurator has been updated to support the conversion of SAP SuccessFactors Work Zone from HXM core to SAP Cloud Identity Services.

Final Part Steps: Configuration Pre-Requisites before running Work Zone Configurator-

There are two ways to do the Pre-Requisites of Work Zone Configuration as mentioned below –

Create a new tenant.
Create a tenant based on an existing SAP Jam tenant.

Here we will go with Option 1 for doing the Pre-Requisites for Work Zone Configurator.

Below are the required steps involved while going with Option 1 i.e. Create a New tenant –

Create a Destination to SAP SuccessFactors.
Set up Environment.
Configure IAS and IPS service for Source & Target System.
Run Jobs in IAS for Sync.

Final Part Setup Process Initialized :

Create a Destination to SAP SuccessFactors

Enter your SAP SuccessFactors OData API URL as this is Sales4Demo Instance API URL will be as mentioned below –

https://apisalesdemo4.successfactors.com/odata/v2/

Enter your company ID which you can find in your Success Factor HXM Tenant.

Enter API key – To Generate the API key follow the steps mentioned below –

Download the X.509 certificate from your Cloud Foundry subaccount

2. Create a SuccessFactors OAuth Client.

In SuccessFactors, go to the Admin Center and search for OAuth. Choose Manage OAuth2 Client Applications.

Click on Register Client Application.

3. In the field <X.509 Certificate>, paste the certificate that you downloaded in step 1.

Choose Register to save the OAuth client.

Note the API key generated here & paste in the Create Destination Steps in Work Zone Configurator.

Set up Environment

Before triggering the final setup steps, you must download the trust from the SAP BTP cockpit Destinations screen. Click the Download Trust link above the table of destinations.

Configure IAS and IPS service for Source & Target System

Set up SAP SuccessFactors as a source system –
A source system is the connector used for reading entities (users, groups, roles).

Source systems can be on-premise or cloud-based, SAP or non-SAP, and usually represent the corporate user store where identities are currently maintained. The Identity Provisioning service reads the entities from the source system and creates or updates them in the relevant target ones. The provisioning is triggered from the Jobs tab of a source system.

You can connect one source system to one or multiple target systems. In the case of multiple (enabled) target systems, when you start a Read or a Resync job, this operation will trigger provisioning of entities from this source system to all relevant target ones

Login to IPS and first create a Source System named “Success Factor” with below mentioned properties under Source Systems –

NAME	VALUE
Authentication	BasicAuthentication
ips.full.read.force.count	5
ips.trace.failed.entity.content	TRUE
Password	<Password of SF Tenant>
ProxyType	Internet
sf.user.attributes	userId,username,status,email,lastName,firstName,lastModifiedDateTime,personKeyNav
sf.user.attributes.expand	personKeyNav,personKeyNav/userAccountNav
sf.user.filter	status eq ‘active’
Type	HTTP
URL	https://apisalesdemo4.successfactors.com/odata/v2/
User	SFCompanyID@Password of SF Tenant

Create Second Source System named for “Success Factor Work Zone” with properties as mentioned below –

NAME	VALUE
Authentication	BasicAuthentication
ips.full.read.force.count	5
ips.trace.failed.entity.content	TRUE
Password	<Password of SF Tenant>
ProxyType	Internet
sf.user.attributes	addressLine1,addressLine2,businessPhone,city,country,department,division,email,fax,jobCode,title,defaultLocale,location,firstName,lastName,hireDate,state,timeZone,userId,username,zipCode,custom01,custom02,custom03,custom04,custom05,custom06,custom07,custom08,custom09,custom10,custom11,custom12,custom13,custom14,custom15,lastModifiedDateTime,personKeyNav
sf.user.attributes.expand	personKeyNav,personKeyNav/userAccountNav
sf.user.filter	status eq ‘active’
Type	HTTP
URL	https://apisalesdemo4.successfactors.com/odata/v2/
User	SFCompanyID@Password of SF Tenant

2. Set up SAP Work Zone as a target system

A target system is the connector used for writing entities.

Target systems are usually cloud systems, where the Identity Provisioning service creates or updates the entities read from the source system.

A target system can be connected to a single or multiple source systems. In the case of multiple source systems, we recommend that you run the provisioning jobs successively for each system, not simultaneously. This way, you’ll avoid incorrect overwriting or merging of entity data, hence failed provisioning jobs.

Login to IPS and first create a Target System named “IAS” with below mentioned properties under Target Systems for IAS Target from IPS –

NAME	VALUE
Authentication	BasicAuthentication
ias.api.version	1
ips.failed.request.retry.attempts	2
ips.failed.request.retry.attempts.interval	60
ips.trace.failed.entity.content	TRUE
ProxyType	Internet
scim.user.unique.attribute	userName
Type	HTTP
URL	<URL for Cloud Identity Services i.e. IAS/IPS>
User	<Admin User for Cloud Identity Services>

Create Second Source System named for “SAP Work Zone” with properties as mentioned below in Target System –

NAME	VALUE
Authentication	BasicAuthentication
ips.failed.request.retry.attempts	2
ips.failed.request.retry.attempts.interval	30
ips.trace.failed.entity.content	FALSE
OAuth2TokenServiceURL	<Oauth Token URL mentioned in Work Zone Configurator>
Password	<Password mentioned in Work Zone Configurator>
ProxyType	Internet
Type	HTTP
URL	<URL mentioned in Work Zone Configurator>
User	<User mentioned in Work Zone Configurator>

Run Jobs in IAS for Sync

Go to the Source System & Run Jobs to Sync the Source System for Success Factor Source Sync to IAS Target in IPS and Success Factor Work Zone to IPS for the both Source System created above.