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.

Similar Messages

  • 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

  • What is process type like delete overlap request

    Hi experts,
    what is process type like DELETE OVERLAP REQUEST. how to use it i mean after load data into target or before loading data.
    for good answer points will assign.

    Hi,
    Whenever you load a data(eg full load). you can delete the previous request and you can load the new data. That's a called deleting overlapping request.
    folllow these links.
    http://help.sap.com/saphelp_nw2004s/helpdata/en/f8/e5603801be792de10000009b38f842/frameset.htm
    process chain - delete request
    deleting overlapping requests via a process chain
    Delete overlapping requests from ODS
    Delete Overlapping Requests from InfoCube: Before or After the Generate Ind
    Delete overlapping request
    Proc chain auto delete of overlapping requests not working.
    if it is useful assign points
    Regards,
    Senthil Kumar.P

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

  • 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

  • Process Chain - Unable to delete overlapping request

    Hi Gurus
    I'm in the mid of creating process chain to load transaction data  in which I need to delete the previous load that loaded in using the same DTP previously
    In the process chain , i have included a process "Delete Overlapping Request from Infocube" . Once i'm in the screen of maintain variant for this process, i selected DTP as the object type but unable to find the DTP that i have created under the object name.
    Can someone point out what is missing
    Thank you

    Hi,
    Looks like you need to give the the techincal name of the DTP. if you are un able to find the technical name of the DTP you can find that in the transport organizer.
    just drag and drop the infoprovider ( with dataflow before) you will ge the DTP as required.
    note the technical name of the DTP .
    include the technical name in the process and activate the process.
    Santosh

  • 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

  • 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

  • "Delete Overlapping Requests from InfoCube" in a Process Chain

    Dear all,
    I encountered a problem when I building the process chain in BW 3.0.
    In a process chain, I schedule daily an InfoPackage to load data to an InfoCube and then delete the previously loaded data by the same InfoPacckage from the InfoCube.
    For example, I have 2 InfoPacakge, A and B, and schedule to load data to InfoCube C. In the process chain, I scheduled daily the following tasks in sequence:
    - Delete index in InfoCube C
    - Load data through InfoPackage A to InfoCube C
    - Delete duplicated request previously loaded through InfoPackage A in InfoCube C
    - Load data through InfoPackage B to InfoCube C
    - Delete duplicated request previously loaded through InfoPackage B in InfoCube C
    - Create index in InfoCube C
    However, when I activate the process chain, a warning message is prompted: No type "Delete Overlapping Requests from InfoCube" process allowed infront of process "Execute InfoPackage" variable ZPAK_4GMFI
    Would anyone tell me why such warning message is prompted?
    Many thanks!
    Best regards,
    Marcus

    Hi all,
    Re Ranjan:
    I previously config the process chain like that:
    (1)   Delete index in InfoCube C
    (2)   Load data through InfoPackage A to InfoCube C
    (3a) Delete duplicated request previously loaded through InfoPackage A in InfoCube C
    (3b) Load data through InfoPackage B to InfoCube C
    (4)   Delete duplicated request previously loaded through InfoPackage B in InfoCube C
    (5)   Create index in InfoCube C
    where (3a) and (3b) is executed simultaneously.
    However, (3b) often reports error. I guess it may be due to the parallel run of (3a) and (3b). So that's why I set the process chain to be executed in serial.
    Re Jacob:
    I found that the process chain can be run even a warning message is prompted when activating the process chain!.
    Thanks you all for your kind support!!
    Best regards,
    Marcus

  • 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

  • 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

  • Duplicate records: Process : Delete Overlapping Requests from InfoCube

    Hi Experts,
    We are loading data in standard costing cube with standard available option Full upload. In our process chain we have included process type "Delete Overlapping Requests from InfoCube". In our scenario we always load yesterday and today's data. In this case after loading yesterday's data, we need to check and delete the overlapping requests and then upload todays data.
    Many a times this deletion process is failing due to message "Couldn't lock cube" because it is already locked by user "ALEREMOTE". This cause system to duplicate the records in cube.
    How we can avoid this?
    Alok

    I tried running again and it again failed. Checked in SM12 and found this entry
    800     ALEREMOTE     08/14/2007     E     RSENQ_PROT_ENQ     CREA_INDX      ZCCA_C11                      DATATARGET     CREA_INDX                     ######################################     0     1
    This locked is not released since 14th. Is there way to remove the lock using some process.

  • 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

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

  • How does Delete overlapping requests work?

    We have a extract which does a full loads into a cube for the current year and a we run this daily. In the process chain we do a delete overlapping requests which I understand will delete the previous requests with the same condition. What happens when the year changes?  On Dec 31 we will load 2008 data while the next time it runs on Jan 2 it will load only 2009 data (variant only looks at current year). Will deletion of overlaps delete all the 2008 data it loaded on Dec 31? Thanks.

    what is removed depends on the settings of your delete request.
    You can use only dtp-name, or dtp name with same selection parameters or with same selection parameter in a certain amount of time.
    Take a look at the settings; i found them quite self explanatory.

Maybe you are looking for