Process Chain - Unable to delete overlapping request

Hi Gurus
I'm in the mid of creating process chain to load transaction data  in which I need to delete the previous load that loaded in using the same DTP previously
In the process chain , i have included a process "Delete Overlapping Request from Infocube" . Once i'm in the screen of maintain variant for this process, i selected DTP as the object type but unable to find the DTP that i have created under the object name.
Can someone point out what is missing
Thank you

Hi,
Looks like you need to give the the techincal name of the DTP. if you are un able to find the technical name of the DTP you can find that in the transport organizer.
just drag and drop the infoprovider ( with dataflow before) you will ge the DTP as required.
note the technical name of the DTP .
include the technical name in the process and activate the process.
Santosh

Similar Messages

  • Process chain is not deleting overlapping requests

    Hi all,
    I did all the steps like I described on my earlier posts to delete the overlapping request from infopackage through process chain.  I tested it in development and it works fine with any condition, I mean automation through event, date and after seven days.  When it comes to production it is not giving me the same result. So when I checked the infopackage of production I saw a routine added in the data selection of infopackage to load two days old data in the routine.  We do not have that added in the development.  Now if this is causing issue, can I add a step in the routine to delete previous request after loading file in the data selection. 
    Code:
    data: l_idx like sy-tabix.
      read table l_t_range with key
           fieldname = 'calday'.
      l_idx = sy-tabix.
    zdate = sy-datum - 2.
      l_t_range-low = zdate.
      l_t_range-sign = 'I'.
      l_t_range-option = 'EQ'.
    modify l_t_range index l_idx.
      p_subrc = 0.
    Please help,
    Suni.
    Edited by: BW on Feb 18, 2009 8:18 PM

    Hi aanjaneya,
    If you want to select and delete only the previous request of previous day, go to the infopackage and in data target tab there is option for each data target for setting the automatic deletion.
    If you select it, you will get a window which has the option to delete the request. Select all the conditions and same or more comprehensive check box and also check the  request date to yesterday and today option.
    This will delete the request loaded yesterday and also with same selection from same source.
    Hope this is clear.
    Regards
    Akhan

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

  • 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 ods’s 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 from info cube

    Hello
    I am getting a issue sometimes where the process chain fails to delete a request from the cube on the conditions i have given in this process type. Now i have been digging into this but cannot find much of why would this happen.
    Please can someone tell me if this is a known issue to you. Also please can someone give me some details on which program name gets generated when we pull this process type in a  process chain. what i mean is what is the program running for this process chain as i want to debug and see how does this process type delete the request.
    thanks

    check the class CL_RSSM_REQUDEL and method IF_RSPC_EXECUTE~EXECUTE

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

  • Process type "Delete overlapping request in cube " in process chain

    Hi
    can somebody suggest me where i need to place the process type "Delete overlapping request" for an infocube.
    Regards,

    Hi,
    When you use the corresponding process in the process
    chain maintenance screens to specify the conditions for
    automatic deletion, these conditions are applied to all
    the InfoCubes for the selected InfoPackages
    Overlapping: If you set this indicator, existing requests are also
    delete from the InfoCube if the selection criteria of the new request partially or wholly overlap the selection criteria of the request to be deleted
    Same or Comprehensive: If you set this indicator,
    requests are only deleted from the InfoCube if
    the selection conditions of the new request are
    the same as or more comprehensive than the selection
    conditions of the request to be deleted.
    Thanks
    Bhagesh

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

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

  • Process Maintenance: Delete Overlapping Requests from InfoCube

    Hi Experts,
    How can I open Process Maintenance: Delete Overlapping Requests from InfoCube Screen? What's T-code? Is that in Process Chain? Please tell me that....
    Thanks in advance,

    Hi
    'Delete overlapping request' is an option(its a process type) in the process chains..
    RSPC>Process types>Load Process and post process folder--->Delete overlapping request from the infocube..
    here you can have more options like 'source systems are same',and infosources are same etc...
    How to delete most recent request in a Cube by using process chain
    Hope it helps
    Thanks,
    Teja
    Edited by: Teja badugu on Apr 28, 2008 11:35 AM

  • 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

  • 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

  • Unable delete overlap request

    Hi
    I created pc like
    start
    load infopackage
    execute dtp
    delete overlap request
    but i am ruiing pc i am getting all request, its not deleting old request. i am riunning full every day
    ple let me know

    Hi
    I have 2 scenerios
    first scenerio.
    i am getting full load only 1 datasource in to 1 cube
    so i created pc
    start- delete psa request-load to psa-execute dtp-deleet content of cube
    2nd scenerio is
    i am getting 1 full load daatsource every day full, another is delta (every day)
    start- delete psa request-load to psa-execute dtp-delet overlap request
    ple give me any modifications  from ur end

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

Maybe you are looking for