Config Display in Production

Question: I wanted to get a general consensus on providing SPRO (activity 03 only) to super users in PRD. The thing that bothers me is that to effectively make SPRO work, you have to put S_TCODE of *. Has anyone found differenlty? With SPRO only, I find that the user will fail on multiple tcodes. I really dislike putting tcode of * in any production roles.

Thanks for any advice!

Answer:
You do not need to give S_TCODE = * to give SPRO in diplay mode.

create a role and save and teh run the following report changing the code to reference your role
REPORT ZLOADIMGTCODE .
tables: cus_actobj, agr_tcodes, cus_acth.
data: ica like cus_actobj occurs 1000 with header line,
icah like cus_acth occurs 1000 with header line,
iagrtc like agr_tcodes occurs 4000 with header line.
Parameters: p_mandt like sy-mandt.
Start-of-selection
select * from cus_actobj into table ica.
sort ica by tcode.
delete adjacent duplicates from ica comparing tcode.
Select * from cus_acth into table icah.
Sort icah by tcode.
delete adjacent duplicates from icah comparing tcode.
iagrtc-agr_name = 'S:CONFIG_ALL'.
iagrtc-TYPE = 'TR'.
iagrtc-direct = 'X'.
iagrtc-mandt = p_mandt.
loop at ica.
iagrtc-tcode = ica-tcode.
append iagrtc.
endloop.
Loop at icah.
iagrtc-tcode = icah-tcode.
append iagrtc.
Endloop.
Sort iagrtc by tcode.
delete adjacent duplicates from iagrtc comparing tcode.
modify agr_tcodes client specified from table iagrtc.
This does cause the role to have a long menu, but if you create a folder and then write a quick abap to shift the tcodes into the folder then the user will only see the folder ratehr thantt he long list.

No comments:

topics