Robin, i've just meet such steps to create, edit, display modes. Haven't check myself, but nevetheless:
Hello THere!
Just to take advantage of the topic:
I think that by now, almost every developer knows about the somewhat "hidden command" &SAP_EDIT entered on the SAPGUI command line at the first screen of SE16N, AFTER YOU SPECIFY THE TABLE NAME TO BE DISPLAYED, to unlock table maintenance buttons (insert/modify/delete) on the result ALV, even if those buttons were not supposed to be there (for system tables, or depending on the table delivery class, for example).
But there's a SAP NOTE that disables this &SAP_EDIT command, leaving all of us in the cold regarding changing any table values uaing SE16N.
Here is a &SAP_EDIT substitute trick:
1) In the same first screen of SE16N, you enter /H followed by ENTER to call the debug,;
2) When in debug, display the name of variables GD-EDIT e GD-SAPEDIT.and change the value of both variables form space to X;
3) Hit F8 key to exit debug and return to SE16N;
4) Now, when you choose to display lines from a table in SE16N, you'll see the insert/modify/delete buttons for the table, even if &SAP_EDIT is not working anymore.
If you leave transaction SE16N and enters it again, you'll have to repeat the steps above.
I Hope this helps the &SAP_EDIT orphans.
Variant 2:
1) SE38 -> LSE16NF10 -> View -> find line CALL FUNCTION 'SE16N_INTERFACE' (between 900 lines and 1000)
2) Start SE16N transaction -> Etner your table -> Execute transaction ->
3) When in debug, display the name of variables GD-EDIT e GD-SAPEDIT.and change the value of both variables form space to X
4) Hit F8 key to exit debug and return to SE16N
