Update of write optimized DSO by csv file

Hi Gurus,
I have observed few things while trying to upload a write optimized (WO) DSO from a flat file in BI 7.0. The data flow is as follows:
data source -> transformation -> data target (DSO - WO).
from a test perspective, i have updated 5 records till PSA with IPAK and subsequently updated it to the DSO using DTP. When i check the in the manage i found records transferred = 5 and added = 5. which is okay.
then i again updated the same 5 records to PSA, and triggered DTP. Now DTP brings 10 records (5 + 5). records transferred = 10 and updated = 10. when i checked in the header tab in DTP monitor i found the selection brings both the PSA request IDs.
again i loaded the same 5 records to PSA, a new PSA request ID generated and DTP extracts this PSA id along with the old 2 already transferred. Now records transferred = 10 added = 15. why transferred 10 ? i am getting confused here. I was expecting it to follow the same way, then it should have transferred 15 and added 15. Ideally there is no routine which generates additional record. There for this is not possible at all. Anybody has observed this strange behaviour ?
Why this is happening ? I was expecting it should only bring 5 records every time ? Is it something specific to write optimized DSO or am i doing something wrong here ? Is there any setting where i can set the parameter no to select the old PSA request that already updated to DSO ?
Please clarify.
Soumya
Message was edited by:
Soumya Mishra

Is your DTP full or delta.
Here is some interesting discussion.
/thread/348238 [original link is broken]

Similar Messages

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

What is the main difference of Direct update DSO and Write optimized DSO

What is the main difference of Direct update DSO and Write optimized DSO?

Hi chandra:
Check this link.
http://help.sap.com/saphelp_nw04s/helpdata/en/f9/45503c242b4a67e10000000a114084/content.htm
You can find another difference on page 147, section "Reclustering DataStore Objects" of the document "Enterprise Data Warehousing"
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/67efb9bb-0601-0010-f7a2-b582e94bcf8a?quicklink=index&overridelayout=true
>You can only use reclustering for standard DataStore objects and DataStore objects for direct update. You cannot use reclustering for write-optimized DataStore objects. User-defined multidimensional clustering is not available for write-optimized DataStore objects
Regards,
Francisco Milán.
Edited by: Francisco Milan on Aug 11, 2010 7:09 PM

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.

Duplicate Semantic Key in Write Optimized DSO

Gurus
Duplicate semantic keys have a unique index KEY in the key fields of the DSO when WRITE OPTIMIZED DSO is used. (Of course this is assuming the Do not check uniqueness of data indicator is not checked..)
See help https://help.sap.com/saphelp_crm60/helpdata/en/a6/1205406640c442e10000000a1550b0/frameset.htm
This means that the DSO can contain duplicate records.
My question is: What happens to these duplicates when a request level delta update is done to a Standard DSO or Infocube?
Do duplicates end up in the error stack? Are they simply aggregated in further loads? - because this would be a problem for reporting (double-counting).
thanks
tony

Hi Tony,
It will aggregate the data in some undesired way.
Read on...
https://help.sap.com/saphelp_crm60/helpdata/en/b6/de1c42128a5733e10000000a155106/frameset.htm
If you want to use write-optimized DataStore objects in BEx queries, we recommend that they have a semantic key and that you run a check to ensure that the data is unique. In this case, the write-optimized DataStore object behaves like a standard DataStore object. If the DataStore object does not have these properties, unexpected results may be produced when the data is aggregated in the query.
Hope it helps...
Regards,
Ashish

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

Semantic keys for write optimized DSO

Hi experts,
Can anyone tell me more about semantic key in a write optimized DSO ?
I have a DSO cocnerning sales orders with 3 Datasources.
How can you define the semantic key ?
I have schedule line number - document number and position number in semantic key but when I load the PSA, I have an error with duplicate data.
Any clues ?
Thanks.

Hi Oliver,
If you specify any of the charaterstics symantic fileds, when you load data to the DSO, if any error record comes the following records which has the same characterstic(symantic) combinations will n't update into DSO even though they are correct. they will be written to error stact to ensure the data quality.
In write optimized DSO, technical fileds are automatically taken, then in the semantic fileds you can specify the charcterstic which should act as primary keys(but not exactly).
Thanks
Sreekanth.

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

Write optimized DSO

Hello Guys,
I have couple of questions regarding write optimized DSO.
1.Can we use write optimized DSO to load to cube.
2.Also in the end routine without adding any code when I check the syntax I get a syntax error. The generated code by sap has some syntax errors.When I try to change the dso to standard and generate it again, I don't have the syntax error in the end routine.
Do anyone encountered this problem.
Please confirm. As always thanks for your help.
Senthil

In the end routine I am getting the following error before writing any abap code:
E:Explicit length specifications are necessary with types C, P, X, N und
W in the OO context.
When u click the error message it takes you to the following data declaration in the code:
TYPES:
      BEGIN OF ,
     InfoObject: 0RECORDMODE BW Delta Process: Update Mode.
        RECORDMODE           TYPE RODMUPDMOD,
      END   OF .
the above data declaration is generated by SAP.
Any input really appreciated.

Sematic group for a write optimized DSO

Hello,
I am loading from a datasource to a write optmized DSO. While doing so, I am not able to set semtantic key/group for the DTP. I have turned error handling on using the setting 'Valid records update, No reporting(request RED)'.
Is this setting not possible for a write optimized DSO? if not why not? and if yes, what am i missing!?
Thanks a lot in advance,
Prakash

Thank you,
here are my findings:
- if data has been loaded with delta using the DTP, it is not possible to change the sematic groups any more - all requests have to be deleted first
- the error handling must be turned on
The issue is resolved.
Marek

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

Disk throughput drops when inserting data packages in write-optimized DSO

Hi all,
we are currently testing our new freshly installed SAN.
To see the performance gain in BI, I'm currently doing some test loads.
And during the monitoring of those loads, I noticed something I'd like someone to explain :-):
I execute a DTP from PSA to a write-optimized DSO.
The n° of parallel processes = 9
Update method = serial extraction, immediate parallel processing
N° of records transferred: +23.000.000
Ok, in the first phase (read the PSA) only one process is used (serial extraction). When I look in OS07, I notice we have very good throughput: +66.000 TransfKB/s. Very nice!
But as soon as BI starts inserting the data packages, and parallel processing kicks in, the throughput drops to 4K or something, and sometimes we get 20K at max. That's not too good.
We have a massive SAN , but the BI system does not seem to use it?
I was wondering why this is the case. I already toyed around with the package size, but it's always the same.
Also I noticed that the allocated processes don't seem to be active. I allocated 9 BTC processes to this load.
They are all used, but we only see 3 inserts at the same time, max. Also in the DTP-monitor, only 3 packages are processed at the same time. As it's a write-optimized DSO, RSODSO_SETTINGS does not apply I presume.
Any ideas?
tnx!

Hi,
can you pls try to give some filetr in DTP and try to pull the data.
I am not sure why first data package is taking long time and otehr data package is taking less time..
Do you have any start routine..If datapak = 1.. the do this logic..
Pls check..
regards
Gopal

Can a write-optimized DSO be used for Delta upload

Hi,
can any one please answer following..
1. can a write optimized DSO be used for Delta upload?
2. Does industry based content is available in BI Content ?
Thanks&Regards
Satya

Hi,
Write-Optimized DataStore does not support the image based delta, it supports request level delta, and you will get brand new delta request for each data load.
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.
Write-Optimized Data Store supports request level delta. In order to capture before and after image delta, you must have to post latest request into further targets like Standard DataStore or Infocubes.

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.

Update of write optimized DSO by csv file

Similar Messages

Maybe you are looking for