<?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: EDI Integration---Using Seeburger Adapter in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/edi-integration-using-seeburger-adapter/qaa-p/8457331#M3007036</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;many discussions on the same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;search in sdn&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jan 2012 09:49:42 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2012-01-05T09:49:42Z</dc:date>
    <item>
      <title>EDI Integration---Using Seeburger Adapter</title>
      <link>https://community.sap.com/t5/technology-q-a/edi-integration-using-seeburger-adapter/qaq-p/8457329</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I have a below requirement.&lt;/P&gt;&lt;P&gt;EDI----&lt;DEL&gt;-&amp;gt;XI&lt;/DEL&gt;--&lt;/P&gt;&lt;HR originaltext="------" /&gt;&lt;P&gt;&amp;gt;SAP and vice versa.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am new to EDI integration,i would like to know the procedure steps to do the above scenario.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;AVR&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jan 2012 09:41:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/edi-integration-using-seeburger-adapter/qaq-p/8457329</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-01-05T09:41:57Z</dc:date>
    </item>
    <item>
      <title>Re: EDI Integration---Using Seeburger Adapter</title>
      <link>https://community.sap.com/t5/technology-q-a/edi-integration-using-seeburger-adapter/qaa-p/8457330#M3007035</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;PI doesnt provide any standard solution when u r dealing with edi messages...in such cases u have to look for out of the box solutions..Seeburger is one of them (adapter module is also an option).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;chk this:&lt;/P&gt;&lt;P&gt;&lt;A href="http://wiki.sdn.sap.com/wiki/display/XI/Seeburger" target="test_blank"&gt;http://wiki.sdn.sap.com/wiki/display/XI/Seeburger&lt;/A&gt;&lt;EM&gt;Suite&lt;/EM&gt;for&lt;EM&gt;SAP&lt;/EM&gt;PI&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_blogpost" href="https://community.sap.com/" __jive_macro_name="blogpost" modifiedtitle="true" __default_attr="50311"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="10917222"&gt;&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jan 2012 09:48:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/edi-integration-using-seeburger-adapter/qaa-p/8457330#M3007035</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-01-05T09:48:23Z</dc:date>
    </item>
    <item>
      <title>Re: EDI Integration---Using Seeburger Adapter</title>
      <link>https://community.sap.com/t5/technology-q-a/edi-integration-using-seeburger-adapter/qaa-p/8457331#M3007036</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;many discussions on the same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;search in sdn&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jan 2012 09:49:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/edi-integration-using-seeburger-adapter/qaa-p/8457331#M3007036</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-01-05T09:49:42Z</dc:date>
    </item>
    <item>
      <title>Re: EDI Integration---Using Seeburger Adapter</title>
      <link>https://community.sap.com/t5/technology-q-a/edi-integration-using-seeburger-adapter/qaa-p/8457332#M3007037</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How you want to communicate with the EDI system... If it is using AS2 adapter, then you need to purchase it from seeburger and configure it in the sender side and receiver side it'll be Idoc adapter. And in the ESR you need to import the xsd of EDI document under external definitions and map it to the idoc.Please refer the below links it may help you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10b17369-9522-2c10-84a6-d75d8a8ace22" target="test_blank"&gt;http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10b17369-9522-2c10-84a6-d75d8a8ace22&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=221354005" target="test_blank"&gt;http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=221354005&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://wiki.sdn.sap.com/wiki/display/XI/Seeburger" target="test_blank"&gt;http://wiki.sdn.sap.com/wiki/display/XI/Seeburger&lt;/A&gt;&lt;EM&gt;Suite&lt;/EM&gt;for&lt;EM&gt;SAP&lt;/EM&gt;PI&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_blogpost" href="https://community.sap.com/" __jive_macro_name="blogpost" modifiedtitle="true" __default_attr="45730"&gt;&lt;/A&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;Priyanka&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jan 2012 09:55:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/edi-integration-using-seeburger-adapter/qaa-p/8457332#M3007037</guid>
      <dc:creator>PriyankaAnagani</dc:creator>
      <dc:date>2012-01-05T09:55:16Z</dc:date>
    </item>
    <item>
      <title>Re: EDI Integration---Using Seeburger Adapter</title>
      <link>https://community.sap.com/t5/technology-q-a/edi-integration-using-seeburger-adapter/qaa-p/8457333#M3007038</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EDI is bit diff than normal scenario.&lt;/P&gt;&lt;P&gt;Here based on the EDI version and signal we need to develope the X2E and E2X mappings by using BIC tool and deploy these files in PI server, this is one time activity.&lt;/P&gt;&lt;P&gt;To generate E2X and X2E mappings check the below link&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00b66651-eeea-2b10-e5a6-8459ec30d948" target="test_blank"&gt;https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00b66651-eeea-2b10-e5a6-8459ec30d948&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Later we need to configure the scenario by using module parameters, for this check the below link&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b17369-9522-2c10-84a6-d75d8a8ace22" target="test_blank"&gt;https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10b17369-9522-2c10-84a6-d75d8a8ace22&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Venkata Ramesh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jan 2012 12:10:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/edi-integration-using-seeburger-adapter/qaa-p/8457333#M3007038</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-01-05T12:10:11Z</dc:date>
    </item>
    <item>
      <title>Re: EDI Integration---Using Seeburger Adapter</title>
      <link>https://community.sap.com/t5/technology-q-a/edi-integration-using-seeburger-adapter/qaa-p/8457334#M3007039</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The question is very generic and should be searched. I am therefore marking it as answered. Try to ask specific doubts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Prateek Raj Srivastava&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jan 2012 05:03:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/edi-integration-using-seeburger-adapter/qaa-p/8457334#M3007039</guid>
      <dc:creator>prateek</dc:creator>
      <dc:date>2012-01-06T05:03:45Z</dc:date>
    </item>
    <item>
      <title>Re: EDI Integration---Using Seeburger Adapter</title>
      <link>https://community.sap.com/t5/technology-q-a/edi-integration-using-seeburger-adapter/qaa-p/8457335#M3007040</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ramesh,&lt;/P&gt;&lt;P&gt;If i have EDI file,what could be the neccesary steps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in Advance,&lt;/P&gt;&lt;P&gt;AVR&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jan 2012 05:07:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/edi-integration-using-seeburger-adapter/qaa-p/8457335#M3007040</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-01-06T05:07:35Z</dc:date>
    </item>
    <item>
      <title>Re: EDI Integration---Using Seeburger Adapter</title>
      <link>https://community.sap.com/t5/technology-q-a/edi-integration-using-seeburger-adapter/qaa-p/8457336#M3007041</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have different types of EDIs are available like ANSI X12, EDIFACT, TRADACOMu2026u2026.&lt;/P&gt;&lt;P&gt;Each EDI type contains different versions. For example take ANSI X12, this contains lot of versions (3050, 4010, 4020, 5010..).&lt;/P&gt;&lt;P&gt;Each EDI version contains many signals (850 - PO, 860 - PO Change, 810 - Invoice....).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We donu2019t know which type of EDI, which version and which signal we are using so instead of providing all X2E and E2X mappings (all types, all versions with all signals), seeburger provided one tool called BIC. By using BIC tool we can generate X2E and E2X mappings based on which type, versions with signal we are using.&lt;/P&gt;&lt;P&gt;Install the BIC tool in any one of the application system, then generate X2E and E2X mappings and deploy those mappings in PI server.&lt;/P&gt;&lt;P&gt;In Com channel configure those in Module tab (for this you can follow the seeburger manuals).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jan 2012 08:59:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/edi-integration-using-seeburger-adapter/qaa-p/8457336#M3007041</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2012-01-06T08:59:40Z</dc:date>
    </item>
  </channel>
</rss>

