soap TO HTTP

[Former Member]

HI GUYS

NOW I HAVE A PROBLEM

WHEN I DO THE SCENARIO SOAP TO HTTP ,I USE THE SOAPUI TOOL TO TEST IT ,THE RESPONSE SHOW MAPPING ERROR

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP:Body>

<SOAP:Fault>

<faultcode>SOAP:Server</faultcode>

<faultstring>System Error</faultstring>

<detail>

<s:SystemError xmlns:s="http://sap.com/xi/WebService/xi2.0">

<context/>

<code>MAPPING.EXCEPTION_DURING_EXECUTE</code>

<text>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_MM_RESPONSE_: RuntimeException in Message-Mapping transformatio~</text>

</s:SystemError>

</detail>

</SOAP:Fault>

</SOAP:Body>

</SOAP:Envelope>

BUT IN sxi_monitor i copy the response payloads and test it in ir ,it's ok.

so now i don't sure is the daty type Case sensitive.

my response data type is that :

MT_RESPONSE_SEND

ICBCYH

opRep

opName

opResult

Account_num

should the 'opRep' 'opResult ' be Capital ?

PLZ help

[former_member200962]

There is no restriction with the case of the names....the only restriction is that the names should be the same as they are in the sender/ receiver system messages.

If your sender sends message with a field named Name then in XI also your data type should have the (source DT) field as Name only and not name

There seems to be some mismatch between the structures that you are using.....can you list down the steps that you have follwed for this interface?

Regards,

Abhishek.

[Former Member]

Hi,

What is the Request payload you are testing in Soap UI , is it same as the one used by you for the testing in MApping tool.

As its a Mapping error, without much details we will not be able to answer your question.

Please do cross check on the strucutres you use. Have you done any recent changes in the strucutre? If yes then I guess you need to generate the WSDL again in ID(senderAgreement->Display WSDL->save).

should the 'opRep' 'opResult ' be Capital 

You must use exactly same names as your DT in ESR,

Regards,

Srinivas