Showing results for 
Search instead for 
Did you mean: 

SOAP BODY data to be Put into SOAP Header

Former Member
0 Kudos

Hi All,

Could you kindly help me out in this issue?

Basically our Requirement is to send the UserID and Password stored in

the R/3 system to the 3rd Party Server as a part of the SOAP Header .

Presently I am using a Message Interface which takes the parameters

UserID and Password and hence its placing them in the SOAP BODY which in

turn in resulting in Rejection of the data sent being us. So I guess we

have to do some take out these parameters from Message Interface and

try out something else.

So Could you help us out in this issue since we are stuck and hence not

able to proceed any further.

Here are some Details :

Here is the extract from the XML File:

A) Format in XI

<?xml version="1.0" encoding="UTF-8" ?>

- <ns1:DPSrequestToken xmlns:ns1="">

- <Username>




- <DPSrequestToken>





B) The way the file needs to be sent to the 3rd party server

<SOAP-ENV:Envelope xmlns:SOAP-ENV="" xmlns:SOAP-ENC="" xmlns:xsi="" xmlns:xsd="">

xmlns:SOAP-ENC="" xmlns:xsi="" xmlns:xsd="">


<wsse:Security xmlns:wsse="">








<m:DPSrequestToken xmlns:m="">


<m:vendorID>your 4 digit vendorID</m:vendorID>




Basically as mentioned above


<Password>p2ssword</Password> ,Tokens should be sent in the SOAP

Header which is now being sent in the Body and hence causing problems.

Do get back to me in case you need any clarifications on this issue.

Best Regards,


Message was edited by: Chandan A C

Accepted Solutions (0)

Answers (2)

Answers (2)

Active Contributor
0 Kudos

see this --> page 2


Former Member
0 Kudos

Dear Chandan,

Did you got any progress on this issue?

I am facing the same problem.

Best regards

Pedro A. Murias

Active Contributor
0 Kudos

Use HTTP adapter instead of SOAP adapter, create the SOAP envelope in mapping.