Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

SCU3 Activity 02 on S_TABU_DIS Auth Group SA?

corinne_lofts
Participant
0 Kudos

Hi,

We recently moved from EHP5 to EHP7 and an additional check is done when using transaction SCU3 for S_TABU_DIS / Group SA / Activity 02.

We have 2 Z tables maintained by our data team; 2 Z transactions allows for the table maintenance via SM30; both tables have been associated to a Z authorisation group.

Since EHP7 has been implemented we can no longer view the log on these tables.

SU53 and traces are listing the need for S_TABU_DIS Activity 02 for the SA Auth group; that group is created by SAP and covers quite a few other tables; I have tried to limit the access to the log table DBTABLOG via S_TABU_NAM but it is still not working.

I can't understand why activity 02 should be required at all in that scenario and can't find any related OSS Note.

Has anyone come accross a similar issue. I am not sure why a change activity shoudl be required when I only want to display the change log.

thank you

Coco

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Maybe the note 1909124 will help you.

regards,

Sebastian

7 REPLIES 7

Former Member
0 Kudos

Hi,

Raise it to SAP,

02 is not required for display and you should be able to bypass S_TABU_DIS for S_TABU_NAM.

BR,

Mangesh

0 Kudos

Thanks Mangesh;

That is what I thought; I will log a call and update this question later on.

Ta!

Coco

martin_voros
Active Contributor
0 Kudos

Hi,

are you sure that missing authorization for DBTABLOG is causing your issue? It is checked because you can delete logs in SCU3. Hence it has to check for 02 - change. It should not get checked when you only want to display logs. Have you tried to debug this transaction and see what's going behind?

Cheers

0 Kudos

Actually, looking at FM DBLOG_READ_TABLE it does check for update even it only reads data from log table. This seems to be a regression introduced by note 1735308.

Cheers

0 Kudos

Thanks Martin,

I will log with SAP and upate the discussion later.

Coco

Former Member
0 Kudos

Maybe the note 1909124 will help you.

regards,

Sebastian

0 Kudos

Thanks Sebastian. That fixed it.