New Key field in DSO

Hi BI Experts,
I want to add a new key field in a DSO.This infoobject is in Data field now.
The DSO contains data now.
Can the new key field be added without deleting data from the DSO?
Thanks

Hi ,
If you want to take datafield as keyfield,firstly you have to delete the data.
Before deleting the data use datamart and upload it into different data target.
After wards you can change the infoobject from data fields to keyfields.
But be aware of that transformation will also be disturbed with these changes.
Regards,
Praveena.

Similar Messages

Key fields of DSO

Hi Experts,
I have a issue with DSO.We extracted data from R/3 in to BI and send it in to DSO.We are getting data from R/3 to PSA with right records with init load.But from PSA to DSO,we are getting duplicate records for 2 invoices.We have 2 invoices say xxxx01 and xxxx02 have problems in DSO.
XXXX01 has 3 items(10,20,30) created on April2008 with billing Doc type A
XXXX02 has 2 Items(10,11) created on April2008 with billing Doc type B
But in DSO we are getting extra Item record for each of document
i.e XXXX 01 has 4items(10,20,30,10).3 items(10,20,30) created on April 2008 with billing Doc type A.One Item(10) created on June 2008 with billing Doc Type C(this is not in R/3 so This extra one).
XXXX02 has 3 items(10,11,10) .First 2Items(10,20) are original ones created on April 2008 with Billing type B.One extra Item(10) created on June 2008 with Billing Doc Type C(this Item is not in R/3).
We have key fields in DSO is Sales Document,Material,Billing Item,Fiscal variant.I din't add Document Type,Document Category,Calender day in Key Fields but they are in Data Fields.
I am not sure how can I overcome this issue either adding Document type ,Calender day,Document Category in DSO or Put some fields in Semantic group.
Please advise me and tell me some possible solutions.
We ran setup tables with init and ran infoPackage and ran delta Infopackage too in Testing box.If I change the design in Dev box and Transport in to the test box,Hope I need to fill the Setup tables again right.Please advise me.
Thanks,
Ran.

Hi,
Use this key fields and sure it will solve.
Doc no.,Doc Item. for Orders
Bill Item and Bill no. for Invoices
Delivery No. and Delivery item no. for deliveries.
Moreover check ur transformations once.
Cheers,
shana

Add a new key field in an InfoObject

Hi all,
I have to add a new key field in a standard InfoObject (0vendor) in order to extract data correctly from a table in R3 which has both the vendor and the plant as keys.
Doubts:
1. the 0vendor InfoObject is already used in several InfoCubes
2. it contains data
3. we have another object built with reference to 0vendor
Any problem with the existent InfoCubes and queries if I change the structure of this InfoObject?
Have I got to delete data on it first?
any problem on the object built with reference to 0vendor?
I have just thought of updating the object 0vendor (this would avoid lots of substitutions and lot of work) instead of developing a brand new object..
Do you agree with this kind of solution or would you do something different?
Thanks
Elisa

Hi Elisa,
"In R/3 the vendor sub-range is blank and we use only one Purch Org, so no matter."
This is OK but remind that it shall remain like this ALWAYS; because if you design your model with these assumptions and later you start getting sub ranges and/or a second P.O then you can forget your model...
Replacing 0VENDOR by ZVENDOR completely will depend on your requirement; I don't know which content you are using but you should try to keep 0VENDOR as such because ZVENDOR will be compounded with 0PLANT and that's not the same... (e.g. the key will be displayed like "PLANT/VENDOR" in reports unless you drilldown the PLANT in front of ZVENDOR... your users may perhaps not appreciate...)
In this matter, how are you going to proceed?
- fill the vendor ID in ZVENDOR and have 0PLANT as compounding key? In this case you'll have to add 0VENDOR attributes in ZVENDOR as well. With this scenario you will end with redundant data since attributes for 0VENDOR will be the same for each combination 0PLANT/ZVENDOR.
- wiser: have 0VENDOR and 0PLANT both in the compounding key. This way you could have ZVENDOR key CHAR1 and leave it empty (it would be a "dummy" key you wouldn't use in reports)
The good thing here is that you don't have to replicate your 0VENDOR design in the ZVENDOR. the bad thing for you is that you NEED to keep both IObjs; thus manage your DIM issue.
Your approach to fill the cubes is absolutely right! What are the sizes of your cubes?
You should take this opportunity to check you cubes datamodel:
- are the dimension well deisgned? (run report SAP_INFOCUBE_DESIGNS in order to see the cardinality of your DIMs). I am sure this can be improved.
- are the cubes partitioned? Every cube should be partitioned for performance reasons.
- if the cubes are huge, wouldn't it be good to do a logical partitioning? E.g have one cube per year and a multicube on top...
Finally use dimension number range buffering when loading data into an empty cube and other techniques like dropping all indexes in order to speed up your load process and minimize reporting downtime. If your reports are based on multicubes and your model is not too complex you could even keep the copy cube instead of moving your data back to the original; you would then just have your multicube transport to make the switch of the new model available for reporting...
hoping this help you to go with the right path...
regards,
Olviier.

New key field creation in between of the 2 existing key fields?

Hello,
I have a custom table with 3 key fields.
Now because of business requirements, we need to add one more key field IN BETWEEN the 2nd key field and 3rd key field of that table, if we create a new key field in the middle of existing 2 key fields, do we loose the data in the table, pls. let me know.
And also do we need to take any precautionary steps to go smoothly?
Thank you

Think about it logically, if you add a key field, how would you lose data, since the primary key is now longer than before? Only if you remove key fields, you might lose data during table adjustment due to duplicate primary keys.
Make sure all other field names remain unchanged.
Try it in dev system first, check the results. For even more confidence, why not download the data first as a backup, "just in case".
Thomas

Implications of adding new key fields to existing table

Hi All,
I have searched forum regarding this. But didn't find exact answer.
We are planning to add new key fields to existing Ztable. I want to know the implications of this.
I have checked the where used list of table and found no impact. Only one point is making me to think again and again.
If we add key fields to existing table then we have to adjust the table from SE14 to activate it. But this adjustment doesn't ask for TR.
So if i release my TR, entries in other systems will also be adjusted accordingly??? Business is OK with the new fields values to be blank for existing entries.
Thanks,
Vinod.

Yes the data in transported systems will also be adjusted. If this table contains too much data make transport at late hours because it will take long and table can't be used while it's adjusted. In this adjustment process data is copied to a temporary table and moved back to original table using move-corresponding command after key added. There will data loss if you remove a key or key fields field length but in your case it shouldn't be a problem.
Edited by: Gungor Ozcelebi on Jul 2, 2009 9:18 AM

Difference between semantic and key fields in DSO

Hello All,
Please help me in understanding about difference between "Key fields" and "Semantic key" in write optimize DSO.
thanks

Hi,
you dont have key fields in write-optimized DSO, key fields terminology is forin standard DSO.
And semantic key is used in write-optimized DSO.
As we know standard DSO is a flat structure similar to transparent tables that we have in R3/ECC system with key fields (combination of values which needs to be unique).
Now, 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 there are standard key fields 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.
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/e3/e60138fede083de10000009b38f8cf/frameset.htm

Data fileds and key fields in DSO

Can any one explain what exactly difference between data fileds and keyfields in DSO or the concept of these two
And how to know which fields should be assigned to data filed or key field
with regards,
musai

Hi Musai,
Let me take an ex. Say you have 3 fields A, B & C. Let us assume 'A' is keyfield, 'B' & 'C' are Datafields.
Lets assume the PSA data is :
A             B              C
001      Musai        89.9
002      Musai        89.9
003      Pavan       75.00
So when you load the data to DSO, since all the keyfield values are unique (001,002,003), all the records will get loaded to DSO.
But If PSA data is :
A             B              C
001      Musai        89.9
001      Musai        85.7
003      Pavan       75.00
Only 2nd & 3rd rows will be loaded to DSO since 1st & 2nd row have same value for keyfield (001). So 1st row gets overwritten(or summation depending on what is the setting in Transformation rule for C considering C is Keyfigure) by 2nd when you load to DSO. 3rd row doesn't have any problem. So that will go as it is.
Also please note that we cannot use Keyfigures as keyfield.
Hope it is clear now!
Regards,
Pavan

Data Fields & Key Fields IN DSO

Hi Guys,
Can any one tel me what exactly key field holds & Data field hold in DSO.
Thanks,
Venkatesh

Hi,
A DSO serves as a storage location for consolidated and cleansed transaction data or master data on a document (atomic) level. This data can be evaluated using a BEx query.
A DSO contains
Key fields (such as document number, document item) and data fields that, in addition to key figures, can also contain character fields (such as order status, customer). The data from a DataStore object can be updated with a delta update into InfoCubes (standard) and/or other DataStore objects or master data tables (attributes or texts) in the same system or across different systems.
Key fields : It will contains both Chars and KeyFigures.
Data Fields : Based on this i.e. the charecterisctics which you will keep in this Data Fields, the DSO will over write the Data in DSO.
Overwriting functionality will works based on Data Fileds.
http://help.sap.com/saphelp_nw2004s/helpdata/en/f9/45503c242b4a67e10000000a114084/content.htm
Thanks
Reddy

Is it good to have more key fields in DSO

Hey Guys ,
is it good to have more key filds in dso , and how will it impact the performance of Loading/Access.
Anurag

The objective of using key fields is to recognize each data record uniquely. So, if we can achieve this by small number of key fields we should go for that.
        Technically if we use many key fields that will create data redundancy. Besiseds that primary index will be bigger.
        Also we cannot use more than 16 key fields.
     Assign pts if helful
       thanx.

Limitation of Key Fields in DSO

Hi, can anybody tell me the max number of key fields that a DSO can have?
Thanks,
Manasa.

in ODS u can maintain--
You can create a maximum of 16 key fields
You can create a maximum of 749 fields
You can use 1962 bytes (minus 44 bytes for the change log)
You cannot include key figures as key fields

Key fields in DSO

HI experts,
I have the requirement to create DSO with Material,Plant,Usage,BOM,Alternative,BOM category,Counter,Valid From,BOM status,Base unit,Base Quantity fields. I am not involved in the functional part. could you please tell me which fields can take in the key part???
Regards,
KP

Hi Kundan,
What is the data source that you are using to laod the data to DSO?
You can fidn the key fileds with the help of data source. or from the source table if you are not having Data source.(there will be a screw symbol for the key fileds).
you can use material, plant, BOM as key fileds.
Regards
KP

DSO Key Field Design

Hi Gurus,
We are using DSO with Billing doc ,Billing item and Material Id as a Key fields in DSO.But I found Billing doc ,Billing item as a key fields in Tables VBRP VBRK(as we are using Billing dataSource) and I didn't find Material no as a Key field in those 2 Tables.Do we need to keep Material no as a Key Field in DSO.What aspects do I need to consider before taking any decission regarding material no as a Key field in DSO. Please can any one throw light on this topic.
Thanks,
Suryam.

Hello,
I am not sure, how it would work but you can try for yourself by changing a material in the Billing item line and loading it into your DSO with material as a key. But I am still confused why would you need material no. as Key in your DSO when the lowest granular level in source itself available is line item. In other words, there is no positive effect, I could see adding material as a key fields. Yes there are chances, it may effect negatively (it may not overwrite the changes in R3 as keys are different in both places - need to check this).
Thanks,

DSO Key Fields

Hi Experts,
Can i use KEY FIGURES as KEY FIELDS in DSO
and
What is MAXIMUM no of Key Fields can i have in a DSO
Thanks

Hi
key figures are the amouts required for reporting, say you are working on sales data, then look at the report what amounts are required to get all the columns / key figurs in the report.
Granularity: is the level of detail you require, some times you only require the sales document level, other times at the sales document item level.
Unique identification of record: uniqueness of a record in ods is maintained by how you define the key fiedls in the ods. key fields in the ods are equal to the primany indexes on a table. eg: if you want the grain to be on the sales document level, then do not keep the item in the key fields. then probably company code, sales org, sales document and fiscal year.
affect on one level up the ods:
if you require item level data in the cube, then you need to keep the sales doc item in the ods key field.
There has to be at least one key field and one data field.
Additional restrictions:
-         You can create a maximum of 16 key fields (if you have more key fields, you can combine fields using a routine for a key field (concatenate).)
-         You can create a maximum of 749 fields
-         You can use 1962 bytes (minus 44 bytes for the change log)
-         You cannot include key figures as key fields
Assign points if it helps
Regards,
Sumit

How to add a new data element for existing table filed(Primary key field)

Hi Experts,
How to add a new data element for existing table field(Primary key field)
For this filed ther is no foreign key relation ships and even check table.
while activating table it is giving message like below.
can you help any one to solve this and wil steps to add new dataelement for existing primary key filed of a table.
Check table (NAMING SPACE/TABLE NAME(EX:/TC/VENDOR)) (username/19.02.10/03:29)
Primary key change not permitted for value table /TC/VENDOR
Check on table /TC/VENDOR resulted in errors
Thanks
Ravi

Hi,
Easiest way is to download the table eg into an Excel table (if possible) or text table. Drop the table from the database. Build your table with the new key field. Build the database table again and fill it.
You can do it also over the database into a new table. Drop the old one. Build the enhanced one and fill it. Afterwards drop your (temporary) table.
Maybe there are other ways, but this works.
Success,
Rob

Creation of key field in a database table

Hi All,
As per my requirement, i have to add few new key fields in an existing table.
Now total number of key fields are 17, but while saving this is giving me an syntax error stating 'According to SAA standard key fields cannot be more that 16'.
I s there any other go? i can not reduce the number of key fields.
Regards,
Pankaj.
Edited by: Pankaj Bist on Sep 5, 2008 3:24 PM

Hi,
In the se11 transaction,In the menu bar o like this.
Utilites-->Database Utility and the Press the button Activate and Adjust Database.
Note:
Make sure that you total data in the table to be downloaded into ur system.
As ctivate and Adjust Database makes data to be deleted.
Regards,
Rama.

New Key field in DSO

Similar Messages

Maybe you are looking for