In SE16N you can change SAP tables directly. I explained how to in a previous post. I also warned for the risks involved in doing this. Luckily direct changes in SAP tables are also logged, so you can trace back to the culprit who messed things up. You can query the following SAP tables to report on hacks:
SE16N_CD_KEY : Change Documents – Header
SE16N_CD_DATA : Change Documents – Data
No related posts.
One Comment
I’ve known about this for a while, but haven’t been very keen to make it known (for all the reasons you mention).
Be aware that the SE16N_CD* tables are not being updated when using SE16N on my ECC6 IDES system (SP levels SAPKB70013 and SAPKA70013 on DB/2 9 on Win2003).