on 01-10-2012 4:40 PM
Hi all,
I am loading 2LIS_02_ITM (Purchasing Document - Item Level) data to a write optimized DSO. I am still checking uniqueness of data. I am getting duplicate data record errors; however, the records don't appear to be duplicates because the difference is that the Reversal Indicator is checked (X) on some of the records that are failing. Why isn't this recognized?
Any suggestions for eliminating these errors with a write optimized DSO? What are the implications of checking the "do not check for uniqueness" option? I am afraid I will lose records - I need all invoice & goods receipt relevant records to be maintained.
Thanks
C
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
For Write optimized DSO, the system generates a unique 'Technical Key' and hence it is not necessary to define standard key fields for this type of DSO. However if you will define standard key fields for Write optimized DSO in 'Semantic Keys' then this will be considered while loading.
If you want all the records to be loaded to write optimized DSO then check the "Do not check for uniqueness" option. In this case it will not perform a check for uniqueness of data and It will load the records having the same logical keys and the "Duplicate record error" will be eliminated.
Thank you.
-Shreya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does "Reversal Indicator" is defined as key (Semantic Key) in W.O.DSO definition? If yes, u should move that to 'Data Fields'.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.