cancel
Showing results for 
Search instead for 
Did you mean: 

Problem in IDOC to SOAP Scenario

Former Member
0 Kudos

Hi All,

we have an IDOC to SOAP scenario in which we have got WSDL from the client for the targets.. Please let us know the WSDL would be the message type and we need to create interface for it . Also the SOAP header is not appearing in the target xml.

Thanks

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

WSDL would be your message type, import it in external definitions.

Yes you need to create Message interface,

Good links to refer for SOAP

/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1

/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2

Former Member
0 Kudos

Hi my problem is I am not getting SOAP header in the target XML.. Also I am testing the configuration in SAP-PI.

Edited by: vishal gadkari on Aug 21, 2009 3:32 PM

Former Member
0 Kudos

Vishal,

Header and payload are different things. You will not get header in the xml, because SOAP adapter would automatically create the header for your webserive. You dont need to do anythign.

To verify use teh weblog given by prateek and test it.

Regards,

---Satish

Former Member
0 Kudos

Hi ,

This means when the data is sent to the webservice it will contain the SOAP header just that we cannot see it in Moni . Also

What about the acknowledgement . Our message is successfull but with message that awaiting acknowledgement.

What we basically need a synchronous scenario of IDOC to SOAP but the response not going back to SAP-R3 . We recieve the response only in SAP-PI. Saw some blogs but the message is going back to SAP-R3. Please help us on this

Thanks

Edited by: vishal gadkari on Aug 22, 2009 4:15 PM

Former Member
0 Kudos

Import the WSDL as External Definition and this external definition will acts as Message Type in Mapping.

No need to create Message Type.

Same External Definition willl be used in Message Interface.

Regards,

Anurag

prateek
Active Contributor
0 Kudos

we need to create interface for it

Yes.

Also the SOAP header is not appearing in the target xml.

Make sure that in the receiver soap channel, option "Do not use Soap envelop" is not ticked.

Regards,

Prateek

Former Member
0 Kudos

Hi Prateek,

That option is not checked in the channel

Thanks

prateek
Active Contributor
0 Kudos

Are you testing it end to end? Is your receiver system complaining about this?

Have you tried to trace your soap call using TCPGateway?

/people/stefan.grube/blog/2007/03/29/troubleshooting-soap-http-and-mail-adapter-scenarios-with-tcpgateway

Regards,

Prateek