Skip to Content

This is a real time production scenario where I faced problem for DTP request stuck in Yellow status – it can not be deleted from DSO and preventing next deltas to load correctly.

Issue:

1. Tried to change technical status to red by clicking on DTP process monitor. Error as below:

/wp-content/uploads/2013/08/1_257074.png

2. Clicked on DTP process monitor- ABAP dump as below:

/wp-content/uploads/2013/08/2_257108.png

3. Tried to change DTP status with function module: RSBM_GUI_CHANGE_USTATE. Error as below:

/wp-content/uploads/2013/08/3_257109.png

4. Checked table:

     a. RSBKREQUEST- USTATE=TSTATE= 0= New request

    /wp-content/uploads/2013/08/4_257110.png

     b. RSPCPROCESSLOG has state= G, and actual state= A.

/wp-content/uploads/2013/08/5_257111.png

     c. RSBKDATAPAKID– this DTP request is not found in this table.

Solution:

The reason of the dump is due to an inconsistency entry in table RSBKREQUEST. The request should not be remain 0 in USTATE and TSTATE. Therefore, we requested Basis to change the status of USTATE and TSTATE in table RSBKREQUEST manually to 4, then deleted this request from DSO. And this solved the issue

SAP message- 299691/2013: http://service.sap.com/sap/support/message/E/002007974700002996912013

/wp-content/uploads/2013/08/6_257112.png


To report this post you need to login first.

31 Comments

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

  1. Antony Grace

    This information is really useful, but recently we had a similar issue in our system and provided the same fix that you have suggested, but during the next load also the same thing happened and we got the support from Basis team for fixing it.

    I’m not sure if the problem was because of the previous setting that we have made and hence would like to ask you about the impact of this setting if any.

    (0) 
  2. MICHELLE LIM Post author

    hi Antony,

    Once the status was set to 4 (Deleted), we deleted the red request from the DSO manually, reran DTP and activated the request. Next load worked fine. 🙂 No impact.

    As a preventive method, since this DSO was getting data from multiple DSOs and all DTPs always run in parallel in a process chain (though we have not seen issues for the last 2 years), we made a change to DTP setting: Extraction Mode -> Uncheck Get all New Data Request by Request. Hope this helps!

    https://fbcdn-sphotos-h-a.akamaihd.net/hphotos-ak-frc1/v/1000249_10152149524544762_502550438_n.jpg?oh=c1a24484ca4ca88eaecff8ffe9593bd2&oe=5202DF5B&__gda__=1375940093_d861415d5e1efb0557815b88a5c517e3

    https://fbcdn-sphotos-h-a.akamaihd.net/hphotos-ak-prn2/v/1146676_10152149524549762_48199866_n.jpg?oh=d254059413bd9b2ca5b1649945c3af2d&oe=5202B030&__gda__=1375938404_417031405fef4d56ac78b268fe154e2d

    (0) 
      1. Arshiyan -

        Hello Michelle

        Today, I come across da same issue and I resolved it within minutes with the help of your blog. Thanks for sharing for new SCN users. Keep it up and we all love to read.

        Arshiyan

        (0) 
  3. M. Shadab Shaikh

    Hi Michelle,

    There is an alternate solution.

    1. Try cancelling the dtp job from sm37. If possible great else

    2. Go to sm12 and check for locks. The one executed the dtp loading would have the target locked by its id. Delete those locks and then try cancelling and deletion of request.

    (0) 
    1. MICHELLE LIM Post author

      Thanks for your reply.

      In this scenario, we only discovered the issue 2 weeks later when delta DTP loaded 0 records in daily process chain- SM37’s log was no longer found (log only keeps for a week in system), and there was no lock found for this DTP in SM12. Therefore, it left us no choice but to make an entry change in RSBKREQUEST table.

      (0) 
  4. Harshil Joshi

    Facing similar issue.

    Found MESSAGE_TYPE_X error while data loading.

    I found a request is pending, so I followed the steps and delete the request. But still having that request available in DTP, not available in RSBKREQUEST. I can not delete it by DSO –> Manage. Even after deleting it is available there. What should do ?

    (0) 
    1. MICHELLE LIM Post author

      Please review the steps again…just to be clear we DO NOT delete the entry in RSBKREQUEST table.

      The solution is to CHANGE/UPDATE the status of USTATE and TSTATE in RSBKREQUEST manually to 4. After updating the value in the table, you should be seeing red DTP request in your DSO, then deletes that request from there. If you have deleted the entry in RSBKREQUEST, there is no way you could still find the entry unless the table is recovered

      (0) 
    1. MICHELLE LIM Post author

      Please review the steps again…just to be clear we DO NOT delete the entry in RSBKREQUEST table.

      The solution is to CHANGE/UPDATE the status of USTATE and TSTATE in RSBKREQUEST manually to 4. After updating the value in the table, you should be seeing red DTP request in your DSO, then deletes that request from there. If you have deleted the entry in RSBKREQUEST, there is no way you could still find the entry unless the table is recovered

      (0) 
  5. Phani KV

    Hi,

    not preferable deleting the data table level in PRD system then some times it will go difficult.

    Thanks for sharing and nice information

    Thanks,

    Phani.

    (0) 

Leave a Reply