<?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: Structural Authorizations in BI in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/structural-authorizations-in-bi/m-p/3724041#M896380</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I dont think BI supports Context based Sensitive Authotizations like how you have in R/3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In R/3 you have P_ORIGINCON that supports the Context based Sensitive Authorizations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think  in this case Employer 2 will be able to see the entire leave absence for 2007-2008 unless the report is based on the validity period or other restrictions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Kiran Kandepalli.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 16 May 2008 16:39:39 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-05-16T16:39:39Z</dc:date>
    <item>
      <title>Structural Authorizations in BI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/structural-authorizations-in-bi/m-p/3724040#M896379</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'm working on a new BI7 project which is extracting structural authorisations from HR.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I'm not sure about is what will happen in the following scenario:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;During 2007, manager 1 in org unit 123 is responsible for employee 1. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In 2008, employee 1 moves to manager 2 who is responsible for org unit 456.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If manager 2 runs a report displaying absence covering 2007 and 2008, would he receive all the absence for employee 1 including 2007 or would it just display the absence for the time manager 2 was responsible for employee 1?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds,&lt;/P&gt;&lt;P&gt;Mark.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Apr 2008 10:58:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/structural-authorizations-in-bi/m-p/3724040#M896379</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-04-25T10:58:53Z</dc:date>
    </item>
    <item>
      <title>Re: Structural Authorizations in BI</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/structural-authorizations-in-bi/m-p/3724041#M896380</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I dont think BI supports Context based Sensitive Authotizations like how you have in R/3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In R/3 you have P_ORIGINCON that supports the Context based Sensitive Authorizations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think  in this case Employer 2 will be able to see the entire leave absence for 2007-2008 unless the report is based on the validity period or other restrictions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Kiran Kandepalli.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 May 2008 16:39:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/structural-authorizations-in-bi/m-p/3724041#M896380</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-05-16T16:39:39Z</dc:date>
    </item>
  </channel>
</rss>

