<?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: Selection Screen in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/selection-screen/m-p/2629055#M604334</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 apply the changes made to the runtime objects of persistent classes to the actual persistent objects in the database, execute the COMMIT WORK statement. (Alternatively, use COMMIT WORK AND WAIT or SET UPDATE TASK LOCAL). Unless you are executing an object-oriented transaction from within the Transaction Service, you must include the COMMIT WORK statement explicitly in the program. Otherwise, it is encapsulated in the Transaction Service. (If you explicitly include the COMMIT WORK statement as described here, the t op-level transaction runs in compatibility mode).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The function of the COMMIT WORK statement is extended when you use it in conjunction with Object Services. Before COMMIT WORK closes the SAP LUW and triggers an update, it calls internal methods of the Persistence Service. These methods bundle the changes made to managed objects of the Persistence Service and pass them to a special update function module using CALL FUNCTION ... IN UPDATE TASK. Thus the Persistence Service works with traditional update methods. The update module is usually registered after any update modules that have already been registered. The update is then triggered and the update task executes the update module in the order in which they were registered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward all helpfull answers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Pavan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 30 Jul 2007 07:00:37 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-07-30T07:00:37Z</dc:date>
    <item>
      <title>Selection Screen</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/selection-screen/m-p/2629053#M604332</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What would happen if the following code is executed&lt;/P&gt;&lt;P&gt;Select * from vbak.&lt;/P&gt;&lt;P&gt;commit work .&lt;/P&gt;&lt;P&gt;Endselect.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Jul 2007 06:58:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/selection-screen/m-p/2629053#M604332</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-30T06:58:41Z</dc:date>
    </item>
    <item>
      <title>Re: Selection Screen</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/selection-screen/m-p/2629054#M604333</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;It will show Error that 'Statement is not Accessible'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Padmam.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Jul 2007 06:59:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/selection-screen/m-p/2629054#M604333</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-30T06:59:37Z</dc:date>
    </item>
    <item>
      <title>Re: Selection Screen</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/selection-screen/m-p/2629055#M604334</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 apply the changes made to the runtime objects of persistent classes to the actual persistent objects in the database, execute the COMMIT WORK statement. (Alternatively, use COMMIT WORK AND WAIT or SET UPDATE TASK LOCAL). Unless you are executing an object-oriented transaction from within the Transaction Service, you must include the COMMIT WORK statement explicitly in the program. Otherwise, it is encapsulated in the Transaction Service. (If you explicitly include the COMMIT WORK statement as described here, the t op-level transaction runs in compatibility mode).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The function of the COMMIT WORK statement is extended when you use it in conjunction with Object Services. Before COMMIT WORK closes the SAP LUW and triggers an update, it calls internal methods of the Persistence Service. These methods bundle the changes made to managed objects of the Persistence Service and pass them to a special update function module using CALL FUNCTION ... IN UPDATE TASK. Thus the Persistence Service works with traditional update methods. The update module is usually registered after any update modules that have already been registered. The update is then triggered and the update task executes the update module in the order in which they were registered.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward all helpfull answers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Pavan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Jul 2007 07:00:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/selection-screen/m-p/2629055#M604334</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-30T07:00:37Z</dc:date>
    </item>
    <item>
      <title>Re: Selection Screen</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/selection-screen/m-p/2629056#M604335</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This code will give dump.you should not  commit before executing dababase selection. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;you can do like...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;select * from vbak.&lt;/P&gt;&lt;P&gt;endselect.&lt;/P&gt;&lt;P&gt;commit work .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rewards the point if helpful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Jul 2007 07:03:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/selection-screen/m-p/2629056#M604335</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-30T07:03:56Z</dc:date>
    </item>
    <item>
      <title>Re: Selection Screen</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/selection-screen/m-p/2629057#M604336</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;First of all u haven't declared a target area where the data will be stored.&lt;/P&gt;&lt;P&gt;It will give syntax error.&lt;/P&gt;&lt;P&gt;and if u declare the internal table also, runtime error will occur because of the commit statement as it is not able to perform database selection fully.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward if useful&lt;/P&gt;&lt;P&gt;anju&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Jul 2007 07:08:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/selection-screen/m-p/2629057#M604336</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-30T07:08:34Z</dc:date>
    </item>
  </channel>
</rss>

