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: 

Missing Radio Button for favorites in APO Transactions SAPAPO/AMON1

Former Member
0 Kudos

Can anyone help here

I am missing the Favorites button in transaction SAPAPO/AMON1 - Alert Monitor Display. I need to know what object

controls this so I can create a new role and assign access as needed to selected Admin staff who will assign user access to required Favorites

Thanks

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi Tyson,

as Julius describes St01 gives you a clear list ofauthorization object, which are checked:


Objekt           Text               
S_TCODE    RC=0  TCD=/SAPAPO/AMON1; 
C_APO_AMON RC=0  ACTVT=22;          
C_APO_AMON RC=0  ACTVT=16;          
C_APO_AMON RC=0  ACTVT=06;          
C_APO_AMON RC=0  ACTVT=02;          
C_APO_AMON RC=0  ACTVT=02;          
C_APO_AMON RC=0  ACTVT=06;          
C_APO_AMON RC=0  ACTVT=22;          
C_APO_AMON RC=0  ACTVT=16;          
C_APO_AMON RC=0  ACTVT=02;          

In the MODULE initialize_1600 OUTPUT of functiongroup /SAPAPO/ASTAND there is the coding:


* Prüfe Änderungsberechtigung
    AUTHORITY-CHECK OBJECT 'C_APO_AMON'
             ID 'ACTVT' FIELD '02'.      "change
    IF sy-subrc NE 0.
      l_exclude_tab_1600 = 'DELETE_SET'.
      APPEND l_exclude_tab_1600.
      l_exclude_tab_1600 = 'SAVE'.
      APPEND l_exclude_tab_1600.
      l_exclude_tab_1600 = 'FAVOURITES'.
      APPEND l_exclude_tab_1600.
 . . .

So if a user has not got the Object 'C_APO_AMON' and the allowance to make changes the button 'Favourites' is not displayed.

Regards

p121848

3 REPLIES 3

Former Member
0 Kudos

If security can control it, then the accepted way which works in most cases is to start an ST01 auth trace in a QAS or DEV system and trace whether authority makes the button visible; or once the tcode is started then whether the button is usable / savable.

Generally, favourites belong to the user, so they will most probably change it anyway (for themselves).

I can imagine that changing user's favourites is an origanizational control (e.g. support). So perhaps you should reconsider the choice of transaction (or choice of user who has access to it)...?

Cheers,

Julius

Former Member
0 Kudos

Hi Tyson,

as Julius describes St01 gives you a clear list ofauthorization object, which are checked:


Objekt           Text               
S_TCODE    RC=0  TCD=/SAPAPO/AMON1; 
C_APO_AMON RC=0  ACTVT=22;          
C_APO_AMON RC=0  ACTVT=16;          
C_APO_AMON RC=0  ACTVT=06;          
C_APO_AMON RC=0  ACTVT=02;          
C_APO_AMON RC=0  ACTVT=02;          
C_APO_AMON RC=0  ACTVT=06;          
C_APO_AMON RC=0  ACTVT=22;          
C_APO_AMON RC=0  ACTVT=16;          
C_APO_AMON RC=0  ACTVT=02;          

In the MODULE initialize_1600 OUTPUT of functiongroup /SAPAPO/ASTAND there is the coding:


* Prüfe Änderungsberechtigung
    AUTHORITY-CHECK OBJECT 'C_APO_AMON'
             ID 'ACTVT' FIELD '02'.      "change
    IF sy-subrc NE 0.
      l_exclude_tab_1600 = 'DELETE_SET'.
      APPEND l_exclude_tab_1600.
      l_exclude_tab_1600 = 'SAVE'.
      APPEND l_exclude_tab_1600.
      l_exclude_tab_1600 = 'FAVOURITES'.
      APPEND l_exclude_tab_1600.
 . . .

So if a user has not got the Object 'C_APO_AMON' and the allowance to make changes the button 'Favourites' is not displayed.

Regards

p121848

Former Member
0 Kudos

Thanks so much p121848 and Julius...exactly what I was looking for