<?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>topic Re: Perform Statement .... in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/perform-statement/m-p/2864856#M671887</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;good&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The structure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;typedef struct {&lt;/P&gt;&lt;P&gt;char * destination;&lt;/P&gt;&lt;P&gt;RFC_MODE mode;&lt;/P&gt;&lt;P&gt;void * connopt;&lt;/P&gt;&lt;P&gt;char * client;&lt;/P&gt;&lt;P&gt;char * user;&lt;/P&gt;&lt;P&gt;char * password;&lt;/P&gt;&lt;P&gt;char * language;&lt;/P&gt;&lt;P&gt;int trace;&lt;/P&gt;&lt;P&gt;} RFC_OPTIONS;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;provides parameters for RfcOpen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Depending on the type of connection, various data have to be supplied to open an RFC connection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are three ways to supply this information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can enter a destination name pointed to an entry in a &amp;#145;saprfc.ini&amp;#146; file which contains the necessary network parameters and RFC-specific parameters for opening the connection at RfcOpen. &lt;/P&gt;&lt;P&gt;You can enter a destination name pointed to an entry in a &amp;#145;sideinfo&amp;#146; file which only contains the necessary network parameters for opening the connection at RfcOpen &lt;/P&gt;&lt;P&gt;In your program you supply all the data needed for opening the connection at RfcOpen.&lt;/P&gt;&lt;P&gt;The first of these methods is recommended (i.e. working with saprfc.ini), because it allows you to use some RFC features today as well as in the future without changing your RFC programs. See sprfc.ini for more details.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_40b/helpdata/es/22/042fe8488911d189490000e829fbbd/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_40b/helpdata/es/22/042fe8488911d189490000e829fbbd/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward point if helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;mrutyun^&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 27 Sep 2007 07:58:41 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-09-27T07:58:41Z</dc:date>
    <item>
      <title>Perform Statement ....</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/perform-statement/m-p/2864853#M671884</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;&amp;lt;b&amp;gt;DATA RFC_OPTIONS LIKE RFCDES-RFCOPTIONS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;RFC_OPTIONS = 'H=%HOST,S=%SID,M=%MANDT,U=%USER,L=%LANGU,Z=%PWD,'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PERFORM REPLACE_STRING USING RFC_OPTIONS '%HOST'   HOSTNAME&amp;lt;/b&amp;gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone explain me how RFC_OPTIONS will be used in USING Clause.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Pranshu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Sep 2007 07:47:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/perform-statement/m-p/2864853#M671884</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-27T07:47:47Z</dc:date>
    </item>
    <item>
      <title>Re: Perform Statement ....</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/perform-statement/m-p/2864854#M671885</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Pranshu,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you pass the variable name RFC_OPTIONS, it actually passes the content in the variable RFC_OPTIONS i.e. 'H=%HOST...... is passed to REPLACE_STRING.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The subroutine REPLACE_STRING will replace %HOST from RFC_OPTIONS with the data which is available in HOSTNAME.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Prashant&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Sep 2007 07:51:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/perform-statement/m-p/2864854#M671885</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-27T07:51:07Z</dc:date>
    </item>
    <item>
      <title>Re: Perform Statement ....</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/perform-statement/m-p/2864855#M671886</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What does ut code in perform Replace_string that can u send that may be it is possible to decide what u r trying to do .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Sep 2007 07:55:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/perform-statement/m-p/2864855#M671886</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-27T07:55:53Z</dc:date>
    </item>
    <item>
      <title>Re: Perform Statement ....</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/perform-statement/m-p/2864856#M671887</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;good&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The structure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;typedef struct {&lt;/P&gt;&lt;P&gt;char * destination;&lt;/P&gt;&lt;P&gt;RFC_MODE mode;&lt;/P&gt;&lt;P&gt;void * connopt;&lt;/P&gt;&lt;P&gt;char * client;&lt;/P&gt;&lt;P&gt;char * user;&lt;/P&gt;&lt;P&gt;char * password;&lt;/P&gt;&lt;P&gt;char * language;&lt;/P&gt;&lt;P&gt;int trace;&lt;/P&gt;&lt;P&gt;} RFC_OPTIONS;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;provides parameters for RfcOpen.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Depending on the type of connection, various data have to be supplied to open an RFC connection.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are three ways to supply this information:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can enter a destination name pointed to an entry in a &amp;#145;saprfc.ini&amp;#146; file which contains the necessary network parameters and RFC-specific parameters for opening the connection at RfcOpen. &lt;/P&gt;&lt;P&gt;You can enter a destination name pointed to an entry in a &amp;#145;sideinfo&amp;#146; file which only contains the necessary network parameters for opening the connection at RfcOpen &lt;/P&gt;&lt;P&gt;In your program you supply all the data needed for opening the connection at RfcOpen.&lt;/P&gt;&lt;P&gt;The first of these methods is recommended (i.e. working with saprfc.ini), because it allows you to use some RFC features today as well as in the future without changing your RFC programs. See sprfc.ini for more details.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_40b/helpdata/es/22/042fe8488911d189490000e829fbbd/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_40b/helpdata/es/22/042fe8488911d189490000e829fbbd/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward point if helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;mrutyun^&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Sep 2007 07:58:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/perform-statement/m-p/2864856#M671887</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-27T07:58:41Z</dc:date>
    </item>
    <item>
      <title>Re: Perform Statement ....</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/perform-statement/m-p/2864857#M671888</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;your responsee do nothing more than confusions ... thanks Mrutun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Sep 2007 08:05:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/perform-statement/m-p/2864857#M671888</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-27T08:05:03Z</dc:date>
    </item>
    <item>
      <title>Re: Perform Statement ....</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/perform-statement/m-p/2864858#M671889</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Prashant .....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Sep 2007 08:20:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/perform-statement/m-p/2864858#M671889</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-27T08:20:46Z</dc:date>
    </item>
  </channel>
</rss>

