Table Edit without SM30 or Maintenance Dialog

We all know you can edit table contents in SM30, but did you know you can also edit table contents in SE16N?

–> execute transaction SE16N

–> enter table name and press enter

–> Type &SAP_EDIT into the transaction code field, you will then receive a confirmation “SAP editing function is activated”

–> NOTE this is a much more powerful method of table editing as one is able to even edit tables which do not have a maintenance dialog for example KNVV (Customer Master – Sales area data.) – Therefore use with extreme caution.

–> NOTE when this table edit mode is used no changes are recorded against the user ID. Therefore in the customer master VD02 it will show the field as not having been changed.

6 Comments

  1. sapguy November 16, 2010 at 11:59 pm · Reply

    Couple of things about this tip:
    1. While it is true that no changes are logged against the customer master, it is not true that SE16N changes are not logged.

    If a change was made with SE16N, it is logged in 2 tables: SE16N_CD_DATA & SE16N_CD_KEY. However, it does not seem to show what changes were made, just that a change was made.

    2. It is automatically deactivated in 6.0 SP17 & SP18.

    3. Requires the following authorization:
    S_DEVELOP with activity 01 and 02 and Object type DEBUG can give you editable access in SE16N.

    4. Believe it also works with UASE16N (Version 6.0?). I don’t have access to 6.0. Can someone confirm?

    5. Key SAP Notes:
    1420281 – CO-OM tools: SE16N: Deactivating &SAP_EDIT
    1446530 – CO-OM tools: SE16N: Technical

    6. I concur with Glen. Proceed with extreme caution. If you make a change that has a dependency, you can cause nasty stuff to happen in SAP – you may become a legend, but not a good one. Only use this if you know what you are doing.

    • Glynn Williams November 17, 2010 at 11:41 am · Reply

      Thanks Paul – great information.

  2. Noqarter January 26, 2011 at 11:59 pm · Reply

    Thanks – great information.

    • Glynn Williams January 30, 2011 at 6:08 pm · Reply

      Pleasure to help, thanks for the feedback.

  3. Noqarter January 26, 2011 at 11:59 pm · Reply

    Thanks – great information.

  4. Robin Ferali May 3, 2012 at 1:41 am · Reply

    Indeed, all modification done within SE16N are traced in table SE16N_CD_DATA & SE16N_CD_KEY.
    It is not the case if you modify the table with Transaction SE16.

    I do agree with Glynn and Sapguy, because of the dependencies we need to be careful when we modify any table.
    More, by modifying customizing table in a system you will loose the consistency between the different system.

    Cheers
    Robin

Leave a Reply