Skip to Content
Actions

How to delete a request from a database table in a debug mode

June 30, 2013 | 412 Views |
 Enterprise Data Warehousing / Business Warehouse
Follow

Warning. The instructions in this blog are not recommend by SAP. The actions taken do appear in various security audit logs, and may be forbidden in your company. Furthermore, if they are done incorrectly, they could cause parts of your BW system to become inoperable, without support from SAP to fix. Use at your own risk.

Introduction

Scenario 1 :

At times, we will be struck while activating requests in a DSO due to some incorrect request deletions in DSO. But these requests might still exists in some database tables like RSICCONT, RSODSACTREQ etc..

Scenario 2 :

Intialization requests would have been deleted from Infopackage–>Scheduler menu. But these requests would have been existing in RSSDLINIT, RSSELDONE, RSREQDONE tables etc..

Unless, we delete these bad requests from the above tables, we will not be able to move forward. The following procedure will help us to delete the requests from the back-end. I strongly advice you to follow this procedure in extreme situations only.

Step 1: Goto the DB table in SE16

Debug1.JPG

Step 2: Enter the Request Num and press execute

Debug2.JPG

Step 3: Sometimes we may not have authority to delete the table entries, delete options will be disabled like below

Debug3.JPG

Step 4: Select the entry and click on Spectacles button and enter /H in the command prompt and press Enter twice

Debug4.JPG

Step 5 :  You will get into debug screen  and observe Code = Show, right hand side screen will have no entries

Debug5.JPG

Step 6 : Double click on Code like below, then you will see an entry in the right hand side.

Debug6.JPG

Step 7 : Please double click on pencil button and type DELE

Debug7.JPG

Step 8 : Click on save on top of debug screen and press F8, then you will get delete entry like below. Press on it to delete the entry.

Debug7.JPG

Conclusion : You can make use this procedure to delete any DB table entries. You must have a debug access to do this. Please be careful while using this procedure. You can take up this procedure in extreme situations only.


To report this post you need to login first.

14 Comments

You must be Logged on to comment or reply to a post.

    1. Suman Chakravarthy K Post author

      HI Mathew,

       

      I am 100% with you. Even I have mentioned the same in my blog. Not to undertake unless it is the only solution to get rid of the issue. This is a wild work around . Thanks for authenticating it now..

       

      Regards,

      Suman

      (0) 
      1. Suman Chakravarthy K Post author

        OK Mathew, I have decided to delete this blog completely. It should be taken utmost care while following this blog. I don’t want to become a person to be blamed if somebody really looses job by following this blog as you said.

         

        Guys, i need a feedback from all of you whether to keep this blog or delete?

        (0) 
        1. Anshu Lilhori

          Hi Suman,

           

          I do not think it is required to delete it.Moderator warning is already there so even if someone follow it then it should not be an issue.

           

          I did the same thing in one of the system and they are one of the privileged customer to SAP.So if a person is technically sound then he/she can use this to fix the corrupt request.

           

          Undoubtedly you need to know the table links behind it as the same entry goes in multiple table which system automatically prompts when you delete the request from any of the table.

           

          SAP system is really smart so if we just follow the instructions then things should work as desired.

           

          This is vote of confidence from my side.

           

          Regards,

          AL

          (0) 
          1. Suman Chakravarthy K Post author

            HI Anshu,

             

            Thanks a lot for your confidence and reply. As you rightly said, the one should be technically sound to handle this scenario. I did some times and never faced any issues or consequences.

             

            Still I am in dilemma to keep it or not.

             

            Regards,

            Suman

            (0) 
          1. Suman Chakravarthy K Post author

            Hi Anand,

             

            I understand your concern. But i had already discussed with Moderator and other folks here and decided to go with the Warning message before following this blog. So no issues now. Please do not worry..

             

            Regards,

            Suman

            (0) 
  2. Harish Allachervu

    Handy info suman…..

     

    But unfortunately in many prod system we don’t have necessary authorizations for debugging so if you’ve any other approach please keep share it’ll be useful for our fellow SAPien’s Hope you do!!!!

     

    Regards,

    Harish

    (0) 
      1. Sam Govaski

        Hello Suman,

        I leveraged similar workflow for table RSTSODSPART, Changed from SHOW to DELE but after saving it returns back to SHOW. Is there other way to either delete/change entries from table RSTSODSPART?Please let us know?

        (0) 

Leave a Reply