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,

Similar Messages

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.

DSO Key Fields Deisgn

Hi Experts,
I have Sales Schedule data( DSO ) and Delivery Item data( DSO ). I would like to combine this two DSO into one new DSO in order to get the Open Order Quantity ( Order Quantity - Delivery Quantiy ).
Fields in Sales Schedule DSO are
Sales Document ( Key Field )
Sales Docment Item ( Key Field )
Schedule Line ( Key Field )
Material Avail Date ( Data Field )
Order Quantity ( Key Figure )
Fields in Delivery Item DSO are
Delivery Number ( Key Field )
Delivery Item Number ( Key Field )
Document number of the reference document ( Data Field ) which is refered to the field Sales Document in 1st DSO
Item Number of the reference document ( Data Field ) which is refered to the Sales Document Item in 1st DSO
Delivery Quantity ( Key Figure )
I would like to create new DSO based on the common fields Sales Document (DSO1)= Document number of the reference document ( DSO2)
and Sales Document Item Number ( DSO1) = Item Number of the reference document (DSO2) in the both DSOs.
I required feilds like Sales Document, Sales Document Item, Material Avail Date, Order Quantity and Deliver Quantity ( Some other fields which are not mandatory ).
Would like to create new DSO on top of two DSOs, please suggest me what are the Key Fields and Data fields should be in the new DSO.
Your quick help is really appreciated.
Thanks
Robert.

Hi Robert,
Define the key as a combination of the keys of both DSO:
Sales Document ( Key Field )
Sales Docment Item ( Key Field )
Schedule Line ( Key Field )
Delivery Number ( Key Field )
Delivery Item Number ( Key Field )
Map the sales doc from the delivery to the key as well.
This will ensure you have a unique key and your data will be aggregated correctly when reporting.
Cheers,
Diego

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

DSO - Key Fields and Data Fields

Hi
Do we need at least one data fields (assigned at least one object to data field at DSO)?? or to create update rule to load data to DSO??
Because I am trying to load data with out any objects at data fields or unable to create update rule - all because, at least I should have one object in data fields - right?? pls clarify this.
Thanks.

Hi Raju,
Yes you are right in understanding this.
-Vikram

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

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

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

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

What key fields should i set in DSO extracting data from 2LIS_02_ITM

hi experts
i extract data from 2LIS_02_ITM into a DSO, i know the DSO isn't a must, becoz the 2LIS_02_ITM delta type is ABR, but i want to keep the info in change log.
so, what the key fields should i set in the dso? just ebeln and ebelp is enough?
hunger for ur advice and thanks a lot!

If you extract ITM toa DSO you cannot maintain a log of every change....the data will come ....but when the data must be activated the reference of the ebelp ebeln will remain only a single record....if you want to maintain all the data you must create another field in extractor with you can difference all the changes for one single ebelp ebeln...
Regards

Key fields and data fields in a DSO ??

i have a question regarding key fields and data fields in a Standard DSO...
i am using 2 datasources to build a open sales report 2LIS_11_VASTH and 2LIS_11_VASTI i am pulling in data from these 2 data sources to a DSO and i am wondering what infoobjects should be in the key fields and data fields .....does this reflect back to table VBUK and VBUP tables and does the key field in the DSO have to be the key fields in VBUK and VBUP tables ???? or what really should be included as key fields and data fields ????
please help....

If you look at the various SD tables, VBELN and POSNR are commonly used as the document number and document line item.
For VBAP and VBUP, it's referring to the Sales Order Line Item with the columns VBELN and POSNR as the key for both tables. However, if you look at the LIPS table, which is the Delivery Line Item table, it too has VBELN and POSNR as the key. Likewise, the VTTP table, which is the Shipment Line Item table, also has VBELN and POSNR as the key.
While using RSOSFIELDMAP as a map is a fairly good "rule of thumb", it still needs to be used with a level of skepticism.

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

How many key fields can we have in a DSO?

Hi,
how many key fields can we have in a DSO.is it 16 or any number of key fields can be used? If only 16 are allowed pls let me know how to add more key fileds (my requirement is 21 keyfields) .
Thanks in advance,
Praveen

Hi,
Thanks for the reply. Pls let me know the procedure to include 5 more key fields because i have 21 keyfields which i have to use.
Thanks&Regards
Praveen

How many key fields can we maintained in dso or ods

HI
pls let me know how many key fields can we maintained in DSO or ODS.
Thanks and Regards.
ASIM.

Hi,
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.
Regards,
Marasa.

DSO Key Field Design

Similar Messages

Maybe you are looking for