IDOC - SOAP scenario

[Former Member]

Hi Guys,

I have configured the IDOC-SOAP scenario and i am sending to the target business partner with the soap receiver adapter.

I did not get any wsdl from the business partner instead i got the xml structure, target url and soap action. I have created a xsd for the given xml and send the data to the business partner.

The data is reacing the target system but the xml document has error saying "invalid at the top level of the document" and no xml is seen. I also get an acknowldegment error in sxmb_moni as

OUTBINDING CO_TXT_Routing_Back_Error

Error occured during back routing, error in communication channel

any help would be appreciated

Thanks,

Raj

[Former Member]

Hi,

the XML structure which you got - is it the WSDL document of your SOAP service........if not, then ask your SOAP application to provide the WSDL of the web-service and then save this as a WSDL file in your local system............then make a external definiton using this WSDL in IR.......then do the mapping and re-execute your scenario...........

Regards,

Rajeev Gupta

[Former Member]

Hi Raj,

if my understanding is correct, By default SOAP will be a Sync call so you should import the WSDL of your target business partner, in which the request and response structure would be defined from that XI will use the sender details to get the response back.

I guess your problem will be solved by importing the WSDL of your target business partner.

Regards,

Karan.

[Markus7]

I think this comes because XI requests Acknowledgement-IDocs by default. In many cases nobody processes these IDocs and so you get this error. Have a look at OSS-note 777175:

You are using Exchange Infrastructure 3.0 and receive IDocs using the IDoc

adapter. You want to be able to request acknowledgments separately in the

XI for each sending system and interface. In the IDXNOALE exception table,

you can deactivate acknowledgments for certain systems or interfaces.

Previously, you could only maintain the table with transaction SE16.

Report IDX_NOALE is delivered with Support Package 10. With the report, you

can add, delete and display table entries.

Report IDX_NOALE is extended with additional functionality as of Support

Package 11. This allows a sender system to request or deny acknowledgements

for all message types centrally. You can set exceptions to this central

setting by message type. Generic exceptions (for example, message type

'ORD*') are not supported. Entries that are already present in the table

are unchanged.

To perform these activities, you need the authorization to maintain IDoc

metadata (Object 'S_IDOCMETA' ID 'ACTVT' FIELD '02').

Hope this helps.

[Markus7]

I think this comes because XI requests Acknowledgement-IDocs by default. In many cases nobody processes these IDocs and so you get this error. Have a look at OSS-note 777175:

You are using Exchange Infrastructure 3.0 and receive IDocs using the IDoc

adapter. You want to be able to request acknowledgments separately in the

XI for each sending system and interface. In the IDXNOALE exception table,

you can deactivate acknowledgments for certain systems or interfaces.

Previously, you could only maintain the table with transaction SE16.

Report IDX_NOALE is delivered with Support Package 10. With the report, you

can add, delete and display table entries.

Report IDX_NOALE is extended with additional functionality as of Support

Package 11. This allows a sender system to request or deny acknowledgements

for all message types centrally. You can set exceptions to this central

setting by message type. Generic exceptions (for example, message type

'ORD*') are not supported. Entries that are already present in the table

are unchanged.

To perform these activities, you need the authorization to maintain IDoc

metadata (Object 'S_IDOCMETA' ID 'ACTVT' FIELD '02').

Hope this helps.

[bhavesh_kantilal]

Is the Inbound Message Interface as Asynchronous Message Interface? As Idoc's are asynch, make sure that the inbound message interface is asynch.

Also you are calling a webservice in a asynch fashion and hence the reponse from the webservice needs to be a HTTP 200 with the empty SOAP Envelope. Is the source webservice sending you this? for more info on this check the SOAP adapater FAQ on service market place

Regards

Bhavesh

[Former Member]

HI Bhavesh,

Ya the inbound MI is asynchronus. I am not getting the HTTP 200 but i am getting the error saying there is error in routing the text back.

Thanks,

raj

[VijayKonam]

Could you please provide the error from the RWB-Message Monitoring? THis would probably give more info on the kind of error.

VJ