<?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: function module  SET_ENQUEUE_OWNER in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/function-module-set-enqueue-owner/m-p/9276064#M1723422</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Heidrun,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the &lt;A href="http://help.sap.com/abapdocu_70/en/ABAPCALL-.htm"&gt;SAP documentation&lt;/A&gt; explicitely states that calling c functions is a poor practice. Besides "Cannot be used" is a misleading translation "Mustnot be used" is the correct term.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp; Klaus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 04 Mar 2013 22:09:55 GMT</pubDate>
    <dc:creator>former_member183804</dc:creator>
    <dc:date>2013-03-04T22:09:55Z</dc:date>
    <item>
      <title>function module  SET_ENQUEUE_OWNER</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/function-module-set-enqueue-owner/m-p/9276063#M1723421</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 need the possibility to set the same enqueus used in a transaction also before we execute the transaction with a CALL TRANSACTION in the same report. In another forum for SAP developers I found this solution: &lt;/P&gt;&lt;P&gt;&lt;BR /&gt;1.) before calling the transaction:&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; call 'C_ENQUEUE'&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; id 'OPCODE' field '7'&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; id 'ENQKEY' field &amp;lt;enqueue userid&amp;gt;.&lt;BR /&gt; 2.) export &amp;lt;enqueue userid&amp;gt; to memory&lt;BR /&gt; 3.) Call Transaction .... &lt;BR /&gt;4.) import &amp;lt;enqueue userid&amp;gt; from memory&lt;BR /&gt; 5.) set the imported&amp;nbsp; &amp;lt;enqueue userid&amp;gt; to your current enqueue user id:&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; call function 'SET_ENQUEUE_OWNER'&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; exporting user&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = &amp;lt;enqueue userid&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; usvb&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = &amp;lt;enqueue userid&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; exceptions illegal_input&amp;nbsp;&amp;nbsp; = 1&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; others&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; = 2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Function module SET_ENQUEUE_OWNER was not released for customer development. But SAP still uses it.&amp;nbsp; I tried this solution and it did work. But afterwards I realized a big problem. The system says there is still an enqueue but doesn't display it in SM12. So there is no possibility to delete the enqueue. Was here anyone faced with the same problem and can tell me how I can remove this enqueu? Have I done it wrong or is there a bug fix from SAP?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Mar 2013 20:01:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/function-module-set-enqueue-owner/m-p/9276063#M1723421</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-03-04T20:01:21Z</dc:date>
    </item>
    <item>
      <title>Re: function module  SET_ENQUEUE_OWNER</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/function-module-set-enqueue-owner/m-p/9276064#M1723422</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Heidrun,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the &lt;A href="http://help.sap.com/abapdocu_70/en/ABAPCALL-.htm"&gt;SAP documentation&lt;/A&gt; explicitely states that calling c functions is a poor practice. Besides "Cannot be used" is a misleading translation "Mustnot be used" is the correct term.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp; Klaus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Mar 2013 22:09:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/function-module-set-enqueue-owner/m-p/9276064#M1723422</guid>
      <dc:creator>former_member183804</dc:creator>
      <dc:date>2013-03-04T22:09:55Z</dc:date>
    </item>
  </channel>
</rss>

