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

Similar Messages

Deletion of data target contents Vs delete overlapping requests

hi,
when do we go for delete overlapping requests? if it is applicable for full load as well as delta load then i would like to first come up with the full load concept, we have the other option called delete data target contents with this we can delete daily full load without going for delete overlapping requests.
Pls let me know exact difference between DELETE OVERLAPPING REQUESTS FROM INFOCUBE with DELETE DATA TARGET CONTENTS.

hi
When you have delta upload twice daily..the date in the previous request and the second request is same....so you might be giving this option to delete the overlap such that data is not loaded twice
Assign points dont forget
Regards
N Ganesh

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:
1.Drop index of Cube
2.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.
3.Load Current Year + 1 data into Cube via Infopackage #2. Loads approximately 32 million recordsSelections on calweek: 200801 200852. Rest is same as above #2.
4.Load Current Year +2 data into Cube via Infopackage #3. Loads approximately 32 million recordsSelections on calweek: 200901 200952. . Rest is same as above #2.
5.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
6.Create index on cube
7.Delete overlapping requests from cube. The process chain step is set up to Use Delete Selections for Infocubes from the Infopackages
The issue is that step #7 runs for more than 5 hours. 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!


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

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.

Delete Overlapping Requests in a DSO

Hi,
I know how to delete overlapping requests for an InfoCube via the process chains using the process "Delete Overlapping Requests from InfoCube"
Is there a way to do the same thing with a DSO?
The reason I want to do this is because I have a custom view which I am extracting from and we want to ensure that deletion of documents are seen in BI. If someone deletes a document it is deleted from the view. So the only way I can think of ensuring we see up to date data is to load the data everynight and delete the duplicate requests.
Thanks,
Leo

Hi Leo,
check out the below mentioned thread:
new DTP situation
hope it helps,
regards,
Supi

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 when month changes

Hi Experts,
Delete overlapping request works fine for all the days but when month changes it is not deleting the request as the filter value gets changed.
I have three Info Package and DTP like below:
Current Month -2
Current Month -1
Current Month
In January selection values are:
Current Month -2     201111
Current Month -1     201112
Current Month         201201
As the month changes, February selection values are:
Current Month -2     201112
Current Month -1     201201
Current Month         201202
We need the request which has selection criteria 201111 should stay, but 201112 and 201201 should get deleted as these two request are duplicated.
Please advice if we have any solution for this issue.
Suggestion will be appreciated.
Thanks,
Muiz Ahmed

Yes Sven,
You are correct,
31-Jan-2012 Current Month -1 had loaded 201112
1-Feb-2012 Current Month -2 had loaded 201112
Now I have to delete request which has got loaded on 31-Jan-2012.
For now I have deleted manually, but I want automate this activity, so no manual intervention is required.
Thanks,
Muiz Ahmed
Edited by: MUIZ AHMED on Feb 1, 2012 7:40 PM

Delta DTP and Delete Overlapping Requests

Hi,
Please check the article:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10339304-7ce5-2c10-f692-fbcd25915c36
-Vikram

Hi
In the Delete Overlapping Requests from Infocube Process there is an button Deletion Selections Check what are all the options selected in that there are some 3 check boxes like
a) Only Delete Requests from Same DTP
b) Only Delete Full DTP Requets
c) Only Delete DTP Requests from Same Source
if option B is checked it will work only for Full Requests not for Delta. Check the same in your system.
Thanks

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

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.

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.

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

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

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

Reasons for "Delete Overlapping Request"

Similar Messages

Maybe you are looking for