A lot of companies using SAP have taken the decision to restrict the use of SAP standard transactions such as SM30 (Maintenance View) or SE16 (Data Browser) for end users. These decisions are most often taken for concerns regarding data protection or security reasons.
However, there are cases where the end users must access data or maintain some data, even on production systems. The customers then have to develop their own program or API for each request. These developments are expensive, must be maintained and over time, the customer loses the main reason for the interdiction of the SE16 and SM30 transactions, namely the restriction on access to display or modify SAP-tables.