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

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

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.

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

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

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.

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

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,

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

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

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 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 overlaping requests doesnt work with delta

Similar Messages

Maybe you are looking for