<?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: doubt in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/doubt/m-p/2194695#M468295</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;There a few options available depending on the type of solution you are looking for.&lt;/P&gt;&lt;P&gt;1) You can use the transaction SE54 to assign the Z tables to a authorization group and give access to the Authorization group through S_TABU_DIS.&lt;/P&gt;&lt;P&gt;and depending on the way you are trying to access the table might require SE16(not mandatory always).&lt;/P&gt;&lt;P&gt;The problem with this is once u have access to the S_TABU_DIS all the the tables which are not assigned to any auth grp are given access.&lt;/P&gt;&lt;P&gt;2) Second approach is to create custom Tcodes (Transaction with Parameters)&lt;/P&gt;&lt;P&gt;for SE16 (if you are creating this for SE16) and give S_TABU_DIS with the Authorization group.&lt;/P&gt;&lt;P&gt;The advantage is that the end user will not have access to Se16 so will not able to see other tables which dont have a authorization group&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to create the scenario for editing then do the same but with SM30 Tcode but the mae suew that it has a maintainance interface from SM30&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        Manohar Kappala&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 08 May 2007 06:59:21 GMT</pubDate>
    <dc:creator>manohar_kappala2</dc:creator>
    <dc:date>2007-05-08T06:59:21Z</dc:date>
    <item>
      <title>doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/doubt/m-p/2194693#M468293</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;I want to restrict a group of Z tables,what will be the steps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 May 2007 00:49:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/doubt/m-p/2194693#M468293</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-08T00:49:19Z</dc:date>
    </item>
    <item>
      <title>Re: doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/doubt/m-p/2194694#M468294</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you want to restrict editing of table data, you have to assign a "Authorisation group" (via the utilities menu in se11) to all the tables you want these users to have access to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then in the role that you are giving to the users, add the S_TABU_DIS object, with the assigned "authorisation group" in the field "DICBERCLS". &lt;/P&gt;&lt;P&gt;Users with this role will then be able to edit/read (depending on the value of the field ACTVT in the object S_TABU_DIS) all tables from this authorisation group.&lt;/P&gt;&lt;P&gt;Also, make sure these users don't have this object with DICBERCLS=* in any other roles.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;More info can be found on &amp;lt;a href="http://help.sap.com/saphelp_erp2005vp/helpdata/en/c6/74ba3bd14a6a6ae10000000a114084/frameset.htm"&amp;gt;help.sap.com&amp;lt;/a&amp;gt;.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 May 2007 06:32:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/doubt/m-p/2194694#M468294</guid>
      <dc:creator>dhorions</dc:creator>
      <dc:date>2007-05-08T06:32:48Z</dc:date>
    </item>
    <item>
      <title>Re: doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/doubt/m-p/2194695#M468295</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;There a few options available depending on the type of solution you are looking for.&lt;/P&gt;&lt;P&gt;1) You can use the transaction SE54 to assign the Z tables to a authorization group and give access to the Authorization group through S_TABU_DIS.&lt;/P&gt;&lt;P&gt;and depending on the way you are trying to access the table might require SE16(not mandatory always).&lt;/P&gt;&lt;P&gt;The problem with this is once u have access to the S_TABU_DIS all the the tables which are not assigned to any auth grp are given access.&lt;/P&gt;&lt;P&gt;2) Second approach is to create custom Tcodes (Transaction with Parameters)&lt;/P&gt;&lt;P&gt;for SE16 (if you are creating this for SE16) and give S_TABU_DIS with the Authorization group.&lt;/P&gt;&lt;P&gt;The advantage is that the end user will not have access to Se16 so will not able to see other tables which dont have a authorization group&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to create the scenario for editing then do the same but with SM30 Tcode but the mae suew that it has a maintainance interface from SM30&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        Manohar Kappala&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 May 2007 06:59:21 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/doubt/m-p/2194695#M468295</guid>
      <dc:creator>manohar_kappala2</dc:creator>
      <dc:date>2007-05-08T06:59:21Z</dc:date>
    </item>
    <item>
      <title>Re: doubt</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/doubt/m-p/2194696#M468296</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi sri,&lt;/P&gt;&lt;P&gt;There are 2 ways of doing this:&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;1st Way&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;1) Assign the Z table to Authorization Group using SE54&lt;/P&gt;&lt;P&gt;2) Add SM30 Transaction in your role&lt;/P&gt;&lt;P&gt;3) Add the Authorization Group just created in the DICBERCLS field of  S_TABU_DIS&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;u&amp;gt;2nd Way&amp;lt;/u&amp;gt;---&amp;lt;u&amp;gt;Creating a Custom Transaction Code&amp;lt;/u&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) goto se93, give a unique name, say zxxx&lt;/P&gt;&lt;P&gt;2)Enter SE16 into the transaction field and select the flag the &amp;#145;skip initial screen&amp;#146; field:&lt;/P&gt;&lt;P&gt;3)On the lower portion of the screen, enter the following information:&lt;/P&gt;&lt;P&gt;Name of screen field: DATABROWSE-TABLENAME&lt;/P&gt;&lt;P&gt;Value: Enter the name of the table you want to browse with &lt;/P&gt;&lt;P&gt;4)save it.&lt;/P&gt;&lt;P&gt;5) Now add the transaction zxxx in th role, and assign it to the user.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it helps.&lt;/P&gt;&lt;P&gt;Please award points if it is useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P&gt;Santosh&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        NAVABOTHU SANTOSH KUMAR&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 May 2007 13:10:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/doubt/m-p/2194696#M468296</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-05-08T13:10:26Z</dc:date>
    </item>
  </channel>
</rss>

