<?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: content-transfer-encoding in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/content-transfer-encoding/qaa-p/8986600#M3189494</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI Suman,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unfortunately, we don't have a standard module for this. So, I have to built a custom adapter module.&lt;/P&gt;&lt;P&gt;My requirement was more to set the description of the attachment as in absence of which there is an exception in the target non-SAP system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Vk&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 30 Sep 2014 16:48:52 GMT</pubDate>
    <dc:creator>vk_k3</dc:creator>
    <dc:date>2014-09-30T16:48:52Z</dc:date>
    <item>
      <title>content-transfer-encoding</title>
      <link>https://community.sap.com/t5/technology-q-a/content-transfer-encoding/qaq-p/8986595</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;ECC-Proxy --&amp;gt;PI --&amp;gt;Legacy-RNIF&lt;/P&gt;&lt;P&gt;ECC sends attachment which is base64 encoded and it sends to PI via Proxy.&lt;/P&gt;&lt;P&gt;But in the RNIF message i see that the content-transfer-encoding is Binary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any way to change content-transfer-encoding in PI or ECC ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;VK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 24 Aug 2012 17:09:20 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/content-transfer-encoding/qaq-p/8986595</guid>
      <dc:creator>vk_k3</dc:creator>
      <dc:date>2012-08-24T17:09:20Z</dc:date>
    </item>
    <item>
      <title>Re: content-transfer-encoding</title>
      <link>https://community.sap.com/t5/technology-q-a/content-transfer-encoding/qaa-p/8986596#M3189490</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have fixed this!!!!!!!!!!!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Sep 2012 20:21:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/content-transfer-encoding/qaa-p/8986596#M3189490</guid>
      <dc:creator>vk_k3</dc:creator>
      <dc:date>2012-09-14T20:21:14Z</dc:date>
    </item>
    <item>
      <title>Re: content-transfer-encoding</title>
      <link>https://community.sap.com/t5/technology-q-a/content-transfer-encoding/qaa-p/8986597#M3189491</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you let us know how this was fixed? Adapter module?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Aug 2014 20:28:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/content-transfer-encoding/qaa-p/8986597#M3189491</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-08-21T20:28:41Z</dc:date>
    </item>
    <item>
      <title>Re: content-transfer-encoding</title>
      <link>https://community.sap.com/t5/technology-q-a/content-transfer-encoding/qaa-p/8986598#M3189492</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Sep 2014 16:04:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/content-transfer-encoding/qaa-p/8986598#M3189492</guid>
      <dc:creator>vk_k3</dc:creator>
      <dc:date>2014-09-30T16:04:35Z</dc:date>
    </item>
    <item>
      <title>Re: content-transfer-encoding</title>
      <link>https://community.sap.com/t5/technology-q-a/content-transfer-encoding/qaa-p/8986599#M3189493</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ok, is it a standard adapter module or did you custom build one? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Sep 2014 16:35:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/content-transfer-encoding/qaa-p/8986599#M3189493</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-09-30T16:35:10Z</dc:date>
    </item>
    <item>
      <title>Re: content-transfer-encoding</title>
      <link>https://community.sap.com/t5/technology-q-a/content-transfer-encoding/qaa-p/8986600#M3189494</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI Suman,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unfortunately, we don't have a standard module for this. So, I have to built a custom adapter module.&lt;/P&gt;&lt;P&gt;My requirement was more to set the description of the attachment as in absence of which there is an exception in the target non-SAP system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Vk&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Sep 2014 16:48:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/content-transfer-encoding/qaa-p/8986600#M3189494</guid>
      <dc:creator>vk_k3</dc:creator>
      <dc:date>2014-09-30T16:48:52Z</dc:date>
    </item>
  </channel>
</rss>

