ABAP Runtime Error: No RFC authorization for function module RSAO_BICS_SESSION_INITIALIZE. (ID-107013)

[chad11]

Hi Folks,

I have AO setup with SSO to BW. Working fine in 2 of my environments for me but in my Production

environment we are seeing this error when choosing our data source in AO (click next) :

ABAP Runtime Error: No RFC authorization for function module RSAO_BICS_SESSION_INITIALIZE. (ID-107013)

Looking for some assistance in identifying the needed security in BW to fix this error message.

Here is some background and spec's.....

Our system is as follows:

BOE 4.1 SP1 Patch 1 

AO version: 1.4 SP11

BW: 7.31 SP12

SSO to BW is enabled (SNC & STS)

SSO setup through BOBJ, users authenticating with LDAP and using WebI/AO to a Olap Connection set to SSO.

This is working in my Development and UAT environment, it is our move to Prod where I see this happening.

I am working with my security and Basis team to dig through this further but thought I would put this out there

should anyone have come across this error message and be able to share their resolution.

appreciated,

Chad

[former_member151004 · Accepted solution]

Hi Chad,

Could you please check if the workaround described below help on your case?

When it is required to open a OSS connection with a previous version that does

not have this correction, you can use following workaround to avoid the

exception.

• Close Analysis Office
• Open your Explorer
• Open %AppData% folder

Navigate to:

              \Roaming\SAP AG\SAP BusinessObjects Advanced Analysis\cache

(the whole path would like e.g.  C:\Users\D057321\AppData\Roaming\SAP AG\SAP BusinessObjects Advanced Analysis\cache)

• Delete OSS.cache
• Start Analysis Office & open the OSS connection

This workaround needs to get repeated every time when opening a OSS connection to a different customer.

This workaround is described on the SAP note 1833344.

Thanks,
Diego Ferrary

[chad11 · Accepted solution]

Thanks for the response Diego - Gave it a try but it didn't make a difference.

Working with my security team in the BW environment they used STAUTHTRACE

It was found that the following RFC Authorizations were missing:

missing RFC authorization to Function Group RSAO_CORE

and RSBOLAP_BICS_DESIGN_TIME

Is there an SAP issued list of RFC or other functions that a user is in need of having for

refreshing using Analysis or WebI? 

Found the following in my research and we are looking into this further now.

http://scn.sap.com/community/semantic-layer/blog/2014/06/19/pre-requisite-authorizations-in-sap-bw-s...

This article suggests the following:

To run the WebI reports against SAP BW system, end uses required below minimal set of

authorizations in the SAP BW system.

• S_RFC (Authorization Check for RFC Access)
• S_RS_ADMWB (Data Warehousing Workbench - Objects)
• S_RS_AUTH (BI Analysis Authorizations in Role)
• S_RS_ICUBE (Data Warehousing Workbench - InfoCube)
• S_RS_IOBJ (Data Warehousing Workbench - InfoObject)
• S_RS_ISET (Data Warehousing Workbench - InfoSet)
• S_RS_MPRO (Data Warehousing Workbench - MultiProvider)
• S_RS_ODSO (Data Warehousing Workbench - DataStore Object)

[former_member151004 · Accepted solution]

Hi Chad,

Answering: Is there an SAP issued list of RFC or other functions that a user is in need of having for refreshing using Analysis or WebI? I don't believe that we have some RFC issue.

Could you please execute the following steps and check if the issue remains?

o  Close Analysis Office
o  Open your Explorer
o  Open %AppData% folder
o  Navigate to: %Appdata%\Roaming\SAP AG\SAP BusinessObjects Advanced Analysis\cache
o  Delete OSS.cache
o  Start Analysis Office & open the OSS connection

Thanks,
Diego Ferrary

[chad11 · Accepted solution]

This was NOT a cache issue - in fact we have jumped around to multiple environments and

never have needed to delete the cache.

Please note:

Working with my security team in the BW environment they used STAUTHTRACE

It was found that the following RFC Authorizations were missing:

missing RFC authorization to Function Group RSAO_CORE

and RSBOLAP_BICS_DESIGN_TIME

This was the what resolved it:

My BW security team added the RFC to the authorization S_RFC

I hope this helps out.

[MPGraziano · Accepted solution]

This message was moderated.

[former_member194892]

Hello Chad,

Please have a look at the following OSS note : 1940100 - Error "Design-time query not available (WIS 00000)" using BICS connectivity with WebI in B...

D.

[chad11]

thanks David - appreciate the reply.

I have looked at this for other issues in my initial set up and testing. This was previously implemented

and had no bearing on the error that I reported.