Why still check S_TCODE "SE16" for customizing tcode (only in ECC)

[Former Member]

I want to limit the access for SE16. So i need to create customizing tocde that allow user to access the specific table by SE16; I try to create this tcode in SE93;

When this tcode assign to role and add the additional necessary auth obj. S_TABU_DIS, put the value for AuthGrp with *, Actvt = 03; When i do the testing, the system still check S_TCODE "SE16". means testing id also need authorization "SE16". If this T-code assign to testing user, then i cant limit the access for SE16;

I also have do the testing in CRM and use the same way to create the customizing tcode. In CRM system, no need S_TCODE "SE16", only assign customizing tcode & S_TABU_DIS to testing user, is ok, this customizing tcode can be used by tester directly;

[RainerKunert]

Hello,

create a parameter transaction in SE93. An example is the already existing parameter transaction SE16_MARA. You can specify the table in the parameters of the transaction.

You will still need S_TABU_DIS. To enter the * isn't a good idea. The better way is to get the correct table dictionary class for the table you have assigned to the parameter transaction. Get the class in transaction SE54 (there you can also specify one, if no class is assigned yet) or from table TDDAT.

If you have a class and a parameter transaction you should join them in SU24. Add object S_TABU_DIS to your transaction and specify activity and class for S_TABU_DIS. Then these values will be added to the role, if you add the transaction in the menu.

regards

Rainer

[Bernhard_SAP]

Hi,

the s_tcode check is hardcoded (see also sap note 947557 ). The only way to avoid that check is the possibility that Rainer mentioned above.(parameter t-code)

b.rgds, Bernhard