I opened a customer message with SAP on this problem. After a couple of back-and-forths and the expected dodge that this is a consulting issue, not a support issue, the HCM Development Team sent me a powerpoint doc entitled "SAP HCM -- SuccessFactors BizX PI Configuration Example." This document answered almost all of my questions about the PI Integration Directory setup for this integration. The document contains the typical legalese about distributing only with SAP's permission--and I don't have such permission, so I will not be posting the document. (I wish I could, because it is immensely helpful!)

I will provide a general overview of the salient points I gleened from the doc, though.

1. you need to set up 2 SOAP communication channels; one that uses uses standard HTTP transport protocol and SOAP message protocol, one that uses HTTP (Axis)transport protocol and Axis message protocol. The standard SOAP CC is used for the Login request; all other requests use the Axis CC.

2. You need to set up a Business Component for SuccessFactors. If you don't already have one, you also need to set up either a Business Component or a Business System for your HCM system. Associate both communication channels with the SuccessFactors Business Component. On the Receiver tab of the SuccessFactors business component you need to add the inbound interfaces SFSFSessionHandlingLoginQueryResult_In, SFSFSessionHandlingLogoutQueryResult_In, and the interface(s) associated with the upsert you will be performing (in my case its SFSFCompensationManagementUpsertRequestConfirmation_In). On the Sender tab of the HCM BC you need to add the corresponding "_Out" interfaces. Note: in my case I already had a business system for our HCM system, and I was not able to add the interfaces to the Sender tab; that didn't seem to matter.

3. You need to set up 3 interface determinations, 3 receiver agreements, and 3 receiver determinations; one of each for the login, the upsert, and the logout.

4. If you are still stuck ask SAP for a copy of the PI Config Example powerpoint they created in response to my customer message--that doc takes most of the mystery out of the PI setup.

Cheers and Good Luck,

TerryB

Once I got past the "no receiver" error I immediately ran into another error in the Axis adapter in PI: "iaik.security.ssl.SSLException: Invalid SSL message, peer seems to be talking plain!."

I resolution to this error pointed out a couple of instances where the info in this blog dd not work for me( both on the Axis communication channel):

1. I had to use "none" for authentication.

2. On the Module tab, I had to remove the two trp entries relating to "proxy". Once I made those two changes I had no more communication issues with my SuccessFactors Integration add-on.

Cheers,

TerryB