Skip to Content

PI.SFSF Integration.DOC – Integration between Non-SAP System and Successfactors BizX. – Part II

This document is in continuation to my previous blog PI.DOC- Integration between Non-SAP System and SFSF BizX. – Part I


Screenshot below shows Development [ESR] object for Update User Data.


PI ESR Object Development Overview

Externel Defination created using Demo WSDL URL:

1.       Open above URL in explorer.

2.       Right Click

3.       View Source

4.       Save as SF.wsdl

5.       Use this WSDL to create External Defination.

6.       Message SFWebSeviceFaultException is used to handle Fault Message.

7.       Message UpdateResponse is used to handle Response Message.

Name : EXTDEF_SuccessfactorsDemoWSDL

Image 8.JPG

Request Message Type


UpdateRequest of WSDL External Defination  is amended and saved again as XSD, which will be used later in Request Message mapping.

Reason of doing changes in updateRequest : It doesn’t have email fields added in it. So in our case we added email field in updateRequest then saved it as .XSD and again uploaded it for further use.


You can use tool like Altova XMLSpy to handle such cases.

Name : EXTDEF_UpdateEmailOperation_XSD

Image 9.JPG

Create Outbound and Inbound synchronous service interface.

Name : UpdateRequest_Sync_Out

Image 10.JPG

Name: UpdateRequest_Sync_In

Image 11.JPG

Message Mappings

Message Mapping – Request

Name :UpdateOperation_Request_MessageMapping

Image 12.JPG

UDF Name :Get_SessionID

Purpose : UDF is to perform soap lookup and get session ID as response. Later pass this UDF to next UDF.

Image 13.JPG

UDF Name :Set_Cookie

Purpose : UDF is to use dynamic configurations and communication channel’s ASMA properties to set SessionID as Cookie parameter of HTTP Header.


Image 14.JPG

Message Mapping – Response

One to One Mapping.

Name : Update_Response_Mapping

Image 15.JPG



Message Mapping – Fault

One to One Mapping.

Name : Messagemapping_Fault

Image 16.JPG

Opeartion Mapping :

Name : UpdateOperation_OperationMapping

Image 17.JPG

to be continued.. PI.DOC- Integration between Non-SAP System and SFSF BizX. – Part III


Due to Size limitation rest will be continued to PI.DOC– Integration between Non-SAP System and SFSF BizX. – Part III

You must be Logged on to comment or reply to a post.
  • Hi Prabhat,

    I appreciate your effort in preparing the document.

    In your scenario , its the 3rd party SOAP system.

    In the message mapping , you have used UDF for capturing the Session Id and Cookies details.

    1.What is the significance of this fields in real time scenario?

    2. Would this UDF be replaced in SAP HCM is used?


    • Yes if HCM will be used : then only one UDF will be required - to set cookie details in SOAP Axis adapter.

      First UDF to get session will be handled by an seprate flow of HCM to bring login information.


  • Hi Prabhat,

    Thanks for the blog. I have 3 questions to you

    1)Regarding the ESR part. How did you 'amend' the WSDL to a XSD to create the Source Data Type.

    2) I did the insert and update operation using SFSF adapter and modellling the structure using Kepler. Worked fine. However Delete operation was not supported by SFSF. You have any idea on how to perform delete using SFSF adapter ?

    3) And with SOAP Axis, I was able to consume the WSDL and do all the operations using NWDS by writing java code to send and receive data. Again, Worked fine.

    But when I used PI, I have doubts in message mapping to generate the target Structure. The WSDL has the below structure for insert. How do I pass value for Business keys field, which should contain the actual field names and values to be inserted. ??


    Kindly provide insights