XI 3.0 No receiver could be determined

[Former Member]

Hello,

I receive, “No receiver could be determined” in SXMB_MONI (XI SAP GUI) when trying to send a business partner to SUS. The data flow is EBP-XI-SUS. The business partner makes it to XI successfully, but it cannot determine the receiver (SUS).

I receive this in the Display XML message version screen:

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

- <!-- Receiver Grouping -->

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

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

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

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

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

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Thanks,

Kyle

[Former Member · Accepted solution]

If you are on SP12 you can do the test of your configuration in Integration Directory.

First check whether your changes in Integr. Repository have been activated or not.

Check your configuration

regards

Shravan

[Former Member · Accepted solution]

Thanks Shravan,

We installed SP13 a few weeks ago and have been using the test tool for about a week now. The web log gives a nice over view of the tool. When testing with the payload we receive the following error:

Runtime error

During the application mapping com/sap/xi/tf/_EBP40Partner2SRM40Partner_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: Fatal Error: com.sap.engine.lib.xml.parser.Parser~

<Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace>... (157 lines)

Note: Sender agreement, receiver determination and Interface determination appear to be Okay.

Thanks Again,

Kyle

[Former Member · Accepted solution]

Hi Kyle,

While testing with Test tool put the data in xml format in the payload.

I think you are putting data in text format.

Hope it helps.

Thanks.

Rekha

[Former Member · Accepted solution]

Hi Rekha,

We are using XML for our payload.

This is the format of the message we are pasting in the payload window. (I have masked the BP info for this post)

<?xml version="1.0" encoding="utf-8" ?>

- <nr1:SupplierPortalTradingPartner xmlns:nr1="http://sap.com/xi/EBP">

<Method>Create</Method>

- <TradingPartnerOrganization>

<TradingPartnerRole>Seller</TradingPartnerRole>

- <Identifier>

<PartnerID>0000103085</PartnerID>

</Identifier>

<SystemID>SRM_charon</SystemID>

<Language />

<Currency>CAD</Currency>

<Title>0003</Title>

<Name1>VENDOR name

- <Address>

<StandardAddress>true</StandardAddress>

<AddressID>0000000000</AddressID>

<Street>123 fake street</Street>

<City>Calgary</City>

<PostalCode>XXX XXX</PostalCode>

<Region>AB</Region>

<Country>CA</Country>

</Address>

- <Communication>

<CommunicationType />

- <Telephone>

<StandardTelephone>true</StandardTelephone>

<Number>555-555-5555</Number>

<TelephoneCountry>CA</TelephoneCountry>

</Telephone>

- <Fax>

<StandardFax>true</StandardFax>

<Number>555-555-5555</Number>

<FaxCountry>CA</FaxCountry>

</Fax>

- <Email>

<StandardEmail>true</StandardEmail>

<EmailAddress>bob@email.com</EmailAddress>

</Email>

</Communication>

</TradingPartnerOrganization>

</nr1:SupplierPortalTradingPartner>

This inbound XML message can successfull make it to XI but the above(first post) error happens when transfering to SUS.

Note: Our XIAPPLUSER is frequently becomming locked in XI.

Any Suggestions?

Thanks,

Kyle

[Former Member · Accepted solution]

This problem was occuring because the connectiopn between EBP and the SLD was not working. EBP and SUS did not have the up-tp-date SLD business system names, therefore the comunication channels in XI would not work.

Best Regards,

Kyle

[Former Member · Accepted solution]

Dear Kvle

How can get the updated information in ID and IR from SLD?

Many thanks!

Jerry

[Former Member]

i am getting similar error.

How did you get it solved