InfoPackage with overlapping requests deletion

Hi,
what is an InfoPackage with overlapping requests deletion? Where is it used?
Regards

hi,
check out the below link it answers your query in detail.
Re: Delete overlapping request
hope it helps.
regards,
AL

Similar Messages

  • Delete Overlapping requests not paying attention to filters

    Hi Experts,
    I have followed all the steps suggested by Chetan in the next thread to cnfigured deletion of overlapping requests.
    Process Chain  Delete a previous request with overlapping values
    In my case I need to delete requests when the data is from the same country and the same day, so I added these fields to the filters in the DTP (I didn't put any value or variable, just added the filters). However the process chain is deleting all requests coming for that DTP and is not paying attention to my filter. What could it be?
    Points will be awarded,
    Regards,
    Raimundo Alvarez

    Hi Amruta,
      Good to hear that your Overlapping Request Deletion process i working fine now
    1) The difference between More Comprehensive & Overlapping  (What is the difference between same or more comprehensive and Overlapping?)
    If overlapping is selected then:
    existing requests are also deleted from the InfoCube if the selection criteria of the new request partially or wholly overlap the selection criteria of the request to be deleted.
    If More Comprehensive is selected then:
    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.
    Also do check the below link, It will be very useful
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0431c48-5ba4-2c10-eab6-fc91a5fc2719?quicklink=index&overridelayout=true
    2) The index creation process should be kept after the overlapping request deletion because if it is placed after the overlapping request deletion then all the overlappings will be removed and then the create index process will take less time to create index for only required request else more time will be taken to create indexes.
    In case if the create index step is included before the Overlapping Request deletion then the performance will decrease instead of increasing..
    Instead you have option of including BIA indexes in case if the reporting performance needs to be improved.
    Please change the status of question to answered in case if all answers are received...
    Thanks
    Pawan

  • Error in PSA Request deletion

    Hey all,
    how are you!
    I have a little glitch in my Processchain and since I can not seem to find an answer myself I was wondering if any of you might give me some feedback
    In a processchain I created, I wanted to delete the PSA-table contents and I added this process called "Deletion of requests from PSA".
    But whenever I check my daily run, I have to get back (due to its "red" nature) and do manually 'rightclick>repeat' and then all seems well.
    The 'red' condition upon monitoring gives me the message "no sub-request for this request"...
    well...anyone?

    Hey Olivier,
    It is a transactional load from an R/3 ODS.
    In the processchain first we load an ODS and then we start with a request-deletion on the PSA.
    Options:
    - older then...zero days
    the others are not used.
    Nothing fancy
    Just following
    http://help.sap.com/saphelp_nw70/helpdata/EN/b0/078f3b0e8d4762e10000000a11402f/frameset.htm
    Edited by: richard boom on Jan 17, 2008 2:29 PM

  • Overlaping request

    Hi Gurus,
    delete overlapping request process variant has been failed, in display message error is 'Unknown error'.
    i have solved the issue,
    but i want know what could be the reason behind this,
    same time attribute change run was running is there any relation between overlapping request deletion and attribute change run.
    could some body can help me for this.
    its urgent,
    Thanks a lot in Advance,
    Dandi

    Hi Aneesh,
    Thanks for you valuable suggestion,
    but still i have doubt why it is showing unknown error.
    Could you help me for this....
    Regards
    Dandi

  • Proc Chain - Delete Overlapping Requests fails with aggregates

    BW Forum,
    Our weekly/daily load process chain loads several full (not delta) transaction infopackages. Those infopackages are intended to replace prior full loads and are then rolled up into aggregates on the cubes.
    The problem is the process chains fail to delete the overlapping requests. I manually have to remove the aggregates, remove the infopackages, then rebuild the aggregates. It seems that the delete overlapping request fails due to the aggregates or a missing index on the aggregates, but I'm not certain. The lengthy job log contains many references to the aggregate prior to it failing with the below messages.
    11/06/2004 13:47:53 SQL-END: 11/06/2004 13:47:53 00:00:00                                                 DBMAN        99
    11/06/2004 13:47:53     SQL-ERROR: 1,418 ORA-01418: specified index does not exist                        DBMAN        99
    11/06/2004 13:47:59 ABAP/4 processor: RAISE_EXCEPTION                                                       00        671
    11/06/2004 13:47:59 Job cancelled                                                                           00        518
    The raise_exception is a short dump with Exception condition "OBJECT_NOT_FOUND" raised.
    The termination occurred in the ABAP program "SAPLRRBA " in
    "RRBA_NUMBER_GET_BW".                                    
    The main program was "RSPROCESS ".                        
    I've looked for OSS notes. I've tried to find a process to delete aggregates prior to loading/deletion of overlapping requests. In the end, I've had to manually intervene each time we execute the process chain, so I've got to resolve the issue.
    Do others have this problem? Are the aggregates supposed to be deleted prior to loading full packages which will require deletion of overlapping requests? I presume not since there doesn't seem to be a process for this. Am I missing something?
    We're using BW 3.3 SP 15 on Oracle 9.2.0.3.
    Thanks for your time and consideration!
    Doug Maltby

    Are the aggregates compressed after the rollup?  If you compress the aggregate completely, the Request you are trying to delete is no longer identifiable once it is in the compressed E fact table (since it throws away the Request ID).
    So you need to change the aggregate so that it the most recent Requests remain in the uncompressed the F fact table.  Then the Request deletion should work.
    I thought what was supposed to happen if the aggregate was fully compressed and then you wanted to delete a Request, the system would recognize that the Request was unavailable due to compression and that it would automatically refill the aggregate - but I'm not sure where I read that. Maybe it was a Note, maybe that doesn't happen in a Process Chain, just not sure.
    The better solution when you regularly backout a Request  is just not the fully compress the aggregate, letting it follow the compression of the base cube, which I'm assuming you have set to compress Requests older than XX days.

  • 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

  • Problems with delete overlapping requests from InfoCube in PC

    Hi guys,
    Iu2019m using delete overlapping requests from InfoCube in Process Chains, but Iu2019m not being able to adjust it to my specific requirement.
    For example:
    I execute DTP to load InfoCube XPTO with Fiscal Year 2008 and 2009. After this I have to load again, but only for 2009.
    In this specific example I want my process chain to delete the 2009 data from my first load, because it is overlapped, and leave 2008 data.
    Is this possible? If yes how?
    Thanks in advance
    Jão Arvanas

    It will not work that way.
    It will look if the selections are same then it wil delete if not then it will not do that activity.
    Overlapping settings which you might chosen is based on the delete overlapping for the same selections..
    So in this case the selections are different and hence its not possible.
    Thanks
    Murali

  • 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

  • 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

  • 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 from infocube

    Hi ALL,
    I have loads to infocube from  5 diffrent infopackages loading adhocly or randomly from same source sytem and same infosource.
    Note:infopackages have dynamic selections.(ex calweek,product)
    My requirement: If i load infopackage-1 today,and when i load the same infopackage next time the prevoius load should be deleted .
    I need the same functionality for other 4 infopackages.
    So at given point of time i should have only 5 requests in the infocube.
    These are the settings i have done.
    1)At infopackage level i have selected option Delete existing requests : overlapping
       Without selecting any conditions like infosources,source sytem are same.
    2)Added process type in the process chain delete overlapping requests from infocube
       selected option: Delete existing requests : overlapping.
       Without selecting any conditions like infosources,source sytem are same.
    Are these settings are enough or is there in best way to do this .
    Please suggest me ...

    Kishore,
    Delete overlapping requests means, delete request with same selection only. If data selection not same, i dont think it will delete any previous request.
    You can select infosource, source system. No issues. System only deletes request if data coming from same infosource or from same source system for same selection.
    But in your case selection changing every day or for every load. I dont think it works.... Try once in DEV.
    If i understand correctly, as you only needed latest 5 requests only, why cant you delete data completely before loading / starting new set of requests...?? This is easy, quicker and better approach.
    But only problem is data will not be available during loading of new set of requests.
    Srini

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

  • Data Transfer Process and Delete Overlapping Requests

    Hi All,
    We are on BW 7.0 (Netweaver 2004s).  We are using the new data transfer processing and transformation.  We want to use the ability to delete overlapping requests from a cube in a process chain.  So lets say we have a full load from an R/3 system with fiscal year 2007 in the selection using an infopackage.  It gets loaded to the PSA.  From there we execute the data transfer process and load it to the cube.  We then execute the delete overlapping requests functionality.  My question is, will the DTP know that the infopackage selection was 2007 so it will only delete requests with selections of 2007 and not 2006 from the cube?  Basically, is the DTP aware of the selections that were made in the infopackage?
    Thanks,
    Scott

    Hi Everyone,
    Figure it out...on a data transfer process you can filter the selection criteria - go to the extraction tab of a DTP and click on the filter icon.  Enter your seleciton conditions to pull from the PSA....these seleciton conditions will be used to delete the overlapping requests from the cube.
    Thanks

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

  • Delete Overlap Requests

    Hi Gurus:
    I need your help so I try to write it down short, for clearer pictures.
    I'd like to know the behaviour of delete overlapping requests.
    I have a basic infocube (ZMYCUBE) and I load it with first requests, for simpliciy, said it request 165 and it has 5 rows in fact table.
    The next request (i.e. request 170) is apparently an indentical request except with 1 row difference (i.e 4 rows identical, 1 row difference, total is still 5 rows).
    Within infopackage with data target ZMYCUBE, and infosource ZMYSOURCE, I try to use delete overlapping request cus ZMYSOURCE The source system has 20 keys so ODS cannot help me.
    Does anybody has experiences how to deal with that issue ? Will "delete overlapping requests" really works on "content of data packet" ? Or it will delete the whole request 165 and upload the whole 5 records again ?
    My goal is to find a solution not to delete Request 165 cuz ZMYCUBE is a simulation for 100.000 lines single request so deleting such lines is not cost effective.
    My expectation is for BW to only add and transfered 1 record. not 5
    Points will be awarded for satisfactory answers ...
    Thank you

    Hi,
    Option "Deletion of over-lapping request'' simply deletes the entire Package from Cube based on the selections and it won't go thro' the content of the data. In your terms this option does the deletion of whole request 165 and upload the whole 5 records again.
    This option looks at the selection conditions specified for request 165 and then look at the selection conditions of request 170 and then look at deletion options specified, based on these options system would delete the Info package 165.
    Hope this helps.
    Bala

Maybe you are looking for