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

Similar Messages

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.

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.

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

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

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.

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

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.

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

Load performance Write-Optimized DSO

Dear all,
I'm looking for some practical tips concerning improving load performance from the PSA to a write-optimized DSO (41M records) via a DTP.
All parameters that could be tweaked have been checked (e.g. packet size, batch jobs, uniqueness of data flag, etc.) and optimized.
However this load stays extremely slow (init load from source to BW is faster).
The BW system runs on SP18.
Please share all your tips our recommendations for us to solve this major issue.
Your help is much appreciated!
Thanks
JvB

Hi JvB,
Here are some options I can think of and let you know if I remember something:
1) Increase number of prallel processes in DTP i.e. DTP->GOTO->Settings for bacth monitor->Number of prallel process to 4 or 5.
2) Note 409641 - Examples of packet size dependency on ROIDOCPRMS
The general formula for data transfer is:
packet size = MAXSIZE * 1000 \ transfer structure size
but not more than MAXLINES.
eg. if MAXLINES < than the result of the formula, MAXLINES size is transferred into BW.
3) you should check if there are any locks or deadlocks in ST04 and also System Analysis SM21....it will show u all the details,,, and Short dump in ST22.....there may be some ..
4) Check and Analyze DSO in RSRV. If there are any issues repair it.
5) If you are loading huge volumes of data split the records by Filters in DTP ex. Plant, calendar year or calendar month selections.
And also Try
Try partioning,craeting indexes/secondary indexes or archiving old data.
Check these links for furtehr reference:
/people/martin.mouilpadeti/blog/2007/08/24/sap-netweaver-70-bi-new-datastore-write-optimized-dso
/message/2987899#2987899 [original link is broken]
Good Luck.
Regards
Satish Arra
Edited by: Satish Arra on Feb 7, 2009 9:28 PM

Multiple data loads in PSA with write optimized DSO objects

Dear all,
Could someone tell me how to deal with this situation?
We are using write optimized DSO objects in our staging area. These DSO are filled with full loads from a BOB SAP environment.
The content of these DSO u2013objects are deleted before loading, but we would like to keep the data in the PSA for error tracking and solving. This also provides the opportunity to see what are the differences between two data loads.
For the normal operation the most recent package in the PSA should be loaded into these DSO-objects (as normal data staging in BW 3.5 and before) .
As far as we can see, it is not possible to load only the most recent data into the staging layer. This will cause duplicate record errors when there are more data loads in the PSA.
We all ready tried the functionality in the DTP with u201Call new records, but that only loads the oldest data package and is not processing the new PSA loads.
Does any of you have a solution for this?
Thanks in advance.
Harald

Hi Ajax,
I did think about this, but it is more a work around. Call me naive but it should be working as it did in BW3.5!
The proposed solution will ask a lot of maintenance afterwards. Beside that you also get a problem with changing PSA id's after the have been changed. If you use the posibility to delete the content of a PSA table via the process chain, it will fail when the datasourcese is changed due to a newly generated PSA table ID.
Regards,
Harald

4 LSA architecture - EDW layer - write optimized DSO settings

Dear Colleagues,
I have a question regarding the 4 LSA architecture, available on the following article.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/306f254c-1e3f-2d10-9da0-bcff4e35e0ef
When we activate a SAP business content dataflow.
If we want to add in the EDW layer write optimized DSO to have a faster upload from source system to SAP BI.
Should we always check the" do not check uniqueness of data" setting in the write optimized DSO to avoid data upload error ?
Based on your experience what would be your recommendation ?
Cheers,

I would suggest to check "ON"
-If the check is ON It will allow to load several records with same semantic key and in next layer
-If the check is OFF It will not allow to load same record twice and throws error
Did you seen this ?
/people/martin.mouilpadeti/blog/2007/08/24/sap-netweaver-70-bi-new-datastore-write-optimized-dso
Edited by: Srinivas on Aug 24, 2010 2:16 PM

Problem loading data into write optimized dso.....

Hi ,
I am having problem loading the data from PSA to write optimised DSO
I have changed the normal DSO into a Write Optimised DSO. I have 2 data sources to be loaded into the write optimized DSO. One for Demand and one for Inventory.
The loading of Demand data from PSA to DSO happens fine with out any error.
Now while loading the Inventory data from PSA to DSO , i get the below errors
"Data Structures were changed. Start Transaction before hand"
Execption CX_RS_FAILED Logged
I have tried reactivating the DSO, Transformation, DTP and tried to load the data again to the write optimised DSO, but no luck, I get the above error message always.
Can some one please suggest me what could be done to avoid the above error messages and load the data successfully.
Thanks in advance.

Hi,
Check the transformations is there any routines written.
Check your Data struture of cube and DS as well.
Is there any changes in structure.
Data will load upto PSA normally, if is there any changes in struture of DSO, then the error may occur.just check it.
Check the below blog:
/people/martin.mouilpadeti/blog/2007/08/24/sap-netweaver-70-bi-new-datastore-write-optimized-dso
Let us know status.........
Reg
Pra

Missing PARTNO field in Write Optimized DSO

Hi,
I have a write optimized DSO, for which the Partition has been deleted (reason unknown) in Dev system.
For the same DSO, partition parameters exists in QA and production.
Now while transporting this DSO to QA, I am getting an error "Old key field PARTNO has been deleted", and the DSO could not be activated in the target system.
Please let me know, how do I re-insert this techinal key of PARTNO in my DSO.
I pressuming it has something to do with partitioning of the DSO.
Please Help.......

Hi,
Since the write-optimized DataStore object only consists of the table of active data, you do not have to activate the data, as is necessary with the standard DataStore object. This means that you can process data more quickly.
The loaded data is not aggregated; the history of the data is retained. If two data records with the same logical key are extracted from the source, both records are saved in the DataStore object. The record mode responsible for aggregation remains, however, so that the aggregation of data can take place later in standard DataStore objects.
The system generates a unique technical key for the write-optimized DataStore object. The standard key fields are not necessary with this type of DataStore object. If standard key fields exist anyway, they are called semantic keys so that they can be distinguished from the technical keys. The technical key consists of the Request GUID field (0REQUEST), the Data Package field (0DATAPAKID) and the Data Record Number field (0RECORD). Only new data records are loaded to this key.
You can specify that you do not want to run a check to ensure that the data is unique. If you do not check the uniqueness of the data, the DataStore object table may contain several records with the same key. If you do not set this indicator, and you do check the uniqueness of the data, the system generates a unique index in the semantic key of the InfoObject. This index has the technical name "KEY". Since write-optimized DataStore objects do not have a change log, the system does not create delta (in the sense of a before image and an after image). When you update data into the connected InfoProviders, the system only updates the requests that have not yet been posted.
PS: Excerpt from http://help.sap.com/saphelp_nw2004s/helpdata/en/b6/de1c42128a5733e10000000a155106/frameset.htm
Hope this helps.
Best Regards,
Rajani

Changing of Write Optimized DSO to Standard DSO

Dear Experts,
I have created few Write Optimized (WO) DSOs based on the requirement and I have created few reports also on these WO DSOs.
The problem is when I am creating an Info Set on the WO DSO, Standard DSO and a Cube (total 3 Info Providers I am including in this info Set) it is throwing an error while I am displaying the data from that Info Set.
I came to know that the problem is with WO DSO So I want to change this WO DSO to Standard DSO.
FYI We are in Development stage only.
If I copy the same DSO and make it as a Standard DSO my reports which I created on these will disturb so I want alternate solution for this.
Regards,
Phani.
Edited by: Sai Phani on Nov 12, 2010 5:25 PM

Hi Sai
Write optimized DSO's always help in optimal data performance. I am sure you created the WOD only to take advantage of this point.
However, WOD are not suitable when it comes to reporting.
So instead of converting the WOD to a standard DSO, (where you do lose the data load performance advantage), why don't you connect the WOD to a standard DSO wherein you extract data from the WOD to a standard DSO and use the standard DSO for reporting. This would give you benefit during data loas as well as reportiing.
Cheers
Umesh

Init from Write optimized DSO

Similar Messages

Maybe you are looking for