<?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: SAP ABAP Proxy in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-abap-proxy/m-p/12082361#M1971060</link>
    <description>&lt;P&gt;BAPI_TRANSACTION_COMMIT is very specific to BAPIs (to empty BAPI buffers), so it really doesn't make sense to use it with HTTP proxys. Instead, use simply COMMIT WORK (AND WAIT as you suggest, but I don't even know if HTTP proxies really use Update Tasks).&lt;/P&gt;</description>
    <pubDate>Tue, 10 Sep 2019 07:34:02 GMT</pubDate>
    <dc:creator>Sandra_Rossi</dc:creator>
    <dc:date>2019-09-10T07:34:02Z</dc:date>
    <item>
      <title>SAP ABAP Proxy</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-abap-proxy/m-p/12082359#M1971058</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
  &lt;P&gt;For outbound proxy.&lt;/P&gt;
  &lt;P&gt;While sending data to PI proxy, I am getting "Message recorded, commit missing" message in SXI_Monitor tcode.&lt;/P&gt;
  &lt;P&gt;I also tried with Commit Work - It is not sending the data in Payload.&lt;/P&gt;
  &lt;P&gt;Please help on this issue.&lt;/P&gt;
  &lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2019 06:36:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-abap-proxy/m-p/12082359#M1971058</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2019-09-10T06:36:29Z</dc:date>
    </item>
    <item>
      <title>Re: SAP ABAP Proxy</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-abap-proxy/m-p/12082360#M1971059</link>
      <description>&lt;P&gt;How are you calling the method ? Let me guess.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Possibility 1: If you are calling method in Program/Class/FM.&lt;/STRONG&gt;&lt;BR /&gt;In this case where you are calling outbound method which will send data, add a commit work and wait over there.&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;      "--- Call Commit Work
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
        EXPORTING
          wait = abap_true.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;STRONG&gt;Possibility 2: If you are testing your proxy via tcode: SPROXY.&lt;BR /&gt;&lt;/STRONG&gt;Trigger commit work after your call from Menu "Extras".&lt;/P&gt;&lt;P&gt;&lt;IMG class="migrated-image" src="https://community.sap.com/legacyfs/online/storage/attachments/storage/7/attachments/1726281-commit.jpg" /&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Possibility 3: Calling Method in Update Task&lt;/STRONG&gt;&lt;BR /&gt;If you are calling method in output program or any update task then create an RFC and add code for calling proxy in RFC along with COMMIT WORK AND WAIT and then call the RFC in new task.&lt;/P&gt;&lt;P&gt;Also check queues (SMQ1/SMQ2).&lt;/P&gt;&lt;P&gt;Thanks &lt;BR /&gt;Rameez&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2019 07:20:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-abap-proxy/m-p/12082360#M1971059</guid>
      <dc:creator>rameez_khan</dc:creator>
      <dc:date>2019-09-10T07:20:11Z</dc:date>
    </item>
    <item>
      <title>Re: SAP ABAP Proxy</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-abap-proxy/m-p/12082361#M1971060</link>
      <description>&lt;P&gt;BAPI_TRANSACTION_COMMIT is very specific to BAPIs (to empty BAPI buffers), so it really doesn't make sense to use it with HTTP proxys. Instead, use simply COMMIT WORK (AND WAIT as you suggest, but I don't even know if HTTP proxies really use Update Tasks).&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2019 07:34:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-abap-proxy/m-p/12082361#M1971060</guid>
      <dc:creator>Sandra_Rossi</dc:creator>
      <dc:date>2019-09-10T07:34:02Z</dc:date>
    </item>
    <item>
      <title>Re: SAP ABAP Proxy</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-abap-proxy/m-p/12082362#M1971061</link>
      <description>&lt;P&gt;Hello Sandra,&lt;/P&gt;&lt;P&gt;Yes Commit Work And Wait should be used.&lt;/P&gt;&lt;P&gt;Regarding HTTP proxies, they don't use update tasks but recently we developed and output program attached to output type.&lt;/P&gt;&lt;P&gt;When this output type was called in "Send Immediately" mode then the output program is called in update task. ( that is what I meant by calling method in output program ).&lt;/P&gt;&lt;P&gt;Since we wanted to call interface in output program we created RFC.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2019 09:27:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-abap-proxy/m-p/12082362#M1971061</guid>
      <dc:creator>rameez_khan</dc:creator>
      <dc:date>2019-09-10T09:27:39Z</dc:date>
    </item>
    <item>
      <title>Re: SAP ABAP Proxy</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-abap-proxy/m-p/12082363#M1971062</link>
      <description>&lt;P&gt;Thanks for the quick reply. I used BAPI_TRANSACTION_COMMIT and its working.Thank you..&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2019 09:55:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-abap-proxy/m-p/12082363#M1971062</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2019-09-10T09:55:56Z</dc:date>
    </item>
    <item>
      <title>Re: SAP ABAP Proxy</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-abap-proxy/m-p/12082364#M1971063</link>
      <description>&lt;P&gt;Use COMMIT WORK AND WAIT. Sandra has already pointed out BAPI_TRANSACTION_COMMIT won't make sense to use at this place, although will perform the task.&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2019 09:59:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-abap-proxy/m-p/12082364#M1971063</guid>
      <dc:creator>rameez_khan</dc:creator>
      <dc:date>2019-09-10T09:59:23Z</dc:date>
    </item>
    <item>
      <title>Re: SAP ABAP Proxy</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sap-abap-proxy/m-p/12082365#M1971064</link>
      <description>&lt;P&gt;Please use the COMMENT button for comments, questions, adding details, etc., ANSWER is only to propose a solution, dixit SAP text at the right of the answer area: "Before answering You should only submit an answer when you are proposing a solution to the poster's problem"&lt;/P&gt;</description>
      <pubDate>Tue, 10 Sep 2019 11:48:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sap-abap-proxy/m-p/12082365#M1971064</guid>
      <dc:creator>Sandra_Rossi</dc:creator>
      <dc:date>2019-09-10T11:48:51Z</dc:date>
    </item>
  </channel>
</rss>

