Delete initial request

Hi,
I did a intial request for 0EC_PCA_3, becasue the data is huge with more that 10000000, I decide to do some separate full uploads and do a new initail updata.
After I deleted this initial request and also delete all the data of cube.
But after I check the requests list in the cube, the original initial request appreared again with data loading.
Is there anyone know how I can stop this data loading?
Many Thanks
Jonathan

Hi Jonathan ,
It is strange that the request is again appearing in the target . To confirm that , please check if any one is trying to push that request from PSA . If so then check for any job BI_BOOK* or BI_BTCH* in SM37 . If any job is progressing check which request it is trying to push .
If it is trying to push your request we can cancel that job and delete the cube contents again
Regards
Venkat

Similar Messages

  • Problem in deleting a request from ODS

    Hi,
    i am trying to delete a request (not activated) from ODS, when i checked in SM37 for the status of the job it shows as Cancelled, but when i see for the request in ODS, the requested is deleted, could anyone please let me know why job in SM37 is cancelling when the request is actually deleting,
    This is not the case with activated request.
    please see the worklog of the cancelled job
                                                                                    Job started                                                                        
    Step 001 started (program RSDELPART1, variant &0000000005236, user ID KUMARV1)     
    Delete running: ODS object ZCFORO01, from 512,483 to 512,483                       
    Delete is scheduled; Selection conditions were substituted                         
    Request REQU_45IYZ9A2BQFRW0IUY5EB4MZ9W successfully deleted from ODS object ZCFORO01
    ABAP/4 processor: MESSAGE_TYPE_X                                                   
    <u><b>Job cancelled </b></u>

    Hi Arun,
    Yes the system raises an exception and saying that there is an error in ABAP code, could you please let me know what is the error, i have tried this deletion with 3-4 different ODS and to different systems i.e. in Q, P system
    Abap code as specified by Exception in ST22 transaction
    The termination occurred in the ABAP program "SAPLRSSM_PROCESS" in         
    "RSSM_PROCESS_REQUDEL_ODSO".                                              
    The main program was "RSDELPART1 ".                                                                               
    The termination occurred in line 114 of the source code of the (Include)   
    program "LRSSM_PROCESSU19"                                                
    of the source code of program "LRSSM_PROCESSU19" (when calling the editor  
    1140).                                                                    
    The program "SAPLRSSM_PROCESS" was started as a background job.                                                                               
    Source code extract                                                                               
    000840       endif.                                                        
    000850       append l_s_rnr_del to l_t_rnr_del.                            
    000860     endif.                                                          
    000870     delete l_t_rnr_del where                                        
    000880            rnr = ''.                                                
    000890     loop at l_t_rnr_del into l_s_rnr_del.                           
    000900       l_idx = sy-tabix.                                             
    000910       if l_s_rnr_del-sid is initial.                                
    000920         call function 'RRSI_VAL_SID_SINGLE_CONVERT'                 
    000930           exporting                                                 
    000940             i_iobjnm = '0REQUID'                                    
    000950             i_chavl  = l_s_rnr_del-rnr                              
    000960           importing                                                 
    000970             e_sid    = l_s_rnr_del-sid.                             
    000980       endif.                                                                               
    000990       if l_s_rnr_del-odssid is initial and             
    001000          not l_s_rnr_del-odsrnr is initial.            
    001010         call function 'RRSI_VAL_SID_SINGLE_CONVERT'    
    001020           exporting                                    
    001030             i_iobjnm = '0REQUID'                       
    001040             i_chavl  = l_s_rnr_del-odsrnr              
    001050           importing                                    
    001060             e_sid    = l_s_rnr_del-odssid.             
    001070       endif.                                           
    001080       modify l_t_rnr_del from l_s_rnr_del index l_idx. 
    001090       if l_min_sid > l_s_rnr_del-odssid.               
    001100         l_min_sid = l_s_rnr_del-odssid.                
    001110       endif.                                           
    001120     endloop.                                           
    001130     if sy-subrc <> 0.                                  
         >       message x000.                                    
    001150     endif.

  • Non-compressed aggregates data lost after Delete Overlapping Requests?

    Hi,
    I am going to setup the following scenario:
    The cube is receiving the delta load from infosource 1and full load from infosource 2. Aggregates are created and initially filled for the cube.
    Now, the flow in the process chain should be:
    Delete indexes
    Load delta
    Load full
    Create indexes
    Delete overlapping requests
    Roll-up
    Compress
    In the Management of the Cube, on the Roll-up tab, the "Compress After Roll-up" is deactivated, so that the compression should take place only when the cube data is compressed (but I don't know whether this influences the way, how the roll-up is done via Adjust process type in process chain - will the deselected checkbox really avoid compression of aggregates after roll-up OR does the checkbox influences the manual start of roll-up only? ).
    Nevertheless, let's assume here, that aggregates will not be compressed until the compression will run on the cube. The Collapse process in the process chain is parametrized so that the newest 10 requests are not going to be compressed.
    Therefore, I expect that after the compression it should look like this:
    RNR | Compressed in cube | Compressed in Aggr | Rollup | Update
    110 |                    |                    | X      | F
    109 |                    |                    | X      | D
    108 |                    |                    | X      | D
    107 |                    |                    | X      | D
    106 |                    |                    | X      | D
    105 |                    |                    | X      | D
    104 |                    |                    | X      | D
    103 |                    |                    | X      | D
    102 |                    |                    | X      | D
    101 |                    |                    | X      | D
    100 | X                  | X                  | X      | D
    099 | X                  | X                  | X      | D
    098 | X                  | X                  | X      | D
    If you ask here, why ten newest requests are not compressed, then it is for sake of being able to delete the Full load by Req-ID (yes, I know, that 10 is too many...).
    My question is:
    What will happen during the next process chain run during Delete Overlapping Requests if new Full with RNR 111 will already be loaded?
    Some BW people say that using Delete Overlapping Requests will cause that the aggregates will be deactivated and rebuilt. I cannot afford this because of the long runtime needed for rebuilding the aggregates from scratch. But I still think that Delete Overlapping should work in the same way as deletion of the similar requests does (based on infopackage setup) when running on non-compressed requests, isn't it? Since the newest 10 requests are not compressed and the only overlapping is Full (last load) with RNR 111, then I assume that it should rather go for regular deleting the RNR 110 data from aggregate by Req-ID and then regular roll-up of RNR 111 instead of rebuilding the aggregates, am I right? Please, CONFIRM or DENY. Thanks! If the Delete Overlapping Requests still would lead to rebuilding of aggregates, then the only option would be to set up the infopackage for deleting the similar requests and remove Delete Overlapping Requests from process chain.
    I hope that my question is clear
    Any answer is highly appreciated.
    Thanks
    Michal

    Hi,
    If i get ur Q correct...
    Compress After Roll-up option is for the aggregtes of the cube not for the cube...
    So when this is selected then aggregates will be compressed if and only if roll-up is done on ur aggregates this doesn't affect ur compression on ur cube i.e movng the data from F to E fact table....
    If it is deselected then also tht doesn't affect ur compression of ur cube but here it won't chk the status of the rollup for the aggregates to compress ur aggregates...
    Will the deselected checkbox really avoid compression of aggregates after roll-up OR does the checkbox influences the manual start of roll-up only?
    This check box won't give u any influence even for the manual start of roll-up....i.e compression of aggreagates won't automatically start after ur roll-up...this has to done along with the compression staus of cube itself...
    And for the second Q I guess aggregates will be deactivated when deleting oveplapping request if tht particular request is rolled up....
    even it happens for the manual deleting also..i.e if u need to delete a request which is rolled up and aggregates are compressed u have to  deactivate the aggregates and refill the same....
    Here in detail unless and until a request is not compressed for cube and aggregates are not compressed it is anormal request only..we can delete without deactivating the aggregates...
    here in urcase i guess there is no need to remove the step from the chain...
    correct me if any issue u found......
    rgds,

  • Delete Overlaping Request

    Hello Experts
    Please read my requirements.
    I have an infocube with Full Load DTP.  It gets the records directly from PSA.  Its all in BI 7.X.  My infopackage is on a datasource that is Delta Capable.  Due to the design flaw, I get the records directly from PSA into InfoCube without DSO and hence the duplicate records.
    What I did was, I initially ran, infopackage with "Initialize Delta with Data Transfer" and ran my DTP.  All the records are in my InfoCube.  So far so good.  Later I created a process chain, in this Order.
    Run Delta InfoPakcage
    Run DTP (Full all the time) - This time it gets the full as well as delta records from PSA. 
    Delete Overlaping Requests
    What I observerd was some of the records are still getting duplicated and some not after couple of days.  Any ideas Why?
    In "Delete Overlaping Request" process I selected the DTP while defining it and not the InfoPackage.  How this process work with Delta InfoPackage.  Please explain?
    Thank you
    BW User 999

    Hi,
    You can avoid using Delete overlapping request,and load the data correctly to the cube via Full DTP.
    Only if you dont need to previous days data in the PSA.
    Every time when the process chain is executed
    1) After the start process delete the PSA.
    2) Load the data through the Infopackage.
    3) Load it to the cube with the Full DTP.
    In this way you wont need to delte the overlapping request. Hope this help...
    Regards,
    Mahesh.

  • 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.

  • Error while deleting a request

    Hi All,
    When trying to delete a request from a master data object an error appears which says:
    Cannot delete request DTPR_* of table RSN* for deletion.
    Please let me know what needs to be done here so that request is deleted.
    This is urgently required..thanks..

    For deleting any master data
    Need to delete first where its referenced to ,so check the where used list for the infoobject and delete the places where that master data is referenced
    Typically - Attributes,Hierarchies,Texts,Transaction data,in Query - Hardcoded master data
    Lots of ways around ,even using database utility ;however that leads to inconsistencies and requires sounds knowledge so wont advocate those steps.
    You can follow below steps -
    R-Click Delete master data ,it wont delete all if its referenced,so now go to
    Tcode - SLG1
    Object = RSDMD
    Subobject = MD_DEL
    Hit execute button
    it will fetch you the log showing all the places(references) where you need to delete the data in order to delete the actual master data.
    After deleting the data from referenced places you can completely delete the master data.
    Hope it Helps
    Chetan
    @CP..

  • Delete Overlapping requests question

    Hi ,
    How would a Delete overlapping requests (DOR)type work in a PC to a Cube that gets a full load every day with selections for rolling 12 months?
    Say there is a scenario to load data into an AR line items cube to update open to closed items history and the loads are configured for a 12 month rolling. eg yesterdays full would be for 03/23/09 to 03/23/10
    today's 03/24/09 to 03/24/10
    Now how can we utilize DOR instead in a PC that would delete the doubling behaviour of data for dates 03/24/09 to 03/23/10?
    All thoughts appreciated.
    Thanks

    Hi,
    in The selection criteria of the info package u can have the following code which takes the selection criteria as the first day to last day of the month  based on previous days date(SY-DATUM - 1.)
    data: l_idx  like sy-tabix,
            dDATE1 LIKE SY-DATUM,
            dDATE  LIKE SY-DATUM,
            L_LOW  LIKE RSSDLRANGE-LOW,
            L_HIGH LIKE RSSDLRANGE-HIGH.
      read table l_t_range with key
           fieldname = 'END_SHIFTDATE'.
      l_idx = sy-tabix.
      dDATE1 = SY-DATUM - 1.
      CALL FUNCTION 'ZFNC_FIRSTDAY_MONTH'
        EXPORTING
          DDATE      = dDATE1
        IMPORTING
          DLAST_DATE = dDATE.
      L_LOW         = dDATE.
      L_T_RANGE-LOW = L_LOW.
      L_T_RANGE-SIGN   = 'I'.
      L_T_RANGE-OPTION = 'BT'.
      CLEAR dDATE.
      CALL FUNCTION 'ZFNC_LASTDAY_MONTH'
        EXPORTING
          DDATE      = dDATE1
        IMPORTING
          DLAST_DATE = dDATE.
      L_HIGH         = dDATE.
      L_T_RANGE-HIGH = L_HIGH.
      modify l_t_range index l_idx.
    and DOR deletes the previous day's request as the selection criteria is same. on first day of the next month it has a request with selection criteria as first to last date of the previous month. and this request is not deleted  since on 2nd of the month it has different selection criteria(Start daay and end day of that month)
    Hope its clear
    Thanks,
    Sandeep

  • HOW TO USE FUNCTION Deletion of Requests from the Change Log IN PRCSES CHAN

    Respected all
    i used Deletion of Requests from PSA from the prcess chain and found good results, now i have only one request at the psa and thus i am doing good space utililisation. but when i am using Deletion of Requests from the Change Log i am not getting any changes in the request of dso. kindly let me know how to use this 2nd function.
    thanks
    abhay

    Hi Mahodaya,
    As per SAp standards its good to delete the requestes that are no longer needed for the delta update and no longer used ffor inti from the change log table and the data is loaded already in to DSO.
    Goto RSPC
    Click on create New PC -> enter the PC name n long descp
    Next we need to define the start process for the PC.Maintain the start variant process.save n come back.
    for deletion of change log we have option in the Other BW Processes -> deletion of requestes from change log
    Once u select the option we get a dialoge box here we need to create the variant for the process enter the process variant n long descp. cick ok.
    Next in the maintenance screen for the deleting the request from change log table will appear.
    Enter the selection patterns to which the requestes should be deleted from the change log.
    In the maintenance screen, select one or more Data Store objects for which requests are to be deleted from the relevant change log tables under Data Store Object column and select theInfo Area of the corresponding Data Store Objects under Info Area
    If you select the first check box exclude selction pattern, this means that del of requests from change log table will be ignored.
    or
    We can delete the requests which are Older than N-number of days (or) date in the above screen. For this one, enter the number of days (or) date in the filed Older than .
    OR
    If we want to select the requests with a certain status then we can also do in the above screen. We can select the following status indicators from the above screen.
    Delete Successfully Updated Requests Only -This status will delete only requests which
    are successfully updated into corresponding Data Store objects.
    Delete Incorrect Requests that were not Updated - This status will delete only incorrect requests which are not successfully updated into the corresponding Data Store Objects.
    Delete Activation Requests only, No Load requests- This status will delete only the activation requests (requests that begin with ODSR_... ). No load requests are deleted.

  • How to delete the request in Direct Update DSO

    Dear Gurus,
    I have a situation where I have an invalid characteristic loaded into the Direct update DSO.  This is related to Spend Performance Management.  This DSO is loaded through a data source with the option Without Archive.  So, I cant see any request in this DSO.   This DSO will then supply data to another DSO which is standard DSO. 
    The data Activation job in the standard DSO is failing. 
    My question is I have to delete the request from the Direct Update DSO and then load it to Standard DSO.  I have already repaired the data in PSA.
    Your Kind help is greatly appreciated.
    -Mohan Kumar

    You must be using some fill or delete APIs to fill the data in Direct update DSO.You can't create transformation to fill the data in DIrect Update DSO as you do in Standard DSO.You will not see  request number under the manage tab for direct update dso for any load.
    Whenever you will fill the Direct update DSO next time,previous data gets deleted automatcally. For Direct update DSO there can only be a Full Update.So just load the data using API's  and previous data will get deleted automatically
    Edited by: shyam agarwal on Mar 2, 2012 7:48 AM

  • 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

  • How to delete the request in se10

    Hi Experts,
    How to delete the request in se10 ....plz explain
    Regards
    Venkat

    Hi,
    Go to SE10,select the request which you wnat to delete.You will find a delete icon on the top.Select it.
    This will delete the request.
    Make sure that this request is the one which is under ur ID.If you want to delete the request which is under other ID,it wont allow to delete.
    Thanks & Regards,
    Suchitra.V

  • How to delete a request in a collapsed and aggregated infocube ???

    Hi all,
    <u><b>The situation :</b></u>
    I have a cube that is collapsed, and that has aggregates.
    I'm not the one that designed this cube but if my understanding is good, aggregates were created to avoid the duplication of the recordings for the same key of characteristics because of the multiple loading. Actually KFs of the same recording are fed by various chains. Each chain creates a segment for the same characteristic values while updating the concerned KF. The aggregates make it possible to gather all these segments within the same recording by aligning the various updated KF.  (that's definitelly not clear to me but...this might be the reason why...)
    In the last chain that feeds the cube, right after loading datas, there is an "adjust" step, and then a "collapse" step.
    <u><b>The problem :</b></u>
    Sometimes for this cube (when we have a problem with figuresfor example) I have to run loading chains a second time for the same day. The result of that is obviously that datas are doubled in the cube, so that I have to delete requests in the cube to have them right.
    The problem is that, when I try to delete a request, the following pop up message appears : "Request ID xxx is aggregated, compressed or scheduled
    Message no. RSM725"
    I think I have to "uncollapse" the cube to do that, but I don't know how to do. By the way I'd want to "recollapse" the cube after that (it seems it's necessary so...).
    Could someone explain steps to solve the problem, and in the same time, explain the necessity and differencies of creating aggregates and collapsing please ????
    That would be so usefull to me, obviously I assign points for helpfull answers !
    Thanks !
    Fabrice

    Aggregates
    check this links for aggregates
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3f66ba90-0201-0010-ac8d-b61d8fd9abe9
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e55aaca6-0301-0010-928e-af44060bda32
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cbd2d390-0201-0010-8eab-a8a9269a23c2
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/2299d290-0201-0010-1a8e-880c6d3d0ade
    How to doc
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e55aaca6-0301-0010-928e-af44060bda32
    relation between agg and comp
    Relation between Rollup and compression.
    Aggregate Rollup and Compression

  • How to delete the Request Number

    Hi all,
                 How to delete the Requset Number in Development Client.Already i transported this Req. Number to Tesing Client.

    For what purpose, deleting the request number won't restore your dev system. You can remove the request from the import queues via transaction STMS to insure it will not be accidentally imported.
    You can usually only destroy a request in source system if it has not been released and all objects are unlocked, but this is risky in some cases and may cause a loss of information or coherence.
    Regards

  • Need help in deleting the requests from DSO

    Hi All,
    I want to delete the data load requests present in the dso, I cant do that from the manage tab as it is throwing error because of some dump been loaded into it.
    Please tell me the tables names which stores these data load requests of the dso's so that I can delete those requests  in the backend.
    If is there any way to delete these requests or complete data, please let me know. I cant do these operations from the mange tab/delet data tab of dso as it is throwing the error.
    Thanks,
    vinay.

    Hi,
    You can delete the Requests form DSO by useing RSICCONT.
    Follow bellow steps:
    1. Goto SE16.
    2. Give the RSICCONT and Click on Technical Contents.
    3. Give the DSO name--> Click on Execuit
    it will dispaly the number of requests which it exists.
    4. Select your request>Select 'Table Entry' Menu> Select 'Delete'
    Regards,
    Suman.

  • 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

Maybe you are looking for