SAP Library - Find your answers

Question: Hi Guru's

How to allow user to see only Area Menu and SAp Menu but not the list of transactions asssigned to his role. I tried in 2 ways..

1. I blocked the User menu , which also blocks Area menu.
2. Deleted transaction code list from Menu of User role and generated the profile. So now in usermenu i can not see any transactions. It is worked.
Here problem is S_tcode is in Display mode only, so we can not add any additional transactions in future. I do not like to uncheck transaction codes in SE97.

Apart from these, is their any other ways to solve this.

Thanks in advance

Pranu

Answer:
Pranu

User menu vs Sap menu and restricting views of transaction ahve been discussed oin ths forum many times before. Usually in those discussions the question is asked "Why do you not want users to see transactions they are allowed to use? It does not add to security, so what is the purpose of hiding access?"

The display only status of S_TCODE has been disucssed a lot recently too. I'm not gonig to answer your question here, because the S_TCODE issue and the menu issue could both be answered by you using the search facility.
_________________
Sandi
~~~~

Apparently Father Christmas, the Easter Bunny, the Tooth Fairy and Star Wars aren't real


Answer:
"Why do you not want users to see transactions they are allowed to use? It does not add to security, so what is the purpose of hiding access?"

If you cannot trust your users enough to let them see the transactions they have access to, then your design should be changed to only give them the access that your risk profiling permits.
Security by obscurity is not proper security

Use profile SAP_UONL while client copy.

By using the following parameters, you can limit the maximum use of the process-specific memory. This in turn limits the maximum use of swap space by an R/3 application server.

Consider the following parameters:

You can find more information on the functions of these parameters under Limits for Allocating Heap Memory in Functions of the R/3 Memory Management System.

Normally, only background work processes use a large amount of swap space.

Dialog processes do not usually use a lot of swap space, as long as the following conditions apply:

• The R/3 Extended Memory is not used up (set with parameter
em/initial_size_MB); and
• Not many of the user contexts have exceeded the upper limit for using the Extended Memory (set with parameter
ztta/roll_extension).

The following generally applies: The more main memory that an application server has, the better the performance.

If the CCMS Alert Monitor or Transaction ST06 (see Monitoring the Status of the R/3 System) displays a high paging rate for the operating system, decrease the size of the roll and paging buffers (only Windows NT and UNIX). In the profile management of the CCMS, set the profile parameters rdisp/ROLL_SHM and rdisp/PG_SHM to 0. You must change the profiles used by the R/3 application servers on the relevant host system.

If free memory is available even during heavy system usage, or if there is only low paging activity, you can increase the size of the roll and paging buffers. This decreases the accesses to the hard disk caused by rolling and paging.