Delete overlapping requests in Cube

Dear all,
I need delete the requests uploaded in the previous day when transferring new request into Cube,and the system is BW 7.0,but I use 3.5 data source and infoSource.
The issue is that when I

Tianli,
You can delete the overlapping request in the infocube.
In the infopackage -
> Data Targets -
> Automatic loading of similar/identical requests
You can set the parameter for deleting the overlapping request here.
If you are using process chains, there is a process type available
Load process and post processing-----> Delete overlapping request from infocube.
Can you post your question again as I see it is incomplete..
Sasi

Similar Messages

  • 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

  • Process type "Delete overlapping request in cube " in process chain

    Hi
    can somebody suggest me where i need to place the process type "Delete overlapping request" for an infocube.
    Regards,

    Hi,
    When you use the corresponding process in the process
    chain maintenance screens to specify the conditions for
    automatic deletion, these conditions are applied to all
    the InfoCubes for the selected InfoPackages
    Overlapping: If you set this indicator, existing requests are also
    delete from the InfoCube if the selection criteria of the new request partially or wholly overlap the selection criteria of the request to be deleted
    Same or Comprehensive: If you set this indicator,
    requests are only deleted from the InfoCube if
    the selection conditions of the new request are
    the same as or more comprehensive than the selection
    conditions of the request to be deleted.
    Thanks
    Bhagesh

  • Problem while deleting overlaping request from cube

    Hi experts,
    I have one process chain in which i have one step where i am executing one DTP to load one cube and in next step deleing overlapping requests from same cube.
    i am getting error at that step "Error when deleting requests for comparison request DTPR_4CCDXZLK1OIGCVGGE1PP31Z3Y"
    what could be reason?
    plz help

    Hello,
    I guess you have not defined the overlapping variant properly.
    Please goto the definition of the variant and check for the right DTP input.
    Then at the bottom, select second option "Edit all Infocubes with Following Delete Selections"
    Click on deletion selections -> select delete existing requests.
    Also select if same datasource and source system. and importantly select the radio button as overlapping.
    Then save the variant. and try to use it.
    Regards,
    Shashank

  • Delete Overlapping Request

    Hi All,
    I am trying to use the process type Delete Overlapping Requests from cube in Process chain after loading the data from the Infopack full load and DTP Delta .  With the infopackage selection in process type the message after execution is no overlapping request found.
    Deletion selection I used is Full or Init loads, Same Datasource. and Selection are same or more comprehensive.
    And in the infopackage I dont have any selections.
    Please help me to solve this error.
    Regards
    PV

    C i'll explain our scenario..
    there was data loaded from 2 data sources to one cube thru 2 dtp's from 2 DS's in process chain...
    Soon after the 2 DTP steps, delete overlapping request step is defined from both the ends.in chain...in whcih variant is
    object type: the same DTP and its name which loads from PSA to cube.
    radio button selected as: edit all infocubes with following delete selections.
    selections: delete existing request under which Only delete request from the same DTP.
    same or cmprehensive.
    the other variant is defined as the same but with another DTP name in object type..
    the Output of the cube will be only latest(current day) requests..
    rgds,

  • Delete overlapping requests runs for 5+ hours ...This is too long

    We are on BW 3.5 and have a process chain that loads 3 years of data from a cube on the APO Server and AOP data from the BW server into a cube on the BW server.  Each load is in its own infopackage.  This loads happens every week.  We want to delete the loads that occurred the week before using the delete overlapping requests.  It is set up as follows:
    <b>1.</b>Drop index of Cube
    <b>2</b>.Load Current Year data into Cube via Infopackage #1.  Loads approximately 32 million records.  Selections on calweek: 200701 – 200752.  Infosource: InfoSource for APO-DP Cube from APO(ZAPODP_I11). Datasource: APO-DP Backup Cube(8ZAPODPC73).  Source System: APP Client 200(APPCLNT200).  The Data targets tab is set up as follows: ‘Automatic Loading of similar/identical requests from the cube’ wherein Delete Existing Requests Conditions: Infosources are the same.  Selections are overlapping.
    <b>3</b>.Load Current Year + 1 data into Cube via Infopackage #2.  Loads approximately 32 million records…Selections on calweek: 200801 – 200852.  Rest is same as above #2.
    <b>4.</b>Load Current Year +2 data into Cube via Infopackage #3.  Loads approximately 32 million records…Selections on calweek: 200901 – 200952. .  Rest is same as above #2.
    <b>5</b>.Load AOP data into Cube via Infopackage #4.  Loads approximately 135,000 records.  Infosource: AOP Plan(8ZAOPC01). Datasource: AOP Plan(8ZAOPC01). Source System: BW Production(BWPCLNT100).  The Data targets tab is set up as follows: ‘Automatic Loading of similar/identical requests from the cube’ wherein Delete Existing Requests Conditions: Infosources are the same.  Selections are overlapping
    <b>6.</b>Create index on cube
    <b>7</b>.Delete overlapping requests from cube.  The process chain step is set up to ‘Use Delete Selections for Infocubes from the Infopackages’
    <b>The issue is that step #7 runs for more than 5 hours.</b>  That is way too long.  When we manually delete the requests, it takes 5 minutes.  How can I fine tune this processing?  Thanks in advance!
    <b></b>

    What is your dbms? Does it support partitioning? If it does then deleting requests merely drops the corresponding partitions, which should be very fast.
    If it does not support partitioning then you're running SQL delete statements to delete the data, which could take a long time if you're deleting tens of million of records. BTW how long does it take to load the same data?
    P.S. Just saw your last point about manually deleting the requests taking only 5 minutes. Did you delete one request at a time or multiple request at once? The previous poster wanted to know whether you had background processes to run the deletion job. i.e. Did the deletion really took 5 hours, or did it wait a few hours to start the job?
    Message was edited by:
            Rick Chau

  • Reasons for "Delete Overlapping Request"

    Hi everyone,
    A simple question for you gurus out there. What is the reason for having a process in the process chains to "Delete Overlapping Requests". I am not sure what it really does. Can someone please explain in simple terms the functionality of Delete Overlapping Requests and it's need. Please use an example if possible.
    <Remoed_By_Moderator>
    Offering or asking for points is against the forum rules
    Edited by: Pravender on Aug 6, 2010 10:54 AM

    Generally we do this Delete Overlapping Requests for cubes because you have a requirement to do daily full loads(assume incremental data) to Cube from the same DS if you don't delete the previous load .. In cube values gets double which is wrong data.. to avoid duplicates we use this Delete Overlapping Requests in PC .. if you don''t use this process in PC .. everyday manual action will be required to delete previous (yesterdays)request in cube.
    Ex.
    Req1 15000 records to cube -day1
    Req2 15600 records to cube -day2
    Req3 15600 records to cube -day3
    in cube you will have 46000 records and keyfigures values gets tripple
    if you use  "Delete Overlapping Request" in PC
    always deletes the previous request from the same DS

  • Delete overlaping requests doesnt work with delta

    Hello
    I need to delete previous request delivered by delta DTP. Process type "Delete overlaping requests from cube" doesnt allow to select delta DTP.
    Is it only for full load DTP?
    Alex

    Hi ,
    Delete Overlapping request from cube works only for full loads.
    Also if you have any such query regarding DTP functionality please reger this article
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10339304-7ce5-2c10-f692-fbcd25915c36
    -Vikram

  • Process Type - Delete overlapping requests from an Info Cube

    I have read many threads on this topic, still have some questions. To give you background, I will be doing delta load (“delta” process chain). But before delta, I want to do setup initialization (“init” process chain). I want to use this process type in my “init” process chain” to delete all data in my cube loaded from a specific ods. I cannot use delete all contents process type because many ods’s feed the same cube.
    1.     Do you put this process type after Load Data or before Load Data. I have seen both cases in SDN forums.
    2.     Variant of this process type is an info package. Does this info package have to be same as in load data step or it can be different.
    3.     I want to delete all data in cube which was loaded from my ods. Term overlapping is confusing to me. Will this process type delete all data or not.
    Tanks in advance.

    Yes, you can do that. Goto RSPC - under process types Load Process and Post Processing, you will see DELETE OVERLAP REQUESTS FROM INFOCUBE option is there.
    Select the proper check boxes like same sourcesystem, same datasource etc...
    If it is one time deletion, why not do that manually?
    Also check: How to delete most recent request in a Cube by using process chain
    Hope it helps..

  • Delete overlapping requests of same DTP from cube

    Dear All,
    i want to delete over lapping requests of same DTP in cube, but here while i am searching for the DTP in process variant, the system is not showing the DTP(it is active).
    can you people have any suggestions.
    Br,
    Vamshi.

    Hey Vamshi,
    Is your DTP a full one or delta one ? Delete Overlapping reqs is not possible for Delta loads.
    In Load Process and Post-Processing option you will find Delete Overlapping Requests from InfoCube, drag and drop and make the following settings:
    Object Type = DTP
    Object Name : DTP Name.
    Check Edit all InfoCubes with the following Delete Selections and click on Delection Selection
    Check Delete Existing Request and check Only Delete Req from same  DTP
    Activate and execute the PC.
    Hope this helps!
    Sheen

  • Cube Compression - How it Affects Loading With Delete Overlapping Request

    Hi guys,
    Good day to all !!!
    Our scenario is that we have a process chain that loads a data to infocube and that has delete overlapping step. I just want to ask how does the cube compression affects the loading with delete overlapping request. Is there any conflict/error that will raise? Kindly advice.
    Marshanlou

    Hi,
    In the scenario you have mentioned:
    First the info cube would be loaded.
    Next when it goes to the step i.e delete overlapping request:  in this particular step, it checks if the request is overlapping (with the same date or accd to the overlapping condition defined in the infopackage, if the data has been loaded). 
    If the request is overlapping, then only it deletes the request. Otherwise, no action would be taken.  In this way,it checks that data is not loaded twice resulting in duplicasy.
    It has nothing to do with compression and in no way affect compression/loading. 
    Sasi

  • 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

  • Delete Overlapping Request from InfoCube.

    Hello,
    I am using process Type "Delete Overlapping Request from infocube" in this I am selecting object type as a "DTP"
    Under "Delete Selection" I am selecting following
    1. Only Delete Requests from same DTP
    2. Only Delete Full DTP request
    3. Only Delete DTP Requests from Same Source
    I am using "Full Load" in my DTP.
    My requirements are like  I need to delete old data and load new data every day in to  a cube for that I am using this process type.
    If anybody have better solution please let me know.
    Thanks,

    Also
    I am not deleting Index  OR  Not creating Indexs while using process type "Deleting overlapping request InfoCube"
    what will be the impact on the cube?
    How many index will have infocube?
    If the cube having more than one index if i delete index, which index will be deleted?
    Thanks,

  • Delete overlapping request in PC - Request from previous month got deleted

    Hi Everyone,
    We are using a 'Delete overlapping request' step in a process chain. Under the Deletion Selections, we have checked the following options:
    1) Only Delete Requests from Same DTP
       |_ Selections are - Overlapping
    2) Request Date - Is in the Current Month
    3) Exceptions:
       |_ New Request will be loaded on - 1st Day of a Month
    The datasource in this case is used for a Full update into a Cube everyday. We've used the above selections so that the request loaded on the last day of a month is not deleted by the subsequent load. We need this to retain a snapshot of the data for each month.
    This month, when the process chain executed on 1st Feb, the request loaded on 31st Jan was not deleted. However, on 4th Feb, the Process chain deleted the request loaded on 3rd Feb and also the one from 31st Jan. There seems to be no reason at all for the 31st Jan request to get deleted. We've made sure of that by choosing the option 'Request Date - Is in the Current Month' in the Deletion Selections.
    Is there any explanation why the request was deleted?
    Thanks,
    Ram

    Hi,
        If you dont have any selections , it will delete the previous request. Based on the selections only overlap will work.  For your scenario , it wont delete previous month request after changing it to current Fiscal period. Once check the selection options , is it displaying month wise or empty selections.
    Regards
    Pcrao.

  • Process Chain Help - Delete Overlapping requests

    Dear Experts,
    I have a requitement where I want to delete the ' previous days' request from the cube. This has to be from the data coming from only one DSO.
    I can use the Delete overlapping request process type but I want to know how.
    And again, this has to be only for the current month.I want to delete the overlapping requests of current month i.e now since I am in April I want to delete only the April requests. When I am in  month May I dont want to delete april request anymore.
    In other words I want to delete the april request until April 30th. On May 1st I dont want to delete the april 30th request. On may 1st it shouldn't delete anything. On May 2nd it should delete the May 1st request.
    Can anyone help me with this.
    Thanks,
    KK

    Hi KK,
    If I have understood you correctly, you mean to say your cube is getting loaded from various Datasources and you want to delete the requests only for a particular Datasource and not for others.
    Please correct me if i am wrong.
    If I am right ! Then on the window "Delete Request from Infocube after update" you can "Delete Existing Requests - > Is current month" and on the bottom of that screen you can see a checkbox for Request Selection Through Routine. Check this and you can simply write a routine to do the deletion for only requests loaded from a particular datasource.
    Hope it helps.
    Regards
    Hemant Khemani

Maybe you are looking for