This example comes from a sandbox system where it was used to remove MLGN entries that enabled the Material Type (MARA-MTART) to be changed. Because this Material Master had been extended to warehouse locations, the MMAM transaction refused to change the Material Type.
Start by launching SE16 and ensuring that the defaults are set accordingly. The "SE16 Standard List" will be used in this case.
Next, select the records to be deleted. This will show the records that will be removed and slightly reduce the risk inherent in touching the tables of SAP directly.
Now, double-click on the first entry to bring it up in the viewer. To this point, nothing has been changed, but the debugger will be launched in the next step.
Type in "/h" in the command window as shown above and hit enter to get this message. This will toggle debugger mode so that the next step will trigger the debugger to launch allowing the user to step through the code and potentially change the values in variables in memory.
Now, in the debugger, find the code variable. This is where the workaround becomes risky.
Double-click on the code variable to bring it up in the "Variables 1" list. Once there, click the pencil next to it in order to edit the value therein.
If the SAP security team has been lax with privileges then this will make the value of this variable editable. Currently it is set to "SHOW".
Change the code variable so that the value is "DELE". Press the Enter key to commit the change.
Click on the Continue button.
This brings the program back to the table where the first entry is being viewed and the "Delete Entry" button is available. Delete and advance until all of the undesirable records have been deleted.
Launch SE16 again and validate that the deleted records are no longer in the table.
Warning!!!
Even if the admins have granted debugger access and allowed for variables to be changed during debugging, this workaround is not recommended. Please do not use it.
Before proceeding, please understand that this workaround is incredibly dangerous and should never be used on a production system. This information is presented with no warranty and its presence here is not meant to condone or encourage its use in any way or in any situation.
