<?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: AUTHORIZATION RESTRICTION in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-restriction/m-p/3255332#M777413</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;You can group them into 2 groups: SM01 itself, and, all the rest.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Locking a transaction is seldomly a formidable hurdle to prevent use of a transaction. It can also cause problems for the system in some cases.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 08 Jan 2008 07:17:50 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-01-08T07:17:50Z</dc:date>
    <item>
      <title>AUTHORIZATION RESTRICTION</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-restriction/m-p/3255330#M777411</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Pals,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was trying to give the authorization to a user for lock/Unlock the transactions [SM01] through the object S_ADMI_FCD with the value TLCK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if i do the same user is getting authorization to LOCK/UNLOCK for all the transactions available in the system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but i want to restrict it to specific transactions only.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is there any other object to restrict??????????????&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Jan 2008 06:35:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-restriction/m-p/3255330#M777411</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-08T06:35:26Z</dc:date>
    </item>
    <item>
      <title>Re: AUTHORIZATION RESTRICTION</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-restriction/m-p/3255331#M777412</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Krishna,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is no authorization object using which we can restrict SM01 for locking only certain transactions. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Sheetal&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Jan 2008 07:11:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-restriction/m-p/3255331#M777412</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-08T07:11:58Z</dc:date>
    </item>
    <item>
      <title>Re: AUTHORIZATION RESTRICTION</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-restriction/m-p/3255332#M777413</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;You can group them into 2 groups: SM01 itself, and, all the rest.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Locking a transaction is seldomly a formidable hurdle to prevent use of a transaction. It can also cause problems for the system in some cases.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Julius&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Jan 2008 07:17:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-restriction/m-p/3255332#M777413</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-08T07:17:50Z</dc:date>
    </item>
    <item>
      <title>Re: AUTHORIZATION RESTRICTION</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-restriction/m-p/3255333#M777414</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;there is no authorization to lock a transaction. and it is better to revoke the access of this to the user.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Jan 2008 08:07:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-restriction/m-p/3255333#M777414</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-08T08:07:18Z</dc:date>
    </item>
    <item>
      <title>Re: AUTHORIZATION RESTRICTION</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-restriction/m-p/3255334#M777415</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;SM01 is usefull if you have made your own transaction to use instead of the standard SAP transaction, otherwise I never excluded an transaction. If you take care of the fact that no * is in authorization object s_tcode you only can do the transactions you are allowed to do. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have fun &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jan van Roest&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Jan 2008 12:22:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-restriction/m-p/3255334#M777415</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-08T12:22:43Z</dc:date>
    </item>
    <item>
      <title>Re: AUTHORIZATION RESTRICTION</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-restriction/m-p/3255335#M777416</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;go to tx LSMW and make a batch-input recording of SM01 and the special transaction you want the user to be able to lock. do a bit of developing (no abap needed) and authorize the user to play this special batch-input (actually you would need two of them; one for locking, one for unlocking).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Jan 2008 16:42:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/authorization-restriction/m-p/3255335#M777416</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-08T16:42:42Z</dc:date>
    </item>
  </channel>
</rss>

