SE16N is allowing modifications to some Z tables

[luis_rod]

Hi all,

We have some (not all) Z tables that can be modified using SE16N (as if they were being browsed under the old &SAP_EDIT option). Why is this so?

BTW, SE16N in our shop is used only by developers and QA personnel, but just the same I wonder if this could be disabled.

TIA,

Luis

[raymond_giuseppi]

Check within SE11 for the value of 'Data Browser/Table View Editing' in 'Delivery and Maintenance' tab

• if X, 'Display Maintenance Allowed', then SE16n will allow maintenance)

[luis_rod]

Raymond,

Thanks for your post. Unfortunately, the value is the same for both, Z tables that allow changes thru SE16N and Z tables that don´t allow changes thru SE16N.

Regards,

Luis

[raymond_giuseppi]

You have also to check authorization (S_TABU_DIS and S_TABU_NAM for example can be restricted to display only) - check with SU53

Nethertheless you should change the flag in SE11 to 'Display/maintenance allowed to limited extent' to prevent SE16n to allow maintenance (but allowing SM30 dialogs) - look at the help associated to the flag.

[jmodaal]

Hello,

> Unfortunately, the value is the same for both, Z tables that allow changes thru SE16N
> and Z tables that don´t allow changes thru SE16N.

maybe the difference is in the attributes in transaction SOBJ - possibly some of them transportable, others not.

Kind regards

Jan

[marco_hammel2]

Hi, depending in your system release there are different criterias when table editing via SE16N is possible.

With note 1420281 it's supposed to be deactivated completely. However when note 1468636 was installed and somebody ran report RKSE16N_EDIT there you go. I assume the different behavior for Z-tables belongs to different S_TABU_NAM or S_TABU_DIS edit permissions assigned.

[marco_hammel2]

Hi, depending in your system release there are different criterias when table editing via SE16N is possible.

With note 1420281 it's supposed to be deactivated completely. However when note 1468636 was installed and somebody ran report RKSE16N_EDIT there you go. I assume the different behavior for Z-tables belongs to different S_TABU_NAM or S_TABU_DIS edit permissions assigned.