<?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: SUSR_BAPI_USER_UNLOCK LOCK_WRONG_LOGON question in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/susr-bapi-user-unlock-lock-wrong-logon-question/m-p/4179409#M998994</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try the same with BAPI_USER_UNLOCK?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS: Also take note that SUSR_BAPI_USER_UNLOCK is not remote enabled itself. So it &lt;EM&gt;might&lt;/EM&gt; be that ES2N unlocked in the calling client / system, and not in the target.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Julius Bussche on Jul 14, 2008 6:34 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 14 Jul 2008 18:31:10 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-07-14T18:31:10Z</dc:date>
    <item>
      <title>SUSR_BAPI_USER_UNLOCK LOCK_WRONG_LOGON question</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/susr-bapi-user-unlock-lock-wrong-logon-question/m-p/4179407#M998992</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When a user is locked because of too many wrong logons, it seems the correct way to unlock the user is to use SUSR_BAPI_USER_UNLOCK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I do this through my native SAP GUI, I need to set LOCK_WRONG_LOGON = 'X'.  This works fine.  I am trying to do it remotely though.  I have the command remote enabled but when I send it, it is not working.  I do not see any error messages in my trace.  Below is the XML version of the command I am sending to the system.  It seems correct to me.  Can anyone see any problems?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;SUSR_BAPI_USER_UNLOCK&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;INPUT&amp;gt;&amp;lt;LOCK_GLOBAL&amp;gt;&amp;lt;BAPIFLAG&amp;gt;&amp;lt;/BAPIFLAG&amp;gt;&amp;lt;/LOCK_GLOBAL&amp;gt;&amp;lt;LOCK_LOCAL&amp;gt;&amp;lt;BAPIFLAG&amp;gt;&amp;lt;/BAPIFLAG&amp;gt;&amp;lt;/LOCK_LOCAL&amp;gt;&amp;lt;LOCK_WRONG_LOGON&amp;gt;&amp;lt;BAPIFLAG&amp;gt;X&amp;lt;/BAPIFLAG&amp;gt;&amp;lt;/LOCK_WRONG_LOGON&amp;gt;&amp;lt;USERNAME&amp;gt;ES2N&amp;lt;/USERNAME&amp;gt;&amp;lt;/INPUT&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;TABLES&amp;gt;&amp;lt;RETURN&amp;gt;&amp;lt;/RETURN&amp;gt;&amp;lt;/TABLES&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;/SUSR_BAPI_USER_UNLOCK&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The response I get is below.  It seems to say that the user was unlocked if it is allowed on the system.  It is allowed, because it works natively.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;SUSR_BAPI_USER_UNLOCK&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;INPUT&amp;gt;&amp;lt;LOCK_GLOBAL&amp;gt;&amp;lt;BAPIFLAG&amp;gt;&amp;lt;/BAPIFLAG&amp;gt;&amp;lt;/LOCK_GLOBAL&amp;gt;&amp;lt;LOCK_LOCAL&amp;gt;&amp;lt;BAPIFLAG&amp;gt;&amp;lt;/BAPIFLAG&amp;gt;&amp;lt;/LOCK_LOCAL&amp;gt;&amp;lt;LOCK_WRONG_LOGON&amp;gt;&amp;lt;BAPIFLAG&amp;gt;X&amp;lt;/BAPIFLAG&amp;gt;&amp;lt;/LOCK_WRONG_LOGON&amp;gt;&amp;lt;USERNAME&amp;gt;ES2N&amp;lt;/USERNAME&amp;gt;&amp;lt;/INPUT&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;TABLES&amp;gt;&amp;lt;RETURN&amp;gt;&amp;lt;item&amp;gt;&amp;lt;TYPE&amp;gt;S&amp;lt;/TYPE&amp;gt;&amp;lt;ID&amp;gt;01&amp;lt;/ID&amp;gt;&amp;lt;NUMBER&amp;gt;246&amp;lt;/NUMBER&amp;gt;&amp;lt;MESSAGE&amp;gt;User ES2N unlocked, if this is permitted in this system&amp;lt;/MESSAGE&amp;gt;&amp;lt;LOG_NO&amp;gt;&amp;lt;/LOG_NO&amp;gt;&amp;lt;LOG_MSG_NO&amp;gt;000000&amp;lt;/LOG_MSG_NO&amp;gt;&amp;lt;MESSAGE_V1&amp;gt;ES2N&amp;lt;/MESSAGE_V1&amp;gt;&amp;lt;MESSAGE_V2&amp;gt;&amp;lt;/MESSAGE_V2&amp;gt;&amp;lt;MESSAGE_V3&amp;gt;&amp;lt;/MESSAGE_V3&amp;gt;&amp;lt;MESSAGE_V4&amp;gt;&amp;lt;/MESSAGE_V4&amp;gt;&amp;lt;PARAMETER&amp;gt;&amp;lt;/PARAMETER&amp;gt;&amp;lt;ROW&amp;gt;0&amp;lt;/ROW&amp;gt;&amp;lt;FIELD&amp;gt;&amp;lt;/FIELD&amp;gt;&amp;lt;SYSTEM&amp;gt;SAP1&amp;lt;/SYSTEM&amp;gt;&amp;lt;/item&amp;gt;&amp;lt;/RETURN&amp;gt;&amp;lt;/TABLES&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;lt;/SUSR_BAPI_USER_UNLOCK&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any thoughts would be greatly appreciated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jul 2008 18:13:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/susr-bapi-user-unlock-lock-wrong-logon-question/m-p/4179407#M998992</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-14T18:13:40Z</dc:date>
    </item>
    <item>
      <title>Re: SUSR_BAPI_USER_UNLOCK LOCK_WRONG_LOGON question</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/susr-bapi-user-unlock-lock-wrong-logon-question/m-p/4179408#M998993</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It looks to me as if the user is being unlocked correctly.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jul 2008 18:21:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/susr-bapi-user-unlock-lock-wrong-logon-question/m-p/4179408#M998993</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-14T18:21:21Z</dc:date>
    </item>
    <item>
      <title>Re: SUSR_BAPI_USER_UNLOCK LOCK_WRONG_LOGON question</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/susr-bapi-user-unlock-lock-wrong-logon-question/m-p/4179409#M998994</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try the same with BAPI_USER_UNLOCK?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS: Also take note that SUSR_BAPI_USER_UNLOCK is not remote enabled itself. So it &lt;EM&gt;might&lt;/EM&gt; be that ES2N unlocked in the calling client / system, and not in the target.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Julius Bussche on Jul 14, 2008 6:34 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jul 2008 18:31:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/susr-bapi-user-unlock-lock-wrong-logon-question/m-p/4179409#M998994</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-14T18:31:10Z</dc:date>
    </item>
    <item>
      <title>Re: SUSR_BAPI_USER_UNLOCK LOCK_WRONG_LOGON question</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/susr-bapi-user-unlock-lock-wrong-logon-question/m-p/4179410#M998995</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Found my problem.  The call actually works correctly.  The user name had been changed by other code that I wasnt aware of.  Thank you guys for taking a look.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Jul 2008 16:44:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/susr-bapi-user-unlock-lock-wrong-logon-question/m-p/4179410#M998995</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-07-15T16:44:01Z</dc:date>
    </item>
  </channel>
</rss>

