Homepage for SAP Professionals

To create custom transaction, it is suggested that you define the naming convention as simple as possible to make sure that users will remember the transaction and do not have to second guess. If a user needs a custom transaction to browse table MARA, you can either call the transaction ZSE16_MARA or simply ZMARA. continue reading…

There are quiet a few companies that want to give end-users access to extract table data via SE16 or SE16N. If you decide to give SE16N, please read our blog that shoes the pitfalls & danger of giving SE16N – In addition, the auditors, security people and basis folks worry about using having transactions such as SQVI, SQ01 etc…. Why is that? For starters, users can access confidential data once they can use SQVI as it is not protecting the data to be extracted by company code or other organizational values. A guideline on how to convert SQVI report into a InfoSet query will be published on this blog.

In addition, SQVI reports, if created poorly, can have a drag on system performance as the endusers never have performance in their minds and run queries over millions of records with inadequate table joins.  The same applies to SQ01 – SQ03 transactions. These are a red flag for most of the auditors also if the user is allowed to add custom code on InfoSet level.  Security managers usually recommend that SQxx transactions are used in a development environment and the queries mapped to transactions so that these can go through Change Control and given to users via roles in a controlled manner . continue reading…

No matter security on table editing. When in transaction SE16N use the command &SAP_EDIT in the command field in SAP and off you go: edit table content directly. This works if you have debug with changes access for object S_DEVELOP, but S_TABU_DIS is ignored as well as the system settings regarding changes. If you use this function for transaction, master data or other tables that cannot be changed with SM30, you can cause quiet some damage.  So, use with caution and this is NOT a Best Practice by all means, but to educate you on a little documented feature:

Step 1: Use transaction SE16N or transaction N (yes, there is a transaction called just ‘N’)  and enter a table of your choice, for example SKA1 G/L Account Master (Chart of Accounts)

2) In the command field enter ‘&SAP_EDIT’ and press enter. The maintenance indicator in SE16N will switch on.

3) Limit the search of your data or execute for all values and you will see, that the table entries can be edited:

If you limit the users access not to have access to S_DEVELOP with change activities for object type DEBUG, this function will not be possible (tested on ECC5)

If you want to allow this function, you can audit who changed data via SE16N by browsing the following tables;

SE16N_CD_KEY : Change Documents – Header
SE16N_CD_DATA : Change Documents – Data

You can also run report RKSE16N_CD via SE38 (or create a custom transaction for it for ease of use).