Master Data -- unable to delete the request

I loaded master data for 0EMPLOYEE info object, all the records Added but the request is in Read,
I am trying to QM status Green Manually it is giving the message “QM action not allowed for DTP requests in master data and Text Tables “.
I am unable to delete the request also, when I am trying to delete it is saying
<b>Error:</b>
Data inconsistency; Partition /BIC/B0000959000 not deleted
Message no. RSAR026
<b>Diagnosis</b>
In table RSTSODSPART you selected all the requests of a partition to be deleted logically. Some entries partno = 0 still exist in the partition. Therefore the partition is not deleted.
<b>System Response</b>
The system outputs an error when deleting the partition.
<b>Procedure&</b>
Check the table for data consistency.
<b>Error:</b>
Termination in problem report 'RSS2_DTP_RNR_SUBSEQ_PROC_SET' in row '      177'
Message no. RSSTATMAN102

Hi,
I have answered to another thread like this one which is still unsolved (I suggested to open the issue in the OSS)
You can try the following OSS note for a start
SAP Note 1048161 P14:Set QM status for yellow requests using funcion module
I've also found a very recent one:
SAP Note 1078527 P16:Request deletion with error RSSTATMAN 102 in row 34
hope this helps...
Olivier.
Message was edited by:
        Olivier Cora

Similar Messages

  • Unable to Delete the request in ODS

    HI Friends,
          I am facing the problem with deleting request in ODS.
              I deleted the request in cube (PPV Analysis cube). But I unable to delete the request in ODS.
        it is showing the message request is already activated;no further QM action possible.
           My system is upgraded by BI 7.0 one week before only. Please give me solution .
    I am waiting for your reply.
    Thanks & Regards,
    Guna.

    Hi,
    Are there other activated requests on top of this requests?
    In that case it wont let you delete this request unless those requests are also deleted.
    Try to change the status to red and delete.
    Else try this.
    Delete requests manually from the ODS tables.
    1. tcode se16.
    2. delete the request in these tables : RSICCONT (delete activated requests OR
    Make the selective deletion of the contents of that request), RSMONICDP, RSODSACTREQ (give the name of the ODS and the
    request ID and delete all the entries pertaining to this selection in that table.), RSODSACTUPDTYPE.
    The request will be removed from your ODS.
    Note 947481 - P32:ODS: Deleting partially active non-condensed requests 
    Hope this helps.
    Thanks,
    JituK

  • Unable to delete the Requests in the data target---Process chain

    Hello Gurus!
                          Can anyone plz help me out knowing this issue...
      <b>Let me explain the whole scenario:</b>
    Like when monitoring the process chains,one of the process chainhas a  sequence of variants like:
    load info-package1>ODS1 activation>load infopackage2-->load infopackage3..
    due to some problems they scheduing it manually.all the infopackages loads data into one ODS1......suddenly info-package3 failed.
    so....when i looked into the datatarget ODS1->manage->requests.
    <b>i found that the info-pack1 requests status was RED.
    info-pack2 requests status was YELLOW.
    info-pack3 requests status was RED</b>.
    ALL THE THREE R FULL UPDATES ONLY.
    so suddenly one of our cologue  deleted the all the three requests by making ino-pack2 requests to red.
    when we r loading again the ino-pack1  again its failed.we deleted it onceagain(removing the requests from the ods),when we are trying to load ino-pack2 for some priority ,automatically the info-pack1 requests with red were seemed in the ODS.so how to solve this issue and also how to load these three ino-packs..
    i hope that all understand the scenario..plz suggest me how to work on it
    Thanks in advance!!!
    Dilip

    Hi,
    Your loads are running on back ground you have to kill this porcess in SM50 or SM51 check which are all jobs are running with your user name and ALEREMOTE if jobs are running with ALEREMOTE you can check wether it is your load or some body else in SM37 so kill your jobs in SM50 or in SM51 and make request into RED of your 3 loads, delete the requests from ODS and repeat the loads it will go with out any issues, as i under stood your question when your colegue deleted the request without killing the process he simply made it to red and delete its wrong he has to kill the process and then make it to red.
    Regards
    Sankar

  • Unable to delete the request from ODS

    Hi All,
    I have loaded a request to ODS from flat file and the load got success, the request is activated and is available for reporting. Now the problem is i want to delete the request, but the  request is not deleting.
    I tried to delete the request by going in to the cube manage and changed the QM status and the technical status to red and delete, but it is not deleted.
    Thanks in advance for your reply

    Hi Prem,
    If the ods has datamart status & has been used to load data to a cube, then u cant delete the ods request. In this case, first, change the QM status of the request in the cube to red (delete) & then it wud be possible to go with the deletion of ods request.
    Also check this thread as well
    Request unable to delete from ODS.
    Regards,
    R.Ravi

  • Unable to delete the request id in ODS....indicating partially activated

    Dear All,
    When I tried deleting a request from ODS, am unable to turn the QM status to red, itz indicating that the request is partially activated.  When I tried deleting the request without changing the status, the delete icon is popped up, but eventually goes back to the previous status and hence does not get deleted.
    Due to the above, the subsequent requests coming into the ODS are not getting activated at all...
    I tried running the function module  RSBM_GUI_CHANGE_USTATE, to delete the request, but to no success.  Similarly, when I tried locating the requests in the four tables RSICCONT, RSMONICDP, RSODSACTUPDTYPE and RSODSACTREQ, could not found the request id to be deleted in any of these 4 tables.
    Please suggest some solution as it is of high importance...
    Thanks and Regards,
    Edited by: sachitp on Feb 27, 2011 12:25 PM

    Hi,
    You can try the below options,
    1. Remove the request data from the active table using the function
    to delete data selectively.
    You must enter selection criterion to select the data of the
    aborted request.
    2. Use Transaction SE37 to execute the 'RSAR_ODS_API_DEL' function
    module as follows:
    I_REQUEST <Name of the activation request>
    I_DATE <current date>
    3. Use Transaction SE16 to delete all entries for this request and
    for this ODS object from the RSICCONT, RSMONICDP, RSODSACTUPDTYPE
    and RSODSACTREQ tables.
    Thanks,
    Vinod

  • Unable to delete the request through process chain

    Hi,
    We included program in a info package to delete the request based on snapshot date. its working fine when we ran info package manually but its not working when the infopackage is included in the process chain.
    Kindly update us how to work on this.
    Thanks & regards
    Bharathi

    Hi Bharathi,
    There are two options in delete request process of chain:
    one is to use deletion seletion from Infocube .....infopackage settings
    and second one is to set new in chain....
    you should try first option...
    Thanks
    Arun Purohit

  • Unable to delete the request Id

    When I tried to delete one Request Id, I got the following messages:
    Previous request (ID 1924) has status 'red'     
    Termination in problem report 'RSS2_DTP_RNR_SUBSEQ_PROC_SET' in row '     175'     
    I just installed SP10, why can I delete this request? And where can I find "Previous rquest (ID 1924)? It's not there.

    Can you please check the code in SE37 for this function module ..with the OSS note corrections...
    I have pasted the corrections of OSS note
    FUNCTION RSS2_DTP_RNR_SUBSEQ_PROC_SET
    Delta 001Context Block 
    function rss2_dtp_rnr_subseq_proc_set.
    ""Lokale Schnittstelle:
    *"  IMPORTING
    *"     REFERENCE(I_SID) TYPE  RSSID
    *"     REFERENCE(I_TSTATE) TYPE  RSBKTSTATE
    *"     REFERENCE(I_S_MSG) TYPE  RSPC_S_MSG OPTIONAL
    Delete Block 
      data: l_r_dtp_rnr type ref to cl_rsbk_request.
      data: l_tstate    type rsbktstate.
      data: l_ustate    type rsbktstate.
      data l_r_error    type ref to cx_rs_static_check.
    Insert Block 
    *"  EXPORTING
    *"     REFERENCE(E_T_MSG) TYPE  RS_T_MSG
    *"  EXCEPTIONS
    *"      ERROR
      data: l_r_dtp_rnr type ref to cl_rsbk_request.
      data: l_tstate    type rsbktstate.
      data: l_ustate    type rsbktstate.
      data: l_r_error   type ref to cx_rs_static_check.
      data: l_s_msg     type rs_s_msg.
      data: l_line      type i.
      refresh e_t_msg.
      do 1 times.
    Delta 002Context Block 
          call method cl_rsbk_request=>create_from_db
            exporting
              i_requid    = i_sid
            receiving
              r_r_request = l_r_dtp_rnr.
        catch cx_rs_not_found into l_r_error.
    Delete Block 
          message l_r_error type 'S'.
          message x000.
    Insert Block 
           message l_r_error type 'S'.
           message x000.
            l_line = 34.
            exit.
    Delta 003Context Block 
                  call method l_r_dtp_rnr->if_rsbk_request~set_ustate_red
                    exporting
                      i_no_commit = rs_c_true.
                catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
    Delete Block 
                  message l_r_error type 'X'.
    Insert Block 
                   message l_r_error type 'X'.
                    l_line = 69.
                    exit.
    Delta 004Context Block 
                  call method l_r_dtp_rnr->if_rsbk_request~set_tstate
                    exporting
                      i_tstate    = rsbc_c_tstate-further
                      i_no_commit = rs_c_true
                      i_s_msg     = i_s_msg.
                catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
    Delete Block 
                  message l_r_error type 'X'.
    Insert Block 
                      message l_r_error type 'X'.
                    l_line = 85.
                    exit.
    Delta 005Context Block 
                call method l_r_dtp_rnr->if_rsbk_request~set_tstate
                  exporting
                    i_tstate    = rsbc_c_tstate-deleting
                    i_no_commit = rs_c_true.
              catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
    Delete Block 
                message l_r_error type 'X'.
    Insert Block 
                    message l_r_error type 'X'.
                  l_line = 99.
                  exit.
    Delta 006Context Block 
                  call method l_r_dtp_rnr->if_rsbk_request~set_tstate
                    exporting
                      i_tstate    = rsbc_c_tstate-further
                      i_no_commit = rs_c_true
                      i_s_msg     = i_s_msg.
                catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
    Delete Block 
                  message l_r_error type 'X'.
    Insert Block 
                      message l_r_error type 'X'.
                    l_line = 130.
                    exit.
    Delta 007Context Block 
                  call method l_r_dtp_rnr->if_rsbk_request~set_ustate_red
                    exporting
                      i_no_commit = rs_c_true.
                catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
    Delete Block 
                  message l_r_error type 'X'.
    Insert Block 
                      message l_r_error type 'X'.
                    l_line = 146.
                    exit.
    Delta 008Context Block 
                  call method l_r_dtp_rnr->if_rsbk_request~set_tstate
                    exporting
                      i_tstate    = rsbc_c_tstate-deleting
                      i_no_commit = rs_c_true.
                catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
    Delete Block 
                  message l_r_error type 'X'.
    Insert Block 
                      message l_r_error type 'X'.
                    l_line = 161.
                    exit.
    Delta 009Context Block 
                call method l_r_dtp_rnr->if_rsbk_request~set_tstate
                  exporting
                    i_tstate    = rsbc_c_tstate-deleted
                    i_no_commit = rs_c_true.
              catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
    Delete Block 
                message l_r_error type 'X'.
    Insert Block 
                    message l_r_error type 'X'.
                  l_line = 175.
                  exit.
    Delta 010Context Block 
                call method l_r_dtp_rnr->if_rsbk_request~set_tstate
                  exporting
                    i_tstate    = rsbc_c_tstate-further_start
                    i_no_commit = rs_c_true.
              catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
    Delete Block 
                message l_r_error type 'X'.
    Insert Block 
                    message l_r_error type 'X'.
                  l_line = 197.
                  exit.
    Delta 011Context Block 
                  call method l_r_dtp_rnr->if_rsbk_request~set_tstate
                    exporting
                      i_tstate    = rsbc_c_tstate-further_start
                      i_no_commit = rs_c_true.
                catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
    Delete Block 
                 data l_x.
                 while l_x is initial.
                 endwhile.
                  message l_r_error type 'X'.
    Insert Block 
                      data l_x.
                      while l_x is initial.
                      endwhile.
                      message l_r_error type 'X'.
                    l_line = 223.
                    exit.
    Delta 012Context Block 
                call method l_r_dtp_rnr->if_rsbk_request~set_tstate
                  exporting
                    i_tstate    = rsbc_c_tstate-further
                    i_no_commit = rs_c_true
                    i_s_msg     = i_s_msg.
              catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
    Delete Block 
               data l_x1.
               while l_x1 is initial.
               endwhile.
                message l_r_error type 'X'.
    Insert Block 
                    data l_x1.
                    while l_x1 is initial.
                    endwhile.
                    message l_r_error type 'X'.
                  l_line = 241.
                  exit.
    Delta 013Context Block 
                  call method l_r_dtp_rnr->if_rsbk_request~set_tstate
                    exporting
                      i_tstate    = rsbc_c_tstate-further_start
                      i_no_commit = rs_c_true.
                catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
    Delete Block 
                  message l_r_error type 'X'.
    Insert Block 
                      message l_r_error type 'X'.
                    l_line = 264.
                    exit.
    Delta 014Context Block 
                call method l_r_dtp_rnr->if_rsbk_request~set_tstate
                  exporting
                    i_tstate    = rsbc_c_tstate-further_error
                    i_no_commit = rs_c_true
                    i_s_msg     = i_s_msg.
              catch cx_rs_foreign_lock cx_rs_failed into l_r_error.
    Delete Block 
                message l_r_error type 'X'.
    Insert Block 
                    message l_r_error type 'X'.
                  l_line = 279.
                  exit.
    Delta 015Context Block 
          endif.
        when others.
          message x000.
      endcase.
    Delete Block 
    Insert Block 
        exit.
      enddo.
      if l_r_error is bound.
        call function 'RS_EXCEPTION_TO_MESSAGE'
          exporting
            i_r_exception = l_r_error
          changing
            c_t_msg       = e_t_msg.
        l_s_msg-msgid = 'RSSTATMAN'.
        l_s_msg-msgno = 102.
        l_s_msg-msgty = 'E'.
        l_s_msg-msgv1 = 'RSS2_DTP_RNR_SUBSEQ_PROC_SET'.
        data: l_char(10) type c.
        l_char = l_line.
        l_s_msg-msgv2 = l_char.
        append l_s_msg to e_t_msg.
        data: l_on type sy-batch.
        call function 'RSSM_RFC_IS_GUI_ON'
          importing
            on = l_on.
        if l_on = 'Y'.
          call function 'RSDC_SHOW_MESSAGES_POPUP'
            exporting
              i_t_msg                 = e_t_msg
              i_txt                   = text-012
            I_WITH_S_ON_EMPTY       = RS_C_TRUE
            I_ONE_MSG_DIRECT        = RS_C_TRUE
            I_ONE_MSG_TYPE_S        = RS_C_TRUE
          IMPORTING
            E_S_EXIT_COMMAND        =
        endif.
        raise error.
        exit.
      endif.

  • How to delete the requests in DTP?

    hi all,
    here i am unable to delete the requests in DTP...
    when i am going to delete the request in DTP it simply showing the error:
    *cannot lock request DTPR_488BDVJVHQPUUTT3R383DJ55Q OF TABLE 0MATERIAL for deletion*
    could you plz help me on this.....

    Hi Kiran,
    Please go through this thread. Here the same problem has been discussed it detail.
    /message/4419400#4419400 [original link is broken]
    Following are the steps mentioned in this thread
    1. RSA1 -->Info provider >0Material>Right Click-->Display
    2. One screen will come , Select the monitor icon to view that (not the one when you go with Manage of 0Material_attr).
    3. In the monitor screen you will see Refresh icon , Refresh that
    screen , Now the status will change , after 2 -3 refreshes you
    will see the request turning to red.
    4. Now go back to the manage tab of the 0Material attribute , You
    can delete now.
    Regards,
    Praveen

  • Unable to delete PSA request

    Hello,
    I am unable to delete the request in PSA the status of the request is Yellow(Undecided)
    But I would like to delete this one.
    Thanks,

    Hello Ram,
    Is it giving any error. If so what is that?
    Right Click the PSA and select Delete
    or you can use the function module RSATREE_PSA_DELETE_BATCH to clear all the PSA.
    Thanks
    Chandran

  • Can we delete the requests from Infoobject master data

    Hello all,
    we load master data process chains everyday. now when when we right click on the attribute "Manage" then there are lots of requests there.
    Can we delete the older requests from there?
    Does having lot of requests there slow down the performance?
    Thanks in advance

    Ravi,
    Yes we have transactional data also loaded. So you mean I cannot delete the requests from Infoobject ?
    So can we use the given FM and delete master data lets says once a week ?
    I am really confused about this. I tried deleting some of the request from ATTR (Right click on attr and then manage -> select request and delete) and it did actually get deleted so was that wrong thing to do ?
    Thanks for reply

  • Unable to delete the Master Data

    Hello Gurus--
    How to delete the unused MD for an Infoobject,.
    Unused MData were in A version in M,P and text tables.
    Thru the program "RSDMD_DEL_PARALLELIZER" and "RSDMD_DEL_BACKGROUND"  The MD hadn't got deleted.
    Scheduled the above programs and checked the logs in SLG1 for both used and unused MD,.
    The logs says that
    a) Checked,.and I confirm that the unused MD is not present in any targets.
    b) MD deletion hadn't happened for my unused MD.
    --> The MD is in A version in the M,P, Text tables, if it is in M version  these data can be deleted,,
    Checked for the same in all the forums .
    Couldn't able to find the same.
    Very very Ungent sirs' !!!
    Regards
    Vishwa.

    Infoobject --> right clikc --> maintain master data
    Select rows u wanted to delete and click 'Delete' icon. And SAVE.
    If system prompt u 'some master data cannot be deleted' .. continue with this message.
    then goto tcode SLG1-- enter Object: RSDMD and Subobject: MD_DEL and User: ur userID and F8
    In the next screen Expand node and dbl click 'Problem class additional information'
    This will give u which ever objects using SIDs of this master data.
    U should delete this SID according to that list.
    Then U should delete particular data from DSO/Cubes.
    Once data deleted from cube, then
    Use Tcode RSRV -> Tests in Transaction RSRV -> All Elementary Tests -> Transaction Data -> Entries Not Used in the dimension of an InfoCube (Dbl Click)
    From the right side window, expand u201CEntries Not Used in the Dimension of an InfoCubeu201D Node &
    Enter InfoCube (like 0SD_C01), click u201CTransferu201D
    Now, click u201CExecuteu201D (Toolbar)u2026 and the results displayed in the right side window..
    Now, click u201CCorrect erroru201D (Toolbar)
    Delecion of the master data

  • Unable to delete bad request in ODS DATA TARGET

    Hi Experts,
    I have got an abend in load and need to rerun from POF manually .So i need to delete bad request in ODS .But I am unable to delete bad request in ODS.
    Please tell me how to delete request in red.

    Hi,
    Try to do the following:-
    1. Note that bad  request number
    2. Go to SE16
    3. Open table RSODSACTREQ.: Filter the contents by that request number . There will be one entry for that request . Delete that entry
    4. Open table RSICCONT. There will be one entry for that request . Delete that entry
    5. Open Table RSMONICDP. Filter the contents by that request number . There will be 3-4 entries for that request  depending on number of data packages in  that request .Delete all those entries
    Once these entries are deleted , the bad request will be automatically deleted from the ODS.
    Regards,
    Satya

  • Unable to delete the last request in full load infopackage

    Hi All,
    I have full load infopackage with many requests with green status  and thier request genetaed is 0.
    Because of last failure request ia m aunable to activate dso.
    i Made last failure request green and triggered. but not successful.
    i made it red and tried deleting, no sucess. when i delete its giving Dump
    Now i am unable to delete the first request in green status also.its not deleting.
    can i delete whole data in dso and do full load again? how to check if there any other infopackages  on this dso..
    ALL This issues camw across triggering process chian...plz let me know oyur answers....
    Thanks,
    Venkat

    Hi Venkatesh,
    I tried deleting through  RSODSACTREQ.. but the delete option was disabled in the  TABLE ENTRY TAB.
    The last request is failed one with red and not tranfered with full records..
    All the other records which are in green status  does not have symbol genated for reporting purpose and
    Request id generated up on activation is zero..
    I  tried deleting the first request.. when i change its satus to red...
    QM action on PSA Z[DSONAME] must have now:Checked to see if automatic activation of the M version should be started.
    The M version is then activated if necessary  Now?
    Req. 0001439786 in DataStore Z[DSONAME]must have QM
    status green before it is activated
    Request 0001427251 is not completely activated.
    Please activate it again.
    But i am unable to find  both the requests under psa and  in adminstartion data target tab... there are some other requests with red status iin psa...
    When i try to delete failed request its giving dump
    Thanks,
    Venkat.

  • Unable  to delete the bad request,and also not activated.

    Hi,
        I am having ods1 existing in process chain,it is exporting 4ods.At the 3 ods the request was failed at datatarget level,but in RSMO  status shows as green only.
    For all the ODSes the data has runned for two days,on first day the request was failed,if i am going to activate or delete its not accepting.plz help me in this issue.update type for that ODS is deltaupdate..
    Thanks & Regards,
    Aswini.

    Hi Ashwini,
    In your case, the data was loaded successfully, but the activation got failed.
    to confirm that, check the number of records loaded as below.
    No. of records loaded.
    No. of records available in "New Data Table"
    If the data load is successful and there are '0' records in new data table, you can turn the QM status to green and then activate the data.
    If still there are records in New Data Table, The failure might be because of the table space problem. Check the short dumps in ST22. You may find a runtime error called "DBIF_RSQL_SQL_ERROR". You'll see a message "Unable to extend table". You can notify this runtime error to Basis team and they can help you out.
    If it's not the table space problem, you can delete the request by turning the QM status to red in RSMO/Data target (though it is already red, turn it to red again) .
    let me know the source system where you are getting the data from. I can suggest you whether to delete the data.
    Regards,
    Shashi

  • Unable to delete the DTP request.

    Hi friends, iam unable to delete the DTP request, its showing in yellow mode, iam unable to change it to green or red, i checked in SM50 and SM51 ...is there any other way to delte the request ....any FM .
    My version is 7.0 and SP16 BI_Content 9.
    Thanks in advance,

    Hi,
    Try this.
    RSBKDATAPAKID DTP: Status Table for Data Packages.
    Check this table if you can change the status to red.
    If yes - than delete all the requests from manage screen.
    Also check table RSBKREQUEST DTP to delete Request if possible.
    Hope this helps.
    Thanks,
    JituK

Maybe you are looking for