<?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 MRS - authorization objects (Multi Resource Scheduling) in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/mrs-authorization-objects-multi-resource-scheduling/m-p/7360887#M1541867</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are implementing MRS for a customer who does not have proper structural authorizations in place, and they would like to avoid using evaluation paths for the authorization check.&lt;/P&gt;&lt;P&gt;Is there a way to use cost centers to limit user access in MRS? We tried to use cost centers in auth. object MRSS/PB1, but it does not work.&lt;/P&gt;&lt;P&gt;Is it possible to modify the default MRS auth. objects and add some extra auth. fields? Would that auth. check work in planning board?&lt;/P&gt;&lt;P&gt;Is there any other way to limit user access in MRS planning board rather than using evaluation paths? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Simon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 12 Oct 2010 22:51:42 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2010-10-12T22:51:42Z</dc:date>
    <item>
      <title>MRS - authorization objects (Multi Resource Scheduling)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/mrs-authorization-objects-multi-resource-scheduling/m-p/7360887#M1541867</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are implementing MRS for a customer who does not have proper structural authorizations in place, and they would like to avoid using evaluation paths for the authorization check.&lt;/P&gt;&lt;P&gt;Is there a way to use cost centers to limit user access in MRS? We tried to use cost centers in auth. object MRSS/PB1, but it does not work.&lt;/P&gt;&lt;P&gt;Is it possible to modify the default MRS auth. objects and add some extra auth. fields? Would that auth. check work in planning board?&lt;/P&gt;&lt;P&gt;Is there any other way to limit user access in MRS planning board rather than using evaluation paths? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Simon&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Oct 2010 22:51:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/mrs-authorization-objects-multi-resource-scheduling/m-p/7360887#M1541867</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-10-12T22:51:42Z</dc:date>
    </item>
    <item>
      <title>Re: MRS - authorization objects (Multi Resource Scheduling)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/mrs-authorization-objects-multi-resource-scheduling/m-p/7360888#M1541868</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Simon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have checked the authorization objects related to MRSS in SU24 where I can see based on the T code. Did you find a way how to get relevant for SAP MRS only like the Resource Planner&amp;nbsp; etc authorizations he need if you have found something like that please share.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 16 Dec 2014 10:49:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/mrs-authorization-objects-multi-resource-scheduling/m-p/7360888#M1541868</guid>
      <dc:creator>former_member201296</dc:creator>
      <dc:date>2014-12-16T10:49:23Z</dc:date>
    </item>
  </channel>
</rss>

