cancel
Showing results for 
Search instead for 
Did you mean: 

IDOC error while receiving

Former Member
0 Kudos

Hi Friends,

In my scenario, I have to receive P.O. message from partner in to my R/3 system.

I am using PI 7.1

When partner is sending me message I am getting error , "Only asynchronous processing supported for IDoc adapter outbound processg" in SXMB_MONI

I tried to find solution on sdn, and I got 2 related foroum,

But from this also I am not sure hw can i solve this error.

Please Suggest.

Thanks & Regards,

Brijesh Soni

Accepted Solutions (1)

Accepted Solutions (1)

prateek
Active Contributor
0 Kudos

Which adapter is being used at sender? Check the sender communication channel and make sure that the Quality of Service is seleced as EO.

Regards,

Prateek

Former Member
0 Kudos

Hi Prateek ,

how r u.

actually i had nt created any sender communication channel.

I had created a receiver communication channel with IDOC adapter in which i had given address of my R/3 system, that is port , rfc destination and release.

I had provided partner with my XI address.. on which they are sending me message.

As per my understanding when ever they will send message to XI system, it will send message to R/3 system.

I am not sure I may be wrong,

Quality of service in my case in BE, that i checked in SXMB_MONI. I processed the same message through run time work bench using QOS as EO then it is processing successfuly.

Please suggest..

Thanks & Regards,

Brij...

Edited by: brijesh soni on Jan 21, 2009 12:59 PM

Former Member
0 Kudos

Hello Brijesh,

Check in the SXMB_moni at which step error as occured.

Are you able to receive message in XI it seems you are able to right..

Provide the more error details it may help us

Rajesh

Former Member
0 Kudos

Yeh Rajesh,

I am able to get message in XI, I can the payload in SXMB_MONI. but in sxmb_moni status is error with message "Only asynchronous processing supported for IDoc adapter outbound processg"

as I am using idoc adapter for this,and idoc adapter supports only asyncronous processing.

Is it possible that I can use any other adapter to send message in my R/3 system?

prateek
Active Contributor
0 Kudos

For sync communication you may use RFC adapter or ABAP proxy at receiver.

You haven't yet mentioned the type of sender and the adapter used at sender. Which system is sending data?

Regards,

Prateek

Former Member
0 Kudos

Yeah you can use RFC or Proxy adapter(only WAS >=6.20) to send data to R/3

Rajesh

Former Member
0 Kudos

Sender is BC system and it wll send XML message,

I had provided partner with HTTP link .

I had created one receiver comm channel n had given address of my R/3 system using idoc adapter.

Former Member
0 Kudos

Hi

For Error Only asynchronous processing supported for IDoc adapter outbound

IDOC adapter support asynchronous only,

Check Quality of Service in your sender adapter. Should be EO or EOIO, not BE.

This thread had same problem and resolved :

In Your case QOS is BE. Plz check in your CC if and BE is by default..

If you use BE, HTTP expects a Response back and as IDOC does not support BE, you go the earlier error.

http://help.sap.com/saphelp_nw04/helpdata/en/43/64db4daf9f30b4e10000000a11466f/content.htm

Regards

Abhishek

Edited by: Abhishek Agrahari on Jan 21, 2009 3:14 PM

Answers (3)

Answers (3)

Former Member
0 Kudos

Error solved, now partner will send with quality of service as EO.

Thanks all

shivhare
Active Contributor
0 Kudos

Hi Brajesh,

In place of using IDOC you can also use BAPI for creation of IDOC ........

So when you define synchronous message interface you can output message BAPI_PO_CREATE and input message BAPI_PO_CREATE.Response .....

this is the suggestion otherwise you can fallow up prateek solution

Regards,

Amit

Edited by: Amit Shivhare on Jan 21, 2009 7:03 PM

Former Member
0 Kudos

Hi,

Kindly Check Whether You have mentioned EO or EOIO in Qos(Quality of service) In Communication channel...

NOTE:Idoc supports only asynchronous Communication..........

Edited by: Sainath Chutke on Jan 21, 2009 2:09 PM