<?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: Replicating authorization checks using SAP provided function calls in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/replicating-authorization-checks-using-sap-provided-function-calls/m-p/1236280#M140879</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Srinivas,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had thought about using the Authority-check as SAP prefers to use this across most programs.  However, as I debugged thru MBST I noticed SAP does not issue a authority check on S_TCODE but rather it was using the function modules I had mentioned in my first request.  SAP further proceeded to issue authority checks against objects (M_MSEG_WWA) and (M_MSEG_WWE, M_MSEG_WWF, or M_MSEG_WWA) depending on the material document that was being canceled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just thought I would mention it, if somebody searches threw the forum for a similar need.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ahmed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 12 Apr 2006 15:20:31 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-04-12T15:20:31Z</dc:date>
    <item>
      <title>Replicating authorization checks using SAP provided function calls</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/replicating-authorization-checks-using-sap-provided-function-calls/m-p/1236274#M140873</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;All:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Due to a business scenario, we need to validate if a user has access to execute transaction MBST.  We need to check the security of the user in question before they issue other material movements in the system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I cannot determine if the function modules AUTH_CHECK_TCODE and/or AUTHORITY_CHECK_TCODE will do the same for me.  Or will the above functions only do half the job?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ahmed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Apr 2006 16:16:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/replicating-authorization-checks-using-sap-provided-function-calls/m-p/1236274#M140873</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-04-11T16:16:51Z</dc:date>
    </item>
    <item>
      <title>Re: Replicating authorization checks using SAP provided function calls</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/replicating-authorization-checks-using-sap-provided-function-calls/m-p/1236275#M140874</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is not direct answer. But if none of mentioned function modules works fine you can do it "manually" in ABAP code&lt;/P&gt;&lt;P&gt;using tables usr02, agr_users, agr_tcodes, agr_define ,agr_1252 and eventualy tstsc and usvart for descriptions in required language.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BR, Jacek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Apr 2006 16:39:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/replicating-authorization-checks-using-sap-provided-function-calls/m-p/1236275#M140874</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-04-11T16:39:24Z</dc:date>
    </item>
    <item>
      <title>Re: Replicating authorization checks using SAP provided function calls</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/replicating-authorization-checks-using-sap-provided-function-calls/m-p/1236276#M140875</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't know how you are planning to do this. Material movements can be done by users using several tcodes. How are you planning to check in each of those transactions to see if the user has MBST access or not? These are standard transactions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So what exactly you intend to find out? Are you looking for a report that shows all the users who have access different material movement transactions but not MBST or you actually want to do an authority check in each of these transactions? The second one is not possible. You can only do a report and pass it on to basis so that they can include MBST access to all those users in your report.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Srinivas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Apr 2006 16:44:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/replicating-authorization-checks-using-sap-provided-function-calls/m-p/1236276#M140875</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-04-11T16:44:52Z</dc:date>
    </item>
    <item>
      <title>Re: Replicating authorization checks using SAP provided function calls</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/replicating-authorization-checks-using-sap-provided-function-calls/m-p/1236277#M140876</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 find bunch of reports in tr.SUIM ..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;also check the post &lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="1470474"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Apr 2006 16:47:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/replicating-authorization-checks-using-sap-provided-function-calls/m-p/1236277#M140876</guid>
      <dc:creator>former_member181966</dc:creator>
      <dc:date>2006-04-11T16:47:18Z</dc:date>
    </item>
    <item>
      <title>Re: Replicating authorization checks using SAP provided function calls</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/replicating-authorization-checks-using-sap-provided-function-calls/m-p/1236278#M140877</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jacek,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the info.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, I am trying to refrain myself from writing a custom validation like you advised.  I was also aware of the tables although you did help in adding one more table I should look at.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But getting back to the original question, is their any "standard" call that I could execute to determine if a user can execute transaction MBST.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your thoughts are appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ahmed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Apr 2006 17:57:26 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/replicating-authorization-checks-using-sap-provided-function-calls/m-p/1236278#M140877</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-04-11T17:57:26Z</dc:date>
    </item>
    <item>
      <title>Re: Replicating authorization checks using SAP provided function calls</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/replicating-authorization-checks-using-sap-provided-function-calls/m-p/1236279#M140878</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Simply do AUTHORITY_CHECK on S_TCODE object.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Apr 2006 18:45:35 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/replicating-authorization-checks-using-sap-provided-function-calls/m-p/1236279#M140878</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-04-11T18:45:35Z</dc:date>
    </item>
    <item>
      <title>Re: Replicating authorization checks using SAP provided function calls</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/replicating-authorization-checks-using-sap-provided-function-calls/m-p/1236280#M140879</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Srinivas,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had thought about using the Authority-check as SAP prefers to use this across most programs.  However, as I debugged thru MBST I noticed SAP does not issue a authority check on S_TCODE but rather it was using the function modules I had mentioned in my first request.  SAP further proceeded to issue authority checks against objects (M_MSEG_WWA) and (M_MSEG_WWE, M_MSEG_WWF, or M_MSEG_WWA) depending on the material document that was being canceled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just thought I would mention it, if somebody searches threw the forum for a similar need.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ahmed&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Apr 2006 15:20:31 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/replicating-authorization-checks-using-sap-provided-function-calls/m-p/1236280#M140879</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-04-12T15:20:31Z</dc:date>
    </item>
  </channel>
</rss>

