Surely, this is not recommended to be used in production.
I am guessing Sil wants to reproduce the case on sandbox for testing purposes, if not Sil, if you are doing this on production, please DO NOT use &SAP_EDIT function.
Yes, &SAP_EDIT is disabled in newer releases but can be forced by easy 10sec debugging.
1) Go to SE16N and type the table name you want to deal with
2) Instead of typing &SAP_EDIT in the command window, type /H to activate the debug
3) Hit the F8 key to enter the data browser for the table you typed on step 1)
4) While in debug, type the name of the following two global variables on the right panel: GD-EDIT and GD-SAPEDIT
5) Change the values of BOTH variables to an uppercase X
6) Finally, press F8 to exit from debug
as shown in thread: SE16N - &SAP_EDIT not working
Again, by no means &SAP_EDIT is not to be used in productive environment, but only on systems that are used for testing purposes!