<?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: Executing subroutine after commit work, not on commit work in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/executing-subroutine-after-commit-work-not-on-commit-work/m-p/992321#M74526</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;so I guess you would like to perform the routne after to avoid lock conflicts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not sure about that transaction but since you are talking of batch input why not scheduling the BI (via Job scheduling - there are a couple of Function modules to achieve that rather easily) with some kind of delay to avoid these conflicts. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Christian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 04 Aug 2005 12:59:34 GMT</pubDate>
    <dc:creator>ChristianFi</dc:creator>
    <dc:date>2005-08-04T12:59:34Z</dc:date>
    <item>
      <title>Executing subroutine after commit work, not on commit work</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/executing-subroutine-after-commit-work-not-on-commit-work/m-p/992314#M74519</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;I want to execute my sub-routine after commit work, not on commit work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If any one have answer please mail me at  emmanuelevy@gmail.com&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Aug 2005 10:17:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/executing-subroutine-after-commit-work-not-on-commit-work/m-p/992314#M74519</guid>
      <dc:creator>manou_manou</dc:creator>
      <dc:date>2005-08-04T10:17:36Z</dc:date>
    </item>
    <item>
      <title>Re: Executing subroutine after commit work, not on commit work</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/executing-subroutine-after-commit-work-not-on-commit-work/m-p/992315#M74520</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;use the addition ON COMMIT in the perform.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;PERFORM sub_form ON COMMIT.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Aug 2005 10:24:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/executing-subroutine-after-commit-work-not-on-commit-work/m-p/992315#M74520</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-08-04T10:24:46Z</dc:date>
    </item>
    <item>
      <title>Re: Executing subroutine after commit work, not on commit work</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/executing-subroutine-after-commit-work-not-on-commit-work/m-p/992316#M74521</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;yes i know but i need AFTER the commit not BEFORE&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Aug 2005 10:48:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/executing-subroutine-after-commit-work-not-on-commit-work/m-p/992316#M74521</guid>
      <dc:creator>manou_manou</dc:creator>
      <dc:date>2005-08-04T10:48:29Z</dc:date>
    </item>
    <item>
      <title>Re: Executing subroutine after commit work, not on commit work</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/executing-subroutine-after-commit-work-not-on-commit-work/m-p/992317#M74522</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;in which context do you want to do something? I guess, it's not a Z-report, that would be simple.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But it's also not every commit in system. There is no general answer (at least I don't know any), but there might be several options in a special case.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Christian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Aug 2005 10:55:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/executing-subroutine-after-commit-work-not-on-commit-work/m-p/992317#M74522</guid>
      <dc:creator>christian_wohlfahrt</dc:creator>
      <dc:date>2005-08-04T10:55:21Z</dc:date>
    </item>
    <item>
      <title>Re: Executing subroutine after commit work, not on commit work</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/executing-subroutine-after-commit-work-not-on-commit-work/m-p/992318#M74523</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;You can use the level (LEVEL idx) with perform on commit.&lt;/P&gt;&lt;P&gt;Give a high value like 99. This will ensure that your subroutine will be the last one which will be executed from the commit queue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But this will be still in the commit work not after.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Vinod&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Aug 2005 10:57:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/executing-subroutine-after-commit-work-not-on-commit-work/m-p/992318#M74523</guid>
      <dc:creator>Vinod_Chandran</dc:creator>
      <dc:date>2005-08-04T10:57:23Z</dc:date>
    </item>
    <item>
      <title>Re: Executing subroutine after commit work, not on commit work</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/executing-subroutine-after-commit-work-not-on-commit-work/m-p/992319#M74524</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Not sure if this helps you but this event is fired, when commit work is fired. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Christian &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;report test.

class lcl_event_handler definition.
 public section.

    class-methods: on_commit_finished
         for event COMMIT_FINISHED
           of CL_OS_TRANSACTION_END_NOTIFIER.
endclass.

set handler lcl_event_handler=&amp;gt;on_commit_finished.

commit work.

class lcl_event_handler implementation.
 method on_commit_finished.
  break-point.
 endmethod.

endclass.&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But check also oss note 704577&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Aug 2005 11:45:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/executing-subroutine-after-commit-work-not-on-commit-work/m-p/992319#M74524</guid>
      <dc:creator>ChristianFi</dc:creator>
      <dc:date>2005-08-04T11:45:07Z</dc:date>
    </item>
    <item>
      <title>Re: Executing subroutine after commit work, not on commit work</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/executing-subroutine-after-commit-work-not-on-commit-work/m-p/992320#M74525</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks for your answer , but i have a user exit before the commit of sap standard .&lt;/P&gt;&lt;P&gt;and there aren't user exit after .&lt;/P&gt;&lt;P&gt;it's about transaction vl32n . i need to use batch input after the commit .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Aug 2005 12:33:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/executing-subroutine-after-commit-work-not-on-commit-work/m-p/992320#M74525</guid>
      <dc:creator>manou_manou</dc:creator>
      <dc:date>2005-08-04T12:33:11Z</dc:date>
    </item>
    <item>
      <title>Re: Executing subroutine after commit work, not on commit work</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/executing-subroutine-after-commit-work-not-on-commit-work/m-p/992321#M74526</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;so I guess you would like to perform the routne after to avoid lock conflicts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not sure about that transaction but since you are talking of batch input why not scheduling the BI (via Job scheduling - there are a couple of Function modules to achieve that rather easily) with some kind of delay to avoid these conflicts. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Christian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Aug 2005 12:59:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/executing-subroutine-after-commit-work-not-on-commit-work/m-p/992321#M74526</guid>
      <dc:creator>ChristianFi</dc:creator>
      <dc:date>2005-08-04T12:59:34Z</dc:date>
    </item>
  </channel>
</rss>

