Security transaction codes that you might have never used

N – Transaction N is the Quickstart SE16N transaction code. You can quickly invoke SE16N with this transaction code. However, this was removed by SAP now. Refer SAP Note 1115699.

SE16T000 – This is a Data Browser for Table T000. Used as alternative to SCC4, and SE16 transaction codes, since both are critical. Some of your auditor roles might have this transaction code. Just to avoid giving authorization to this transaction code also, SAP has introduced a new transaction code RSAUDIT_SYSTEM_ENV. SAP Note 1433352 will get you this.

RSUSR200_UNUSED30 – This is an extension to RSUSR200 which add 30 days as default to No. days since last logon. This still uses the RSUSR200 program with a correction. Refer SAP Note 1479062 for more information.

SU12 – SU12 does not call its own report/program. Instead, it calls SU10 which triggers report SAPMSUU0M. Don’t know why SAP has an additional transaction code 🙂

SU01 Backdoors – User Maintenance can be invoked not only with SU01. There are about 10 transaction codes which are known as SU01 Backdoors. Read more about them at SU01 Myths.

Author - Raghu Boddu


Raghu is a SAP Security specialist with expertise in SAP Governance, Risk Management, Compliance and SAP Forensic Security. He is a regular blogger of topics like Security, Governance & Compliance, Application Security, Technology and other trending topics.

VN:F [1.9.22_1171]
Rating: 8.9/10 (8 votes cast)
Security transaction codes that you might have never used, 8.9 out of 10 based on 8 ratings

Share This Post

Related Articles

Leave a Reply

© 2019 SAP Security Expert. All rights reserved. · Entries RSS · Comments RSS
Managed by 7n Domains