How to delete perviously loaded request from cube

Hi All,
I am loading a standard cube from r3 w/o PSA through DTP.
1 ) how to delete data automatically from cube w/o using Process chains.( previously we have a facility in Infopackage to delete old loaded data ) .In BI7 how to delete the same automatically.
2) How to schedule the DTP to run on daily basis( w/o process chain ) .I am not able to schedule it via RSRDA ?
What might be the reason ?
Regards
  KK

Chivukula,
I'm curious as to why you aren't using the process chains.  There's now a "delete overlapping request" process type within rspc.
You are right thought, the DTP does not offer a facility to delete out the old loaded data.  This feature is not in BI 7.0
As for scheduling a DTP to run daily, there's no way I know of to run it daily without rspc.  Yes I understand that rspc could get very messy but just create a separate holding area, say DAILY DTPS and put your DTP's in there.
Cheers,
Pom

Similar Messages

  • How to delete a single request from DSO in BI 7.0

    Dear Experts,
    Could you please tell me how to delete a single request from DSO?
    I mean, in DSO if we delete one request it also delete the requests which are above it. But i don't to delete the above it.
    Please suggest me this issue.
    Regards,
    Prathap

    IN DSO--its a very basic thing....
    ACTIVE TABLE and CHANGELOG tables are overwritten after activation of each request.
    So ,each new request has a realationsip with the older request.
    So in the cases:
    1.If you activate the older request it will delete the new one ,because changelog entries have been written from the data of new request on the basis of the older one.
    e.g older request  entries:
    a x 1
    new request
    a x 2
    change log
    a x 1
    a x -1
    a x 2
    so its quite obvious you can't have  a x 2 directly (because in the infocube you will be sending wrong entries by deleting the just the older request and loadning new request).
    2.If you have activate new and old request toghterh then also system will not allow you to delete the newer request alone and you will have to delete both the requests.
    I guess already someone proposed correct solution to you ...thats selective deletion...but rahter than doing selective deletion there is a better way if you want to cancel out a particular request:
    thats request reverst posting
    IN the process monitor of any particular request you can find out the option for request reverse posting..Its good for individual request cancellation(keyfig values will become 0 for that particular request)
    regards,
    rk

  • How to delete 100+ released requests from the import queue?

    Hello
    How to delete 100+ released requests from the import queue?
    One by one or there is more convinient way?
    Thanks

    To delete multiple non-imported transport requests, you do the following while in the import queue on STMS:
    1) Highlight the status field of the import queue.
    2) Sort the import queue by the status.
    3) Put your cursor on the first non-imported transport, right-click, and click on Select Block.
    4) Scroll down and put your cursor on the last non-imported transport, right-click and click on Select Block. This will highlight all requests from the first one selection to the last one selected.
    5) Go to menu option Request > Delete.
    If all of the requests in the import queue haven't been imported (no imported, including failed import, requests), you can jump to Steps 3-5.

  • How to delete a specific request from ODS

    Hi all,
    We have an ODS which we're loading invoices from legacy system. In legacy system, there are two tables for invoices. First one is daily records which is archived on last day of each month. As you guess, second table is  for archive records. We need all of the records from  both tables. Because of performance issue , we don't want to load both tables everyday . So we created two transformation. Since there is no delta option, we need to delete the first table request from data targets before extraction. And delete the request from the second table only last day of month. We're created process chain. But there is no option for deleting only the request from a specific data source or transformation. Are there any solution for this?
    thanks,
    Yigit

    Hi,
    Thanks for your code. But is there any function module to delete most recent request from the ODS.
    I had 2 requirements...One in need to delete from ODS & Other one from Cube.
    FM - 'RSSM_DELETE_REQUEST' will be used to delete from Cube only.
    Can please you send FM & ABAP Code to delete request from ODS.
    Thanks in advance.
    Yigit
    Message was edited by:
            Yigit

  • How to delete a noncompress request from the aggregates

    hello gurus
              i have a request in an infocube, which is not compressed in the cube. i rolled up the request, so that the data will  be moved to the aggregate. is it? then i found that the data is inconsistant. so i delete the request from the infocube manage scree, under the request tab. now my question is whether the data will be deleted from the aggregate or not?
    thanks in advance
    rams.

    If the Request has not been compressed in teh cube or the aggregate, you should simply be able to delete the Request form the Cube and it will be automatically deleted form teh Aggregate.  Since it has NOT been compressed in the aggregate, it should be a very quick process - no need to deactivate the aggregate.
    If it has been compressed in the aggregate, but not the InfoCube, you should still be able to delete the Request form the InfoCube, but the BW will have to refill the aggregate.  It should do this on it's own, but at differnt sopport packs, I had some problems with that always working.  As others have mentioned, in this case you could always deactivate the aggregate, the delete the Request from the InfoCube.
    As yo ureview this situation, you should consider how often you have/might have a problem like this.  If it occurs very often, then you should have your aggregate(s) for this cube setup so they do NOT automatically compress after Rollup.  Instead the Requests in the aggrgate will only be compressed when the Request in the InfoCube is compressed.

  • How to delete the previous request in Cube ?

    Hi All
      I have 2 sources loaded to Cube..
    Ex:
    ODS A --> Cube 1
    ODS B --> Cube 1
    Today they 31.10.2011 for both  in CUBE1
    so it becomes...
    ODS A --> Cube 1 --> 31.10.2011
    ODS B --> Cube 1 --> 31.10.2011
    tomorrow they load... CUBE 1 shld be..
    ODS A --> Cube 1 > 31.10.2011--
    DELETED
    So finally my cube has only following requests..
    ODS B --> Cube 1 --> 31.10.2011
    ODS A --> Cube 1 --> 01.11.2011
    ODS B --> Cube 1 --> 01.11.2011
    ODS A request which is older than 1day must be deleted before loading the next day...
    Can I use DELETE OVERLAPPING requests for this requirement? I am not too sure...what are the steps to be created..?
    as I tried but it was not successful.
    can anyone help me with IDEAS or steps??
    thanks a lot

    yes, you are right. You should use Delete overlapping request option.
    If it is not working, please let us know what option did you select for overlapping request deletion, may be you missed something there because overlapping request deletion is the best fit for your requirement.
    One thing you need to make sure that loads on both the days are done through PC only.
    If you do a manual load on 31.10.2011 and then PC loads data on 01.11.11, overlapping request deletion step will not delete the request loaded manually on 31st but if loads are done throught PC only, there should not be a problem.
    Regards,
    Gaurav

  • Unable to delete Failed Load Request from ODS

    Hi Ev'one
    I have a strange error.
    I try to delete a couple of red requests from the ODS and they do not delete. When i see the log for this Job; it says there is an Invalid table name and i guess the request is also not present anywhere to delete. Any Suggestions on how to resolve this
    This table is apparently present in the Prod Sytem and not present in the Dev and QA Systems.
    Would appreciate any pointers to cure this.
    Regards
    Shweta

    Hi Shweta,
       Go throuh the following OSS NOTE.
       We too faced the same problem.It was sorted with SP13
    <b>Note 1020120 - P13:DSO: Restarting terminated, deletion w/o ODS request SID</b>
    Assign points if it helps...
    Regards
    Prasad

  • How to delete a loaded DLL from an applet

    I succesfully wrote some code that extracts a Windows DLL from the applet jar to a temporary file and loads the extracted DLL (using a System.load call).
    Now I want to remove the DLL after the applet is closed. I tried to use the shutdown hook functionality of the java.lang.Runtime object, but this doesn't seem to work for an applet.
    Anyone any ideas about how to tackle this? Note that I'm not interested in installing the DLL's in for example the windows/system32 directory. To prevent any potential DLL versioning troubles I just want to use the DLL's as a temp file and remove them afterwards.

    I succesfully wrote some code that extracts a Windows
    DLL from the applet jar to a temporary file and loads
    the extracted DLL (using a System.load call).Once you loaded a DLL into JVM you cannot unload it.
    Now I want to remove the DLL after the applet is
    closed. I tried to use the shutdown hook
    functionality of the java.lang.Runtime object, but
    this doesn't seem to work for an applet.This is b/c the applet is running in the browser JVM and this isn't shutdown when an applet is closed.
    Anyone any ideas about how to tackle this? Note that
    I'm not interested in installing the DLL's in for
    example the windows/system32 directory. To prevent
    any potential DLL versioning troubles I just want to
    use the DLL's as a temp file and remove them
    afterwards.Maybe you can add to the DLL name as a suffix its version number.

  • Deleting requests from Cube with code using infopackage with two targets

    hi experts,
    Working on BW 3.5.
    I am creating a process chain to load from a table in a source system to two Infocubes.
    In the start routines of the update rules depending on the date of load, if it is not the last day of month InfoCube A will be loaded with data and InfoCube B will have Datapackage deleted but a request will still load but will contain no data.
    And vice versa if it is the last day of month.
    In InfoCube A I only want to retain a rolling 15 days of data and have entered a "Delete Overlapping Request from Cube" step.
    In the "Deletion-selections" of this step I have added a "Request Selection through Routine" and put in the following code;
      del_date = sy-datum - 15.
      loop at l_t_request_to_delete.
        if l_t_request_to_delete-timestamp+0(8) GT del_date.
          delete l_t_request_to_delete.
        endif.
      endloop.
    My question is, how can I ensure this delete code will only work for InfoCube A, as I only want the rollings 15 days of data in here, in Infocube B I want to store all the requests that are loaded here for the end of month.

    Hi
    Try in some sql browser with outer joins and you will see the problem.
    select *
    from (select nvl(leverklant.klant_code,'-1') fk_cube_abonnementen_kla_code,
         nvl(factuurklant.klant_code,'-1') fk_cube_abonnementen_kl2_code
         from ods_titsub
         left outer join dim_klant leverklant on (leverklant.klant_code = ods_titsub.cust)
         left outer join dim_klant factuurklant on (factuurklant.klant_code = ods_titsub.sta_cust)
         where (case substr(ods_titsub.isbn,1,8) when 'FBVISTAQ' then 'J' else 'N' end) = 'N'
         and ods_titsub.rec_sta <> 'X'
         and ods_titsub.curr_start >= to_date('01011999', 'DDMMYYYY')
         and ods_titsub.curr_start <= to_date('01022008', 'DDMMYYYY')
         and (leverklant.klant_sk is null or leverklant.klant_sk = leverklant.dimension_key)
         and (factuurklant.klant_sk is null or factuurklant.klant_sk = factuurklant.dimension_key)) a
    left outer join dim_klant b on
         b.klant_code = a.fk_cube_abonnementen_kla_code and
         b.dimension_key = b.klant_sk and b.klant_sk is not null
    left outer join dim_klant c on
         c.klant_code = a.fk_cube_abonnementen_kl2_code and
         c.dimension_key = c.klant_sk and c.klant_sk is not null
    Regards
    Result will be like:
    FACT_TABLE DIM1 NULL
    FACT_TABLE NULL DIM2
    but never like:
    FACT_TABLE DIM1 DIM2
    Message was edited by:
    Armands

  • How to delete the duplicate requests in a cube after compression.

    Hi experts,
        1. How to delete the duplicate requests in a cube after compression.?
        2. How to show a charaterstics and a keyfigure side by side in a bex query output?
    Regards,
    Nishuv.

    Hi,
    You cannot delete the request as its compressed as all the data would have been moved to E table ..
    If you have the double records you may use the selective deletion .
    Check this thread ..
    How to delete duplicate data from compressed requests?
    Regards,
    shikha

  • Delete overlapping requests from cube not working in processchain.

    In a process chain, 'deletion of overlapping requests from the cube ' step is used.
    Before this step a DTP step runs with a full update to load the cube. This process chain is scheduled every day.
    Issue is, the process chain failed at the DTP step and after correcting and repeating, the step got executed.
    However, the next step after the DTP,'delete overlapping requests from the cube'
    gets executed but without deleting the previous day's request.
    In the step details a message that 'No request for deletion were found' can be seen.
    Then next day when the DTPstep is executed without any problem the 'delete overlapping requests from cube' step is successful
    and the previous requests from cube are deleted.
    the deletion selections in the step ' delete overlapping request from infocube' is
    Delete existing requests
    Conditions:
    only delete requests from same DTP
    Selections
    Same or more comprehensive
    Because of this issue on a particular day because of the presence of 2 days requests the data is getting aggregated and shown as double in the reports.
    Please help.

    Hi Archana,
    When you delete the bad request from target and before repeating your DTP in PC, make sure the bad request deleted from table RSBKREQUEST also.
    If you find the same request in table, first delete the request from table and repeat the DTP in PC.
    Now Delete overlapping step should work.
    As this is not the permanent solution, please raise an OSS for SAP
    Regards,
    Venkatesh

  • Program to delete a specific request from a Cube

    Hi Everyone,
    I've been trying to delete a certain DTP request from a cube but I'm unable to delete it. Is there any ABAP program to delete a specific request from a cube by provinfing requeset ID as the input.
    Thanks,
    Ram

    HI
    SE37RSSM_DELETE_REQUESTGIVE YOUR REQUEST NO & INFOCUBE NAME here. and execute.
    Table is :RSBKDTP contains DTP and target details.
    Hope it helps

  • How to delete selective data in a cube

    Hi all,
    Can any one tell me, how to delete selective data in a cube. For example if i want to delete data corresponding particular Matrial Id  or particular Customer ID (say C400) ? And even deleting the data based on particular Request numer.?
    Sandy.

    Hi,
    RSMO > Infocube > Manage > contents tab > selective deletion
    Then define your selections for deletions (Matrial Id or particular Customer ID (say C400)).
    Request based deletions can be done directly from Request tab.
    Thanks,
    JituK

  • How to delete aggreagetd data in a cube without deleting the Aggregates?

    Hi Experts,
    How to delete aggreagetd data in a cube without deleting the Aggregates?
    Regards
    Alok Kashyap

    Hi,
    You can deactivate the aggregate. The data will be deleted but structure will remain.
    If you switch off the aggregates it wont be identified by the OLAP processor. report will fetch the data directly from the cube. Switching off the aggreagte won't delete any data,but temporarly the aggregate will not be availbale as if it is not built on the info cube. No reporting is not possible on swtiched off aggregates. The definition of the aggregate is not deleted.
    You can temporarily switch off an aggregate to check if you need to use it. An aggregate that is switched off is not used when a query is executed.This aggregate will be having data from the previous load's. If the aggregate is switched off means it wont be available for reporting but data can be rolled up into it.
    If u deactivate the aggregates the data will be deleted from the aggregates and the aggregate structure will remain the same.
    The system deletes all the data and database tables of an aggregate. The definition of the aggregate is not deleted.
    Later when you need those aggregate once again you have to create it from scratch.
    Hope this helps.
    Thanks,
    JituK

  • How to delete repair full request

    Hi,
    There was a delta load scheduled in background. By mistake before the delta load a repair full load with particular company code selection was run. So after the delta load, data is duplicated in the system. Now the request is compressed. I want to delete this repair full load request from the ODS. Please let me know step by step solution for this.
    Thanks.

    Hi,
    from where u r loading data into cube from ODS or R/3. if u run a repair full load then it will not check the data mart symbol although it is successfull so the next delta will brings data again, so u have to run init with out data transfer to make deltas 0 in source. this happened in ur case .
    but the cube is compressed so u cant delete data request based
    is there any PSA there if there is PSA then u can use REVERSE POSTING from PSA this will brings key figure values with - values so the records will be nullified
    in manage of the cube -> select that repair full request -> click on monitor button -> u can find an icon in the top(psa request symbol with red mark) click on that and execute.
    if there is no PSA then u have to do selective deletion.
    assign points if it helps,
    thanks,
    pavan.

Maybe you are looking for