<?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 Maintaining Parameter Values in User Master Alternatives in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/maintaining-parameter-values-in-user-master-alternatives/m-p/8313423#M1636680</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;Requirement&lt;/STRONG&gt;: I have a user that needs to maintain parameter values for other users.  This user is a power user.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Issue&lt;/STRONG&gt;: The only option I see are SU01 (which is too wide open), and SU3 (which is self-service).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Question&lt;/STRONG&gt;: Is there a transaction that would allow me to grant this user access to update Parameter ID and Parameter Values of &lt;EM&gt;other&lt;/EM&gt; users, but not allow them to change other User Master information such as Name, Email, Roles etc?  When I say not give them access, I mean I don't want the tabs there at all.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 17 Nov 2011 21:57:39 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2011-11-17T21:57:39Z</dc:date>
    <item>
      <title>Maintaining Parameter Values in User Master Alternatives</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/maintaining-parameter-values-in-user-master-alternatives/m-p/8313423#M1636680</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;Requirement&lt;/STRONG&gt;: I have a user that needs to maintain parameter values for other users.  This user is a power user.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Issue&lt;/STRONG&gt;: The only option I see are SU01 (which is too wide open), and SU3 (which is self-service).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Question&lt;/STRONG&gt;: Is there a transaction that would allow me to grant this user access to update Parameter ID and Parameter Values of &lt;EM&gt;other&lt;/EM&gt; users, but not allow them to change other User Master information such as Name, Email, Roles etc?  When I say not give them access, I mean I don't want the tabs there at all.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Nov 2011 21:57:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/maintaining-parameter-values-in-user-master-alternatives/m-p/8313423#M1636680</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-11-17T21:57:39Z</dc:date>
    </item>
    <item>
      <title>Re: Maintaining Parameter Values in User Master Alternatives</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/maintaining-parameter-values-in-user-master-alternatives/m-p/8313424#M1636681</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;variant for US01 might work. Probably, the safest option is to develop a custom transaction that would use standard BAPIs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Nov 2011 22:27:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/maintaining-parameter-values-in-user-master-alternatives/m-p/8313424#M1636681</guid>
      <dc:creator>mvoros</dc:creator>
      <dc:date>2011-11-17T22:27:47Z</dc:date>
    </item>
    <item>
      <title>Re: Maintaining Parameter Values in User Master Alternatives</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/maintaining-parameter-values-in-user-master-alternatives/m-p/8313425#M1636682</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Emmonskr,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think there´s no such specific transaction to do that. The table where SAP stores the parameters is USR05.&lt;/P&gt;&lt;P&gt;You can create your own development or provide the user with a change view of the table I mentioned above.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Diego.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 20 Nov 2011 19:09:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/maintaining-parameter-values-in-user-master-alternatives/m-p/8313425#M1636682</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-11-20T19:09:28Z</dc:date>
    </item>
    <item>
      <title>Re: Maintaining Parameter Values in User Master Alternatives</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/maintaining-parameter-values-in-user-master-alternatives/m-p/8313426#M1636683</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Please don't suggest direct update of DB tables. It's always risky because you might still need to update other tables. In this case SAP provides BAPIs BAPI_USER_* so I don't see any reason why to do direct update DB.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 20 Nov 2011 22:33:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/maintaining-parameter-values-in-user-master-alternatives/m-p/8313426#M1636683</guid>
      <dc:creator>mvoros</dc:creator>
      <dc:date>2011-11-20T22:33:16Z</dc:date>
    </item>
    <item>
      <title>Re: Maintaining Parameter Values in User Master Alternatives</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/maintaining-parameter-values-in-user-master-alternatives/m-p/8313427#M1636684</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Martin is 100% correct. Perhaps you are a DB admin without any application respect?  &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyway, in addition to the BAPIs to changing the PIDs you must consider that it is a personal preference of the user to change them and many transactions use GET / SET Paramter statements regardless of what the SU01 record might have been set to initially.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So what you are actually looking for is a template to create the user from with the desired &lt;STRONG&gt;default&lt;/STRONG&gt; PIDS, right?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If so then you need to tell us whether these defaults are general or need to be role specific? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, are any of these PIDs security relevant for you (the user should ideally not be able to change it)? In this case PIDs are not the solution - you should have used Personalizations.&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>Mon, 21 Nov 2011 18:43:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/maintaining-parameter-values-in-user-master-alternatives/m-p/8313427#M1636684</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-11-21T18:43:16Z</dc:date>
    </item>
  </channel>
</rss>

