No matter security on table editing. When in transaction SE16N use the command &SAP_EDITin 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).
Reblogged from Home4Sap.com