DB tables deleted - manage request ?

Hello,
what if the Data from the SAP DB tables are deleted do the request in the manage screen of cubes/DSO exsists or it will also get deleted.
response is much appreiciated.
Thanks

Hello,
Sorry i was not insterested in the OS /Db2 but my query was related to Bw only hence i posted in this message.
The query was whether manage screen holds the request number in the Bw or not yes it will.
Thanks

Similar Messages

Issue in deleting PSA request in the backend table.

All
We have been facing this strange issue with PSA - Ideally, when we delete a request in the PSA, the contents of the respective back end table also get deleted. However, in case of one of the PSAs, if we delete the contents of the PSA, the same is not reflected in the backend table. As of today, the PSA is empty but the back end table has around 1 mn records. Looks like it has appended all the requests that we have loaded so far and not deleted the earlier entries.
Any help on this issue will be appreciated. Thanks.
Regards
Niranjana

In continuation it all depends on the SP you are ,i presume you are above SP>10 so below should not be an issue for you.
When you try to delete requests from the PSA that were loaded into the PSA using an old 3.X DataSource and the DataSource has been convertes into a new NW2004S DataSource in the meantime, you cannot delete the requests properly.
The administration information is deleted, but the data remains in the PSA table
Note 983618 - P10:PSA: Deleting requests after converting old DS to new DS
Hope it Helps
Chetan
@CP..

URGENT: How to delete the request in version management

Hi,
Please let me know how to delete a request in version management whcih is not released yet.
I have released a request to quality server for an object. After that I was asked to make some changes to that object as there are some defects.
So, i have created a new request and proceeded with the changes. Under that request I have made some changes and activated. but the result is worthless. So, I want to get the result of the object which i have released. i.e. i want to get back only the released request changes.

Hi,
yeah............goto version management......first ull hav ur new request......
below that ull have ur previous request right.............
check the check box of ur previous request.............
and click retrine button.......all changes made in ur latest request ll be retrived back to its previous version.........
come back activete it.............in ur program ull not find ur new useless changes........release it...........
Cheers,
jose.........

How to delete the requests in DTP?

hi all,
here i am unable to delete the requests in DTP...
when i am going to delete the request in DTP it simply showing the error:
*cannot lock request DTPR_488BDVJVHQPUUTT3R383DJ55Q OF TABLE 0MATERIAL for deletion*
could you plz help me on this.....

Hi Kiran,
Please go through this thread. Here the same problem has been discussed it detail.
/message/4419400#4419400 [original link is broken]
Following are the steps mentioned in this thread
1. RSA1 -->Info provider >0Material>Right Click-->Display
2. One screen will come , Select the monitor icon to view that (not the one when you go with Manage of 0Material_attr).
3. In the monitor screen you will see Refresh icon , Refresh that
screen , Now the status will change , after 2 -3 refreshes you
will see the request turning to red.
4. Now go back to the manage tab of the 0Material attribute , You
can delete now.
Regards,
Praveen

Need help in deleting the requests from DSO

Hi All,
I want to delete the data load requests present in the dso, I cant do that from the manage tab as it is throwing error because of some dump been loaded into it.
Please tell me the tables names which stores these data load requests of the dso's so that I can delete those requests in the backend.
If is there any way to delete these requests or complete data, please let me know. I cant do these operations from the mange tab/delet data tab of dso as it is throwing the error.
Thanks,
vinay.

Hi,
You can delete the Requests form DSO by useing RSICCONT.
Follow bellow steps:
1. Goto SE16.
2. Give the RSICCONT and Click on Technical Contents.
3. Give the DSO name--> Click on Execuit
it will dispaly the number of requests which it exists.
4. Select your request>Select 'Table Entry' Menu> Select 'Delete'
Regards,
Suman.

Problem in deleting a request from Dso

Hi Experts,
I have loaded the request into DSO, after activation, i have changed the QM status to red and try to delete it from the manage screen. But it is not getting deleted from DSO.
I have used following tables :
RSREQDONE
RSICCONNT
RSODSACTREQ
For deletion purpose, but i'm not provided with authorization ..
And also i have used FM to delete the request from DSO , but it also failed ..
Can you please help me out in this regard..
Thanks
PT

Hi,
Please check if your DSO is locked by any other process. You can check the lock status from SM12. If your DSO is locked by some other process, you will have to wait till that process finishes or kill the process if it is not required so that your DSO will be unlocked. Once your DSO is unlocked you can retry activation. If this doesn't work, please check if you have the authorization to delete data. after trying to delete the DSO you can run the transaction SU53 to see if there is any authorization failure.
Hope this helps you.
Thanks,
Nithin Reddy.

Problem in deleteing the request

H All,
We ran a load to Master Data (info provider)object.The Load got failed due to invalid data entries.Wheb i tried to dele that particular request from infoprovider .Request is not getting deleted and got folloed msg.
You want to delete request(s) from InfoProvider 0AUVEHICLE
The data target is a master data table
The records in the request are no longer transparent in the table
Only the control entry that shows that the request has been updated
already, is deleted.
This means that the request can be updated again.
Can you please help me in deleting this request.
Kranthi

Kranthi,
This means that even though you delete the request - the master data entries still remain. This happens for Master Data.
You will have to delete the same and reload the data back in.
For example if you data load has :
1|BCD|Sales
and this is part of your master data load , even if you delete the request the entry is not deleted - the entry still remains - you can delete the request in the manage atb and reload the data once again.... SAP is just givig you information that Master Data Objects are not like a DSo where if you delete the request the entries go away. This is because the Infobject tables do not have any request based data - al the data gets updated into the same tables and once you load the data - the data remains there till a manual delete is triggered and request based deletion is not possible...

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

Hi Experts,
1. I need to delete PSA request(50 request) in BI 7.0 production system.
2. Also need to include the process type 'deletion of PSA request' to the existing process chain.
Pls provide me the steps to follow to perform the above activities.
Regards,
Anand

Hi,
I found this answer for deleting the psa request.
1.      Select the DataSource that you want to delete requests from the PSA for and choose Manage.
       2.      On the next screen, select one or more requests from the list and choose Delete Request from DB.
       3.      When asked whether you want to delete the request(s), confirm.
The system deletes the requests from the PSA table.
You can also delete requests in DataSource maintenance. Choose Goto ®   Manage PSA (pushbutton). Follow the instructions above, starting from step 2.
Can i follow the same in production. Pls confirm.
Regards,
Anand.

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

Managing Request without Monitor Log: APO Request or Terminated Request Gen

Hello Everyone,
Need some help of managing a system created DTP named Request without Monitor Log: APO Request or Terminated Request Generation. This is like a staging DTP provided by SAP to support data loads to DSO or Cube and, it's good if the process goes smoothly.
However when we encountered unnecessary error such as tables space or memory problem, this particular job will get stuck and there's no way to move forward or backwards from this point. There were some answers to delete the request from RSICCONT, but I don't see the direct relations here, or maybe I'm wrong.
My only question - Have anyone any idea on how to work around this.
The last thing I've in hand is to delete the whole thing (requests) and re-do from start (extraction). Not a pleasant thing as this DSO feeds to 2 Cube & 1 DSO and then to another Cube.
Thanking everyone in advance.
Regards,
Azmadi

Hi,
sad to knw you had to delete the whole data and reload. I faced the same issue today and here is what i did,
when you go to the reconstruction tab, you will find 2 ticks present
1st one that tells if request is available in data target and
2nd which gives the transfer structure status.
Now, if the first check is crossed it could mean 2 things....data no longer exists in data target or data was not updated to data target these are 2 different things.
So, in your case it wud have sed data was not updated to the target.
Solution, just reconstruct that request and then in the request tab mark it red and delete again since you dont need it.... then the activation through process chain will not fail.

Error while deleting a request

Hi All,
When trying to delete a request from a master data object an error appears which says:
Cannot delete request DTPR_* of table RSN* for deletion.
Please let me know what needs to be done here so that request is deleted.
This is urgently required..thanks..

For deleting any master data
Need to delete first where its referenced to ,so check the where used list for the infoobject and delete the places where that master data is referenced
Typically - Attributes,Hierarchies,Texts,Transaction data,in Query - Hardcoded master data
Lots of ways around ,even using database utility ;however that leads to inconsistencies and requires sounds knowledge so wont advocate those steps.
You can follow below steps -
R-Click Delete master data ,it wont delete all if its referenced,so now go to
Tcode - SLG1
Object = RSDMD
Subobject = MD_DEL
Hit execute button
it will fetch you the log showing all the places(references) where you need to delete the data in order to delete the actual master data.
After deleting the data from referenced places you can completely delete the master data.
Hope it Helps
Chetan
@CP..

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.

How to delete the request in Direct Update DSO

Dear Gurus,
I have a situation where I have an invalid characteristic loaded into the Direct update DSO. This is related to Spend Performance Management. This DSO is loaded through a data source with the option Without Archive. So, I cant see any request in this DSO. This DSO will then supply data to another DSO which is standard DSO.
The data Activation job in the standard DSO is failing.
My question is I have to delete the request from the Direct Update DSO and then load it to Standard DSO. I have already repaired the data in PSA.
Your Kind help is greatly appreciated.
-Mohan Kumar

You must be using some fill or delete APIs to fill the data in Direct update DSO.You can't create transformation to fill the data in DIrect Update DSO as you do in Standard DSO.You will not see request number under the manage tab for direct update dso for any load.
Whenever you will fill the Direct update DSO next time,previous data gets deleted automatcally. For Direct update DSO there can only be a Full Update.So just load the data using API's and previous data will get deleted automatically
Edited by: shyam agarwal on Mar 2, 2012 7:48 AM

DB tables deleted - manage request ?

Similar Messages

Maybe you are looking for