RSA3 No Authorization for Checking Extractors (error)

[Former Member]

RSA3 No Authorization for Checking Extractors (error)

Hi Everyone,

I am trying to test a scenario where RSA3 access is required and the test ID has all the authorizations. When I execute RSA3 and try to Extract in Dialog mode, I get this message: No Authorization for Checking Extractors (error)

SU53 reveals that S_TABU_DIS is needed with ACTVT=03, and DICERBLS=&NC&

Do I have to give this access? or is there any other way.

[Former Member · Accepted solution]

You definitly missing some authorization to run it in dialog mode, any how it is test id, you can get sap all access and run it. It should work fine.

[Former Member · Accepted solution]

SU53 reveals that S_TABU_DIS is needed with ACTVT=03, and DICERBLS=&NC&

When I create a small role with this authorization and assign it to the test ID, the extracts work.

My question is: Do I have to assign this Authorization to all IDs that would need RSA3 access eventually? or there is another way to tackle this issue? I am thinking in terms or customization. I think I have provided all the details that are necessary for this issue. Let me know if there is anything missing and I will fill you in.

Sincerely,

Amrit

[Former Member · Accepted solution]

Hi Amrit,

Yes, you have to assign the authorization to all users who need RSA3. I do not think many users would need RSA3 access as it is just to test the datasources and debug them when necessary.

Authorization object S_RO_OSOA should work in your case.

Thanks

Amit

[RamanKorrapati]

If your checking HR related data source then you need to have roles - P_BAS_ALL/P_PLAN_ALL.

[Former Member]

Hi Amrit,

Sometime, to extract data from specific datasource, extra authorization is required.

Try to perform the same activity using your coleegue's user ID, fi it works, then request basis security team to compare the roles between your's and your collegue's user ID.

Thanks,

[Former Member]

Hi,

Please use tracing tool then (ST01, RSECADMIN) to understand which kind of authorities are missed.

Take help from basis.

One more thing as suggested by Ramanjaneyulu, Please check roles who has authorization on RSA3 and ask security/basis team to add the same roles to your user id also.

Thanks.

[RamanKorrapati]

Hi,

Take basis team help and get the required authorization to execute RSA3.

Other take your TL help and test the RSA3. it may work your TL user id(expecting has he may be required access).

Thanks

[Former Member]

Ask Basis to keep authorization trace on, as there can be authorization issue to read a data from specific table. In such a case you will not able to capture same in su53 screen.

Work closely with Security to identify missing authorization.

Regards,

Ganesh

[former_member197610]

Hi Amrit,

S_TABU_DIS is not needed for the extraction authorization, check for auth objects - S_RO_OSOA assigned in  the  test id roles.

Are there any missing auth errors in the SU53 display? And which datasource you are using in RSA3 ?

[Former Member]

The role already has this auth object S_RO_OSOA with following values:

Activity                       03                                                                          ACTVT

DataSource                     *                                                                           OLTPSOURCE

DataSource Application Compone *                                                                           OSOAAPCO

Subobject for DataSource       DATA, DEFINITION                                                            OSOAPART

[former_member197610]

Amrit,

Pls make sure you have the auth objects S_RO_OSOA  defined in all your system, ECC, BW and APO .

This should solve the issue.