<?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: Record Locking when using BAPI in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/record-locking-when-using-bapi/m-p/1140520#M114463</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rajkumar,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This really helpful thanks for this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Conor.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 14 Feb 2006 15:10:41 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-02-14T15:10:41Z</dc:date>
    <item>
      <title>Record Locking when using BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/record-locking-when-using-bapi/m-p/1140513#M114456</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;Just wondering if any of you have come across this before.&lt;/P&gt;&lt;P&gt;We have a bespoke program that runs in the background as a scheduled job and it reads data from a flat file on the network, it then proceeds to call the BAPI (BAPI_PLANNEDORDER_CHANGE) and directly after that I use BAPI_TRANSACTION_COMMIT (with no WAIT time) but the record is locked, we presume its because the current PO in the ITAB is the same as the previous row, but maybe it because of some other reason.  Any suggestions??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind Regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Feb 2006 09:59:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/record-locking-when-using-bapi/m-p/1140513#M114456</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-02-14T09:59:33Z</dc:date>
    </item>
    <item>
      <title>Re: Record Locking when using BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/record-locking-when-using-bapi/m-p/1140514#M114457</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi conor,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. I don't know whether i understood ur question properly !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. U are reading from flat file, into internal table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. Loop at itab.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   Call BAPI_PLANNEDORDER_CHANGE&lt;/P&gt;&lt;P&gt;   call BAPI_TRANSACTION_COMMIT &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;  endloop.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4. Use the above logic,&lt;/P&gt;&lt;P&gt;  (ie , with each loop pass, use commit)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;amit m.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Feb 2006 10:06:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/record-locking-when-using-bapi/m-p/1140514#M114457</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-02-14T10:06:36Z</dc:date>
    </item>
    <item>
      <title>Re: Record Locking when using BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/record-locking-when-using-bapi/m-p/1140515#M114458</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;May be some one else is editing the order at the same time.&lt;/P&gt;&lt;P&gt;are you sure that same order is there is next record.&lt;/P&gt;&lt;P&gt;is it the same case with rest of the orders&lt;/P&gt;&lt;P&gt;i mean for the repeated orders.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;vijay&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Feb 2006 10:07:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/record-locking-when-using-bapi/m-p/1140515#M114458</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-02-14T10:07:13Z</dc:date>
    </item>
    <item>
      <title>Re: Record Locking when using BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/record-locking-when-using-bapi/m-p/1140516#M114459</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi There,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Vijay, Because of the time that this job runs (schedule time) there are no users on the system and it highly unlikly that another job is processing that PO. There are other occurances where the PO is repeated and thease rows process through fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Amit, this is what I am doing only I dont specify a COMMIT-WORK because the BAPI_TRANSACTION_COMMIT takes care of that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It look like maybe the system was a bit to fast for my program, will have to get some more processing going on.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for you help, points on the way&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Feb 2006 10:26:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/record-locking-when-using-bapi/m-p/1140516#M114459</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-02-14T10:26:00Z</dc:date>
    </item>
    <item>
      <title>Re: Record Locking when using BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/record-locking-when-using-bapi/m-p/1140517#M114460</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;  Before calling the BAPI just try to lock that purchase order using EKKOE lockobject if you can able to lock sucessfully then release the lock and call the bapi.&lt;/P&gt;&lt;P&gt;if you are unable to lock then keep it in loop till that po is unlocked and then call the bapi.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Feb 2006 10:47:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/record-locking-when-using-bapi/m-p/1140517#M114460</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-02-14T10:47:37Z</dc:date>
    </item>
    <item>
      <title>Re: Record Locking when using BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/record-locking-when-using-bapi/m-p/1140518#M114461</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rajkumar,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is very useful never thought of that I will investigate this further in the mean time how do you use the EKKOE lockobject ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Feb 2006 12:05:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/record-locking-when-using-bapi/m-p/1140518#M114461</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-02-14T12:05:10Z</dc:date>
    </item>
    <item>
      <title>Re: Record Locking when using BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/record-locking-when-using-bapi/m-p/1140519#M114462</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi conor,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; You can use EKKOE lock object by calling function module ENQUEUE_EKKOE. For this you pass the PO number which you want to lock. For releasing the lock same DEQUEUE_EKKOE function module.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Feb 2006 12:25:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/record-locking-when-using-bapi/m-p/1140519#M114462</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-02-14T12:25:36Z</dc:date>
    </item>
    <item>
      <title>Re: Record Locking when using BAPI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/record-locking-when-using-bapi/m-p/1140520#M114463</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rajkumar,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This really helpful thanks for this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Conor.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Feb 2006 15:10:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/record-locking-when-using-bapi/m-p/1140520#M114463</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-02-14T15:10:41Z</dc:date>
    </item>
  </channel>
</rss>

