Unable to delete a request from a Cube which is loaded by Open hub to flat

Hi,
We have one Cube from which we are transferring data to a flat file by open hub.
the DTP for the OPEN HUB is delta DTP.
Now when i am trying to delete a request from Cube its not allowing me.
Its giving error as request is already updated to the target so delete the request from target first.
I tried deleting the open hub request entry from RSBKREQUEST table.
but still its not deleting the request from the Cube.
Can you please help me in solving this problem.
Thanks in Advance,

I think request is having datamart, which is not allowing it to delete.
You can try to reset (delete) the datamart by clicking on it in cube request and then try to delete.
Or if it does not work, you can delete it from RSICCONT table, which will delete the request from cube also.

Similar Messages

BW: Error during Delete Overalpping requests from a cube 0PCA_C01

Hello Experts
For the past 1 week, I am getting the following error in a process chain when trying to do Delete Overlapping requests from a cube.
The error I am getting is:
The chain failed while deleting the overlapping requests from 0PCA_C01 with an error messages "Error when deleting requests for comparison request" & "Deletion of request REQU_DBC7DZ51QY from data target 0PCA_C01 failed"
CL_RSDRD_REQ_PHYS_DEL:REQUEST_DELETE RSDU_FACT_REQUID_DELETE SQL-ERROR: 0
reqdel_infocube_with_aggr-0PCA_C01 CL_RSDRD_REQ_PHYS_DEL:REQUEST_DELETE RSDU_FACT_REQUID_DELETE
Deletion of request REQU_DBCFVY9N1691OYQYNCMUGCSGM(290265) from InfoCube 0PCA_C01 terminated
Error deleting request REQU_DBCFVY9N1691OYQYNCMUGCSGM from InfoCube 0PCA_C01. Exception: Unknown error
Any suggestions on how to fix this problem permanently..i mean any SAP Note to be applied or any adjusting the database tables?
Thanks
Jyothi

Hi Jyothi,
This error usually comes because of presence of zombie ./ bad request. I would suggest you to check few of the tables and search for your request "REQU_DBCFVY9N1691OYQYNCMUGCSGM" in them if you are able to find it then delete that entry from there, there after you should not face error. Check if the request mentioned above is present in the below mentioned tables? If yes delete them from there.
RSREQICODS, RSTSODS, , RSICCONT, RSODSACTREQ.
Also check if the notes mentioned in the below thread are applicable in your case?
Error when deleting requests in cube
Thanks

BW: Error during Delete Overalpping requests from a cube

Hello, I am getting the following error in a process chain for the last few days when trying to do Delete Overlapping requests from a cube. If I do a "repeat" the chain completes successfully.
The error I am getting is:
Error when deleting requests for comparison request REQU_4MNC5NXH00MJI1LRHAFV3I3BH
Deletion of request REQU_4MQ0NT0ISDRZA444OQRDBGC3X from data target ZZCCA_C11 failed
Any suggestions on how to fix this problem?
Thanks.

Hi Sam,
The job might be failing because the request might me compressed. Take the request id from the error message(for instance
REQU_4MQ0NT0ISDRZA444OQRDBGC3X here) and check whether this request is compressed in the target ZZCCA_C11 or not.
If it is compressed then the data target deletion step will fail obviously.
If this is the case then change the setting of the compression step in the PC to compress the requests loaded 15 days back or whichever you feel comfortable.
If this is not the case then please check the job log once why the deletion is failing.
Hope this helps.
Regards,
Vijay.

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

Deleting a request from a cube

Hi Experts
I deleted few(old) requests from a cube in quality server. They got deleted, after some time i checked back. Those request are appeared in the request tab with a tick mark under compression status in InfoCube. I am confused !!!
Can any you clear my doubt...
Thanks
Pavan

Hi RMK,
is it the same ID-Pavan used by you above??anyways...
I guess we are dealing here with two scenarios..
1)If it was Infocube than the solution above i suggested holds true
2)Ifs its ODS ,the physical requests are still there because you deleted the CHANGE LOG data for those requests...so now there is no WAY you can delete those request PHYSICALLY !!!
Please check to verify/confirm the same..
the only way to get rid of those contents is through the SELECTIVE DELETE for those request ..
However;even after selective delete those request would appear physically in the manage TAB of the ODS ..but if you go to the ACTIVE table content for that ODS ,the data wont be there ,its deleted.so you can reconcile the reports now.
Hope it Helps
Chetan
@CP..

Delete data from Cube which is uploaded to Open hub

Hello Friends I am required to delete the data from GL Cube, But it is connected to 2 Open Hub
which has one as table /BIC/OHZZIGL_C10 defined in Open hub destination. I deleted the data from this table in SE14, but still when I try to delete the data from cube it throws the below error
Please help me how to now delete the data from cube, when should i go in open hub t delete all the uploaded requests.
Request 1.882 already updated in target 3.913 by DTP request DTPR_4CU6JHRJ7MY889A7XBUJ0GDVK(ZZIGL_C10)
Thanks
soniya

just check on your datamart status for that request. Go to the manage screen of your infocube and check where all that request got updated using datamart status.

Unable to delete the request from ODS

Hi All,
I have loaded a request to ODS from flat file and the load got success, the request is activated and is available for reporting. Now the problem is i want to delete the request, but the request is not deleting.
I tried to delete the request by going in to the cube manage and changed the QM status and the technical status to red and delete, but it is not deleted.
Thanks in advance for your reply

Hi Prem,
If the ods has datamart status & has been used to load data to a cube, then u cant delete the ods request. In this case, first, change the QM status of the request in the cube to red (delete) & then it wud be possible to go with the deletion of ods request.
Also check this thread as well
Request unable to delete from ODS.
Regards,
R.Ravi

Unable to Delete failed requests from Infocube

Dear Experts,
I tried to uploaded the data through flat file. Since it has gone to Idle state i Killed the process. Now i Need to delete the red request from Infocube but It is not allowing me to delete the failed request. If I do so, I am getting ABAP runtime error.
Please Suggest me . Its bit Urgent
Many Thanks,
Suraj

Hi Suraj,
There is might be a deadlock detected in the system
So go the reqeust
click on the details tab
Each Package which is yellow or red has to be updated manually (right click Manual Update). This can take few minutes.
Change request status to green
Change to Status doppleclick on total status
Change from red to Delete status;back to request status
Note:
This case is only applicable, if the data are stored in PSA.

Use transaction FILE to store data from a cube into a file with Open Hub

Hi people:
I'm using BI 7.0 .Mi requirement is to make a flat file using the information of a virtual cube. The file name must have the number of the month and the year. I know that this is possible through FILE transaction.
Can anybody give me a clue how this transaction is used?Which are the steps in order to assemble the name of the file? Or is there any other option? I have defined the physical directory where the file must be leaved
Any help will be great. Thanks in advanced

Hi,
pick up the code which you need from below.
REPORT RSAN_WB_ROUTINE_TEMP_REPORT .
TYPES: BEGIN OF y_source_fields ,
         /BIC/ZTO_ROUTE TYPE /BIC/OIZTO_ROUTE ,
         ZINT_HU__Z_WM_HU TYPE /BIC/OIZ_WM_HU ,
         CREATEDON TYPE /BI0/OICREATEDON ,
         ROUTE TYPE /BI0/OIROUTE ,
         PLANT TYPE /BI0/OIPLANT ,
         PLANT__0STREET TYPE /BI0/OISTREET ,
         PLANT__0CITY TYPE /BI0/OICITY ,
         PLANT__0REGION TYPE /BI0/OIREGION ,
         PLANT__0POSTAL_CD TYPE /BI0/OIPOSTAL_CD ,
         /BIC/ZRECVPLNT TYPE /BIC/OIZRECVPLNT ,
         ZRECVPLNT__0STREET TYPE /BI0/OISTREET ,
         ZRECVPLNT__0CITY TYPE /BI0/OICITY ,
         ZRECVPLNT__0REGION TYPE /BI0/OIREGION ,
         ZRECVPLNT__0POSTAL_CD TYPE /BI0/OIPOSTAL_CD ,
         KYF_0001 TYPE /BI0/OIDLV_QTY ,
         ROUTE__Z_CR_DOCK TYPE /BIC/OIZ_CR_DOCK ,
         REFER_DOC TYPE /BI0/OIREFER_DOC ,
       END OF y_source_fields .
TYPES: yt_source_fields TYPE STANDARD TABLE OF y_source_fields .
TYPES: BEGIN OF y_target_fields ,
         RECORDTYPE TYPE /BI0/OISTREET ,
         CONTAINER TYPE /BI0/OICITY ,
         /BIC/ZTO_ROUTE TYPE /BIC/OIZTO_ROUTE ,
         TRACKINGNUMBER TYPE /BIC/OIZ_WM_HU ,
         PO TYPE /BI0/OICITY ,
         STAGEDDATE TYPE /BI0/OICITY ,
         MOVEMENTTYPE TYPE /BI0/OICITY ,
         ROUTE TYPE /BI0/OIROUTE ,
         PLANT TYPE /BI0/OIPLANT ,
         PLANT__0STREET TYPE /BI0/OISTREET ,
         PLANT__0CITY TYPE /BI0/OICITY ,
         PLANT__0REGION TYPE /BI0/OIREGION ,
         PLANT__0POSTAL_CD TYPE /BI0/OIPOSTAL_CD ,
         ORIGINCONTACTNAME TYPE /BI0/OISTREET ,
         ORIGINCONTACTPHONE TYPE /BI0/OISTREET ,
         /BIC/ZRECVPLNT TYPE /BIC/OIZRECVPLNT ,
         ZRECVPLNT__0STREET TYPE /BI0/OISTREET ,
         ZRECVPLNT__0CITY TYPE /BI0/OISTREET ,
         ZRECVPLNT__0REGION TYPE /BI0/OISTREET ,
         ZRECVPLNT__0POSTAL_CD TYPE /BI0/OISTREET ,
         DESTINATIONCONTACTNAME TYPE /BI0/OISTREET ,
         DESTINATIONCONTACTPHONE TYPE /BI0/OISTREET ,
         RCCCODE TYPE /BI0/OISTREET ,
         GLCORCLLICODE TYPE /BI0/OISTREET ,
         JFCCODE TYPE /BI0/OISTREET ,
         DESCRIPTIONOFWORK1 TYPE /BI0/OISTREET ,
         DESCRIPTIONOFWORK2 TYPE /BI0/OISTREET ,
         INSTRUCTIONS TYPE /BI0/OISTREET ,
         REQUESTEDSHIPDATE TYPE /BI0/OICITY ,
         ROUTE__Z_CR_DOCK TYPE /BIC/OIZ_CR_DOCK ,
         REQUESTEDDELIVERYDATE TYPE /BI0/OICITY ,
         ATTSEORDER TYPE /BI0/OICITY ,
         CUBE TYPE /BI0/OISTREET ,
         WEIGHT TYPE /BI0/OISTREET ,
         PIECES TYPE /BI0/OIREFER_DOC ,
         REEL TYPE /BI0/OISTREET ,
         REELSIZE TYPE /BI0/OISTREET ,
         VENDORSKU TYPE /BI0/OISTREET ,
         ATTSESKU TYPE /BI0/OISTREET ,
         COMPANYNAME TYPE /BI0/OISTREET ,
         OEM TYPE /BI0/OISTREET ,
         REFER_DOC TYPE /BI0/OIREFER_DOC ,
         REFERENCENUMBER2 TYPE /BI0/OISTREET ,
         REFERENCENUMBER3 TYPE /BI0/OISTREET ,
         REFERENCENUMBER4 TYPE /BI0/OISTREET ,
       END OF y_target_fields .
TYPES: yt_target_fields TYPE STANDARD TABLE OF y_target_fields .
Begin of type definitions -
*TYPES: ...
End of type definitions -
FORM compute_data_transformation
     USING     it_source TYPE yt_source_fields
               ir_context TYPE REF TO if_rsan_rt_routine_context
     EXPORTING et_target TYPE yt_target_fields .
Begin of transformation code -
DATA: ls_source TYPE y_source_fields,
        ls_target TYPE y_target_fields,
        var1(10),
        var2(10),
        year(4),
        month(2),
        day(2),
        date(10),
        it_workdays type table of /bic/pzworkdays,
        wa_workdays type /bic/pzworkdays,
        sto_date(10),
        V_tabix TYPE sy-tabix,
        Y_tabix TYPE sy-tabix,
        sto_var1(10),
        sto_year(4),
        sto_month(2),
        sto_day(2),
        sto_final_date(10),
        W_HEADER LIKE LS_TARGET-RECORDTYPE,
        W_HEADER1(12) TYPE C VALUE 'HEDR00000000',
        W_FOOTER LIKE W_HEADER VALUE 'TRLR0000',
        CNT(5),
        CMD(125) TYPE C.
**********CODE FOR GENRATING CSV FILE PATH*******************
data: OUTFILE_NAME(100) TYPE C,
      OUTFILE_NAME1(10) TYPE C VALUE '/sapmnt/',
      OUTFILE_NAME3(18) TYPE C VALUE '/qoutsap/ATTUVS',
      DATE1 LIKE SY-DATUM,
      DD(2) TYPE C,
      MM(2) TYPE C,
      YYYY(4) TYPE C.
MOVE SY-DATUM+6(2) TO DD.
MOVE SY-DATUM+4(2) TO MM.
MOVE SY-DATUM(4) TO YYYY.
CONCATENATE YYYY MM DD INTO DATE1.
CONCATENATE OUTFILE_NAME1 SY-SYSID OUTFILE_NAME3 '.CSV' INTO
OUTFILE_NAME.
**********END OF CODE FOR GENRATING CSV FILE PATH*************
OPEN DATASET OUTFILE_NAME FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
Code for generating Header.
CONCATENATE W_HEADER1 SY-DATUM SY-UZEIT INTO W_HEADER.
APPEND W_HEADER TO ET_TARGET.
TRANSFER W_HEADER TO OUTFILE_NAME.
CLEAR W_HEADER.
End of code for generating Header.
code for excluding the rows who's Quantity(PIECES) equal to zero.
LOOP AT it_source INTO ls_source where KYF_0001 NE '0'.
end of code for excluding the rows who's Quantity(PIECES) equal to
*zero
    MOVE-CORRESPONDING ls_source TO ls_target.
    ls_target-RECORDTYPE = 'PKUP'.
    ls_target-CONTAINER = ''.
    ls_target-TRACKINGNUMBER = ls_source-ZINT_HU__Z_WM_HU.
    ls_target-PO = ''.
Date Conversion for Staged Date.
    var1 = ls_source-CREATEDON.
    year = var1+0(4).
    month = var1+4(2).
    day = var1+6(2).
    CONCATENATE month '/' day '/' year INTO date.
End of Date Conversion for Staged Date.
    ls_target-STAGEDDATE = date.
    ls_target-MOVEMENTTYPE = 'P'.
    ls_target-ORIGINCONTACTNAME = ''.
    ls_target-ORIGINCONTACTPHONE = ''.
    ls_target-DESTINATIONCONTACTNAME = ''.
    ls_target-DESTINATIONCONTACTPHONE = ''.
    ls_target-RCCCODE = ''.
    ls_target-GLCORCLLICODE = ''.
    ls_target-JFCCODE = ''.
    ls_target-DESCRIPTIONOFWORK1 = ''.
    ls_target-DESCRIPTIONOFWORK2 = ''.
    ls_target-INSTRUCTIONS = ''.
    ls_target-REQUESTEDSHIPDATE = date.
Calculating STO Creation Date + 3 working Days.
    select /BIC/ZWORKDAYS from /bic/pzworkdays into table it_workdays.
    loop at it_workdays into wa_workdays.
        if wa_workdays-/bic/zworkdays = ls_source-CREATEDON.
            V_tabix = sy-tabix.
            Y_tabix = V_tabix + 3.
        endif.
        If sy-tabix = y_tabix.
            sto_date = wa_workdays-/bic/zworkdays.
        endif.
    Endloop.
    clear v_tabix.
    clear Y_tabix.
    sto_var1 = sto_date.
    sto_year = sto_var1+0(4).
    sto_month = sto_var1+4(2).
    sto_day = sto_var1+6(2).
    CONCATENATE sto_month '/' sto_day '/' sto_year INTO sto_final_date.
End Of Calculating STO Creation Date + 3 working Days.
    ls_target-REQUESTEDDELIVERYDATE = sto_final_date.
    ls_target-ATTSEORDER = ''.
    ls_target-CUBE = ''.
    ls_target-PIECES = ls_source-KYF_0001.
    ls_target-REEL = ''.
    ls_target-REELSIZE = ''.
    ls_target-VENDORSKU = ''.
    ls_target-ATTSESKU = ''.
    ls_target-COMPANYNAME = 'AT&T'.
    ls_target-OEM = ''.
    ls_target-REFERENCENUMBER2 = '0'.
    ls_target-REFERENCENUMBER3 = '0'.
    ls_target-REFERENCENUMBER4 = '0'.
    APPEND ls_target TO et_target.
    TRANSFER ls_target TO OUTFILE_NAME.
    CNT = CNT + 1.
ENDLOOP.
    CNT = CNT + 2.
Code for generating Header -Footer.
SHIFT CNT LEFT DELETING LEADING SPACE.
CONCATENATE W_FOOTER CNT INTO W_HEADER.
APPEND W_HEADER TO ET_TARGET.
End of code for generating Header -Footer.
Code for file permissions
TRANSFER W_HEADER TO OUTFILE_NAME.
CLOSE DATASET OUTFILE_NAME.
CONCATENATE 'chmod 644' OUTFILE_NAME INTO CMD SEPARATED BY SPACE.
CALL 'SYSTEM' ID 'COMMAND' FIELD CMD.
End of code for file permissions
End of transformation code -
ENDFORM.
Hope it helps
bhaskar

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 Full Requests from an InfoCube with a BIA index on it

Hello all
I need to delete certain random Full requests from a cube which has both DB indexd and BIA index on it?
What will be the steps i should be following in regards to deleting/ rebuilding indexes ?
Regards
Sanjyot

Thanks Vitaliy but I have multiple requests with huge amount of data to be deleted.
So I was wondering if the following steps are correct
1. delete DB indices
2. delete BIA indices
3. delete requests from cube
4. rebuild DB indices
5. rebuild BIA indices
Are there any steps to ensure that indices are rebuilt correctly?
Regards
Sanjyot

Unable to delete the Requests in the data target---Process chain

Hello Gurus!
Can anyone plz help me out knowing this issue...
<b>Let me explain the whole scenario:</b>
Like when monitoring the process chains,one of the process chainhas a sequence of variants like:
load info-package1>ODS1 activation>load infopackage2-->load infopackage3..
due to some problems they scheduing it manually.all the infopackages loads data into one ODS1......suddenly info-package3 failed.
so....when i looked into the datatarget ODS1->manage->requests.
<b>i found that the info-pack1 requests status was RED.
info-pack2 requests status was YELLOW.
info-pack3 requests status was RED</b>.
ALL THE THREE R FULL UPDATES ONLY.
so suddenly one of our cologue deleted the all the three requests by making ino-pack2 requests to red.
when we r loading again the ino-pack1 again its failed.we deleted it onceagain(removing the requests from the ods),when we are trying to load ino-pack2 for some priority ,automatically the info-pack1 requests with red were seemed in the ODS.so how to solve this issue and also how to load these three ino-packs..
i hope that all understand the scenario..plz suggest me how to work on it
Thanks in advance!!!
Dilip

Hi,
Your loads are running on back ground you have to kill this porcess in SM50 or SM51 check which are all jobs are running with your user name and ALEREMOTE if jobs are running with ALEREMOTE you can check wether it is your load or some body else in SM37 so kill your jobs in SM50 or in SM51 and make request into RED of your 3 loads, delete the requests from ODS and repeat the loads it will go with out any issues, as i under stood your question when your colegue deleted the request without killing the process he simply made it to red and delete its wrong he has to kill the process and then make it to red.
Regards
Sankar

Program to delete a specific request from a Cube

Hi Everyone,
I've been trying to delete a certain DTP request from a cube but I'm unable to delete it. Is there any ABAP program to delete a specific request from a cube by provinfing requeset ID as the input.
Thanks,
Ram

HI
SE37RSSM_DELETE_REQUESTGIVE YOUR REQUEST NO & INFOCUBE NAME here. and execute.
Table is :RSBKDTP contains DTP and target details.
Hope it helps

Process Type - Delete overlapping requests from an Info Cube

I have read many threads on this topic, still have some questions. To give you background, I will be doing delta load (delta process chain). But before delta, I want to do setup initialization (init process chain). I want to use this process type in my init process chain to delete all data in my cube loaded from a specific ods. I cannot use delete all contents process type because many odss feed the same cube.
1.     Do you put this process type after Load Data or before Load Data. I have seen both cases in SDN forums.
2.     Variant of this process type is an info package. Does this info package have to be same as in load data step or it can be different.
3.     I want to delete all data in cube which was loaded from my ods. Term overlapping is confusing to me. Will this process type delete all data or not.
Tanks in advance.

Yes, you can do that. Goto RSPC - under process types Load Process and Post Processing, you will see DELETE OVERLAP REQUESTS FROM INFOCUBE option is there.
Select the proper check boxes like same sourcesystem, same datasource etc...
If it is one time deletion, why not do that manually?
Also check: How to delete most recent request in a Cube by using process chain
Hope it helps..

Problem while deleting overlaping request from cube

Hi experts,
I have one process chain in which i have one step where i am executing one DTP to load one cube and in next step deleing overlapping requests from same cube.
i am getting error at that step "Error when deleting requests for comparison request DTPR_4CCDXZLK1OIGCVGGE1PP31Z3Y"
what could be reason?
plz help

Hello,
I guess you have not defined the overlapping variant properly.
Please goto the definition of the variant and check for the right DTP input.
Then at the bottom, select second option "Edit all Infocubes with Following Delete Selections"
Click on deletion selections -> select delete existing requests.
Also select if same datasource and source system. and importantly select the radio button as overlapping.
Then save the variant. and try to use it.
Regards,
Shashank

Unable to delete a request from a Cube which is loaded by Open hub to flat

Similar Messages

Maybe you are looking for