SuccessFactor Implementation at Viridor

SAP HCM – SuccessFactors PI Configuration Example

2

Introduction

Using SAP ERP HCM applications together with SuccessFactors applications in a so-called hybrid environment, integrating talent management applications delivered in the cloud with applications such as personnel administration and organizational management that reside on their premises.

3

The hybrid delivery model enables organizations to keep their investments for the core HR applications and, at the same time, take advantage of the rapid innovation provided by SuccessFactors BizX Suite applications.

The goal is to make the integration provided by SAP FAST:

F - Functionally rich (pre-packaged yet extensible integrations)

A - Affordable (lowering your total cost of ownership and cost to deliver integration)

S - Simple to implement, maintain, and support

T - Trusted, based on deep SAP domain know-how

Process integration supports the execution of business processes that span SAP and SuccessFactors systems and that require data to flow from SAP to SuccessFactors and vice versa.

4

The Employee Data to be automatically populated in the SuccessFactors BizX environment. The transfer of data will occur as per the below diagram:

5

This document provides an example of the setup in the PI Integration Directory needed for the hybrid integration of SAP ERP HCM and SuccessFactors BizX.

The login service needs to be configured differently from all other services. This is necessary due to the session handling mechanism. While the login service receives the session ID in the payload of the response message, all subsequent requests must use an HTTP header cookie to transfer the session ID to SuccessFactors. Therefore, all services other than the login need to use a communication channel that uses SOAP AXIS adapter in order to write the cookie to the HTTP header. Therefore this document explains the setup for the user data scenario consisting of the login, logout, and user data upsert services. This procedure can also be copied for other scenarios.

PI Configuration Overview

6

PI Design Overview

SAP provides standard ESR content for integration between SAP and SuccessFactors Biz Ex Suite. This content is available on the Service Market place as a part of the Software components SFIHCM01 and SFIHCM02 (Version 600). Note- ESR content can be downloaded from below location in Service Market Place

Software Downloads SAP Software Download Center Support Packages and Patches Browse Our Download Catalog SAP

Content ESR Content (XI Content)

7

For Employee Data Synchronization, the required content is entirely contained in the first SWCV – SFIHCM01 600. There is a Process Integration scenario dedicated for this synchronization.

The process flow has the following steps:

1. Login into SFSF to establish a session and fetch the session ID 2. Inserting/ Updating the Employee data into SFSF 3. Logging out of the session.

Employee Data Synchronization

8

Recruitment Data Synchronization

For Recruitment Data Synchronization, the required content is partially contained in the first SWCV – SFIHCM01 600 and partially in the second SWCV – SFIHCM02 600. There is a Process Integration scenario (in SFIHCM02 600) The process flow has a number of steps, out of which we are implementing the following ones as a part of this RDS:

1. Login into SFSF to establish a session and fetch the session ID2. Submitting Job Query Request to SFSF3. Fetching Job status 4. Get Job Result Embedded5. Sending Job Application Status Update to SFSF6. Retrieving Candidate data from SFSF7. Logging out of the session.

9

Recruitment Data Synchronization

10

Compensation Data Synchronization

For Compensation Data Synchronization, the required content is partially contained in the first SWCV – SFIHCM01 600. There is a Process Integration scenario. The process flow has a number of steps, out of which we are implementing the following ones as a part of this RDS:

1. Login into SFSF to establish a session and fetch the session ID2. Submitting Compensation details3. Fetching Compensation details4. Submitting Compensation Cancel details5. Fetching Compensation cancel details6. Sending List message to SFSF7. Sending DescribeEX message to SFSF8. Logging out of the session.

11

Compensation Data Synchronization

12

PI Configuration Overview

The screenshot below shows the objects of a sample configuration for the user data scenario using business components.

Employee Data Synchronization

13

The back-end business component contains all the sender interfaces.

14

The SuccessFactors business component contains the communication channels.

15

PI Configuration Login Service The ICO for the login interface contains all objects needed to connect the following two interfaces:

SSFSFessionHandlingLoginQueryResult_Out

SFSFSessionHandlingLoginQueryResult_In

In inbound Processing tab Only the sender communication channels that are assigned to the communication component and which correspond to a supported adapter type are offered.

16

In Receiver tab we specified receiver(SuccessFactors) ,In the Communication Component column, We can then select the communication component of the receiver. If we want to select a communication component that is assigned to a communication party for the receiver, you can first select this in the Communication Party column.

Here in our case SuccessFactors is outside landscape(B2B) so we have is assigned to a communication party for the receiver

17

In receiver interfaces tab, The receivers that you already created are displayed in rows under Receivers(SuccessFactors)

Under Receiver Interfaces and Mappings we specified a receiver interface for outbound interface operation

18

In outbound Processing tab Only the receiver communication channel that are assigned to the communication component(receiver) and which correspond to a supported adapter type are offered.

19

PI Configuration Logout Service

The ICO for the logout interface basically look the same as for the login interface except for the communication channel.


20



21



22


Ensure that for the logout service you use the communication channel with SOAP AXIS adapter. The corresponding template is CC_SuccessFactors_Soap_Axis_Recv

23

PI Configuration User Data Upsert Service

The configuration for the user data upsert service is the same as for to the logout service.


24



25



26


Ensure that for the user data upsert service you use the communication channel with SOAP AXIS adapter. The corresponding template is CC_SuccessFactors_Soap_Axis_Recv

27

PI Configuration Communication Channels

This communication channel is to be used for the login service. It can be created based on the template SFSF_Soap_Adapter.

28

PI Configuration Communication Channels

This communication channel is to be used for all steps other than login. It can be created based on the template SFSF_Soap_Adapter.

Note: In this document PI Configuration overview for Employee Data Synchronization is covered. Recruitment Data Synchronization, Compensation Data Synchronization can be configured similarly.

SuccessFactor Implementation at Viridor

Documents

Transcript of SuccessFactor Implementation at Viridor