<?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: issue with BAPI_REQUISITION_DELETE in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/issue-with-bapi-requisition-delete/m-p/441146#M12994</link>
    <description>&lt;P&gt;If the BAPI uses an update task (usually an asynchronous process triggered at commit work), then the lock may be transmitted there, and is retained until the end of the asynchronous update task, so it may still be there when the BAPI is called again.&lt;/P&gt;&lt;P&gt;You may use either commit work AND WAIT, or deactivate the update task (SET UPDATE TASK LOCAL) to execute the updates synchronously.&lt;/P&gt;&lt;P&gt;And, of course, Krishna's answer is correct too.&lt;/P&gt;</description>
    <pubDate>Wed, 07 Jun 2017 05:55:42 GMT</pubDate>
    <dc:creator>Sandra_Rossi</dc:creator>
    <dc:date>2017-06-07T05:55:42Z</dc:date>
    <item>
      <title>issue with BAPI_REQUISITION_DELETE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/issue-with-bapi-requisition-delete/m-p/441142#M12990</link>
      <description>&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;I am using BAPI_REQUISITION_DELETE to delete a complete purchase requistion . issue is I am able to delete only the first line item when it comes to deletion of second line item its throwing an error as PURCHASE REQ locked with my id itself.&lt;/P&gt;&lt;P&gt;I am using a loop and passing line item numnber for that PR and a commit work.&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;P&gt;rg&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jun 2017 12:13:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/issue-with-bapi-requisition-delete/m-p/441142#M12990</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2017-06-05T12:13:24Z</dc:date>
    </item>
    <item>
      <title>Re: issue with BAPI_REQUISITION_DELETE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/issue-with-bapi-requisition-delete/m-p/441143#M12991</link>
      <description>&lt;P&gt;please suggest how to overcome this error&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jun 2017 12:13:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/issue-with-bapi-requisition-delete/m-p/441143#M12991</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2017-06-05T12:13:46Z</dc:date>
    </item>
    <item>
      <title>Re: issue with BAPI_REQUISITION_DELETE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/issue-with-bapi-requisition-delete/m-p/441144#M12992</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Can u show the code.I think &lt;/P&gt;&lt;P&gt;BAPI_REQUISITION_DELETE will take all line items to be deleted for a PR in a table using Tables parameter.&lt;/P&gt;&lt;P&gt;So no need to loop for single line item.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;krishna.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jun 2017 12:34:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/issue-with-bapi-requisition-delete/m-p/441144#M12992</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2017-06-05T12:34:42Z</dc:date>
    </item>
    <item>
      <title>Re: issue with BAPI_REQUISITION_DELETE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/issue-with-bapi-requisition-delete/m-p/441145#M12993</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;i used standard lock object to lock the PR and the issue is solved.&lt;/P&gt;&lt;P&gt;rg&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jun 2017 05:05:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/issue-with-bapi-requisition-delete/m-p/441145#M12993</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2017-06-07T05:05:38Z</dc:date>
    </item>
    <item>
      <title>Re: issue with BAPI_REQUISITION_DELETE</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/issue-with-bapi-requisition-delete/m-p/441146#M12994</link>
      <description>&lt;P&gt;If the BAPI uses an update task (usually an asynchronous process triggered at commit work), then the lock may be transmitted there, and is retained until the end of the asynchronous update task, so it may still be there when the BAPI is called again.&lt;/P&gt;&lt;P&gt;You may use either commit work AND WAIT, or deactivate the update task (SET UPDATE TASK LOCAL) to execute the updates synchronously.&lt;/P&gt;&lt;P&gt;And, of course, Krishna's answer is correct too.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jun 2017 05:55:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/issue-with-bapi-requisition-delete/m-p/441146#M12994</guid>
      <dc:creator>Sandra_Rossi</dc:creator>
      <dc:date>2017-06-07T05:55:42Z</dc:date>
    </item>
  </channel>
</rss>

