DataLoad into Write-optimized DSO with DTP and semantic groups

hi gurus,
i'm going crazy with my current problem.
i searched in the other posts of this topic, but i did not found a solution.
here my situation:
i created a w-o-DSO with semantic key (0ucinstalla, 0calmonth, zbelnum, 0unit) and three key figures.
now i'm loading from several cubes data into the DSO. (i need the historical data)
in every transformation, i implemented an expertroutine which collects the data into the result_package.
in the routine, i even clear the record number before collecting the result_rows.
in the DTPs, i'm using a semantic group for 0ucinstalla in order to select all rows for one 0ucinstalla into one data-package.
each DTP has to run one time in full mode.
but when i schedule the third DTP, i get the message: "duplicate record"
i checked the active data in dso. there was no record with that semantic key.
i found a record with the same 0ucinstalle for a diferent month - in my opinion, thats no duplicate record...
is there a dependence between semantic key in DSO and semantic group in DTP?
how can i solve this error?
regards,
philipp

Hi,
thx for your fast replies!!
@ Passing by:
I know the option "Do not check uniqueness of data".
At DSO do not arrive any duplicates and i would like to use the check of uniqueness in future, if there really arrive duplicate records.
@ Durgesh Gandewar: thx for the hint, but i also checked this website...
Regards,
Philipp

Similar Messages

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

Standard DSO - Write Optimized DSO, key violation, same semantic key

Hello everybody,
I'm trying to load a Write-Optimized DSO from another Standard DSO and then is raised the "famous" error:
During loading, there was a key violation. You tried to save more than
one data record with the same semantic key.
The problematic (newly loaded) data record has the following properties:
o   DataStore object: ZSD_O09
o   Request: DTPR_D7YTSFRQ9F7JFINY43QSH1FJ1
o   Data package: 000001
o   Data record number: 28474
I've seen many different previous posts regarding the same issue but not quite equal as mine:
[During loading, there was a key violation. You tried to save more than]
[Duplicate data records at dtp]
...each of them suggests to make some changes in the Semantic Key. Here's my particular context:
Dataflow goes: ZSD_o08 (Standard DSO) -> ZSD_o09 (Write-Optimized DSO)
ZSD_o08 Semantic Keys:
SK1
SK2
SK3
ZSD_o09 Semantic Keys:
SK1
SK2
SK3
SK4 (value is taken in a routine as SY-DATUM-1)
As far as I can see there are no repeated records for semantic keys into ZSD_o08 this is confirmed by querying at active data table for ZSD_o08 ODS. Looking for the Temporary Storage for the crashed DTP at the specific package for the error I can't neither see any "weird" thing.
Let's suppose that the Semantic Key is crucial as is currently set.
Could you please advice?. I look forward for your quick response. Thank you and best regards,
Bernardo

Hi Bernardo:
By maintaining the settings on your DTP you can indicate wether data should be extracted from the Active Table or Change Log Table as described below.
>-Double click on the DTP that transfers the data from the Standard DSO to the Write Optimized DSO and click on the "Extraction" Tab, on the group at the bottom select one of the 4 options:
>Active Table (With Archive)
>Active Table (Without Archive)
>Active Table (Full Extraction Only)
>Change Log
>Hit the F1 key to access the documentation
>
>===================================================================
>Indicator: Extract from Online Database
>The settings in the group frame Extraction From... or Delta Extraction From... of the Data Transfer Process maintenance specify the source from which the data of the DTP is extracted. For a full DTP, these settings apply to all requests started by the DTP. For a delta DTP, the settings only apply to the first request (delta initialization), since because of the delta logic, the following requests must all be extracted from the change log.
>For Extraction from the DataStore Object, you have the following options:
>Active Table (with Archive)
>The data is read from the active table and from the archive or from a near-line storage if one exists. You can choose this option even if there is no active data archiving process yet for the DataStore object.
>Active Table (Without Archive)
>The data is only read from the active table. If there is data in the archive or in a near-line storage at the time of extraction, this data is not extracted.
>Archive (Only Full Extraction)
>The data is only read from the archive or from a near-line storage. Data is not extracted from the active table.
>Change Log
>The data is read from the change log of the DataStore object.
>For Extraction from the InfoCube, you have the following options:
>InfoCube Tables
>Data is only extracted from the database (E table and F table and aggregates).
>Archive (Only Full Extraction)
>The data is only read from the archive or from a near-line storage.
Have you modified the default settings on the DTP? How is the DTP configured right now? (or how was configured before your testing?)
Hope this helps,
Francisco Milán.

Is a DTP mandatory in order to load into Write-optimized DSO ?

I'm wondering if a DTP is mandatory in order to load data into a WO-DSO.
Reason: in BI7 i have a 3.x load process of order item data:
2LIS_11_VAITM -> Transfer Rules -> Comm.Area -> Update Rules -> standard ODS.
I now wanted to load the same data from 11_VAITM into a WO-DSO. I actually simply created the WO-DSO using the template of the standard ODS. THis means that the key fields of the WO-DSO are Request#, Datapak-is and Record#. The semantic key is identical to the key used in the standard ODS.
I then created the same Update Rules from the InfoSource goint into the new WO-ODS and last but not least I simply changed the InfoPackaging saying that the data should be now loaded into both the standard ODS and WO-DSO.
2LIS_11_VAITM -> Transfer Rules -> Comm.Area -> Update Rules -> standard ODS
|-> Update Rules -> WO-DSO
What happened is quite annoying and nor understandable right now. Using this process I always get only one record into the new WO-DSO (it's always the first record of the data flow), not more. The PSA clearly shows me all the records with different record-numbers per request/datapak, therefore the key elements of the WO-DSO are clearly unique.
However, as there is always only one record appearing the new WO-ODS, I'm really wondering if the overall process isn't correct at all and that I actually need a DTP to load into WO-DSOs.
Am I right or are there other ideas related to my problem ?
Thanks

As far as I understand in order for you to use transformations, you need to use DTP. Infopackages will not work.
But iyour case u are using update rules, then it should work.
But because the WOD is a new technology, you need to only use DTP to load from PSA may be.

Duplicate Error while loading data to Write Optimized DSO

Hi,
When i do a dataload for Write Optimized DSO, I am getting an Error as "Duplicate Data Record Detected". I have Sales Document Number, Fiscal Year Variant & Billing Item as Semantic Key in the DSO.
For this DSO, I am getting data from a Test ECC system, in which most of the Sales Document Number column is Blank for this Datasource.
When i go into the Error Stack of the DSO, all the rows whichever has Sales Document number as Blank are displayed. For all this rows, the Item Number is 10.
Am i getting this Duplicate error as the Sales Document Number is Blank & Item number is 10 for all of them? I read in Threads that Write Optimized DSO doesnt care about the Key Values, it loads the data even if the Key values are same.
Any help is highly appreciated.
Regards,
Murali

Hi Murali,
Is the Item Number a key field ?
When all the key fields are same then data gets aggreagted depending on the setting done in the transformation for the key figures. These 2 options for key figures are :
1. Add up the key figures
2. Replace the key figure
Since the Sales Document No is blank and Item Number is same then their is a possibility that the key figures for these records might get added up or replaced and thus due to this property of SDSO it might not be throwing error.
Check the KF value in the SDSO for that Sales Doc No and Item No. and try to find out what is the value for KF. It may have addition of all the common data fields or the KF value of last common record.
Regards
Raj Rai

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

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

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 ?

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

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.

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.

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.

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]

DataLoad into Write-optimized DSO with DTP and semantic groups

Similar Messages

Maybe you are looking for