Do Not Check Uniqueness of Data in Write Optimised DSO

Hello,
I am working with write optimised DSO with already billion records in it. I have flag 'Do Not Check Uniqueness of Data' in Settings as checked(means it will surely not check for uniqueness of data). I am thinking of removing this flag off and activate the DSO again. I am willing to remove this flag as it will provide option of Req ID input in listcube on DSO and without this list cube will never return back with results.(I have to analyze aggregations)
I tried removing this flag and then activate DSO in production system with 17 million records which took 5 mins for activation (index creation). So maths says for a billion records activation transport will take around 6 hrs for moving to Production.
I am willing to remove this flag as it will provide option of Req ID input in listcube and without this list cube will never return back with results.
Questions:
How does this flag checks the uniqueness of record? WIll it check Active table or from the Index?
To what extent DTP will slow down the process of subsequent data load?
Any other factors/risks/precautions to be taken?
Let me know if questions are not clea or further inputs are required from my side.
Thanks.
Agasti

Hi,
Please go through the site :
/people/martin.mouilpadeti/blog/2007/08/24/sap-netweaver-70-bi-new-datastore-write-optimized-dso
As far as your ques are concerned... i hope above blog will answer most of it , and if it does'nt please read below mentioned thread.
Use of setting "Do Not Check Uniqueness of Data" for Write Optimized DSO
Regards
Raj

Similar Messages

Error while displying the data of Write-opt DSO

Hai SAP BI Gurus,
I have created Write-opt DSO with settings
"Do Not Check Uniqueness of Data" CHECKED
and data also loaded. Further If i try to "Display data" giving me the below dump.
Short text
    Field symbol has not yet been assigned.
What happened?
Error in the ABAP Application Program
The current ABAP program "GP08EBRNJU17FO7EUSU63XGV20Y" had to be terminated
because it has
come across a statement that unfortunately cannot be executed.
Error analysis
    You attempted to access an unassigned field symbol
    (data segment 26).
    This error may occur if
    - You address a typed field symbol before it has been set with
      ASSIGN
    - You address a field symbol that pointed to the line of an
      internal table that was deleted
    - You address a field symbol that was previously reset using
      UNASSIGN or that pointed to a local field that no
      longer exists
    - You address a global function interface, although the
      respective function module is not active - that is, is
      not in the list of active calls. The list of active calls
      can be taken from this short dump.
Any body can help me ... out if u face the same scenario..!
Thanks in Advance 2 Gurus...
Vijay

HERE IS THE DUMP
Runtime Errors         GETWA_NOT_ASSIGNED
Date and Time          06.05.2011 09:32:55
     Short text
          Field symbol has not yet been assigned.
     What happened?
          Error in the ABAP Application Program
          The current ABAP program "GP08EBRNJU17FO7EUSU63XGV20Y" had to be terminated
           because it has
          come across a statement that unfortunately cannot be executed.
     What can you do?
          Note down which actions and inputs caused the error.
          To process the problem further, contact you SAP system
          administrator.
          Using Transaction ST22 for ABAP Dump Analysis, you can look
          at and manage termination messages, and you can also
          keep them for a long time.
     Error analysis
          You attempted to access an unassigned field symbol
          (data segment 26).
          This error may occur if
          - You address a typed field symbol before it has been set with
            ASSIGN
          - You address a field symbol that pointed to the line of an
            internal table that was deleted
          - You address a field symbol that was previously reset using
            UNASSIGN or that pointed to a local field that no
            longer exists
          - You address a global function interface, although the
            respective function module is not active - that is, is
            not in the list of active calls. The list of active calls
            can be taken from this short dump.
     How to correct the error
          If the error occures in a non-modified SAP program, you may be able to
          find an interim solution in an SAP Note.
          If you have access to SAP Notes, carry out a search with the following
          keywords:
          "GETWA_NOT_ASSIGNED" " "
          "GP08EBRNJU17FO7EUSU63XGV20Y" or " "
          "INITIALIZATION"
          If you cannot solve the problem yourself and want to send an error
          notification to SAP, include the following information:
          1. The description of the current problem (short dump)
             To save the description, choose "System->List->Save->Local File
          (Unconverted)".
          2. Corresponding system log
             Display the system log by calling transaction SM21.
             Restrict the time interval to 10 minutes before and five minutes
          after the short dump. Then choose "System->List->Save->Local File
          (Unconverted)".
          3. If the problem occurs in a problem of your own or a modified SAP
          program: The source code of the program
             In the editor, choose "Utilities->More
          Utilities->Upload/Download->Download".
          4. Details about the conditions under which the error occurred or which
          actions and input led to the error.
     System environment
          SAP-Release 701
          Application server... "sapdw1i2"
          Network address...... "10.51.11.41"
          Operating system..... "Linux"
          Release.............. "2.6.16.60-0.58.1-smp"
          Hardware type........ "x86_64"
          Character length.... 16 Bits
          Pointer length....... 64 Bits
          Work process number.. 3
          Shortdump setting.... "full"
          Database server... "chrbl170"
          Database type..... "ORACLE"
          Database name..... "DW1"
          Database user ID.. "SAPSR3"
          Terminal.......... "INA50001"
          Char.set.... "C"
          SAP kernel....... 701
          created (date)... "Oct 31 2010 21:31:41"
          create on........ "Linux GNU SLES-9 x86_64 cc4.1.2"
          Database version. "OCI_102 (10.2.0.2.0) "
          Patch level. 117
          Patch text.. " "
          Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
          SAP database version. 701
          Operating system..... "Linux 2.6"
          Memory consumption
          Roll.... 16192
          EM...... 29328936
          Heap.... 0
          Page.... 114688
          MM Used. 1220192
          MM Free. 2967056
     User and Transaction
          Client.............. 500
          User................ "S33Z5X"
          Language key........ "E"
          Transaction......... "RSA1 "
          Transactions ID..... "4DB9F0087F7A43ADE10000007F000002"
          Program............. "GP08EBRNJU17FO7EUSU63XGV20Y"
          Screen.............. "GP08EBRNJU17FO7EUSU63XGV20Y 1000"
          Screen line......... 3
     Information on where terminated
          Termination occurred in the ABAP program "GP08EBRNJU17FO7EUSU63XGV20Y" - in
           "INITIALIZATION".
          The main program was "GP08EBRNJU17FO7EUSU63XGV20Y ".
          In the source code you have the termination point in line 0
          of the (Include) program " ".

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

ACTIVATION OF DSO error: write optimise dso -

I have taken two info objects 1. customerid and 1. price
created data source and done activation
created DSO with WRITE OPTIMISE DSO (ticked the below line also) and after clicking activation, getting error message
info object 0request is not available in version A
info object 0datapakid is not available in version A
info object 0record is not available in version A
inconsistencies found while checking dso object aaa
activation failed
help please
S madhu

my basic objective is to load data covering characterstics and key figures(I have no idea whether to take write optimise or std etc)
into dso
for this I have done the following
1. infoarea
2. info ob cat for char and key
3. info objects 1. customerid --- char (no additional attribute)
2. price --- key (USD)
3. source system
4. ac and DS
5. activated the ds and preview data---- ok
6. created DSO and added the two info objects customer id under symatic key and price under data fields
version showing as in process
then activated and noticed that its not activating and showing as object status not activated.
1. If this is wrong, pl tell me the steps in this regard, if possible step by step screenshots
2. without activation, can I go ahead for the remaining steps
regards
madhu

System is not checking Account assignment data in shopping cart

Dear Experts,
We are implementing SRM7 with SP06. We are using extened classic scenario. Recently we have noticed that system is not validating account assignment data at shopping cart level and creating purchase order in SRM, however at the time of PO transmission to backend system it is failing.
Does any one has faced this issue?If yes help me how to resolve this issue.
Thanks in advance.
Umakanth

Hello Umakanth,
Could you check if in your settings for Define backend system customizing ( BBP_BACKEND_DEST table), option "realtime backend validation of FI data" is set or not ?
Regards.
Laurent.

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

Delta in Write optimised DSO

How delta datas are handled when loading the write optimised, transactional DSO(sice they don't have any change log tables)?

Hi,
Delta Administration:
Data that is loaded into Write-Optimized Data Store objects is available immediately for further processing. The activation step that has been necessary up to now is no longer required. Note here that the loaded data is not aggregated. If two data records with the same logical key are extracted from the source, both records are saved in the Data Store object, since the technical key for the both records not unique. The record mode (0RECORDMODE) responsible for aggregation remains, however, the aggregation of data can take place at a later time in standard Data Store objects. 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.
the matter is taken from one of the recent weblogs in BI forum.Check for more details on WO-dso.
SAP NetWeaver 7.0 BI: new DSO " Write-Optimized DataStore"
The specified item was not found.
cheers
Sunil

Duplication Error while loading data in write optimized DSO

Hi Experts,
I have an issue.In BI7 I'm trying to load the data in a WRITE OPTIMIZED ODS from the controlling data source 0CO_OM_CCA_10. I'm getting the data properly in PSA, but while loading it into my WODSO i'm getting the duplication error although my keys fields and data fields are properly placed in my data target(WODSO).
pls let me know what is the solution to load it successfully.
Thanks in Advance.
Amit

Hi,
thanks for your reply
I'm getting this error message:
Diagnosis
    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: GWFDSR02
    o   Request: DTPR_4BA3GF8JMQFVQ8YUENNZX3VG5
    o   Data package: 000006
    o   Data record number: 101
Although i have selected the key fields which identifies unique record,then also i'm getting the duplication error.
Even i have reffered to the BI content for this data source and found that it has the same key fields as of mine.
Debjani: i need unique records without duplication and i'm doing a full load in DTP.
What is to be done pls help
Thanks in advance.
Edited by: Amit Kotwani on Sep 26, 2008 10:56 AM

Is Write optimised DSO is delta enabled?

Hi friends,
I have seen in this forum, some of them are saying they are doing Delta extraction from W/O DSO. Since it doesnot have change log table how it is possible.
Can one please clarify?
Thanks,
sudha

Hi,
It is request based.
When you update data into the connected InfoProviders, the system only updates the requests that have not yet been posted
Refer
http://help.sap.com/saphelp_nw04s/helpdata/en/b6/de1c42128a5733e10000000a155106/frameset.htm
Hope this helps.
Thanks,
JituK

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

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

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

Data archiving for Write Optimized DSO

Hi Gurus,
I am trying to archive data in Write Optimized DSO.
Its allowing me to archive on request basis but it archives entire requests in the DSO(Means all data).
But i want to select to archive from this request to this request.(Selection of request by my own).
Please guide me.
I got the below details from SDN.Kindly check.
Archiving for Write optimized DSOs follow request based archiving as opposed to time slice archiving in standard DSO. This means that partial request activation is not possible; only complete requests have to be archived.
Characteristic for Time Slice can be a time characteristic present in the WDSO, or the request creation data/request loading date. You are not allowed to add additional infoobjects for semantic groups, default is 0REQUEST & 0DATAPAKID.
The actual process of archiving remains the same i.e
Create a Data Archiving Process
Create and schedule archiving requests
Restore archiving requests (optional)
Regards,
kiruthika

Hi,
Please check the below OSS Note :
http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bw_whm/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d31313338303830%7d
-Vikram

Error occurs while activating a 'Write Optimized' DSO.

I am getting error " There is no PSA for infosource 'XXXX' and source system 'XXX' while activating a newly defined DSO object.
I am able to activate a Standard DSOs, however the error occurs while activating a 'Write Optimized' DSO

Hi,
For write optimised DSO, check if you have tick the uniqueness of the records. If you check that and if there are two same records coming from source in one go, then you will get error
From SAP help
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.
Thanks
Srikanth

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.

Do Not Check Uniqueness of Data in Write Optimised DSO

Similar Messages

Maybe you are looking for