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

Similar Messages

DTP and Deleting overlapping requests

Do we have the option to delete overlapping requests when using DTP to load data? Thanks

hi ,
Pls create a process chain.
1. Add Delete Overlapping Requests from InfoCube .
2. In the deletion selection check : Conditions:
mark : Only delete request from same DTP
Only delete full DTP request
Only delete full DTP request from Same source
Then Mark : Overalapping.
In the DTP : Add date in the Filter .(Cal/Year Mth) ..You can use variable also.
hope this helps ..
Regards,
shikha

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.

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.

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

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

HOW TO USE FUNCTION Deletion of Requests from the Change Log IN PRCSES CHAN

Respected all
i used Deletion of Requests from PSA from the prcess chain and found good results, now i have only one request at the psa and thus i am doing good space utililisation. but when i am using Deletion of Requests from the Change Log i am not getting any changes in the request of dso. kindly let me know how to use this 2nd function.
thanks
abhay

Hi Mahodaya,
As per SAp standards its good to delete the requestes that are no longer needed for the delta update and no longer used ffor inti from the change log table and the data is loaded already in to DSO.
Goto RSPC
Click on create New PC -> enter the PC name n long descp
Next we need to define the start process for the PC.Maintain the start variant process.save n come back.
for deletion of change log we have option in the Other BW Processes -> deletion of requestes from change log
Once u select the option we get a dialoge box here we need to create the variant for the process enter the process variant n long descp. cick ok.
Next in the maintenance screen for the deleting the request from change log table will appear.
Enter the selection patterns to which the requestes should be deleted from the change log.
In the maintenance screen, select one or more Data Store objects for which requests are to be deleted from the relevant change log tables under Data Store Object column and select theInfo Area of the corresponding Data Store Objects under Info Area
If you select the first check box exclude selction pattern, this means that del of requests from change log table will be ignored.
or
We can delete the requests which are Older than N-number of days (or) date in the above screen. For this one, enter the number of days (or) date in the filed Older than .
OR
If we want to select the requests with a certain status then we can also do in the above screen. We can select the following status indicators from the above screen.
Delete Successfully Updated Requests Only -This status will delete only requests which
are successfully updated into corresponding Data Store objects.
Delete Incorrect Requests that were not Updated - This status will delete only incorrect requests which are not successfully updated into the corresponding Data Store Objects.
Delete Activation Requests only, No Load requests- This status will delete only the activation requests (requests that begin with ODSR_... ). No load requests are deleted.

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

"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

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

Hi guys,
In my Process chain, after a daily full load delete overlapping requests (as part of pc) is setup. How do I identify if something was deleted. The Data Target is a Infocube.

zsl05,
There are two ways you can do the delete overlapping request.
1. In the info package, under the Data Targets tab, the sixth colum if you clcik that push button against the info provider, you will see a pop up saying ''Deleting request from infocube and you can set different options here like simillar info source, data source etc' also you can set 'Do Not delete Requests'. If manual update was done, unless you have selected 'Delete Existing Requests' and condition it cannot have deleted. IT IS ONLY FOR MANUAL LOADS.
2. When you execute thru process chain even if you use the same info package with all this options it won't delete unless you attached the process type 'Delete Overlapping Request' and the info package technical name. If you have not done these setup , you can be sure the data is not deleted, worse yet if you have rolled up as part of your process chain with out this it would have rolled up, you have to fix it by selective deleteion, and more work.
3. If you have done all correctly, the request would have gone, and if it is the only request you would see only one active request with Green under requests all the deleted identical request will be under 'Reconstruction' Tab.
I hope you have done everything right and just need to be sure of it.
Hope this helps, award points if useful.
Goodluck,
Alex (Arthur Samson)

Delete overlapping request when month changes

Similar Messages

Maybe you are looking for