<?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: Call Transaction problem in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-problem/m-p/1373265#M183343</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Go to SM12 and delete the lock by using delete icon in the application tool bar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 30 May 2006 10:01:51 GMT</pubDate>
    <dc:creator>rahulkavuri</dc:creator>
    <dc:date>2006-05-30T10:01:51Z</dc:date>
    <item>
      <title>Call Transaction problem</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-problem/m-p/1373258#M183336</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Implemented call transaction to upload data to a transaction. If someone else is also working with same transaction SAP gives message in popup to confirm step screen 'Data locked by user XXXX Display only?' and call transaction fails by message 'No batch input data for screen &amp;amp; &amp;amp;'. No E or A type messages. How to handle this kind of lock problem in CT. Please advise&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;srinivas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 May 2006 09:54:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-problem/m-p/1373258#M183336</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-05-30T09:54:15Z</dc:date>
    </item>
    <item>
      <title>Re: Call Transaction problem</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-problem/m-p/1373259#M183337</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Srini,&lt;/P&gt;&lt;P&gt; There is only one way to avoid this.&lt;/P&gt;&lt;P&gt;Ask the other user to log out of the transaction and then run your program again.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ravi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 May 2006 09:56:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-problem/m-p/1373259#M183337</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-05-30T09:56:40Z</dc:date>
    </item>
    <item>
      <title>Re: Call Transaction problem</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-problem/m-p/1373260#M183338</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hii&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Go to transaction &amp;lt;b&amp;gt;SM12&amp;lt;/b&amp;gt; and &lt;/P&gt;&lt;P&gt;select the corresponding user &lt;/P&gt;&lt;P&gt;and select &amp;lt;b&amp;gt;delete  or (shift + F2)&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;delete the corresponding locked one&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Naresh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 May 2006 09:58:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-problem/m-p/1373260#M183338</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-05-30T09:58:58Z</dc:date>
    </item>
    <item>
      <title>Re: Call Transaction problem</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-problem/m-p/1373261#M183339</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yup...Programmatically you can trace this error message. In fact it&amp;#146;s suggested to use the session method and execute it programmatically in the background mode using jobs. The advantage over here is you can re-execute the session even the transaction is failed due to any error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thomas.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 May 2006 10:00:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-problem/m-p/1373261#M183339</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-05-30T10:00:04Z</dc:date>
    </item>
    <item>
      <title>Re: Call Transaction problem</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-problem/m-p/1373262#M183340</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;By using SM12 Transaction please remove all locks and again try it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers &lt;/P&gt;&lt;P&gt;Prabhu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 May 2006 10:00:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-problem/m-p/1373262#M183340</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-05-30T10:00:17Z</dc:date>
    </item>
    <item>
      <title>Re: Call Transaction problem</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-problem/m-p/1373263#M183341</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi srinivas,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. There must be some FM&lt;/P&gt;&lt;P&gt;   ENQUEU/DEUQUE for your transaction,&lt;/P&gt;&lt;P&gt;   to check if the particular&lt;/P&gt;&lt;P&gt;   record&lt;/P&gt;&lt;P&gt;   is locked or not.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. We should detect this lock,&lt;/P&gt;&lt;P&gt;   and stop the bdc before only from going further.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. Since R/3 is multi-user environment,&lt;/P&gt;&lt;P&gt;   it will not allow in any case&lt;/P&gt;&lt;P&gt;   to go further and post the data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&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, 30 May 2006 10:00:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-problem/m-p/1373263#M183341</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-05-30T10:00:55Z</dc:date>
    </item>
    <item>
      <title>Re: Call Transaction problem</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-problem/m-p/1373264#M183342</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;try to create a session whenever u hav a pop up coming up&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 May 2006 10:01:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-problem/m-p/1373264#M183342</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-05-30T10:01:32Z</dc:date>
    </item>
    <item>
      <title>Re: Call Transaction problem</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-problem/m-p/1373265#M183343</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Go to SM12 and delete the lock by using delete icon in the application tool bar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 May 2006 10:01:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/call-transaction-problem/m-p/1373265#M183343</guid>
      <dc:creator>rahulkavuri</dc:creator>
      <dc:date>2006-05-30T10:01:51Z</dc:date>
    </item>
  </channel>
</rss>

