Unable to delete request from write-optimized DSO (Error during rollback)

Hi Gurus,
I am trying to delete a delta request from a Write-Optimized DSO. This request was uploaded with a DTP from another Write-optimized DSO.
The actual overall status of the request is RED and the description of that status is now: 'Error during rollback of request DTPR_4JW6NLSVDUNYY3GTD6F4DQJWR; only rollback allowed'.
I checked the log of all Request Operations in DataStore (from the same line where the red request is now) and I see my several attemps to delete this request under a RED radiobutton with the title Rollback. The details for this error are the following:
Could not delete request data from active table
Message no. RSODSO_ROLLBACK114
Diagnosis
The system could not delete the request data from the active table of a write-optimized DataStore object.
System Response
Write-optimized DataStore object: DTFISO02
Active table: /BIC/ADTFISO0200
Request: DTPR_4JW6NLSVDUNYY3GTD6F4DQJWR
Procedure
Search for Notes containing the key words "Delete write-optimized DSO PSA"
I am relatively new to SAP BI 7.0 and I do not know how to delete this request. Any help will be highly appreciated !!
Leticia

Hi Leticia:
Take a look at the SAP Notes below.
Note 1111065 - "701: Delta consistency check for write-optimized DSOs"
Note 1263877 - "70SP20: Delta consistency check for write-optimized DSOs"
Note 1125025 - "P17:PSA:DSO:ODSR missing in PSA process for write-opt. DSO"
Additionally, some ideas from the alternative presented on the blog by KMR might help you.
"How to generate a selective deletion program for info provider"
Regards,
Francisco Mílán.

Similar Messages

Deletion of requests from Write optimized DSO

Hi all,
Tried using this RSSM_DELETE_WO_DSO_REQUESTS to delete requests more than 60 days, via process chain.
But this is not removing all requests more than 60 days. Quite a few are not getting deleted and even on second run of this program, deletes one request at a time. Not sure why this behaves this way.
Any other alternative as Deletion of WDSO (Write-optimized DataStore object) Load requests and active table data without deleting it from target
This also seems to work...?
Also, how should I ensure uniformity of timelines w.r.to PSA and changelog of this DSO flow? PSA 15 days and changelog 90 days retain is fine? Want to ensure no data comes again thats deleted in WDSO

Can some one suggest pls

Delta loading procedure from Write Optimized DSO to Infocube

Hi All,
We are using Write optimized DSO in our project to which I am loading data using Standard DSO 0FI_GL_12
From Write optimized DSO, we are loading delta records into Infocube, please provide your inputs to my following questionnaire:
1) I am quite interested to know how the delta records gets loaded into infocube whenever we are using 'Write optimized DSO' as we don't have any image concept in Optimized DSO
Ex: If am using Standard DSO, we have Change log table and image concept will allow to get updated value to Cube
let us assume
Active Table
111            50
111            70 (overwrite)
Change Log Table
111            -50        (X -- Before Image)
111             70    ( ' ' -- After Image) symbol for after image is 'Space'
So if we load this record to the target as a delta the above two records from change log table will get loaded to the CUBE and Cube will have 70 as the updated record
If am using 'Write Optimized',
Active Table
111            50
111            70 (overwrite)
When this record loaded to the cube, as Info Cube is always having 'Additive' feature so the total value will 50+70 =120 which is wrong?
Correct me what feature will work here to get updated value as '70' into Cube from Write Optimized DSO'
2)As the data source is delta capable and having 'ADDITIVE' delta process, only the delta records based on REQUEST ID are loaded into Info Cube with the updated key figure value?
Thanks for your inputs and much appreciated.
Regards,
Madhu

Hi Madhu,
In best practice, we use WODSO in Initial layer and then Standard DSO. Just for mass data load/staging purpose.
In best practice : Data source ----> WODSO ---> std. DSO
In your case : Data source ----> Std.DSO -----> WODSO.
In both cases if data load design is not in accurate way, then your cube will have incorrect entries.
For ex: today 9 am : 111, 50 (in active table)
Data load to cube, same day 11 am : then cube will have 111    50.
Same day, value got changed in std. DSO 1 pm :   111   70(over write function @ active table).
Same day/next day if you load data to cube, it will have 2 records one is with value 50 and other would be 70. So to avoid such scenarios we should plan load in accurate way. Else make change your DTP settings as ‘source table : change log table.
Coming to your case:
Once after the load to Std. DSO, load data to WODSO by changing the DTP settings ‘Delta Init.Extraction from’ : Change log.
Now data available @WODSO from change log table, then you load to cube In delta mode.

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

Unable to delete requests from ODS

Hi Experts,
I am trying to delete requests fwhich is having some added records rom an ODS. I changed the status of QM to RED and in the monitor screen as well. Now, when I try to select the request and delete, a trash can appears and after hitting the refresh button the reportinng availability appears against the request.
I deleted the entries in the change log table...then I was able to delete the request from the ODS. Now when I try to reconstruct those deleted requests from the Reconstruct tab by changing the QM status in the monitor to green, the status of these request are in Yellow and there are updated records but the added records are 0. When I try to change the QM status it give s message "Request is already (partially) activated, no further QM action is possible.
How do I change the request QM status to Green and the get all the added records as there were in previous instead of 0's with out reloading the ods from r/3.
Thanks in advance,
HT

Hello,
This error may be RSMPC141 error.
Please see Note 643880 and Note 849857
this may occur becos of loss f records in change log.
You will need to reload to fix this problem
regards,
karthik

Unable to delete request from ODS - BW 3.5

Hi experts,
I am not able to delete request from ODS in BW 3.5, patch level 21. I put the request red, but it does not help to delete it. The request is full load and quite hudge (16GB). Deleting actually takes too long (several hours), but does not finish, so I cannot tell you any error description. It seems that this job can run forever... I was trying to activate the request before, but because of a tablespace limitations I received some short dumps. That is why I am trying to load it agin in smaller parts. It is strange thou that in Manage/requests tab the request has flag 'available for reporting' but the data cannot be viewed as active (only as new data). Any ideas, OSS notes?
Thank you,
Michal

Hi,
If you want to delete requests manually from the ODS tables.
1. tcode se16.
2. delete the request in these tables : RSICCONT (delete activated requests OR
Make the selective deletion of the contents of that request), RSMONICDP, RSODSACTREQ (give the name of the ODS and the
request ID and delete all the entries pertaining to this selection in that table.), RSODSACTUPDTYPE.
You can check OSS Notes 947481
Regards.

Init from Write optimized DSO

Hello,
I have a requirement wherein a WDSO (Write Optimized) get everyday's Delta where we apply all Business rules. Then need to load this DELTA into a Cube in Analytical layer which is in a different system.
Questions:
1. Can we do Init without Data transfer from WDSO to Cubes while using Update rules from Exp DS of this WDSO to the Cubes, and then run Delta loads subsequently?
2. Can we do Init without Data transfer from WDSO to Cubes while using DTP from this Exp DS to Cubes in a different system, and run Delta loads subsequently?
As mentioned, please be aware that source WDSO and the Cubes are in 2 different systems.
thanks in advance for the help...
Kumar

Hello Chetan,
Really appreciate your help on this.
Guess I am failing to explain my requirement.
Process that you had suggested works fine if it is full load from source WDSO to the Cubes in a different system. But for this I have to drop and reload the delta in WDSO everyday.
My actual requirement is to keep adding new Delta requests into WDSO everyday, then pull ONLY DELTA records (Requestes that are loaded on each day) into the Cubes across system.
So in order to achieve this we have to load from WDSO to PSA in a different system (for doing Init or Delta), then pull using DTP into the Cubes.
So as said earlier, while doing this Init from WDSO to PSA using Infopackage it is working fine but no subsequent Delta are getting pulled though new records added in WDSO.
Hope it makes sense....
This makes me to think whether we can load Deltas from WDSO or not. Appreciate your help.
thanks
Kumar

Unable to delete request from an ODS

Hai All,
I have a requestng in an ODS which I am trying to delete in the Manage ODS- screen by selecting the request and then deleting it. But every time I press delete, I get the trashcan symbol in place of the reporting symbol of the request and when I press refresh , the trash can disappers and the reporting Icon comes back. Any idea why this is happening? I then changed the QM status of both the request and in the Monitor and tried to delete without any luck.
Can somebody please tell me what the problem is, I have no errors showingup but the request is not getting deleted.
Thank you.

Hi Visu,
Check if you have set the status of the request you want to delete as RED before deleting it..
We had a similar issue bcoz of this before..
Also check if all the requests that came in after that are also deleted..
Ashish.
Message was edited by: Ashish Gour

Unable to delete data target contents of Write-Optimized DSO in Process Chain

Hi Experts,
We are using SAP Net Weaver BW 7.01 version and we need to delete the entire data target contents of Write-Optimized DSO in the process chain before the next data load.
I included this step in process chain but still it is failing with errore message"Message not found (in main memory), Drop Cube Failed In Data Target"
This process type is working during BW 7.0 version but not in BW 7.01 version.
However i found that we can use the program RSSM_DELETE_WO_DSO_REQUESTS to delete old requests in the Write-Optimized DSO for BW 7.01 SP07 as per SAP Note 1437407 but still it's not working even after implementing this program as the Prerequisite to delete the request is the data mart status should be updated where it is not happening for the program.
We had an process type option to 'delete the requests from Write-Optimized DSO' directly in BW 7.3 but still not available in 7.01 version.
Could you please suggest me on how to resolve this issue in BW 7.01?
Many thanks for your help in advance.
Regards,
Madhu

Create ABAP program as attached code.
Then you can use that ABAP program in process chains through ABAP variant
ABAP varaint should have following properties
Select call mode as Synchronous; call from Local; and Program
Give your ABAP program name in "program name" and create one program variant for each write optimized DSO.
Please refer how to use ABAP program in process chains for further details.
Hope this helps

Issue with Write Optimized DSO in BI 7.0

Hi Guys,
I have an issue reagarding Write Optimized DSO in BI 7.0.
First, I explain the scenario..
We have some Master Data Objects around 5. We have a source system for load master data.
The design is like this
There is a DSO which gets the data from 30 Master Data Sources and feeds 30 Master Data objects (Info Objects).
The process of loading master data is before loading the new loads previous load requestes have to be deleted from this Write Optimized DSO and current loads have to be loaded. This entire process is done through Process Chains.
In this regard. every thing is going smoothly. But for last somedays Deletetion of Requests in Write Optimized DSO process showing its failed (Red Color) with error (pls. check the below screen shot for that) even though the previous requested in DSO got deleted and new load requested added in DSO Manage Tab.
What I am thinking is, its merely Fron End Problem, If am not wrong please help me in this regard.
Please let me know is there any notes for related this issue, ot something other solution.
THanks in Advance
Peter ....

how it is resolved how u did u done the procedure ?

Write optimized dso - Stand DSO loading by Delta Req by req is not working

Hi All,
We have a data flow which has 1st layer having write optimized dso and then we are loading data to Standard DSO.
We are using Delta DTP to load the data with the option "Get All New Data Request By Request", but it is not working.
Suppose if i have 2 requests which are need to update to Standard Dso from Write Optimized Dso, it is updating in single request. We are on SAP BW 701 patch level is 005.
Please suggest me ....

Hi Prasanna,
For reasons of downward compatibility, the system behaves differently for DTPs that were created before "SAP NetWeaver 7.0 Support Package Stack 13"
DTPs for which the indicator is set only get the first new request, even if there is more than one new source request at the time of processing. This restricts the way in which these DTPs can be used in process chains, because requests accumulate in the source and the target may not contain the current data. The Retrieve Until No More New Data indicator is therefore displayed for these DTPs.
I Suggest you to set this indicator and activate the DTP.
If you set the Retrieve Until No More New Data indicator and then activate the DTP, once it completes processing, a DTP request checks whether there are any further requests in the source. If the source contains more requests, a new DTP request is automatically generated and processed. Once the DTP is activated, the indicator is no longer visible in DTP maintenance.
This applies when the DTP is started by a process chain and also when you start the DTP directly from DTP maintenance.
The indicator is set by default for new DTPs that get data request by request.
If you do not select the indicator, the label for the Get All New Data Request By Request indicator changes to Get One Request Only. Once the DTP is activated, only this indicator is displayed in DTP maintenance.
Regards,
Sudheer.

Error while deleting data from a write optimized DSO using a Process Chain?

Dear Bwers,
I am facing a strange error while using process chains to delete data from data target which is a write optimized DSO. The process shows as failed but the data gets deleted in the DSO. The error message is as below. Did anybody have a similar problem? Any suggestions.
Thanks
Raj
Error while deleting content of InfoCube/DataStore object ZLSD_G03
Message no. RSDODSO153

Please, check if you get any short dump in ST22 related to this issue.

Write-Optimized DSO data deletion

Hello All,
We have a requirement to delete old data from a write-optimized DSO. The specific requirement is to delete the data older than 15 days (requests older than 15 days) in the DSO. I could not find any process type that could be used in process chains which would automatically delete the old data based on our settings (similar to the one used for PSA or Change-log deletion). Has any of you come across a process type or a batch job that be scheduled to delete old data in a Write-optimized DSO. Your help is much appreciated.
Thanks,
Veera

Hi Nagesh,
Thanks for your answer. But the use of these function modules would still require custom development to identify the requests to be deleted. We are trying to see if SAP has any standard process for deleting the old request out of a write optimized DSO or if anyone was successful in achieveing this with least amount of customization.
Thanks,
Veera

Error during loading and deletion of write-optimized DSO

Hey guys,
I am using a write optimized DSO ZMYDSO to store data from several sources (two datasources and one DSO).
I have disabled the check of uniqueness in the DSO, but I defined a semantic key for the fields ZCLIENT, ZGUID, ZSOURCE, ZPOSID which are used in a non-unique index.
In the given case, I want to delete existing rows in the DSO. I execute these steps in the endroutine. Here the abstract coding:
LOOP AT RESULT_PACKAGE ASSINING <RESULT_FIELDS>.
u201Csome other logic [u2026]
DELETE /BIC/AZMYDSO00
WHERE /BIC/ZCLIENT = RESULT_FIELDS-/BIC/ZCLIENT
     AND /BIC/ZGUID = RESULT_FIELDS-/BIC/ZGUID
AND /BIC/ZSOURCE = RESULT_FIELDS-/BIC/ZSOURCE
AND /BIC/ZPOSID = RESULT_FIELDS-/BIC/ ZPOSID.
ENDLOOP.
COMMIT WORK AND WAIT.
During the Loading (after the transformation step in the updating step), I get the messages (not every time):
1.     Error while writing the data. (RSAODS131)
2.     Could not Save DataPackage xy in DataStore ZMYDSO (RSODSO_UPDATE027).
Diagnosis: DataPackage XY could not be saved. Reasons therefore could be violation of key uniqueness (duplicate data) or general database error.
3.     Error in the substep of updating DataStore.
I have checked the system log (SM21) and the system dumps (ST22) but I could not find an exact error description.
I guess, I am creating some inconsistencies or locks (I also checked the SM12) so that the load process interrupts. But I also tried a serial updating within the DTP (I reduced the number of batch processes to 1). No success.
Perhaps the loading of one specific package could take a longer time so that the following package would overtake the predecessor. Could that be a problem? Do you generally advise against the deletion of rows within the endroutine?
Regards,
Philipp

Hi,
is ZMYDSO the name of the DSO?
And is this the end routine of the transformation while loading the same DSO?
if so we never do such a thing.
you are comparing the DSO with the data that is flowing in and then deleting the data from the DSO...
Which doesnt actually make any sense... because when loading the data to a DSO (or a cube or any table) the DSO (or cube) will be locked exclusively for any modifications of data. You can only read data from it.
If your requirement is that existing duplicate records need not arrive in the DSO then you can delete the data from the SOURCE_PACKAGE in the start routine like below
SELECT FIELDS FROM /BIC/AZMYDSO00 INTO INTERNAL_TABLE WHERE <CONDITION>.
LOOP AT INTERNAL_TABLE.
   DELETE SOURCE_PACKAGE
WHERE SOURCE_PACKAGE-/BIC/ZCLIENT = INTERNAL_TABLE-/BIC/ZCLIENT
     AND SOURCE_PACKAGE-/BIC/ZGUID = INTERNAL_TABLE-/BIC/ZGUID
AND SOURCE_PACKAGE-/BIC/ZSOURCE = INTERNAL_TABLE-/BIC/ZSOURCE
AND SOURCE_PACKAGE-/BIC/ZPOSID = INTERNAL_TABLE-/BIC/ ZPOSID.
ENDLOOP.
or if your requirement is that you need to delete the old data from the DSO for the same key which is arriving newly in order to load the new data into the DSO in that case, you could do something like this in the start routine
SELECT FIELDS FROM /BIC/AZMYDSO00 INTO INTERNAL_TABLE FOR ALL ENTRIES IN SOURCE_PACKAGE
WHERE /BIC/ZCLIENT = SOURCE_PACKAGE-/BIC/ZCLIENT
     AND /BIC/ZGUID = SOURCE_PACKAGE-/BIC/ZGUID
AND /BIC/ZSOURCE = SOURCE_PACKAGE-/BIC/ZSOURCE
AND /BIC/ZPOSID = SOURCE_PACKAGE-/BIC/ ZPOSID.
* now update the new values you want to write in the loop
LOOP AT INTERNAL_TABLE INTO WORK_AREA.
"CODE FOR MANIPULATION of WORK_AREA
*write a modify statement to update the RESULT_PACKAGE.
MODIFY RESULT_PACKAGE FROM WORK_AREA TRANSPORTING FIELDS.
ENDLOOP.
hope it helps,
Regards,
Joe

Load Data with 7.0 DataSource from Falt file to Write Optimized DSO

Hi all,
we have a problem loading data from flat file using the 7.0 datasource.
We have to load a flat file (monthly) into a WO DSO. The infopackage load file in full mode into the Datasource (PSA) and the DTP Load in delta mode data from datasource into the WO DSO.
When i load the second file in the Datasource, the DTP load all data present in the Datasource and not only the new one as aspected using Delta mode.
Has anyone any tips to help me?
Thank you for help.
Regards
Emiliano

Hi,
Iam facing the similar problem.
Iam using Write Optimized DSO and i have got only 1 req in PSA (have deleted all previous req from PSA and DSO).
When iam doing a delta load from PSA to DSO, i expect to see only that 1 req to get loaded into DSO.
But, its picking up the data from 3 other reqests and doubling the records...
Can you please help me, how did you managed to get out of that isue?
Cheers,
Nisha

Unable to delete request from write-optimized DSO (Error during rollback)

Similar Messages

Maybe you are looking for