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.
See my other post on how to track change by people who edited tables with this method.
Step-by-step
1) Go to transaction SE16N or alternatively use shortcut and type just ‘N’. Enter here the table that you wish to edit.
SE16N or just N
2) In the command field enter ‘&SAP_EDIT’ and press enter. The maintenance indicator in SE16N will switch on.
Command field entry
3) Narrow your search results by entering selection criteria and press F8 to run the report.
4) You can remove lines or just add/change data and press save.
&SAP_EDIT - SE16N - Table results
Voila! You just hacked your way into the table structure and made some changes.
Update 05-Oct-2009: interesting comments made on this hack: blog on IT toolbox
If you like this post, you may also like:
VERY interesting and useful, thanks
Cheers, I appreciate you leaving the site with a thank you.
Hi,
I found this very interesting. I can use it on R/3 but I do not see transaction code se16n or n in SCM system. Is there any other way to edit the table entries directly on SCM system ?
Thank you
Manish.
Hi Manish, I’m assuming you are referring to the APO system? Information is managed different. Unfortunately I have no in-depth experience with this system. Regards, Kowboy
Very very useful tip. Thanks a ton for sharing!!
Thank you for the tips … I can edit my FMIOI table
I put this link in of of my posting …
Thanks to the distribution in your Blog the function was deactivated. Have a look at SAP Note 1420281.
Hi Kowboy, we are in a development freeze (due to our current upgrade) but need an emergency change to a table in production. Since this would have required a program change (very frowned upon at present), we used this method instead for now. Great for only changing a few entries, but dangerous for large scale table changes, as you of course know. Thanks for sharing this useful knowledge!
Are the changes transportable ??
donde trabajo instalaron unos SP y ahora no se puede utilizar la SE16N para modificar tablas… como se hace ahora?
Hola Pablo, intenta crear un programa ABAP con las lineas de insert y listo.
Thank you for the tips. This is very usefullllllllllllllllll
Kowboy by name Cowboy by nature..
why would you want to post about something that undermines the very principles of a fully integrated ERP? And those that use this… why?? maybe have a chat with your local friendly Auditor and see what they think?
Thanks mate!!! Very useful.
To Disdainful
… you obviously don’t live in the real world.
Sometimes this is the only way to rectify critical situations in a Production environment. Ur probably a not techie type manager .. This has been around a while ..
See quote from SAP themselves
“The sole purpose of this function was to enable the well-trained SAP Support experts to provide a fast solution for customers in a highly critical situation.
The special function &SAP_EDIT was protected in the system by the highest developer authorization that could be assigned.”
But obviously you don’t fill the criteria mentioned by SAP
this code ‘&SAP_EDIT’ is not working. before i can used this when i edit sap table. but now it doesnt open the maintenance indicator.
this is very interesting.
Thanks
Thanks, With this explenation we can do it by our own!
saving a lot of time and money!
Regards,
Bart
It’s possible that the security to access &SAP_EDIT is tightened so the transaction cannot be used anymore. SAP gave some attention to this loophole after the wider publicity this feature got.
“Using &SAP_EDIT functionality users can update tables even with SE16N (SAP has removed this
function with note 1420281.). ”
“The content was delivered in Release 600 with Support Package 17 and Support Package 18.”
Good that the backdoor’s been closed, as this would be extremely damaging in the hands of a cowboy. But agree, there are occassions where this may be the only way to correct a critical error.
I expect SAP have another way, or it’s possible to roll back the Note in extreme circumstances, but likely to be unsupported!
Thanks for the advice, Will have to check but it is certainly very useful for the urgent situation and for the experienced consultant.
&SAP_EDIT is not working to activate Maintain entries.
Could you please help how to edit table entries…
Thanks,
Vijay.
Instead use the transaction UASE16N until they take it away
Utilizar la transaccion UASE16N mientras no la deshabiliten tambien.
Un saludo
Hi,
with proper authorizations you can still make &sap_edit work
Check http://stankowski.it/sap/adm/editse16n.html for details.
=F=
After support packages Ehp4 we lost SE16N and UASE16N. I found the possibility to go over SE37 and SE16N_INTERFACE, i can see and change tables, but can not search for specific fields. Can you help me?
regards
JR
mit EHP4 (und den Sicherheitspatches im Dezember 2010) ist die SE16N nicht verschwunden, aber man kann nun die Nutzung komplett verbieten oder wirklich einschränken.
Wenn Sie sich mit Ihren SAP-Basis-Leuten und der Revision zusammensetzen und ein Konzept zur Nutzung der SE16N in Ausnahmefällen erarbeiten, dann verliert die Nutzung dieser Funktion auch den Hackerstatus.
Wenn man die SE37 nutzt, um verbotene Funktionen auszuführen, halte ich das für nicht legal. Sie sollten sich auch da vor einer Nutzung sicher sein, dass Ihr Arbeitgeber das akzeptiert.
Gruß Renate
Yeah, my last resort is quite same as stankowski.it : find the line “call function ‘SE16N_INTERFACE’” in the include “LSE16NF10″ and put a break-point, run SE16N and change values of gd-edit & gd-sapedit to ‘X’ in the debug mode and continue.