Activate &SAP_EDIT in SE16N (SAP ECC 6.0)
Moderator warning
“This is a powerful hack which can be used to change even the standard tables and even in a production environment (if you have CHANGE access in Debugger). The changes cannot be tracked in anyway and it may lead to inconsistencies. I would think twice before using this..”
“you could not make use of this in our production environment. With a right authorization concept in place you would not be allowed to debug in production.”
“To prevent its misuse by end users, they should be restricted with debugging authorizations.”
“This functionality has been removed by SAP from Ehp5 (SAP Note 1420281) onwards”
Activate &SAP_EDIT in SE16N (SAP ECC 6.0)
In SAP ECC 6.0 EHP6, the function code &SAP_EDIT, which enables the change mode of transaction SE16N, is deactivated (SAP Note 1420281) due to security breaches that were detected. In order to activate it (temporarily), follow the steps below:
- Go to SE16N, as usual, and type the table for which you want to make modifications.
- Instead of typing
&SAP_EDITin the command field, type/Hand press “Enter” key to activate debugging. - Press F8 key to enter the data browser for the above table.
- If you are using EHP6, then you may need to press F7 for several times to reach to the Screen 100 of program SAPLSE16N
- While in debugging mode & once you are in Screen 100, enter the two variables GD-EDIT and GD-SAPEDIT and press “Enter” key.
- For each variable, click on the change button, change the value to an uppercase “X” and press “Enter” key.
- Press F8 key to exit debugging and enter the table in change mode.
Here is how the Entry to be changed in the debug mode.
Please be careful while using this trick.
Cheers,
Bharat Bajaj
This is a powerful hack which can be used to change even the standard tables and even in a production environment (if you have CHANGE access in Debugger).
The changes cannot be tracked in anyway and it may lead to inconsistencies. I would think twice before using this..
you could not make use of this in our production environment. With a right authorization concept in place you would not be allowed to debug in production.
Hi Yuvraj,
This is just an alternate to &SAP_EDIT & majorly meant to be used by developers & support persons. To prevent its misuse by end users, they should be restricted with debugging authorizations.
Hello Yuvaraj S,
The changes cannot be tracked in anyway and it may lead to inconsistencies.
You can track changes made in SE16N by
&SAP_EDIToption in SE16N_CD_KEY table.Regards,
Devendra B.
Great job...
I usually use the FM SE16N_INTERFACE... I don't know if in Production this can be used though..
Module fonction SE16N_INTERFACE
Majuscules/minuscules Paramètres d'import Valeur
I_TAB EKKO
Paramètres d'import Valeur
I_SAPEDIT X
I_TAB EKKO
I_EDIT
I_SAPEDIT X
I_NO_TXT X
I_MAX_LINES 500
I_LINE_DET
I_DISPLAY X
I_CLNT_SPEZ
I_CLNT_DEP
I_VARIANT
I_OLD_ALV
I_CHECKKEY
I_TECH_NAMES
I_CWIDTH_OPT_OFF
I_SCROLL
I_NO_CONVEXIT
I_LAYOUT_GET
IT_SELFIELDS 0 Entrées
Tables Valeur
IT_OR_SELFIELDS 0 Entrées
IT_SELFIELDS 0 Entrées
You can use UASE16N transaction if SE16N is not working.
UASE16N is obsolete
hi all ;
please check related tables when you update a record...
UASE16N is obsolete now in ECC and SAP throws you out of the transaction if you try to use it.
Hi Shyam,
are you facing any error ? make sure you are doing the things right.
regards,
Bharat
Hi Bharat,
Amazing workaround. Thanks for sharing. I just used this functionality as a last resort.
Theerthesh.
Very good tool, thank you..
i am not sure if the changes themselves can be seen (most probably not), but the ID from which GD-EDIT and GD-SAPEDIT were changed does show up in the system log (SM21).
hi,
can we edit primary keys using this tool. i know primary keys can not be changed. and we can do by deleting record and create new but still can we do it?
You cannot not change the primary keys.
However, you can create new primary key entries with this tool.
I know this is pretty old, but why not just implement note 1468636 (https://launchpad.support.sap.com/#/notes/1468636/E) which turns allows activation again through RKSE16N_EDIT
I am sure any auditor seeing a debugging event in a prd system will be asking a ton of questions.
Hi Chris,
I wonder why customer would allow you to implement this note and give a chance of data security breach.
Hi All,
How about to change the value of GD-EDIT GD-SAPEDIT.
"you are not authorized to edit field contents" " and I cant debug it.
Looking Forward. Thanks
Hi Tongol,
You can use FM SE16N_INTERFACE.
Enter your <Table Name> and pass “X” to I_EDIT and I_SAPEDIT.
Please note all the changes done by this FM are captured in table SE16N_CD_KEY and SE16N_CD_DATA.
So this should be used in very critical situations only, as the system admin can see the change log.
As a side note, you can always skip creation of log entries in debug mode by skipping the INSERT in Include LSE16NF30 -> FORM SAVE_CHANGES.
( Just look for insert se16n_cd_key & insert se16n_cd_data )
Regards,
Bharat