<?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: regarding sap authorizations in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-sap-authorizations/m-p/1377809#M184994</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This method does not force, but it does suggest.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
set parameter id 'MPN' field '*'.
set parameter id 'BDC_CREATOR' field sy-uname.
call transaction 'SM35'.

&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can set these parameters ids in the user profile.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rich Heilman&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 07 Jul 2006 17:57:09 GMT</pubDate>
    <dc:creator>RichHeilman</dc:creator>
    <dc:date>2006-07-07T17:57:09Z</dc:date>
    <item>
      <title>regarding sap authorizations</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-sap-authorizations/m-p/1377805#M184990</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is there anyway to limit the users access to only their own batch input sessions in tcode sm35 using sap authorizations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks in advance&lt;/P&gt;&lt;P&gt;mohan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jul 2006 17:17:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-sap-authorizations/m-p/1377805#M184990</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-07-07T17:17:56Z</dc:date>
    </item>
    <item>
      <title>Re: regarding sap authorizations</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-sap-authorizations/m-p/1377806#M184991</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;See the authorization objects&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;S_BTCH_ADM Background Processing: Background Administrator      &lt;/P&gt;&lt;P&gt;S_BTCH_NAM Background Processing: Background User Name          &lt;/P&gt;&lt;P&gt;S_BTCH_JOB Background Processing: Operations on Background Jobs &lt;/P&gt;&lt;P&gt;S_BDC_MONI Batch Input Authorizations                           &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Kiran&lt;/P&gt;&lt;P&gt;*Please reward useful answers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jul 2006 17:22:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-sap-authorizations/m-p/1377806#M184991</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-07-07T17:22:01Z</dc:date>
    </item>
    <item>
      <title>Re: regarding sap authorizations</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-sap-authorizations/m-p/1377807#M184992</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;check this&lt;/P&gt;&lt;P&gt;Checking User Authorizations in your ABAP Program &lt;/P&gt;&lt;P&gt;How to set Authorization to an ABAP Programs? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Much of the data in an R/3 system has to be protected so that unauthorized users cannot access it. Therefore the appropriate authorization is required before a user can carry out certain actions in the system. When you log on to the R/3 system, the system checks in the user master record to see which transactions you are authorized to use. An authorization check is implemented for every sensitive transaction. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you wish to protect a transaction that you have programmed yourself, then you must implement an authorization check. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This means you have to allocate an authorization object in the definition of the transaction. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;program an AUTHORITY-CHECK. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AUTHORITY-CHECK OBJECT &amp;lt;authorization object&amp;gt; &lt;/P&gt;&lt;P&gt;ID &amp;lt;authority field 1&amp;gt; FIELD &amp;lt;field value 1&amp;gt;. &lt;/P&gt;&lt;P&gt;ID &amp;lt;authority field 2&amp;gt; FIELD &amp;lt;field value 2&amp;gt;. &lt;/P&gt;&lt;P&gt;... &lt;/P&gt;&lt;P&gt;ID &amp;lt;authority-field n&amp;gt; FIELD &amp;lt;field value n&amp;gt;. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The OBJECT parameter specifies the authorization object. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ID parameter specifies an authorization field (in the authorization object). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The FIELD parameter specifies a value for the authorization field. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The authorization object and its fields have to be suitable for the transaction. In most cases you will be able to use the existing authorization objects to protect your data. But new developments may require that you define new authorization objects and fields. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Use T/Code SE80 to Create Authorization object.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if u find it useful mark the points&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Naveen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jul 2006 17:23:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-sap-authorizations/m-p/1377807#M184992</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-07-07T17:23:08Z</dc:date>
    </item>
    <item>
      <title>Re: regarding sap authorizations</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-sap-authorizations/m-p/1377808#M184993</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There&amp;#146;s a way in CUA ( Central User Administration )to restrict the user session. Its not on top of my head at the moment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Saquib&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jul 2006 17:36:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-sap-authorizations/m-p/1377808#M184993</guid>
      <dc:creator>former_member181966</dc:creator>
      <dc:date>2006-07-07T17:36:15Z</dc:date>
    </item>
    <item>
      <title>Re: regarding sap authorizations</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-sap-authorizations/m-p/1377809#M184994</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This method does not force, but it does suggest.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
set parameter id 'MPN' field '*'.
set parameter id 'BDC_CREATOR' field sy-uname.
call transaction 'SM35'.

&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can set these parameters ids in the user profile.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rich Heilman&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jul 2006 17:57:09 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-sap-authorizations/m-p/1377809#M184994</guid>
      <dc:creator>RichHeilman</dc:creator>
      <dc:date>2006-07-07T17:57:09Z</dc:date>
    </item>
    <item>
      <title>Re: regarding sap authorizations</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-sap-authorizations/m-p/1377810#M184995</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can create a variant transaction for SM35 adn prefill the user id in display only mode. Give that to the users instead of SM35.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jul 2006 17:59:58 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/regarding-sap-authorizations/m-p/1377810#M184995</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-07-07T17:59:58Z</dc:date>
    </item>
  </channel>
</rss>

