Request Deletion from Cube stuck in execeptional state

Hi All,
We are stuck with a strange situation caused by below steps.
1. We loaded a full request in cube
2. Next day we scheduled deletion of the request from cube
3. While deletion was in progress, we deletd the DTP through which the request was loaded
4. DTP was deleted. Now this request stuck with status 9 (deletion started) in RSBKREQUEST table.
5. If we check the request ID it shows deleted but we can see the request still in cube
6. Compression of newer requests is not happening as they are referrins issue with this stuck request
Now I am looking for below help
1. How can we delete the request from cube now
2. Is there any way to create the DTP with old technical name
3. Can we compress the request with this request in cube
Regards
Jitendra

Hi Jitendra,
1. How can we delete the request from cube now
As suggested by raman change it to red and then try deleting.Check the backend tables also system is saying its deleted then tables should not have entries for this request.
2. Is there any way to create the DTP with old technical name
I think DTP technical name is decided by system so we can not not create tech names for DTP.
3. Can we compress the request with this request in cube
Current status of you request is not green so we can not compare it.so delete it first.
Regards,
Ganesh Bothe

Similar Messages

Delete from two tables in one statement

Hi,
Is there a way to delete from two tables in one statement?
Actually I have two tables:
1. Base table (id, name, age)
2. Person table (id, city, street)
The id in both tables is identical.
I would like to delete using something like a join:
Delete from base, person where id=2;
Thanks
dyahav

Hi,
If you want to delete records both at a time them your table must use ON DELETE CASCADE. See the below example.
CREATE TABLE supplier
( supplier_id numeric(10) not null,
supplier_name varchar2(50) not null,
contact_name varchar2(50),
CONSTRAINT supplier_pk PRIMARY KEY (supplier_id)
CREATE TABLE products
( product_id numeric(10) not null,
supplier_id numeric(10) not null,
CONSTRAINT fk_supplier
FOREIGN KEY (supplier_id)
REFERENCES supplier(supplier_id)
ON DELETE CASCADE
In this example, we've created a primary key on the supplier table called supplier_pk. It consists of only one field - the supplier_id field. Then we've created a foreign key called fk_supplier on the products table that references the supplier table based on the supplier_id field.
Because of the cascade delete, when a record in the supplier table is deleted, all records in the products table will also be deleted that have the same supplier_id value.
Thank you.

Request Deletion from Write-optimized DSO

Hello,
With the new Write-optimized technology, it is possible to delete manually "older" requests from the W-O DSO.
Could anyone of you think of an automated process to delete "old" requests from a W-O DSO (not the entire content , the most recent should still be available.
For instance : delete everyday the request older than 7 days.
Already checked solutions :
- Selective deletion at the administration level of the DSO -> cannot be repeatedly scheduled
- Copying the Selective Deletion generated program to make one's own program and schedule it (system cannot "remember" the generated program)
- Diverse SAP Function Module -> do not work for this scenario (like RSSM_DELETE_REQUEST, only for cubes, RSSM_PROCESS_REQUDEL_ODSO or    RSSM_DELETE_REQUEST, where you need to specify the Request number
- We do not want to include a delete job in a routine at the Transformation level.
- We do not want to complicate the Data Model by creating a new intermediate DSO allowing to flush the DSO at each load..
Any other ideas??
We are on Version 7.0, SP 13.
Many thanks!
amanda

Hi ,
We have worked on similar business requirement .We wrote a report program in SE38 and running it via a process chain .
If you want i can help you to write code for same .
It will be a two step process :
1.deleting request from RSICCONT so that it get deleted from manage tab.
2.deleting data from active table of that WDSO .
Code for Program :
data :v_time type c length 17,
          v_date like sy-datum .
( N) = 7 put no of days here before which you want to delete records
v_date = sy-datum.
subtract 7 from v_date.
concatenate v_date   sy-uzeit into v_time.
delete from rsiccont where icube = wdso_name and timestamp LT v_time .
delete from wdso_active_table_name where rstt_tsmp LT v_time.
It will do your work .
Regards ,
Jaya

Full request deletion from same datasource in different R/3 systems.

Hi,
I have a cube in which data is full loaded . I have a two R/3 Systems e.g. A and B. there is a standard datasource which is loading data as a full load. this same datasource is pulling data from these two R/3 Source system i.e. A and B. Now My problem is I want to remove earlier data from the same datasource from cube before new data arrives in the cube.
There are settings to be done at infopackage level, I want to know what setting shall I do so that only source system relevant data get deleted from the cube before new data with full load arrive in the cube.

Hello,
you need to check:
Datasources Are the same
Source Systems Are the same
Selections are same or more comprehensive
When you start the infopackage manually, it will ask you to confirm deletion of data packages.
BR
Ondrej

Change Request deleted from Buffer

Hello,
If a Change request is deleted from the buffer, before it is imported into the system.
Can we determine which user ID deleted the Change Request from the buffer?
Thanks,
Gautam.

Not sure ...if u can get this info directly....However have a look into the table E070USE...Might help!

Request Deletion in Cube

Hello Experts
I deleted a request in the cube (Manage) as there was error in loading data,I changed the status to red and deleted it and started a new one.The new request sucessfully loaded the data but the issue is the deleted request is still there with a 'Bin' picture in the request list and the sucessfully loaded request is not avaliable for reporting.
Thanks

Hi Krishna,
The deletion would be running in background. check in SM37, if there is active job running there for this cube. check the job log for more information.
even you can check in sm12 on your logon. if threre are any lock entries, then be patient till it get cleared. the process might be runnig. you will be getting the reporting symbol once it is deleted.
Hope it clears your doubt.
Points if helpful.
with regards,
sreekanth.

Request deletion from Manage-Master data infoobjects

Hi All,
I have a master data infoobject, for which i have created a process chain for deleting the data. I am deleting the P and S table in a program.
When i run this chain data is getting deleted from the tables, but i see the request (green/red/yellow) in the manage section of the infoobject. I want to delete those entries as well from the manage section.
Any inputs ?
Regards,
Sandeep

Hi,
to delete those entries you will have to delete the entries from standard SAP tables...all the tables begining with RSREQ stores the information about the requests...but you may not have authorization for that...
did you tried RSDMD_DEL_BACKGROUND or RSDMD_DEL_MASTER_DATA_TEXTS function modules....you can use in the program and use at as a ABAP variant in the process chain.
Thanks
Ajeet

Data to be deleted from cube conditionally

Hi,
We are facing a problem in maintaining data from ODS to CUBE. Actually some data is loaded in cube and agian the same set is to be rectified which needed delta. The DTP has been created as delta loading . but every time data is loaded the total data from ODS is loaded to CUBE. So we need that data set to be delted from a huge cube and needed fresh loading from ODS.
But from cube data can be deleted toatally. But here data is to be deleted with some keys i.e. conditionally.
Regards
Indranil

hi Indranil,
Apart from what my other Friends have suggested.
Try to delete the Data based on Date as far as possible.......And also laod based on date.
So that there is Stability of Data.
Rgds
SVU123

Selective Deletion From Cube and ODS using Process chain

Hi all,
is there any way that i can include selective deletion in a process chain, there is no stand process types for selective deletion, I need to delete the closed items from cube and ods and i need to schedule this??? any ideas?
Thanks,
Shetty.

Shetty,
You can delete Data from this using One custom Program. You need to use either RSDRD_SEL_DELETION(function module ) or RSDRD_BUILD_REPORT_FOR_BATCH(Function Module). there is a parameter in above functioen modules I_THX_SEL which needs to be populated using selections.
or
You need to schedule the Background job from Manage screen on Monthly Basis(Provided that selection should be fixed in every month).
I will update the thread with psudo code.
all the best.
Regards,
Nagesh Ganisetti.
Message was edited by:
Nagesh Ganisetti

Delete request Ids from Cube

Hello Experts,
We have 2 cubes (ZC_CB1, ZC_CB2). We are loading delta load to ZC_CB1. I need to move the specified period data from ZC_CB1 cube to ZC_CB2 cube and delete the specified period data from ZC_CB1 after finish the load. They don't want to use SELECTIVE DELETE to delete the data from ZC_CB1. Please let me know options to achieve the same.
Thank you
Regards,
Prasad

Selective deletion and deleting by request is the only way of deleting the data from the cube.
May I ask why they don't want to use a selective deletion?
You can also try to create a flatfile source system for this cube and load a reversal document to the cube.
thanks.
Wond

Compression request deletion in cube bi7

please guide me how to delete
Thanks

Read abt Selective deletion.
Re: what is the use of request reverse posting in rsmo?
Re: Selective deletion after compression
Re: Info Cube Compression
Re: how can we delete the request after compression? is it possible ?if so how?
http://help.sap.com/saphelp_nw04/helpdata/en/ca/5c7b3cbd556915e10000000a114084/frameset.htm

Delta Request deletion from info object

Hi,
We are loading 'DELTA's' for master data to an info object.
Last night delta was failed due to idoc error.
how can i delete the delta request from the info object and re do the delta again...
I inserted the info object as data target so that i can get an option of manage on context menu...but when i did that there are no requests show in the manage of info object
how can i delete failed data request from an info object and re do the delta again
Thanks

Hi BW KING,
An infoobject can be a data target and also use direct update. Are you loading using an InfoSource? Check where you have the load infopackage, if it's under an infosource, you can do that. If you have your infopackage under the infoobject "icon" (without update rules), then you don't have the option to manage the loads.
Hope this helps.
Regards,
Diego

Transport request deleted from buffer how to retain it?

Hi geeks please help me.
As the support package upload,i have found that some transport request request are blocking the support package upload.The error issued was Queue_not_empty .I went to command prompt to get the list of transport request with status "will not be import because it is tagged".
then to remove them from the buffer I executed commands
tp addtobuffer <tr.request> <SID> pf=<path of tp profile> U1 tag=SPAM
tp delfrombuffer <tr.request> <SID> pf=<path of tp profile> tag=SPAM
.But now I see the transport request in the queue is in "RED" status.
I need to retain the transport request and reimport it.Is there any way to do that?
I have both K-file and R-file corresponding to this requests in cofile and data directories respectively.
Regards
Syamkrishnan

Hi Syamkrishnan,
just copy the cofile and data file in the transport directory, then go to STMS click on Extras -> Other requests -> Add and add the transport to the queue.. then just reimport.
Hope this help
Juan
Please reward with points if helpful

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

Deleting request options in Cube?

Hi,
The Cube is Not Compressed where Aggregate Rollup and Compression of Aggregate rollup are available.
Now, I need to delete only one request from the Cube.
I have found two options
1) Delete this request directly from Cube (Via Manage option of RSA1)
2) Delete this request from Selective Delete option.
I need to know which is the best option in order to avoid further maintanace of already available Aggregate Rollup and its Compression. For which option Aggregate Maintanace is needed ?
Thanks
Tony
Edited by: BI Dev on Oct 24, 2008 12:35 PM

Hi......
You are saying that roll up and compression is not done........then you can easily make the QM status red........and delete the request.......
In any case if roll up is done...then at first you have to deactivate the aggregate........as already said ..........then you can only delete the request..................and if compression is done.............not possible to delete any more..........because after compression request number dos'nt exist any more....
Besides deleting entire requests, you also have the option of deleting data according to business-orientated aspects from the fact table. For example, you can delete the data for a cost center or of a customer even if these are spread over several requests.
Remember that if you delete data selectively from an InfoCube, the aggregate belonging to this InfoCube is automatically deleted...........
For you the best option is to delete the request from the target......
Hope this helps.......
Regards,
Debjani......

Request Deletion from Cube stuck in execeptional state

Similar Messages

Maybe you are looking for