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

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

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

  • 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

  • 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

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

  • 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

  • Reg Data fields in DSO

    Hello SAP Guru's!!!!
    I have some doubt on maximum number of data fields in DSO. I gone through so many threads on SCN, but could not clarify my doubt.
    The max no of key fields in DSO is -- 16
    Max no of data fields in DSO is --749.
    But i read in some of the scn documents  a table can have maximum 256 columns .
    DSO is also like a two dimensional table which can also have the same properties of a two dimensional table.
    if the above statement of mine is correct.. the number of columns in a DSO is 256 columns = 16(primary key)+240 (data fields--non key fields)
    but how come 749 data fields (max) will be there ? if it is so ... the max no of  fields will be  749+16 = 765.
    I need some clarification on this ....
    Awaiting for your responses!!!!
    regards,
    vamshi

    Hi Rajavamshi,
    For DSO:
    1. See for Standard DSO we have Key fields & Data Fields will be there
    2. Key Fields will store only Characterisitc Info Objects, maximum no.of characteristic info object we can add here was 16
    3. But in Data fields we can add both Characterstics & Keyfigure infoobjects, Max of 749 data fields we can add here.
    4. Atleast one field should be there in either Key fields & Data fields.
    For InfoCube :
    1. Info cube structure will be having the 16 Dimensions and the Key Fields.
    2. In that 16 Dimensions 13 User defined and the 3 pre defined dimensions.
    3. One user defined Dimension will maximum can hold 248 Characteristics Info Object, not the Keyfigure Info Object here.
    4. But the Key Fields here will store maximum will hold 233 Key Figure Info Object.
    Thanks..!!
    Regards,
    Harish. K

  • Identify key fields and data fields

    Hi
    i have datasource 0co_om_cca_9 .
    i want build 1 DSO, how can i identify what are key fields and data fields to build DSO based on that datasource.

    Hi sunnel,
    The DSO are like 2-D database tables.
    We use the technical keys here in counterpart to the business keys in Infocubes.
    The key fields are the one based on which the records are identified uniquely in the database table.
    And the data fields are the ones which are aggrgated or summarised or overwritten based on the value in key filed.
    For example:
    The ID no.s of the employees will be unique and it can be used as a key field.
    The feilds like the Salary taken by the employee every month :"SALARY"
    and the no. of leaves they taken: " NO. OF LEAVES" can be used as data fields.
    So that the salary or the leaves taken by a particular employee can be aggregated based on her/his ID no.
    The key fields in DSO doesnty mean Key figures.The key field means any unique key or a key based on which the records are sorted in the DSO
    And key figures are the data fields.Some of the Characteristics can also be data fields in DSO.
    Please give points if u r satisfied wit the information
    Also let me know if u hav any doubt and if any thing is wrong.
    Regards,
    Kalpana M

  • DSO - What key fields and data fields in dso

    Hi experts,
    I need to create a dso in between the cube and 2 data sources(2lis_11_vaitm, 2lis_12_vcscl) to stage the data. My question is: what key fields and data fields to choose for the dso? is there a standard dso to copy? please explain in detail the model to set up, whether to connect both the ds's to dso and then to cube or one ds to dso and the other to the cube. more details will help.

    Check this for standard DSO:
    http://help.sap.com/saphelp_nw04/helpdata/en/43/fcdc387f34384f94c3227baf3837a8/content.htm
    Thanks...
    Shambhu

  • Key Fields & Data Fields in DSO.

    In Standard DSO, Maximum how many number of key fields and data fields we can enter in one DSO?
    For e.g : In Cube Char - 248      KF - 233
                  In DSO Key Fields - ?   Data Fields - ?
    Regrards,
    Nithi.

    Hi Nithi,
    Since Key fields are decide by us we can add according to our requirement.
    Key fields can only be 16 you cannot exceed this. but if you have more key fields, you can combine fields using a routine for a key field
    Max Data Fields - 749 data fields can be added in a DSO.
    Warm regards
    Gokul

  • DSO - Key Field doubt?

    Hi All,
    I want to know the functionality of the Key Field in the DSO.
    I know based on the Key Fields(Primary Key) data is pulled to DSO, but please explain me the below scenario
    E.g
    I have 3 records in the Extractor( Generic) and i am pulling data to DSO - Full load.
    Material                 Qty       Date
    100                       20        1-Jan-2010
    100                       30        5-Jan-2010
    100                       10        10-Jan-2010
    In DSO i have only one Key field called 0MAT_NM (Material Number), but i have 3 records in the Extractor , shown above.
    Now my Question is
    On what basis data will be pulled to DSO?
    Whether latest date records will be pulled to DSO or let me know correct method? because i have got material no 100
    but date and Qty is different (means one time it is taking Qty - 30 and date as 1st Jan 2010, other run it is taking differnet).
    Please clear my doubt.
    Regards,
    Nithi.

    in your dso you can have one record per key. keyfigures will be in addition or overwrite option. if in "addition' the value will be the sum of all the values for a given key. in 'overwrite', you'll only keep the last record written to the dso; char are always in overwrite, so you'll keep the last record written to the dso
    M.

Maybe you are looking for

  • DVD Drive Broken -Can I install from another Mac?

    Hello All A friend has a MacMini with a broken DVD Drive. He also has a MacBook, which has a working drive. He is still using Leopard and wants to upgrade to Snow Leopard. Can he upgrade the MacBook, then upgrade the MacMini using the MacBook? If so,

  • Default values for fields in infotype 0017

    Is there any way to set default values for fields in infotype 0017? Maybe a feature? I'm thinking about defaulting values based on pay scale group. Thanks before.

  • JDBC Connector : pool gets depleted

    Hi, we are currently working with SAP EP 6.0 SP2 and trying out some development work with the connector framework. We are writing a component which uses the CF to retrieve information from a Microsoft SQL Server 2000. The portal component works, we

  • Problem with setVector & Setdatabufferarray

    I am using occi c++ api interface The type is a table of number index by binary integer. I am trying to use "type created inside a package" to pass as a last argument to setVector() , which will be my OUT parameter. But the error I am getting is "OCI

  • Updates for iPhoto in Mountain Lion, on a work computer.

    Updates for iPhoto in Mountain Lion are only available from the App Store. I'm on a new iMac which is a work computer, owned by my employer, and don't want to enter my credit card details.  The brand new iMac came with iPhoto installed, so I don't se