No receiver could be determined - SAP HCM Integration with SuccessFactors Recruiting module

[Former Member]

Hi,

RH_SFI_SYNCH_METADATA program running in SAP HCM for SFSF ad hoc reports, is giving me the following error in the PI system

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Receiver Determination

--> 

- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>No receiver could be determined</SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

      Add trace log

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Receiver Determination

--> 

- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">

<Trace level="1" type="T">Party normalization: sender</Trace>

<Trace level="1" type="T">Determining the sender agreement</Trace>

<Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=entry</Trace>

<Trace level="1" type="T">Remote address = 192.168.200.99</Trace>

<Trace level="1" type="T">User = XIUSER</Trace>

<Trace level="1" type="T">Process ID: 15050</Trace>

<Trace level="1" type="T">Work Process ID: 0</Trace>

<Trace level="1" type="T">Message ID = 0050569F00D31ED59FC2A57DCAC10A10</Trace>

- <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS">

<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>

<Trace level="1" type="T">Hop engine name = is.00.sappipod11</Trace>

<Trace level="1" type="T">Hop engine type = IS</Trace>

<Trace level="1" type="T">Hop adapter name = XI</Trace>

<Trace level="1" type="T">Hop adapter namespace = http://sap.com/xi/XI/System</Trace>

<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />

<Trace level="1" type="T">system-ID = POD</Trace>

<Trace level="1" type="T">client = 100</Trace>

<Trace level="1" type="T">language = S</Trace>

<Trace level="1" type="T">user = XIUSER</Trace>

<Trace level="1" type="Timestamp">2015-10-29T08:15:10Z CET</Trace>

<Trace level="1" type="T">ACL Check is performed</Trace>

<Trace level="1" type="T">XML validation is executed</Trace>

</Trace>

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE">

<Trace level="1" type="T">PLNAME = CENTRAL</Trace>

<Trace level="1" type="T">QOS = BE</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />

- <!-- ************************************
--> 

<Trace level="1" type="T">>>>PID delete old pid determination coding</Trace>

<Trace level="1" type="T">system-ID = POD</Trace>

<Trace level="1" type="T">client = 100</Trace>

<Trace level="1" type="T">language = S</Trace>

<Trace level="1" type="T">user = XIUSER</Trace>

<Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_LOG_TO_PERSIST" />

- <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">

- <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV">

<Trace level="1" type="T">Reading sender agreement</Trace>

<Trace level="1" type="T">Message does not contain a sender agreement</Trace>

<Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace>

</Trace>

</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_LOG_TO_PERSIST" />

<Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION" />

- <!-- ************************************
--> 

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />

- <!-- ************************************
--> 

- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>

<Trace level="1" type="T">Cache content is up to date</Trace>

<Trace level="1" type="T">No Relation found - accept given Receivers.</Trace>

</Trace>

</Trace>

<Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_TO_PERSIST" />

</Trace>

<Trace level="1" type="T">An Exception has occured</Trace>

<Trace level="1" type="T">Error Text: No receiver could be determined</Trace>

<Trace level="1" type="T">SystemError message generated. Guid: 005056AA2AB51EE59FC2A57B95E98810</Trace>

<Trace level="1" type="T">Error during execution of message : 0050569F00D31ED59FC2A57DCAC10A10</Trace>

<Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): 0050569F00D31ED59FC2A57DCAC10A10</Trace>

<Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>

<Trace level="1" type="B" name="CL_XMS_MESSAGE_PERS_MAN-WRITE_MESSAGE_TO_PERSIST" />

- <!-- ************************************
--> 

</SAP:Trace>

Thank you

Rubén Moral.

[former_member186851 · Accepted solution]

Hello Ruben,

check for the proper SWCV and interfaces.

[Former Member · Accepted solution]

hello Raghuraman,

when check the service SFSFSessionHandlingLoginQueryResult_Out in SWCV is giving me the same error

RCVR_DETERMINATION.NO_RECEIVER_CASE_BE No

receiver could be determined

thank you

[former_member186851 · Accepted solution]

Ruben,

Do a cache referesh,else re-configure the scenario once and check.

[Former Member · Accepted solution]

The cache refresh I've done several times.

[former_member186851 · Accepted solution]

Rubesh reconfigure and check once.

[Former Member · Accepted solution]

I just did and continues to play the same error.

[former_member186851 · Accepted solution]

Try creating a BS in SLD and associate the SFSF software component with the BS and then check.

[former_member182412 · Accepted solution]

Hi Ruben,

• According to below configuration all interfaces from ECC by default send to PI integration engine.So your interface by default it is sending to integration engine and there is no receiver determination for your interface that is why you are getting RCVR_DETERMINATION.NO_RECEIVER_CASE_BE error.

• You have created the ICO for your interface, ICO wont run on integration engine it will run only on adapter engine, you need to route your interface to adapter engine not to integration engine. Please check below document for configurations.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70066f78-7794-2c10-2e8c-cb967cef4...

Regards,

Praveen.

[Former Member · Accepted solution]

hi,

I have been following the manual sap

"Talent HRH50e_Col43_EN-Hybrid Set SAP PI Integration"

which refers to the interface must be directed to integration engine.

[Former Member · Accepted solution]

I did and unfortunately the error remains.

[former_member182412 · Accepted solution]

Hi Ruben,

If you read properly the sentence it is saying integration engine or adapter engine. if you are using PI single stack only then the global configuration data point to adapter engine then all your interfaces from ERP will go to adapter engine

If you are using dual stack PI and if you want to send some of the interfaces must go to integration engine and some the interfaces must go to adapter engine then leave the global configuration data point to integration engine add another IS_URL parameter with SUB_PARAMETER as shown below.

Regards,

Praveen.

[Former Member]

Hi Ruben

- Do you have any conditions maintained in the Receiver Determination? If yes, then check if the conditions are being satisfied or not. If no conditions are maintained then check the xml payload that you are receiving from hcm.

- Check if your receiver agreement.

- Check if your receiver interface is active.

Regards

Osman

[Former Member]

Hi,

I have not any conditions maintained in the Receiver Determination.

I am using predefined by SAP Integrated Configuration.

Thank you very much Osman

[Muniyappan]

what is the sender interface you are seeing in the message monitoring?

have you created ID objects for that interface?

[former_member139572]

Hi Ruben,

check this thread

https://scn.sap.com/thread/1141648 (NO_RECEIVER_CASE_BE - Error)

It can gave you a clue...

Regards

Gab

I

[Former Member]

hi!

the sender interface is http://sap.com/xi/SFIHCM01

[Muniyappan]

That is not an interface. it is namespace.

is it ICO or classic scenario?

can you share us the ID configurations?

[Former Member]

Sorry, you're right,

The sender interfaces is CO_SFI_SE_SESS_HNDL_LOGIN_QR

[Muniyappan]

it is difficult to suggest without looking at your configuration.

Please share us the receiver determination and interface determination.

if you have ICO, please share the screen shots of that.

[Former Member]

Attached screenshots of ICO

[Muniyappan]

I believe "HRD_HR_Desarrollo" is your business system. i.e creating business system in SLD and importing into ID.

what do you see in ECC sxmb_monitoring? is HRD_HR_Desarrollo  appearing in the sender component?

also what do you see in the cache notification of ID? all green?

[Former Member]

Effectively "HRD_HR_Desarrollo" is my business system.

I am attaching the screenshot of sxmb_monitor which shows that "HRD_HR_Desarrollo" appears on sender component.

The cache is refreshed and I have ok.

[Muniyappan]

can you check if you RFC connections are mentioned in the below blog?

ECC should be sending the message to PI adapter engine.

[Former Member]

In principle I see a successful connection of all RFCs, as you can see in the screenshots. My question now is RFC PI_INTEGRATION_SERVER_POD if the test is successful, understand this well. Would I can confirm?

[former_member186851]

Ruben try configuring once again.If it is BS try creating new and assign it.