excluded HR structural profiles not corectly loaded into BI

[Former Member]

Hi

We are using structural authorisation profiles in HR and use the functionality to exclude certain parts of the org structure by using the exclusion flag in OOSB. This works perfect for HR.

The problem arises when we use the standard SAP process to upload this data in DSO on BI. Excluded org units are actually showing as "I EQ nnnnnn" in the generated analysis authorisations that are created for the users.

Does anybody know about a workaround, without negatively affecting performance, because it seems that BI can not handle "exclusions"?

Thank you for your help,

Johan Lauwens

[sdipanjan]

Hi,

The "Flag for Excluded Structural Profiles" was not being transferred by the BI content responsible for acting the role of Data Source in earlier SP levels of NW BI 7. Later it has been fixed by newer version of support packages. Please upgrade the SP level as per the [SAP Note# 1514901|https://websmp230.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=1514901] and also make sure that the [SAP Note#1342620|https://websmp230.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=1342620] has been implemented with the included note (# 1096931) stated in it.

After you implement these notes, redraw the source data once more for the affected set of users.

Regards,

Dipanjan

[Former Member]

Dipanjan

Thank you for your quick and helpfull reply. My main concern is however that SAP BI does not allow exclusions (we know that) BUT treats what should be handled as exclusions as includes . This is tototaly contrary to what the intent was on R3 when excluding org units via transaction OOSB.

I am looking for a solution that would exclude these intended exclusions correctly in BI instead of addding them to the allowed authorisation values.

Kind regards,

Johan

[sdipanjan]

>

> Thank you for your quick and helpfull reply. My main concern is however that SAP BI does not allow exclusions (we know that)

In this case you are not creating or manipulating the standard BI authorization concept. Rather you are inheriting the image of Authorization concept of other system ........ like parasites

So, the concept of exclusion (as you have seen in Analysis Authorization for BI) is not valid for this case. Since the inheritance of other authorization structure is possible here in BI so you can see the display variant of some HR Structural tcodes like OOSP, OOAW, OOSB etc. And as we don't have the authority for maintaining them in BI (only using after getting transferred) so we don't have the tcodes OOAC, OOPS etc.

> BUT treats what should be handled as exclusions as includes . This is tototaly contrary to what the intent was on R3 when excluding org units via transaction OOSB.

>

Please check the above paragraph discussion. Also update the system with the Support pack level as per the notes mentioned. As we are not manipulating BI authorization concept as I told already so there is no interference of the BI authorization concept.

Regards,

Dipanjan