Mapping in Soap

Is there any different to the mapping in SOAP and NOSOAP mode
Thanks

Hi,
No there is no specific format for mapping SOAP or NonSOAP message types.
Normally SOAP related Message Type contains the the Header structure for Header details and then SOAP body.
Your incoming message does not have to follow a specific structure. But you have to take care that your Message Mapping fits to the incoming structure. Especially namespaces are frequently causing problems there.
When you reate a test instance in the test tool of your mapping you'll find an example for a message that can be mapped at runtime.
If by SOAP you mean WSDL then WSDL uses XSD (schema)
to define the data types of the arguments used
but WSDL and XSD are a little bit different things
Data types are used in accordance with SOAP specifications. In the document style, XML documents are exchanged. The data types are defined with the help of the XML schema.
Refer
http://help.sap.com/saphelp_nw04s/helpdata/en/2b/036829d238dc46bad91bff1563e183/frameset.htm
Thanks
swarup
Edited by: Swarup Sawant on Feb 21, 2008 7:07 AM

Similar Messages

Handling/Mapping a SOAP response message back to the RFC request Message

Hi
I was wondering if you could kindly offer some advice on how to handle the SOAP response back to an RFC in a RFC>SOAP>RFC.Response scenario. When executing an RFC function module that triggers a message to XI, the outbound message seems to process successfully, however, there is an error in the response message. I am not sure how to map the response back to the function module response message because it looks like the response payload is empty. It is also strange that the interface seems to run in synchronous mode despite being configured as an asynchronous interface. If it ran in asynchronous mode, there would not be a problem because we actually do not need a response back. The interface also runs perfectly when executing it from the Runtime Workbench, and it also runs in asynchronous mode as it should.
I would really appreciate any suggestions on how to solve this problem.
Thank you,
Brendon

Hi Reyaz,
This is actually an RFC-->SOAP scenario where the message structure of the source and target systems are different. We don't actually need a reponse back from the SOAP system. I was wondering if you perhaps know how we can cancel the Response response back to the requestor or at leaset map the SOAP response back?
The interface runs perfectly in asynchronous mode when executing it from the Runtime Workbench in the test section, but it runs in synchronous mode for some reason when executing the RFC function call in SAP.
Thank you,
Brendon

XSLT mapping with SOAP Envelope

Hi
I'm trying map SOAP response (with Envelope) to pick two values into the target. Here's the data:
Source (with data):
<?xml version="1.0"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
     <soap:Body>
          <EnumerateResponse xmlns="http://www.approva.net/BizRights/Services">
               <EnumerateResult>
                    <TaskID>-1</TaskID>
                    <Result>FinishedSuccessfully</Result>
                    <StatusInfo/>
               </EnumerateResult>
               <pageObject>
                    <startIndex>0</startIndex>
                    <pageSize>10</pageSize>
                    <totalRows>1</totalRows>
                    <moreRecords>false</moreRecords>
                    <rowsReturned>1</rowsReturned>
               </pageObject>
               <xmlObjects>(large string of valid data in here)</xmlObjects>
          </EnumerateResponse>
     </soap:Body>
</soap:Envelope>
Target:
Only need Result and xmlObjects into target.
Mapping:
<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
     <xsl:template match="/">
          <poll_status_resp_r3>
               <Result>
                    <xsl:value-of select="EnumerateResponse/Result"/>
               </Result>
               <xmlObjects>
                    <xsl:value-of select="EnumerateResponse/xmlObjects"/>
               </xmlObjects>
          </poll_status_resp_r3>
     </xsl:template>
</xsl:stylesheet>
The values are not getting picked-up into the target.
What am I missing here?
Any help is appreciated.

Hi,
Save the following XSL file as RSpace.xsl
<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" indent="no"/>
<xsl:template match="/|comment()|processing-instruction()">
    <xsl:copy>
      <xsl:apply-templates/>
    </xsl:copy>
</xsl:template>
<xsl:template match="*">
    <xsl:element name="{local-name()}">
      <xsl:apply-templates select="@*|node()"/>
    </xsl:element>
</xsl:template>
<xsl:template match="@*">
    <xsl:attribute name="{local-name()}">
      <xsl:value-of select="."/>
    </xsl:attribute>
</xsl:template>
</xsl:stylesheet>
Zip it and import it under Imported Archive.
In the interface mapping click "+" to add one more mapping.
Use this XSL as first mapping and your XSL mapping as the second mapping.
In your XSLT mapping you can use the XPath as
"Envelope/Body/EnumerateResponse/Result".
I mean remove the namespace and use the XPATH.
Thanks,
Prakash

MAPPING JCO_COMMUNICATION_FAILURE (SOAP to RFC scenario)

Hi,
Our system is PI 7.1 EHP1 and the scenario is to SOAP to RFC (Synchronous). I have imported the RFC into ESR and used it as data type for Outbound interface for SOAP.
Initially i havent created any mapping because all Interface fields are same (name and type) with RFC because i have used RFC as data type. When we have tested the integration via SOAPUI we have seen that the request message wasn't transferred to RFC but the response was transferred from RFC to SOAP response. Could it be a bug? or is it normal behaviour?
Later, i have created a graphical mapping without any data conversion etc.. It is just mapping. This time it transferred the request and response as well.
When we have started stress test on a PI system (6000 SAPS), the PI JAVA stack started to use %100 of CPU. We have processed 100 message per minute. After 20 minutes, Java stack of PI has crashed and restarted.
Our plan is to process message more then this test numbers. Possibly it is approx 400 message per minute.
I have found below errors on RWB (approx 250 message have below errors).
How this high CPU consumption can be resolved?
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>
<SAP:P1>Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=67</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>"COMMUNICATION FAILURE" during JCo call. Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=67</SAP:Stack>
</SAP:Error>
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>
<SAP:P1>connection to partner 'loopback:0' broken / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 th</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>"SYSTEM FAILURE" during JCo call. connection to partner 'loopback:0' broken / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 th</SAP:Stack>
</SAP:Error>
Kind regards,
Altuğ Bayram

Hi,
Connection between ABAP and JAVA has been broken...thats the reason for the JCO_COMMUNICATION Error
you need to either restart the java or have a look at the RFC Connection JCO_AI_CONNECTION...
re you making use of AAE for this scenario..which can improve the performance than using classic scenario.
performance depends on the hardware of the server also...
Check the sizing Guide of the PI 7.1 on SDN.
Check the below link it may help you..
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f0b96675-87cf-2c10-b489-dee0ac03f782
HTH
Rajesh

No mapping logic : soap to proxy scenario

Hi,
I have a soap to proxy scneario with no mapping logic.wanted to confirm certain things.
Wanted to confirm certain things.
1) So i can exclude mapping and interface mapping step since i just need to pass value to proxy ?
2) in interface determination ,what i need to provide for interface mapping ?
3) sync proxy will be generated from one outbound message interface "( there will be only one outbound message interface which will be synchronous : which will be synchronous ?
4) in receiver business system , i need not put any message interface since we only have one outbound sync message interface
Thnx

how many message interfaces wil be needed for synchronous scneario without mapping ?
Two....one for Sender (Outbound) and one for receiver (Inbound)
in case ur answer is 2 for above ? proxy needs to be generated from outbound or inbound interface?
For your SOAP --> XI/ PI --> PROXY, scenario the proxy should be generated for the inbound interface
1) So i can exclude mapping and interface mapping step since i just need to pass value to proxy ?
If both the source and target structures are the same , then you do not need to perform mapping....do not create message and Interface mapping .....you should however create Interface Determination with appropriate Source and Target interfaces.
2) in interface determination ,what i need to provide for interface mapping ?
Nothing.....including a mapping is not mandatory.
4) in receiver business system , i need not put any message interface since we only have one outbound sync message
interface
The message interface needs to be associated with the Business System.....it will be the inbound interface for SOAP --> XI --> PROXY scenario.
Regards,
Abhishek.

Fault Message Mapping for SOAP Scenario

Hi ,
I have configured a Proxy to SOAP synchronous scenario. The scenario is working fine. Now I need to map the fault message and display the message in SAP in case of any errors. I have used the standard Fault message. But I dont have any message from the WSDL which I can map to the standard fault message. Is it that we need to tell the wenservice team to modify the WSDL to include the fault message or is there any other way out to acheive the same.
Thanks
Amit

>>> Is it that we need to tell the wenservice team to modify the WSDL to include the fault message or is there any other way out to acheive the same?
Fault message is to provide meaningful message to the other end if there is a validation error or business exceptions or so...
a) You are importing WSDL of the third party and using it in soap receiver target side.
b) Normally it is best practice to create a WSDL which contains request, response and fault message. if your wsdl has fault message type declared then you can map the wsdl fault message with your proxy side fault message(which you can create). Please note you rely on the third party wsdl. Third party WSDL must have application logic coded to support fault message in case of application error occurs. Example if there is a validation that does not go through then their application logic must populate data in the fault message of wsdl. Then only if we map the wsdl fault msg to our proxy fault msg, we get meaningful fault details.
If your target WSDL does not support fault mesg, it is not going to be helpful at all.

Mapping Design - SOAP body content needs to be different between test and production

Hello,
We are integrating with a 3rd party SOAP receiver who uses the same web service URLS for test and production.
So to differentiate they exposed 2 web services which do the same thing but have different root and payload node names...along with account details.
For example, for production our SOAP XML must follow pattern like:
<Envelope>
<Body>
<appRequest>
<userID>produser</userID><password>prodpwd</password>
<appPayload>
<?xml>
blah blah this XML is the same between test and production
</xml>
</appPayload>
etc
But for their testing we must use:
<Envelope>
<Body>
<appRequestTest>
<userID>testuser</userID><password>testpwd</password>
<appPayloadTest>
<?xml>
blah blah this XML is the same between test and production
</xml>
</appPayload>
etc
So I'm trying to think of a good way to handle this difference in one set of mappings that we can use in our 3 PI platforms Dev / Test / Prod
Since these differences are in the SOAP Body does it need handled in mapping or is there a way to handle it in the Adapter Config which is naturally different between our environments (mapping we like to keep the same).
What is a smart way to handle this scenario?
Many thanks,
Aaron

I second Artem when he states that this is a bad design decission from the caller's side.
However this is not gonna help you in the current situation, right?
The problem you are facing is that by poor design the message does not have a root node which you may use to handle occurences. Let me explain further
You would be good if prod message looked like so
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header/>
<soapenv:Body>
<appData>
   <appRequest>
   </appRequest>
</appData>
</soapenv:Body>
</soapenv:Envelope>
and test message looked like so
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Header/>
<soapenv:Body>
<appData>
   <appRequestTest>
   </appRequestTest>
</appData>
</soapenv:Body>
</soapenv:Envelope>
--> Then you would have been able to specify occurence of <appRequest> and <appRequestTest> as 0..1
So I think you have (besides what Artem already pointed out) 2 other options:
1. activate "do not use SOAP envelope" on sender SOAP channel and then designing the data types like above
2. Use HTTP instead of SOAP adapter and designing data types like above
Hope I didn't miss something crucial :-)
Cheers
Jens

Message mapping: SOAP Receiver to IDOC Sender

hi,
i have an idoc sent to SOAP receiver. SOAP Response will have only the "Status code" and the "Reason of failure".
IDOC Sender will have the PO Number and the Vendor Name to which we are sending.
The SOAP Response will not have the PO Number and the Vendor Name.
How can i have the Reason of failure, PO Number and Vendor in one message type?
Thanks in advance,
Tirumal

Praveen -
Thanks for the response and appreciate your observation.
Very tight deadlines with the client and have to finish lot of tasks in short time so putting hands in everything.
There are lot of vendors who run their proprietary web services. So cannot change their stuff.
How would i map the SOAP request to the SOAP Response since some information is in one message type and other half of information available in other message type.
I created a SOAP Response Type with the "Reason Code" information.
I created another message type with all the information that i want.
How would i map the SOAP Request to the SOAP Response msg type and the other message type.
Let me know.
Thanks in advance,
Tirumal

Mapping SOAP Fault Message on PI

Hi there,
I'm trying to map a SOAP Fault Response From a Legacy system on PI, but i have some doubts on how to create the Data Type and the fault message Type,
Basically the response will look like this:
<SOAP-ENV:Body>
   <SOAP-ENV:Fault>
      <faultcode>SOAP-ENV:Client</faultcode>
      <faultstring>Data failed validation</faultstring>
      <detail>
           <fault xsi:type="ns1:Fault">
                <ns1:code>1002</ns1:code>
                <ns1:errorMessage>Data failed validation</ns1:errorMessage>
                <ns1:detailMessage>Invalid (does not exist) Zone Identity...</ns1:detailMessage>
           </fault>
      </detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
so basically i defined a data type detail ( named detail aswell in pi ), with a fault element and code errorMessage and detailMessage xsd:String attributes ( i dont know what to do with that ns1 xsi type )
but when i want to creat the whole message PI only allows me to have 1 outter element like this:
<FaultMessage>
   <faultcode>
   <faultstring>
   <detail>
so pretty much i want to have a data type with 4 independent elements cause i know the SOAP-ENV tags wont get to the mapping, im almost sure i'm missing something very dumb here but i dont see it ,
Thanks in advance for all the help you guys can provide,
Regards,
Roberto.

Thanks for the documention it was really helpful,
now i have another problem, i alredy created the data type for the detail tag to match the soap response, but when creating de Fault Message Type on the Data Type Used area, PI inserts me some standard data that is mandatory and does not correspond with the structure im going to receive, it only allows me to import the detail data type as Additional data :S.
Regards,
Roberto.

SOAP Header in SOAP Receiver adapter

Hi All,
I am doing a Proxy to Webservice scenario where webservice requires the SOAP request as below.
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header>
        <mh:CustomHeader xmlns:mh="http://schemas.test.com/customHeader">
            <mh:MessageData>
                <mh:MessageId>12345</mh:MessageId>
                <mh:Timestamp>2004-06-09T14:41:44Z</mh:Timestamp>
            </mh:MessageData>
        </mh:CustomHeader>
        <wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/04/secext">
            <wsse:UsernameToken>
                <wsse:Username>test</wsse:Username>
                <wsse:Password>test123</wsse:Password>
            </wsse:UsernameToken>
        </wsse:Security>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
    </SOAP-ENV:Body>
Need your help to understand how can we achieve this using Standard SOAP adapter to customize the Header part as it requires to include "<mh:CustomHeader " & "UsernameToken".
Or Do i need to go for adapter module development to create this SOAP request.
Please provide your suggestion to achieve this scenario.
Thanks & regards
Ashwin
Edited by: ashwin dhakne on May 17, 2010 5:32 PM

Hi all,
Created a below target payload in a message mapping with SOAP Header & Body part as per the requirement.
In SOAP receiver communication channel, checked the option " Do Not Use SOAP Envelope".
But while executing an sceanrio, i am facing an error in SOAP receiver channel as Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
And if i don't check the option " Do Not Use SOAP Envelope" it gives an error as
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Unable to obtain service binding,error=Payload Envelope is not a known message for TestWebserviceService.
Please provide your suggestions to handle this issue.
<?xml version="1.0" encoding="UTF-8" ?>
<ns1:Envelope xmlns:ns1="http://schemas.test.com/CustomrHeader">
<ns1:Header>
<ns1:CustomrHeader>
<ns1:MessageData>
<ns1:MessageId>Constant</ns1:MessageId>
<ns1:Timestamp>Constant</ns1:Timestamp>
</ns1:MessageData>
<ns1:Security>
<ns1:UsernameToken>
<ns1:Username>Constant</ns1:Username>
<ns1:Password>Constant</ns1:Password>
</ns1:UsernameToken>
</ns1:Security>
</ns1:CustomrHeader>
</ns1:Header>
<ns1:Body>
<ns1:Details>
<ns1:Information>
<ns1:Title>Test</ns1:JobTitle>
</ns1:Information>
<ns1:Contacts>
<ns1:Street>Test Drive</ns1:Street />
</ns1:Contacts>
</ns1:Details>
</ns1:Body>
</ns1:Envelope>
Thanks
Ashwin
Edited by: ashwin dhakne on May 18, 2010 5:47 PM
Edited by: ashwin dhakne on May 18, 2010 5:48 PM
Edited by: ashwin dhakne on May 18, 2010 5:48 PM

Query reg adding custom tags in SOAP Header - AXIS Receiver Adapter

Hi All,
I need to send custom tags as mentioned below to my traget webservice application. I think I can do this with Receiver AXIS adapter but not sure how it can be done. Can any of you suggest?
                                              <WSContext>
               <FromAppId>ABC</FromAppId>
               <ToAppId>XYZ</ToAppId>
          </WSContext>
Thanks,

If you want to add custom tags in the soap header, one possible solution is use XSLT mapping or Java mapping to create header first then do message mapping for mapping the payload structure between your source and target as usual.
So in operation mapping you sequence mapping like this... first XSLT mapping for custom tags for the SOAP Header followed by payload mapping.
Hope that helps.
Search SDN for XSLT Mapping for soap header. Already we have handled these issues.

SOAP Lookup in PO 7.30 Single Stack.

Hi,
I am creating a scenario from HTTP to File . In between Message Mapping has SOAP Lookup .
But While I executing the Sceanrio, I am facing some error .
Now While reading lots of Blogs over Internet , Some of them pointed towards Creating a Dummy ICO (mandatory in PI 7.30 ) for SOAP Lookup.
So Now my Question are :
1. Why are we creating this Dummy ICO ?? what is the purpose ??
2. How do we create it ?? - Need to know abt Sender Service Interface , Sender Communication channel , Receiver Service Interface ??? What would be these values while creating a Dummy ICO ???
Regards
PS

Hi, the dummy ICO is actually not needed for the lookup, but may fix a bug as stated in your previous thread http://scn.sap.com/message/14054811#14054811 as well as it is meant to test and verify that your SOAP receiver actually works.
Did you follow SAP Help Using the Lookup API in a Message Mapping, especially using a mapping parameter of type Adapter and using the parameter as demonstrated in Implementing Lookups Using SystemAccessor?
I see in your previous thread Error while SOAP LookUp in PI 7.3 Single Stack. that you hardcoded the channel name and business component to retrieve the channel
Channel channel = LookupService.getChannel("BC_Successfactors_Two_D","CC_SOAP_Receive_SessionCreate");
Implement as recommended by SAP Help (above links) may be it solves your problem.

Same interfaces - is mapping needed?

Hi guys,
I have a lot of integration scenarios with soap->XI>proxy and I don't need mapping, because soap messages are quivalent to proxy ones.. Is it needed to cerate message mapping and interface mapping, although the messages have the same structure? I think, it must decrrese the prformance.. Is there some way, how to ommit it?
Thanx for answer, Olian

hi Olian,
As per my knowledge you will not require mapping.
But one thing i can tell you that if you will do the mapping then also it will not reduce your performance
Regards,
Hetal

SOAP Envelope encodingStyle

Hi experts,
I have a PI SOAP Receiver, sending to a Java Powerbuilder app. I am getting an HTTP 200, but with an error message in SXMB_MONI:
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: java.lang.NullPointerException; HTTP 200 OK</SAP:AdditionalText>
When I execute the same scenario using soapUI instead of PI, using the same SOAP Payload, I get no SOAP body, only this HTTP Response (HTTP 200 OK as well):
" No mapping found for 'class java.lang.String' using encoding style 'http://xml.apache.org/xml-soap/literalxml' "
When I change the Payload slightly in soapUI, ie. adding an encodingStyle attribute to the SOAP Envelope, I get the expected response message ("Test OK").
To summarize:
PI sends this SOAP Envelope, which the remote app cannot accept (no mapping found):
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
When the SOAP Envelope is modified like below, the test is ok:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
Any ideas how I can add an encodingStyle attribute ?
kr,
Peter Glas

An sdn search gave me this thread to create custom SOAP envelop
Generating SOAP Envelope when DO NOT USE ENVELOPE option is marked

Fault Mapping to RFC

Hello,
I would like to call a webservice from a RFC Function module. The funtcion module stub has no declared exceptions, but a return structure which should return the errors. Is it possible to map a SOAP-Fault message to this return structure which is in the normal response of the message? I read some blogs about handling SOAP errors, but these errors were always mapped to exceptions.
regards,
Jens

Why dont you define the return strucuture in PI and use it instead of Fault message? That would be an easier solution if all that you want to do is return some response..!!
VJ

Mapping in Soap

Similar Messages

Maybe you are looking for