<?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: Inbound interface in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/inbound-interface/qaa-p/2127319#M926899</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi naresh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  while dealing with the RFC or IDoc adapters we no need to create the interfaces either at the sender or receiver side.......&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  because we directly import these interfaces...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Coming to the Asynchronous and Synchronous communication we need to create outbound and inbound interfaces but abstract interfaces comes into picture when dealing with the BPMs......like (file to RFC scenario)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanx,&lt;/P&gt;&lt;P&gt;krish...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 02 Apr 2007 11:19:59 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-04-02T11:19:59Z</dc:date>
    <item>
      <title>Inbound interface</title>
      <link>https://community.sap.com/t5/technology-q-a/inbound-interface/qaq-p/2127313</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;&lt;/P&gt;&lt;P&gt;When there is a Inbound interface existing in XI repository, Do we need a outbound interface on the other side to communicate with it or else it can be done in some other way?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any example scenario to expalin the above case?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Apr 2007 10:49:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/inbound-interface/qaq-p/2127313</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-02T10:49:37Z</dc:date>
    </item>
    <item>
      <title>Re: Inbound interface</title>
      <link>https://community.sap.com/t5/technology-q-a/inbound-interface/qaa-p/2127314#M926894</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Nagesh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP XI scenario must need both inbound and outbound interfaces.&lt;/P&gt;&lt;P&gt;However in certain cases you can directly import xml structure as inbound or outbound interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But interfaces are anyhow necessary.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Shri&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Apr 2007 10:55:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/inbound-interface/qaa-p/2127314#M926894</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-02T10:55:06Z</dc:date>
    </item>
    <item>
      <title>Re: Inbound interface</title>
      <link>https://community.sap.com/t5/technology-q-a/inbound-interface/qaa-p/2127315#M926895</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi naresh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  To send the Source message we need outbound Interface......&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Outbound Message Interface is must.........&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanx,&lt;/P&gt;&lt;P&gt;krish...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Apr 2007 10:56:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/inbound-interface/qaa-p/2127315#M926895</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-02T10:56:09Z</dc:date>
    </item>
    <item>
      <title>Re: Inbound interface</title>
      <link>https://community.sap.com/t5/technology-q-a/inbound-interface/qaa-p/2127316#M926896</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Naresh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  For every inbound interface we need a outbound interface unless it is idoc.If our source is IDoc den no need to create any outbound interface...directly we can use..the idoc segment in message mapping to corresponding message type and similarly it is used with the corresponding inbound message interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Prasanthi.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Apr 2007 10:56:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/inbound-interface/qaa-p/2127316#M926896</guid>
      <dc:creator>prasanthi_chavala</dc:creator>
      <dc:date>2007-04-02T10:56:37Z</dc:date>
    </item>
    <item>
      <title>Re: Inbound interface</title>
      <link>https://community.sap.com/t5/technology-q-a/inbound-interface/qaa-p/2127317#M926897</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;  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are there any dependencies for Using Outbound interfaces and inbound on the following,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.)  Asynchronous and Synchronous communication.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.) Service provider side and Service Consumer side.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Apr 2007 11:06:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/inbound-interface/qaa-p/2127317#M926897</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-02T11:06:31Z</dc:date>
    </item>
    <item>
      <title>Re: Inbound interface</title>
      <link>https://community.sap.com/t5/technology-q-a/inbound-interface/qaa-p/2127318#M926898</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Naresh,&lt;/P&gt;&lt;P&gt;  if u r using BPM then u need to use &amp;lt;b&amp;gt;Abstract interface&amp;lt;/b&amp;gt;along with inbound and outbound interfaces.&lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt; if u r doing &amp;lt;b&amp;gt;asynchr&amp;lt;/b&amp;gt; or &amp;lt;b&amp;gt;synchr &amp;lt;/b&amp;gt;in both cases u need to use inbound and outbound interfaces.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Maheshwari.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        Maheshwari Morbale&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        Maheshwari Morbale&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Apr 2007 11:11:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/inbound-interface/qaa-p/2127318#M926898</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-02T11:11:03Z</dc:date>
    </item>
    <item>
      <title>Re: Inbound interface</title>
      <link>https://community.sap.com/t5/technology-q-a/inbound-interface/qaa-p/2127319#M926899</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi naresh,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  while dealing with the RFC or IDoc adapters we no need to create the interfaces either at the sender or receiver side.......&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  because we directly import these interfaces...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Coming to the Asynchronous and Synchronous communication we need to create outbound and inbound interfaces but abstract interfaces comes into picture when dealing with the BPMs......like (file to RFC scenario)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanx,&lt;/P&gt;&lt;P&gt;krish...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Apr 2007 11:19:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/inbound-interface/qaa-p/2127319#M926899</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-02T11:19:59Z</dc:date>
    </item>
    <item>
      <title>Re: Inbound interface</title>
      <link>https://community.sap.com/t5/technology-q-a/inbound-interface/qaa-p/2127320#M926900</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;To send a message, simply call the outbound interface to which you want to transfer parameters for the request message. Furthermore, on the receiver side, you must implement receiver processing for the inbound interface. Communication can only comprise the transfer of one message, depending on whether the communication is synchronous or asynchronous.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Outbound and inbound interfaces are used to separate (potential) senders and receivers. The interface parameters do not have to match for a message exchange to be possible (but a mapping is required at runtime if they do not). This enables various different senders and receivers to communicate with each other. In particular, this loose coupling also enables you to assign interfaces to each other when one side of the communication must not, or cannot be changed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, an outbound interface can be a message interface for calling an RFC in a 4.6C SAP system. In this call, the RFC has the role of an inbound interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can check out the following link:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/cd/0b733cb7d61952e10000000a11405a/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/cd/0b733cb7d61952e10000000a11405a/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward points if useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;  Sumit Jain&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Apr 2007 11:37:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/inbound-interface/qaa-p/2127320#M926900</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-04-02T11:37:52Z</dc:date>
    </item>
  </channel>
</rss>

