For some, SE16 is an unfamiliar transaction code. For SAP administrators, it is part of daily life — and often, unfortunately, for others too. This article covers what SE16 does, how many variants exist, and why access to it needs to be carefully controlled.
For some SE16 may be an unknown acronym. For others it is the "bread and butter." It is a SAP transaction remarkably familiar to administrators. And often not only them, unfortunately.
But what is it used for? How many versions of it are there? How do you use it and what are the risks involved?
We discuss it in this article!
Topics: se16n, se16, SAP Security, supporto sap ams, sap query, SAP GDPR
For those that don't know SAP's authorization aspects this title might be just a tongue-twister.
On the contrary for those who manage authorizations in SAP these are very well-known authorization objects. How should you go about managing them?
Topics: se16, s_tabu_dis, s_tabu_rfc, s_tabu_nam, sql
Every Friday a new post, interview or content related to SAP Security.
Aglea s.r.l. P. IVA: IT 03868780960 - 2026 | Copy | Note legali
