Difference between sm30 and se16n(&sap_edit)

[Former Member]

Hello Gurus,

I am trying to change a set of values in a table in the dev environment.

We have a special requirement to modify some of the values in our development environment.

Whats the difference between using sm30 and se16n with &sap_edit to do this?

What are the advantages and disadvantages of one over the other?

I would appreciate if some of the gurus can throw more light into this.

Regards,

Vikas.

[markus_doehr2 · Accepted solution]

> Whats the difference between using sm30 and se16n with &sap_edit to do this?

> What are the advantages and disadvantages of one over the other?

SE16 is direct table editing, that should NEVER be used.

SM30 uses views and puts the entries in a transport request.

Markus

[MPGraziano · Accepted solution]

Markus...

I believe you have those two backwards...,

SM30 DOES NOT restrict any table updates.... You can change ANYTHING

se16n, does have restrictions....

maria

[MPGraziano · Accepted solution]

also.... you should test the two out...

[markus_doehr2 · Accepted solution]

> SM30 DOES NOT restrict any table updates.... You can change ANYTHING

Did I say something different?

> se16n, does have restrictions....

SE16N is a "special" transaction that also allows to edit table entries in a different client.

Markus

[MPGraziano · Accepted solution]

Markus...

Maybe we're both confused

SM30 is the more powerfull transaction and should be limited

SE16N is the trxn that should be used

maria

[MPGraziano · Accepted solution]

And... so what are you recommending?

[markus_doehr2 · Accepted solution]

> SM30 is the more powerfull transaction and should be limited

Most customizing in SPRO are jumps to SM30 views, they can, of course, be restricted and they are client dependent. If the application supports it changes will be tracked. Depending on the table class all the new/deleted/modified entries are also put into a transport request.

> SE16N is the trxn that should be used

SE16N was developed as a display transactions, the &EDIT is a hack for developers. Everything else from above is not true for SE16.

Markus

[Former Member · Accepted solution]

Thanks for the replies.

We were told that if we use se16 and &sap_edit to edit data in a field then it would edit the value of that value only in that table whereas change through sm30 would make the change across all the tables of which the field is part of.

Is this correct ?

If yes then sm30 is a better way of editing that se16n &sap_edit.

Thanks,

Vikas

[markus_doehr2 · Accepted solution]

> We were told that if we use se16 and &sap_edit to edit data in a field then it would edit the value of that value only in that table whereas change through sm30 would make the change across all the tables of which the field is part of.

SE16 is a DISPLAY transaction, the "hack" &sap_edit" was created by developers for developers. It's not to be considered as a proper way to enter/change data to the system since it bypasses all security check and consistency necessities.

I would use SM30 which is used all over in the customizing (SPRO).

Markus