How to Edit SAP Table in Debug Mode Using SE16


Sometimes we are required to edit the value of the SAP table directly. In such a situation we can adopt different methods depending on the nature of the SAP Table. One of the approaches is the debugging mode. 

Step1:- Use T.code [SE16]

Edit SAP Table in Debug Mode Using SE16

And provide the table name, e.g.  MARV, and Click on the OK button or press enter. 

Step2:- Provide any information against which you want to edit the table, like company code for our case.

Edit SAP Table in Debug Mode Using SE16

Click on Execute button. 

Step3:- Select that row and click on the Display button. 

Edit SAP Table in Debug Mode Using SE16

Step4:- Activate debug mode for the table SAP table. 

Edit SAP Table in Debug Mode Using SE16

In the command bar type /h and click the OK button.

Edit SAP Table in Debug Mode Using SE16

Now Debugging has been switched on and click the ok button. 

Step4:- Double click CODE variable in debugging screen. 

Edit SAP Table in Debug Mode Using SE16

 Now the pointer has stopped at the IF statement, On the red marked statement,  Double click the “CODE” variable. 

Edit SAP Table in Debug Mode Using SE16

After double click the CODE variable, it appears in the variable. 

Now click the Pencil button to change its value. 

Edit SAP Table in Debug Mode Using SE16

Value of CODE now editable. 

Step5: Replace the value from SHOW to EDIT of “CODE” variable. 

Edit SAP Table in Debug Mode Using SE16

Now replace the value of CODE with “EDIT” then press the “F8” button or click on the Continue button.

HJb8DAZhzD2LsxdC CvzIc1DctsunIq

Now we can see this table is now editable and in which we can change it and save it. 

Edit SAP Table in Debug Mode Using SE16

For this company code, we have modified the year and month and save it. 

Edit SAP Table in Debug Mode Using SE16

After saving for this company code Year and the month has been changed. 

Note:- it is not advisable to adopt this approach directly without proper permission or approval of a Business or concern authority Team member. If you are doing it in the Production system, It should be done through FireFighter ID if it is applicable in your project. 

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *