Skip to Content
Author's profile photo Former Member

Interfacing with SuccessFactors using SFSF adapter in SAP PI dual stack environment – Part II

4. Download the Successfactor certificates and upload them in SAP PI Netweaver key-store.


a. To download the Successfactors certificate, open the target url in a browser such as Google chrome. First click on the lock button, then on the connection tab      and finally on the certificate information hyperlink.

Screen Shot 2016-04-11 at 4.10.10 PM.png

b. There are going to be 3 certificates, which need to be downloaded.


ℹ Successfactor certificate

(ii) Symantec certificate

(iii) Verisign certificate


c. Open the successfactor certificate first.


Screen Shot 2016-04-11 at 5.15.22 PM.png


d. Go to the details tab and click on the Copy to File.


Screen Shot 2016-04-11 at 5.16.49 PM.png


e. Click on Next and select the format as DER encoded binary X.509, which is compatible with SAP PI.


Screen Shot 2016-04-11 at 5.20.00 PM.png

Screen Shot 2016-04-11 at 5.21.13 PM.png


f. Specify the directory and the certificate name and finish the download.


Screen Shot 2016-04-11 at 5.23.09 PM.png

Screen Shot 2016-04-11 at 5.27.29 PM.png


g. Go to the certification path and double click the first two line to access the next two certificates one by one.


h. Repeat the steps from d to f for these two certificates.


Screen Shot 2016-04-11 at 5.29.38 PM.png


i. Upload the 3 certificates in NWA keystore in SAP PI. Keep the entry type as X.509


Note: Uploading the certificates in NWA keystore is not covered in this guide.


Screen Shot 2016-04-11 at 5.31.42 PM.png


5. Configure the runtime objects in ID.


a. Create a communication component for successfactor i.e. BC_Successfactor. And assign the outbound interface as created in 3d.


Screen Shot 2016-04-11 at 5.34.44 PM.png


b. Create a sender communication channel using SFSF adapter. Specify the message protocol as SOAP.


Screen Shot 2016-04-11 at 5.36.28 PM.png


c. Select the endpoint URL for SuccessFactors from the list. If not already available, then specify it as others and then mention it in the Alternate Endpoint URL.


d. Specify the SFAPI URL suffix as /sfapi/v1/soap


e. Specify company name, user id and password.


Screen Shot 2016-04-11 at 5.38.05 PM.png


f. Go to the Processing tab and specify the SFQL query as obtained in step 2q above.


g. Specify the poll interval accordingly. This is the interval which the SF adapter is going to be using to poll the SFEC entity.


Screen Shot 2016-04-11 at 5.40.03 PM.png


h. Specify the SSL certificate. Tick on the specify SSL certificate and specify the certificate key for verisign certificate.


i. Create a standard receiver file communication channel on SAP HR system with NFS protocol. Specify the target directory and file name.


j. Create a standard ICO with the design and run time objects created in Step 3 and Step 5.


k. Save and activate the ID objects along with ICO.


Screen Shot 2016-04-11 at 5.42.56 PM.png


6. Test the interface.


To test the interface, follow the below steps.


a. Stop and then start the Sender SFSF communication channel.


b. A message can be seen entering the Adapter engine in Sender communication channel monitoring.


c. A success message can be seen in message monitoring.


Screen Shot 2016-04-11 at 6.00.26 PM.png


d. Go through the Message log to understand the message processing better.



Screen Shot 2016-04-11 at 5.49.16 PM.png


e. The request payload will look like this.


Screen Shot 2016-04-11 at 5.51.48 PM.png

7. Troubleshooting tips.


Few common errors related to the SF Adapter and their resolutions.


a. Error: A previous lock still persists. Aborting poll operation.


    Resolution: Ensure to increase the polling period in the receiver SF communication channel. In the example shown here, the polling period was increased         from 5 mins to 1 day to correct the issue.


Screen Shot 2016-04-11 at 6.00.26 PM.png


b. Error: INVALID_SFQL. Invalid SFQL! Error: Query “—–“ is not properly formed.


Resolution: Ensure that the SFQL query is maintained correctly in Receiver SF channel. In the example shown here, comma (“,”) was placed between the         fields in SFQL query to correct the issue.


Screen Shot 2016-04-11 at 6.03.22 PM.png





1. Install Operation Modeler:


2. Create a new project:


3. Modelling Operations:





SFEC: SuccessFactors Employee Central

SFQL: SuccessFactors Query Language

Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.