Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

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

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 Member
Former Member replied

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.

1 View this answer in context
Not what you were looking for? View more on this topic or Ask a question