cancel
Showing results for 
Search instead for 
Did you mean: 

IDoc Adapter - ATTRIBUTE_BE_NOT_SUPP Async processing

Former Member
0 Kudos

Hello,

I'm trying to establish IDoc communication. Here is the scenario that I need:

<XML Data> --- <SOAP> --> PI Server ( Map XML to IDoc XML) --- <IDoc> --> SAP Retail System

I have the following components set up:

1. Sender SOAP Communication Channel that receives XML - Message Interface "InXML" - Outbound Asynchronous

2. Sender Agreement

3. Map from InXML to OutIDoc. OutIDoc - Message Interface - Inbound Asynchronous

4. Receiver Determination

5. Interface Determination

6. Receiver Agreement

7. Receiver IDoc Communication Channel

8. Business Service for all this

No Integration Scenario.

If I replace item 7 to the FTP for example, everything works just perfect - I send XML it gets Mapped to IDoc and in my FTP I have the IDoc file.

Now, I've asked SAP support specialist to establish communication from PI Server to Retail using IDoc. He send me parameters, which I used for IDoc Communication Channel:

RFC Destination: NX7CLNT800

Port: A000000022

SAP Release: 3 - this is I put myself

But when I run the whole system again, I'm getting the error:

IDOC_ADAPTER ATTRIBUTE_BE_NOT_SUPP - "Only asynchronous processing supported for IDoc adapter outbound processg"

This is very confusing because both my message interfaces are Asynchronous.

Can anyone tell me what I'm doing wrong and why I'm getting this error.

Thanks.

Accepted Solutions (1)

Accepted Solutions (1)

former_member200962
Active Contributor
0 Kudos
8. Business Service for all this

Should it not be Business System for IDOC.....for SOAP it will be Business Service

1. Sender SOAP Communication Channel that receives XML - Message Interface "InXML" - Outbound Asynchronous

Check what is the QoS that is specified in the SOAP Channel.....if it is Best Effort then it will be a cause of the error......change it to Exactly Once (EO).

Regards,

Abhishek.

Edited by: abhishek salvi on Dec 4, 2009 10:29 AM

Former Member
0 Kudos

Thanks a million! This was exactly the problem. Once I changed that to "Exactly Once" it started working perfectly.

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

is the port mentioned here created in the Retail or in the PI system itself. ?

Did you created the RFC destination and Port in PI ...(port should be SAPSYSID) ?

which needs to be provided in the idoc channel...

if not created port and RFC destinations in PI create them and test them...

HTH

Rajesh