<?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: R/3 Lock/unlock users from SCRIPT in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/r-3-lock-unlock-users-from-script/m-p/3236947#M772466</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The logs in SUIM you refer to are obviously not logs on table changes. They're application logs. &lt;/P&gt;&lt;P&gt;You could consider to  rewrite your script and make it log to the same location the other transactions you mentioned do. &lt;/P&gt;&lt;P&gt;That way you'll have your information in one place. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Besides that, maybe there's a 'more sophisticated' way to programmatically lock your users. You might even find a way that does log to the proper location, like a function module........&lt;/P&gt;&lt;P&gt;There's also an interesting thread in this forum about the values for UFLAG in USR02.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jurjen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 15 Jan 2008 14:05:54 GMT</pubDate>
    <dc:creator>jurjen_heeck</dc:creator>
    <dc:date>2008-01-15T14:05:54Z</dc:date>
    <item>
      <title>R/3 Lock/unlock users from SCRIPT</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/r-3-lock-unlock-users-from-script/m-p/3236946#M772465</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We use a script to block users the weekends less those necessary for the business, If I want to see the log of the users in the table ush02 or in the transaction S_BCE_68001439, suim...etc Only shows the information of the users blocked across the transactions EWZ5 and SU10 does not show the information of the users blocked and unblocked by the script, Then the information is not real.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is not never log in SAP that shows the block and unlocks the users across scripts? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SCRIPT&lt;/P&gt;&lt;P&gt;update usr02 set uflag ='64' where mandt='010' and bname not in &amp;lt;users&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Jan 2008 13:51:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/r-3-lock-unlock-users-from-script/m-p/3236946#M772465</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-15T13:51:03Z</dc:date>
    </item>
    <item>
      <title>Re: R/3 Lock/unlock users from SCRIPT</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/r-3-lock-unlock-users-from-script/m-p/3236947#M772466</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The logs in SUIM you refer to are obviously not logs on table changes. They're application logs. &lt;/P&gt;&lt;P&gt;You could consider to  rewrite your script and make it log to the same location the other transactions you mentioned do. &lt;/P&gt;&lt;P&gt;That way you'll have your information in one place. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Besides that, maybe there's a 'more sophisticated' way to programmatically lock your users. You might even find a way that does log to the proper location, like a function module........&lt;/P&gt;&lt;P&gt;There's also an interesting thread in this forum about the values for UFLAG in USR02.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jurjen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Jan 2008 14:05:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/r-3-lock-unlock-users-from-script/m-p/3236947#M772466</guid>
      <dc:creator>jurjen_heeck</dc:creator>
      <dc:date>2008-01-15T14:05:54Z</dc:date>
    </item>
    <item>
      <title>Re: R/3 Lock/unlock users from SCRIPT</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/r-3-lock-unlock-users-from-script/m-p/3236948#M772467</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I ran scripts through SECATT and I do have logs.  &lt;/P&gt;&lt;P&gt;Run SECATT select your script-&amp;gt;Goto-&amp;gt;Logs-&amp;gt;search your logs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Jan 2008 16:06:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/r-3-lock-unlock-users-from-script/m-p/3236948#M772467</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-15T16:06:30Z</dc:date>
    </item>
    <item>
      <title>Re: R/3 Lock/unlock users from SCRIPT</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/r-3-lock-unlock-users-from-script/m-p/3236949#M772468</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I strongly recommend the usage of API functions, such as&lt;/P&gt;&lt;P&gt;   - function module BAPI_USER_LOCK&lt;/P&gt;&lt;P&gt;   - function module BAPI_USER_UNLOCK&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Refrain from updating any DB tables directly !!!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 15 Jan 2008 16:19:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/r-3-lock-unlock-users-from-script/m-p/3236949#M772468</guid>
      <dc:creator>Wolfgang_Janzen</dc:creator>
      <dc:date>2008-01-15T16:19:38Z</dc:date>
    </item>
  </channel>
</rss>

