Error: No Receiver could determined

[mrahhaoui]

Hi all:

I am setting up one scenario about ' XML to IDOC '.

When I send XML from one R3 system to XI , I meet with the following errors.

"No receiver could be determined"

Anybody could help? Thank you,

Mohamed.

[udo_martens · Accepted solution]

Hi Mohamed,

pick up the values from SXMB_MONI for sender Business System, sender Interface and sender Namespace and use just that values for Receiver Determination.

Regards,

Udo

[mrahhaoui · Accepted solution]

When I test the configuration by the tools "Test Configuration": The test pass successfully the sender agreement but it bloks at the receiver determination. I receive the following internal error:

Receiver Determination

Internal Error

HTTP connection to ABAP Runtime failed. Error: 403 Forbidden URL: http://frces4143:8000/sap/xi/simulation?sap-client=001 User: PIDIRUSER

[Former Member · Accepted solution]

Hi,

This could help you..

Go to SICF transaction and activate the services under path default_host/sap/xi/engine.

If the above hint doesn't help then plz check the below mentioned points..

Refer SAP Note -751856

Refer SAP Note -517484

Refer SAP Note -796726

Error in SOAP Adapter - "403 Forbidden" from the adapter's servlet. u2013Because of the URL is incorrect or the adapter is not correctly deployed.

Regards,

Sarvesh

[mrahhaoui · Accepted solution]

Which services do you mean?

[Former Member · Accepted solution]

enter transaction SICF then navigate to default_host->sap->xi--->engine. Check if engine is active else right click on engine and activate it.

[Former Member · Accepted solution]

Hello,

Check the servicesspecified are active or not.

Did you created receiver agreement in the integration directory with appropriate receiver interface?

Rajesh

[mrahhaoui · Accepted solution]

I configured a partner profile, a RFC destination and I went also to SICF transaction.

I did all but the problem persists.

[Former Member · Accepted solution]

> Internal Error

> HTTP connection to ABAP Runtime failed. Error: 403 Forbidden URL: http://frces4143:8000/sap/xi/simulation?sap-client=001 User: PIDIRUSER

I think the problem is in your entry poing url which sends the message to pipeline.

In your case it should be

http://frces4143:8000/sap/xi/engine?type=entry

but you have configured it as

http://frces4143:8000/sap/xi/simulation?sap-client=001

whch is incorrect.

Just copy the url (which i have suggested), as it is without changing anything, and then try. it should work. I sitll have one dout about your port "8000" used in above url is correct or not. Go to transacton SMICM and then press Shift+F1, compair the HTTP port. If it is not same then make the changes in your above url with this port.

Regards,

Sarvesh

[mrahhaoui · Accepted solution]

The port is the same.

I remarked also one thing. When I am kin the configuration and I choose my BS receiver which is BS_ER6CLNT001, I cannot select as inboud interface my Idoc for this BS which is imported in my repository. I have to switch to "all" and then I can choose the idoc "CREMAS.CREMAS05".

Maybe the problem is here. Anybody have a suggestion?

Thank you,

Mohamed.

[udo_martens · Accepted solution]

Hi Mohamed,

>...my Idoc for this BS which is imported in my repository

but obvisiosly not into the right SWC?

Regards,

Udo

[Former Member · Accepted solution]

Receiver will be determined based on the following factors/keys

SenderBusinessSystem/servicesenderInterfaceNamesenderNameSpace .

So check in the receiver determination object what are these configured as and check in SXMB_MONI what values at runtime it is showing

This sholud definitely guide you for analysing further

Rajesh

[mrahhaoui · Accepted solution]

I added idoc "CREMAS.CREMAS05" in ACN_BASE_COMP. I did the message mapping with that.

But in my configuration it's still the same, I don't find CREMAS in the list of the receiver determination of BS_ER6CLNT001.

[mrahhaoui · Accepted solution]

I had to add in the idoc adapter the receiver of messge status (the partner n° and partner profile). The communication works apparently but now in the Monitor for Processed Xml Messages in the tab "Aknowledgement message status" the error : Aknowledgement Contains Systems Error.

Anybody could help me please?

Thank you,

Mohamed.

[Former Member · Accepted solution]

Hi Mohammed,

If you do not have a requirement to receive the IDoc Acknowledgements, then create the entries in IDXNOALE table to suppress them.

refer to

[https://websmp105.sapag.de/_{sapdownload/011000358700003477212005E/HowTo_IDOC_Ack_20040817RR.pdf|https://websmp105.sap-ag.de/}sapdownload/011000358700003477212005E/HowTo_IDOC_Ack_20040817RR.pdf]

Regards,

MK

[Former Member · Accepted solution]

Just go to table IDX_NOALE (se11) and added your entry for not receiving idoc ack or go se38 and run the report IDX_NOALE and add your sapport and client ans messagetype.

HTH

Rajesh

[udo_martens · Accepted solution]

Hi Mohamed,

you need to add the SWC to the BS (product to technical system) at SLD level to get the IDoc into the Receiver List.

Regards,

Udo

[mrahhaoui · Accepted solution]

Hi MK,

I have not access to your site. It requires an user and pwd.

Thank you.

Mohamed R.

[mrahhaoui · Accepted solution]

This table doesn't exist in se11 !!!

[Former Member]

Hi,

Check the reciver system In Integration directory...The error Lies Here

[mrahhaoui]

In my test configuration I pass now the receiver. It bloks now at the interface determination & mapping the error is :

Interface Mapping

[Former Member]

Payload is empty

Looks like data is empty to the mapping .Check the source payload in SXMB_MONI and try to execute the same in Test tab of MessageMapping

Rajesh

[mrahhaoui]

Please find in below my configuration. I don't understand why it doesn't Apparently the XML goes well and it generates an Idoc Number when I see in SXMB_MONI. But when I type this number in WE05, there is nothing with that number.

Thank you,

Mohamed.

Configuration:

Display Receiver Determination:

Sender

Service : Z_SAP_ECC_BS

Interface: MI_Order_Outband1

Namespace :http://test.com/PI01/Idoc

Receiver:

Service: *

-

---

Display Interface Determination:

Sender

Service : Z_SAP_ECC_BS

Interface: MI_Order_Outband1

Namespace :http://test.com/PI01/Idoc

Receiver

Inbound interface

Name:Cremas.Cremas05 Namespace:urn:sap-com:document:sap:idoc:messages

Interface Mapping

Name:IM_Order_Idoc Namespace:Z_SAP_ECC_00 , 1.0 of accenture

-

---

Display Sender Agreement:

Sender

Service: Z_SAP_ECC_BS

Interface: Z_SAP_ECC_00 , 1.0 of accenture

Namespace :http://test.com/PI01/Idoc

Receiver

Service :BS_ER6CLNT001

-

---

Display Receiver Agreement:

Sender

Service: Z_SAP_ECC_BS

Receiver

Service :BS_ER6CLNT001

Interface: CREMAS.CREMAS05

Namesapce: urn:sap-com:document:sap:idoc:messages

Receiver Communication Channel : GeneratedReceiverChannel_IDoc

Edited by: rahhaoui mohamed on Feb 11, 2009 5:10 PM

[Former Member]

Sender Agreement interface name should be MI_Order_Outband1 instead of Z_SAP_ECC_00 , 1.0 of accenture

Check in MONI for this how it is interpreting at runtime after this

Rajesh

[mrahhaoui]

Rajesh ,

It's an error type, the interface is MI_Order_Outbound1.

Do you have an idea?

[mrahhaoui]

In Moni, I have

@DF\QProcessed successfully@ @8Y\QAcknowledgment contains system errors

______________________________________________________________________________

My First Line In Black Flag

Sender Service: Sender Namespace: Sender Interface:

Z_SAP_ECC_00_BS http://accenture.com/PI01/Idoc MI_Order_Outbound1

Recever Service: Receiver Namespace: Receiver Interface

BS_ER6CLNT001 urn:sap-com:document:sap:idoc:messages CREMAS.CREMAS05

CENTRAL AENGINE IDOC @DF\QMessage successful on outbound side @ 1F8ADE1BD6DC4B20236FE321F9837064 001 Asynchronous "Current Status"

-

---

The Second Line In RedFlag

@F1\QSystem Error - Manual Restart Possible@ @8Y\QAcknowledgment contains system errors @

Sender Service: Sender Namespace: Sender Interface:

BS_ER6CLNT001 urn:sap-com:document:sap:idoc:messages CREMAS.CREMAS05

Edited by: rahhaoui mohamed on Feb 11, 2009 11:58 PM

[Former Member]

Your scenario is File to idoc right?

In that an ack will not be sebt by default only in case of idoc to ..... ack will be sent back to sender R/3

May be in your case receiver R/3 is sending some ack with batch program or schedule job,check it out in receiver R/3

HTH

Rajesh

[mrahhaoui]

Hi Rajesh,

Indeed my scenario is File To Idoc. What is strange is when I check in Monitor an Idoc number is created but when I go in the transaction WE05 i don't find any Idoc with this number.

Could you please give the transaction to check the schedule job.

I'm a rookie in XI.

Regards,

Mohamed.

[former_member181955]

Hi

Pls check this service also in SICF:

default_host>sap>xi-->simulation

Thanks

Prasad Nemalikanti

[Former Member]

Hi,

Bounce the Java stack, it should solve your problem.

Regards,

Karna....

[Former Member]

Hi,

In your Receiver Determination are you able to see your Business System when you take F4 help?

If yes then from menu "Environment --> Clear SLD Data Cache".

And if not then go to "Objects" Tab in your ID and expend the Business System and see if your business system exists there, if not then right click on Business System and assign it and again do "Environment --> Clear SLD Data Cache".

Regards,

Sarvesh

[Former Member]

Try as Doss Said, if it doesn't work then reactivate your Receiver Determination. just edit the Description of the Receiver Determination, save and activate and do complete cache refresh. sometimes this will help.

Karna...

[agasthuri_doss]

Hi,

1) Check Cache is Upto date ( tcode- sxi_cache )

2) Check Whether the Receiver Determination is in the respective Scenerio, Else go to - Object & add to your Scenerio

Cheers

Agasthuri Doss