<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Question Re: Issue in synchronous Response Message mapping at Integration Engine in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949222#M3176485</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I guess you can also add an XSLT mapping before your message mapping.&lt;/P&gt;&lt;P&gt;This XSLT should be able to add the namespace, so that your mapping would work correct.&lt;/P&gt;&lt;P&gt;Also, you can remove the &amp;lt;Response&amp;gt; node in your new structure as you already have RESPONSE as the message type.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 19 Sep 2012 13:30:42 GMT</pubDate>
    <dc:creator>zameerf</dc:creator>
    <dc:date>2012-09-19T13:30:42Z</dc:date>
    <item>
      <title>Issue in synchronous Response Message mapping at Integration Engine</title>
      <link>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaq-p/8949214</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My scenario is ECC Outbound Proxy &amp;lt;==&amp;gt; SAP-PI 7.31 &amp;lt;===&amp;gt; WEb Service (WEB Page)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am sending request to Web service of web page by using HTTP_AAE adapter (Get Method).After testing the proxy, I am able to see the succesful &lt;/P&gt;&lt;P&gt;synchronous&amp;nbsp; message in Tx SXMB_MONI of SAP-PI.There is no data/payload in the message.I had the put the trace as 3 in config to check the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/138347" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/138348" width="450" /&gt;&lt;/P&gt;&lt;P&gt;The config I did : &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MT_ECC_Request and MT_WS_Request&lt;/P&gt;&lt;P&gt;MT_ECC_Response and MT_WS_Response&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;SI_ECC_OB:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Request Message : MT_ECC_Request&lt;/P&gt;&lt;P&gt;Response Message : MT_ECC_Response&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;SI_WS_IB:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Request Message : MT_WS_Request&lt;/P&gt;&lt;P&gt;Response Message : MT_WS_Response&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;Message Mapping:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MM_Request&lt;/P&gt;&lt;P&gt;MT_ECC_Request (Source) and MT_WS_Request (Target)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MM_Response&lt;/P&gt;&lt;P&gt;MT_WS_Response (Source) and MT_ECC_Response (Target)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;Operation Mapping:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Request tab: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MT_ECC_Request (Source) and MT_WS_Request (Target)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Response Tab:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MT_WS_Response (Source) and MT_ECC_Response (Target)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I assumed there would be issue in the response mapping , double verified but could not found the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Rebecca Alice&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Sep 2012 13:42:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaq-p/8949214</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-09-18T13:42:30Z</dc:date>
    </item>
    <item>
      <title>Re: Issue in synchronous Response Message mapping at Integration Engine</title>
      <link>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949215#M3176478</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Alice,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The reason for this is that there is a mismatch of the root message name in the webservice response e.g&lt;/P&gt;&lt;P&gt;&amp;lt;RESPONSE&amp;gt; but you are using &amp;lt;ns0:MT_Response&amp;gt;. Please recheck your response message mapping by loading the RESPONSE payload.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Sep 2012 04:12:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949215#M3176478</guid>
      <dc:creator>markangelo_dihiansan</dc:creator>
      <dc:date>2012-09-19T04:12:25Z</dc:date>
    </item>
    <item>
      <title>Re: Issue in synchronous Response Message mapping at Integration Engine</title>
      <link>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949216#M3176479</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I did the response mapping test and I could find the ESR mapping test results produces the tartget structure but without any data.This is basically 1:1 mapping and each mapping is using node function : mapWithDefault&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How to map the source and target structure if there is mismatch in the root node.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;Source structure&lt;/STRONG&gt;&lt;/SPAN&gt; is &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;RESPONSE&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;EXPR&amp;gt;USD&amp;lt;/EXPR&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;EXCH&amp;gt;INR&amp;lt;/EXCH&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;AMOUNT&amp;gt;1&amp;lt;/AMOUNT&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;NPRICES&amp;gt;1&amp;lt;/NPRICES&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;CONVERSION&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;DATE&amp;gt;Fri, 01 Jun 2001 14:06:30 GMT&amp;lt;/DATE&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;ASK&amp;gt;0.02130&amp;lt;/ASK&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;BID&amp;gt;0.02128&amp;lt;/BID&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;/CONVERSION&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;/RESPONSE&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;Target structure&lt;/STRONG&gt;&lt;/SPAN&gt; is &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P class="e"&gt;&amp;lt;?xml version="1.0" encoding="UTF-8" ?&amp;gt; &lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;- &amp;lt;ns0:Messages xmlns:ns0="&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://sap.com/xi/XI/SplitAndMerge"&gt;http://sap.com/xi/XI/SplitAndMerge&lt;/A&gt;&lt;SPAN&gt;"&amp;gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;- &amp;lt;ns0:Message1&amp;gt;&lt;/P&gt;&lt;P&gt;- &amp;lt;ns1:MT_Response_OB xmlns:ns1="urn:curr.exchange.rate.integration.automation"&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;EXPR /&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;EXCH /&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;AMOUNT /&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;NPRICES /&amp;gt; &lt;/P&gt;&lt;P&gt;- &amp;lt;CONVERSION&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;DATE /&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;ASK /&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;BID /&amp;gt; &lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;/CONVERSION&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;/ns1:MT_Response_OB&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;/ns0:Message1&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;/ns0:Messages&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/jiveimages/138665" width="450" /&gt;&lt;/P&gt;&lt;P&gt;Log of mapping test:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;STRONG&gt;13:33:33&lt;/STRONG&gt; Start of test&amp;nbsp; &lt;/P&gt;&lt;UL&gt;&lt;LI&gt; Document start &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Start tag [ns0:Messages] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt; Add raw attribute [ xmlns:ns0="&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://sap.com/xi/XI/SplitAndMerge"&gt;http://sap.com/xi/XI/SplitAndMerge&lt;/A&gt;&lt;SPAN&gt;"] &lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Start tag [ns0:Message1] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Start tag [ns1:MT_Response_OB] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Add raw attribute [ xmlns:ns1="urn:curr.exchange.rate.integration.automation"] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Start tag [EXPR] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Put value [] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Close tag [EXPR] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Start tag [EXCH] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Put value [] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Close tag [EXCH] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Start tag [AMOUNT] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Put value [] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Close tag [AMOUNT] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Start tag [NPRICES] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Put value [] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Close tag [NPRICES] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Start tag [CONVERSION] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Start tag [DATE] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Put value [] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Close tag [DATE] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Start tag [ASK] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Put value [] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Close tag [ASK] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Start tag [BID] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Put value [] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Close tag [BID] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Close tag [CONVERSION] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Close tag [ns1:MT_Response_OB] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Close tag [ns0:Message1] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Close tag [ns0:Messages] &lt;/LI&gt;&lt;LI&gt;&lt;/LI&gt;&lt;LI&gt; Document end &lt;/LI&gt;&lt;/UL&gt;&lt;P&gt; Execution of mapping on server took &lt;STRONG&gt;4&lt;/STRONG&gt; milliseconds&lt;/P&gt;&lt;P&gt;Executed successfully&amp;nbsp; &lt;STRONG&gt;13:33:33&lt;/STRONG&gt; End of test&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P class="e"&gt;&lt;/P&gt;&lt;P class="e"&gt;PLS HELP ME ON THIS!!!!&lt;/P&gt;&lt;P class="e"&gt;&lt;/P&gt;&lt;P class="e"&gt;Regards&lt;/P&gt;&lt;P class="e"&gt;Alice Rebecca&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Sep 2012 10:26:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949216#M3176479</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-09-19T10:26:46Z</dc:date>
    </item>
    <item>
      <title>Re: Issue in synchronous Response Message mapping at Integration Engine</title>
      <link>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949217#M3176480</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you get the wsdl file from web service provider to construct External Definition which can be used in service interface/mapping?&lt;/P&gt;&lt;P&gt;I guess that might solve the issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Sep 2012 10:49:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949217#M3176480</guid>
      <dc:creator>zameerf</dc:creator>
      <dc:date>2012-09-19T10:49:28Z</dc:date>
    </item>
    <item>
      <title>Re: Issue in synchronous Response Message mapping at Integration Engine</title>
      <link>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949218#M3176481</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Instead of using MT_Response_IB, your message type should look exactly like the one below&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;Source structure&lt;/STRONG&gt;&lt;/SPAN&gt; is &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;RESPONSE&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;EXPR&amp;gt;USD&amp;lt;/EXPR&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;EXCH&amp;gt;INR&amp;lt;/EXCH&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;AMOUNT&amp;gt;1&amp;lt;/AMOUNT&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;NPRICES&amp;gt;1&amp;lt;/NPRICES&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;CONVERSION&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;DATE&amp;gt;Fri, 01 Jun 2001 14:06:30 GMT&amp;lt;/DATE&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;ASK&amp;gt;0.02130&amp;lt;/ASK&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;BID&amp;gt;0.02128&amp;lt;/BID&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;/CONVERSION&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;/RESPONSE&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Create a datatype and message type that looks like that, use it in your service interface and response message mapping.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Sep 2012 10:53:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949218#M3176481</guid>
      <dc:creator>markangelo_dihiansan</dc:creator>
      <dc:date>2012-09-19T10:53:30Z</dc:date>
    </item>
    <item>
      <title>Re: Issue in synchronous Response Message mapping at Integration Engine</title>
      <link>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949219#M3176482</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Zameer,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The 3rd party is not SOAP based API. The data can be retrieved through HTTP_AAE Get method.&lt;/P&gt;&lt;P&gt;So there is no WSDL file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I manually created the Response structure based on their response.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the pipeline steps, it fails at the "XML Validation Inbound Channel Response" step.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Alice Rebecca&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Sep 2012 10:55:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949219#M3176482</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-09-19T10:55:36Z</dc:date>
    </item>
    <item>
      <title>Re: Issue in synchronous Response Message mapping at Integration Engine</title>
      <link>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949220#M3176483</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Below is my Target structure as per the source structure. But I don't think this would work as its impossible to create the same structure without the xml tags and namespace in MT and DT editor.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&amp;lt;?xml version="1.0" encoding="UTF-8"?&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;ns0:RESPONSE xmlns:ns0="urn:curr.exchange.rate.integration.automation"&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &amp;lt;Response&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;EXPR/&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;EXCH/&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;AMOUNT/&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;NPRICES/&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;Conversion&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;DATE/&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;ASK/&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;BID/&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;/Conversion&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &amp;lt;/Response&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;/ns0:RESPONSE&amp;gt;&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Alice Rebecca&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Sep 2012 12:28:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949220#M3176483</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-09-19T12:28:54Z</dc:date>
    </item>
    <item>
      <title>Re: Issue in synchronous Response Message mapping at Integration Engine</title>
      <link>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949221#M3176484</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is possible to remove the XML namespace in your message type by:&lt;/P&gt;&lt;P&gt;1. Opening your message type&lt;/P&gt;&lt;P&gt;2. Edit&lt;/P&gt;&lt;P&gt;3. Remove the entry under XML namespace.&lt;/P&gt;&lt;P&gt;4. Save and activate&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Sep 2012 13:17:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949221#M3176484</guid>
      <dc:creator>markangelo_dihiansan</dc:creator>
      <dc:date>2012-09-19T13:17:05Z</dc:date>
    </item>
    <item>
      <title>Re: Issue in synchronous Response Message mapping at Integration Engine</title>
      <link>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949222#M3176485</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I guess you can also add an XSLT mapping before your message mapping.&lt;/P&gt;&lt;P&gt;This XSLT should be able to add the namespace, so that your mapping would work correct.&lt;/P&gt;&lt;P&gt;Also, you can remove the &amp;lt;Response&amp;gt; node in your new structure as you already have RESPONSE as the message type.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Sep 2012 13:30:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949222#M3176485</guid>
      <dc:creator>zameerf</dc:creator>
      <dc:date>2012-09-19T13:30:42Z</dc:date>
    </item>
    <item>
      <title>Re: Issue in synchronous Response Message mapping at Integration Engine</title>
      <link>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949223#M3176486</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rebecca,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why are you building your mapping to include the "mapWithDefault" for the Messages, Message1 &amp;amp; MT_Response_IB nodes?&amp;nbsp; For the mapping of the three levels of the XML that only deal with the structure of the XML content I would simply map 1:1 without using that function.&amp;nbsp; Since this is a nested structure you could be telling the mapping system at runtime to ignore all nested values in the XML.&amp;nbsp; I've never seen the usage of "mapWithDefault" on these nested structures before... merely at the element level to ensure one is created even if the element does not exist in the source.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ryan Crosby&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Sep 2012 15:18:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949223#M3176486</guid>
      <dc:creator>Ryan-Crosby</dc:creator>
      <dc:date>2012-09-19T15:18:47Z</dc:date>
    </item>
    <item>
      <title>Re: Issue in synchronous Response Message mapping at Integration Engine</title>
      <link>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949224#M3176487</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Alice ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope what Mark suggested to remove the XML namespace would help. Yes you may receive warning information once you activate the changes without XML namespace i.e. Using an empty namespace contradicts the WS standard.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can ignore the message and test the response message mapping.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Robinson Thomas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Sep 2012 08:24:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949224#M3176487</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-09-20T08:24:37Z</dc:date>
    </item>
    <item>
      <title>Re: Issue in synchronous Response Message mapping at Integration Engine</title>
      <link>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949225#M3176488</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Mark,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Great !!! Lots of thanks for your input. The issue is solved.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Alice Rebecca&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Sep 2012 08:52:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/issue-in-synchronous-response-message-mapping-at-integration-engine/qaa-p/8949225#M3176488</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-09-20T08:52:31Z</dc:date>
    </item>
  </channel>
</rss>

