Delete Overlapping Requests - by Filename via ABAP Routine

Hi SDN Community
Do you know if it is possible to set the delete overlapping request parameters to recoginse the file name, and remove it via the derivation of the file name via an ABAP Routine.
I am using an ABAP routine to derive the flat flat file upon loading, but do not know the syntax, or if it is possible to set this equivalent code into the delete overlapping request Routine area
(The code basically derives the first day of the calendar week, for previous weeks in the Do n times Loop
Thank you.
Simon
DATA: ld_CWEEK         TYPE scal-week,
      ld_DATE          TYPE SY-DATUM,
      ld_DATE1         TYPE SY-DATUM,
      lc_DIRECTORY(30) TYPE c,
      ln_YYYY(4)       TYPE n,
      ln_WW(2)         TYPE n.
*Derive week from sy-datum
ld_date = SY-DATUM.
Determine the calendar week from the entered calendar date
CALL FUNCTION 'DATE_GET_WEEK'
    EXPORTING
      date           = ld_date
    IMPORTING
      week          = ld_cweek
    EXCEPTIONS
      date_invalid = 1
      OTHERS        = 2.
Get the First day of the week
        CALL FUNCTION 'WEEK_GET_FIRST_DAY'
          EXPORTING
            week         = ld_CWEEK
          IMPORTING
            date         = ld_DATE1
          EXCEPTIONS
            week_invalid = 1
            OTHERS       = 2.
Need to find the previous calendar week and reconvert to the first
day in order to accomodate weeks less than 7 days
Get the last day of the current calendar week - 2
    DO 2 TIMES.
        ld_DATE1 = ld_DATE1 - 1.
Determine the calendar week from the last day of the previous week
        CALL FUNCTION 'DATE_GET_WEEK'
          EXPORTING
            date         = ld_DATE1
          IMPORTING
            week         = ld_CWEEK
          EXCEPTIONS
            date_invalid = 1
            OTHERS       = 2.
Get the First day of the week
          CALL FUNCTION 'WEEK_GET_FIRST_DAY'
            EXPORTING
              week         = ld_CWEEK
            IMPORTING
              date         = ld_DATE1
            EXCEPTIONS
              week_invalid = 1
              OTHERS       = 2.
    ENDDO.
*ln_YYYY = ld_CWEEK(4).
ln_YYYY = ld_DATE1(4).
ln_WW = ld_CWEEK+4(2).
*DIRECTORY represnts path where file is stored .
lc_DIRECTORY = '/interfaces/EDW/data/CSM/'.
CONCATENATE lc_DIRECTORY
ld_date '_WEEK' ln_WW '_c1_pri_' ln_YYYY '.csv' into p_filename.
'MIC_NT_' ld_date1 '_' ln_YYYY '.csv' into p_filename.

Thank you for your response Debanshu
However, i could not find this process type in the process chain area.
Is this where you meant, can you please give me more detailed steps including long syntax of names of process types
We are on BW 3.50
i assumed the filename had to be constructed via abap according to some of the sdn replies i've searched through.
Thank you.
Simon

Similar Messages

Delete overlapping requests from ODS

Hi,
Since it iss not possible to delete overlapping requests from an ods by any automated process like in info cube.
Can we still delete overlapping request using abap code or the only way to do it is to delete data (selective deletion) in a start routine.
Any tips would be helpful

Hi ,
Try the following logic to delete the ovelapping requests from a particular data source.
*& Report ZV_DELETE_REQS *
*&Description:This program is for deletion of eixsting Full requests *
*& from ODS *
REPORT ZV_DELETE_REQS.
data: RSICCONT like rsiccont,
 rsseldone like rsseldone.
data: begin of i_req occurs 0,
 rnr like RSICCONT-rnr,
 end of i_req.
refresh i_req.
select * from RSICCONT UP TO 2 ROWS
 where ICUBE = 'ZCS_D10'
 order by TIMESTAMP descending.
i_req-rnr = rsiccont-rnr .
append i_req.
clear i_req.
endselect.
loop at i_req.
select single * from RSSELDONE where RNR eq i_req-rnr and
 source in ('0CO_OM_OPA_5',
 '0CS_OM_OPA_1').
if sy-subrc eq 0.
 CALL FUNCTION 'RSSM_DELETE_REQUEST'
 EXPORTING
 REQUEST = i_req-rnr
 INFOCUBE = 'ZCS_D10'
 EXCEPTIONS
 REQUEST_NOT_IN_CUBE = 1
 INFOCUBE_NOT_FOUND = 2
 REQUEST_ALREADY_AGGREGATED = 3
 REQUEST_ALREADY_COMDENSED = 4
 NO_ENQUEUE_POSSIBLE = 5
 OTHERS = 6.
 IF SY-SUBRC <> 0.
 MESSAGE ID sy-MSGID TYPE 'I' NUMBER sy-MSGNO
 WITH sy-MSGV1 sy-MSGV2 sy-MSGV3 sy-MSGV4.
 else.
 message i799(rsm1) with i_req-rnr 'deleted'.
 ENDIF.
 do.
 select single * from RSICCONT where ICUBE = 'ZCS_D10'
 and rnr = i_req-rnr.
 if sy-subrc ne 0.
 exit.
 endif.
 enddo.
endif.
endloop.
hope it helps....
regards,
raju

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.

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

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,

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 request in DTP

Hi,
Is there an option to set "Delete overlapping request" in DTP?.

Helllo,
There is no direct option in DTP to do so, but u can do it via process chain.
You need to have your DTP set to full update in order to make use of it in delete overlapping request process type.
Regards,
Shashank

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

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

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,

Delete Overlapping Requests - by Filename via ABAP Routine

Similar Messages

Maybe you are looking for