<?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: Data Locking in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-locking/m-p/5410887#M1242484</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Why don't you create lock object for you ZTABLE via SE11 ?&lt;/P&gt;&lt;P&gt;Then use function ENQUEUE_ZTABLE (with exclusive lock option) to lock and DEQUEUE_ZTABLE to unlock.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and regards,&lt;/P&gt;&lt;P&gt;Thanagit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 27 Mar 2009 02:13:18 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-03-27T02:13:18Z</dc:date>
    <item>
      <title>Data Locking</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-locking/m-p/5410886#M1242483</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a Z program that performing ZTABLE delete and update. The execution of the program is being scheduled every night, and multiple jobs need to be created for the same program due to different job need to update/delete different company code data into ZTABLE. Like below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Job 1, Company code = A100, A200, A300, A400&lt;/P&gt;&lt;P&gt;Job 2, Company code = B100, B200, B300, B400&lt;/P&gt;&lt;P&gt;Job 3, Company code = C100, C200, C300, C400&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since jobs are execute at the same timing, so i need to implement locking on ZTABLE. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Im thinking to lock ZTABLE at record level. Means During Job1's execution, i will lock data for company code A100, A200, A300 and A400. Once lock obtained, then program will proceed to delete company A* data and then follow by update company A* back to ZTABLE with latest data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On the other side, same program for Job 2 is executing at the same time. This time program is locking data for company B100, B200, B300 and B400. And then program will delete and update ZTABLE dealing with company B* data only.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I might need your advice with the above design if it is workable. Please comment.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Mar 2009 01:28:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-locking/m-p/5410886#M1242483</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-03-27T01:28:54Z</dc:date>
    </item>
    <item>
      <title>Re: Data Locking</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-locking/m-p/5410887#M1242484</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Why don't you create lock object for you ZTABLE via SE11 ?&lt;/P&gt;&lt;P&gt;Then use function ENQUEUE_ZTABLE (with exclusive lock option) to lock and DEQUEUE_ZTABLE to unlock.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and regards,&lt;/P&gt;&lt;P&gt;Thanagit&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Mar 2009 02:13:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-locking/m-p/5410887#M1242484</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-03-27T02:13:18Z</dc:date>
    </item>
    <item>
      <title>Re: Data Locking</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-locking/m-p/5410888#M1242485</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, im using the ENQUEUE FM to achieve my locking purpose.&lt;/P&gt;&lt;P&gt;I need advice if my design is acceptable.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Mar 2009 02:44:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-locking/m-p/5410888#M1242485</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-03-27T02:44:24Z</dc:date>
    </item>
    <item>
      <title>Re: Data Locking</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-locking/m-p/5410889#M1242486</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;Yes it would work, and its a good approach too which will save lots of time&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Siddarth&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Mar 2009 03:42:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-locking/m-p/5410889#M1242486</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-03-27T03:42:56Z</dc:date>
    </item>
    <item>
      <title>Re: Data Locking</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-locking/m-p/5410890#M1242487</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes. Your approach holds good.&lt;/P&gt;&lt;P&gt;Use Commit statement to update the records and Enqueue/Dequeue statements to lock and unlock.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For more information use F1 or search SDN forums.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this is helpful&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Babu Kilari&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Mar 2009 04:24:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-locking/m-p/5410890#M1242487</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-03-27T04:24:43Z</dc:date>
    </item>
    <item>
      <title>Re: Data Locking</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/data-locking/m-p/5410891#M1242488</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No explanation why 'Yes'.&lt;/P&gt;&lt;P&gt;How come you believe ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;good luck&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Mar 2009 06:22:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/data-locking/m-p/5410891#M1242488</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-03-27T06:22:05Z</dc:date>
    </item>
  </channel>
</rss>

