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

Similar Messages

DTP Questions: Delete overlapping requests; Repair Full Request

Hello,
I'm new with the DTP concept in BI 7.0.
It is clear to me how DTP is working for normal loads like: full, delta, delta without data transfer etc.
But I don't see where I can specifies "Delete overlapping requests". Is this still possible in a DTP, or is it only possible by creating a Process Chain and insert the process-type "delete overlapping requests" ?
Also I have a question about "Repair Full request" using DTP. Is this option still possible ? Or do I have to create a DTP with extraction-mode = Full => Extraction from Active table. => Is delta than still working ?
Thanks for your input,
Wim

But I don't see where I can specifies "Delete overlapping requests". Is this still possible in a DTP, or is it only possible by creating a Process Chain and insert the process-type "delete overlapping requests" ?
This option is available only in Process Chains when u use DTP's.
/people/community.user/blog/2007/06/21/sap-netweaver-70-bi-data-transfer-process-with-147only-get-delta-once148
/people/community.user/blog/2007/06/21/sap-netweaver-70-bi-data-transfer-process-with-147get-data-by-request148
Also I have a question about "Repair Full request" using DTP. Is this option still possible ? Or do I have to create a DTP with extraction-mode = Full => Extraction from Active table. => Is delta than still working ?
Full Load was made Repair Full to Initialize if loading an ODS but however you dont need to worry abt the same in Netweaver 7.0 as DTP is taking care of the loading from PSA to DSO.
Initialization can be done after a full load as the load is only till PSA ( At Datasource Level ).
DTP doesnot require any initialization.
U can jst do a Delta DTP after a Full DTP to a DSO or u can even start with a Delta DTP directly.
For the first time -> Delta DTP = Full DTP !!

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 odss 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 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

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

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

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

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

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

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 question

Similar Messages

Maybe you are looking for