Skip to Content
0
Former Member
Dec 04, 2009 at 05:44 AM

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

34 Views

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;

My concern is why still check S_TCODE "SE16" for customizing tcode in ECC system