0CALDAY as a key field

Hello All,
I made some changes to tansformation for calculation of some keyfigures from one DSO to another. The changes were calculating the keyfigure correctly. But in the target DSO the 0CALDAY is selected as a key field, due to which the records from the past are getting deleted. How can make sure that the deletion doesnt happen.
Thanks in advance.
Regards,
NK

Hi,
Addition of extra key field will not delete or overwrite any records from the DSO for eg. if you have A,B, C as key fields in source and in target you have A,B,C & date then in target you will have more records in target DSO than source.
Give more details about your scenario, If you are loosing some data then you might be missing some field from key field.
Regards,
Durgesh.

Similar Messages

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

No key field found for creation of DataSource - Classification Datasource

Hello,
While trying to create a clasiffication datasource based on 0PLANT_ATTR, when i assign a characteristic and push the DataSource button, i get the following message:
No key field found for creation of DataSource
Diagnosis
During generation of a classification or configuration DataSource, only those key fields for the object table (field "Obj.Tabelle") that are already present in the basis DataSource transferred to the extract structure. This is the case when none of the key fields of the object table were found in the structure of the basis DataSource.
System response
A DataSource cannot be created without key fields. The action was cancelled.
Procedure
Check whether you have selected the correct basis DataSource and object table. For more information, please see SAP Note 569849.
Do you know what can be the problem?
Thank you and regards

Hi Alberto,
plants are a special case. The key which is used for the classification
of plants (object type BETR) is not the same as the key which is used in
datasource 0PLANT_ATTR.
BETR has key LOCNR (Site). That's a customer related to a plant. The
customer number will be extracted in field LOCNR.
0PLANT_ATTR extracts the plant in its key field WERKS.
Transaction CTBW and the generic extraction program for classifications
don't know the relationship between LOCNR and WERKS. So they cannot map
them.
I do recommend a solution which would add the mapping between
LOCNR and WERKS:
1. Create please the classification datasource as intended, but use
datasource 0RT_LOC_MGR_ATTR as basis datasource. It's the only
datasource of the content where LOCNR is a key field. So
0RT_LOC_MGR_ATTR is used as a dummy here, to allow transaction CTBW to
create the classification datasource. It's not necessary to extract
data with datasource 0RT_LOC_MGR_ATTR.
2. Extend please the extract structure of the created classification
datasource. Add please field WERKS using component type WERKS_D. Make
this field visible.
3. Fill field WERKS in the extractor user exit EXIT_SAPLRSAP_002. WERKS
can be read from table KNA1 by using the customer number extracted to
LOCNR to select on field KNA1-KUNNR.
4. Transaction CTBW_META on the BW system isn't able to append the
characteristics from the classification datasource to infosource
0PLANT, because the keys are different. So create please a new info
source with CTBW_META. This allows CTBW_META to create the info objects
for the characteristics used in the classification datasource.
5. Add please the characteristics used in the classification datasource
to infosource 0PLANT manually. You will find the info object names of
the characteristics by looking up the characteristic datasources which
are assigned to the classification datasource in transaction CTBW. From
these names you can derive the info object names:
1CL_A... -> C_A...
6. Disconnect the infosource which has been created with CTBW_META from
the classification datasource.
7. Connect please the classification datasource to infosource 0PLANT
Use following info object:
info object   field
0PLANT       WERKS
The info object names for the characteristics are explained in step 5.
8. Add an infopackage to infosource 0PLANT for the classification
datasource.
Now the extraction of classifications of sites should work.
Best regards,
Rolf
P.S. I saw the system messed it up and doesn't display any new and empty lines. Sorry, I hope you still can read it.
Edited by: Rolf Doersam on Mar 26, 2010 6:56 PM

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.

Key Field missing in transformation

Hi
I am trying to use BI7.0 transformation (1-1 mapping basically) to send data from one DSO to another DSO
Source : DSO1
Key fields : Account ,Itemid, Position number
Target: DSO2
Key fields : Account ,Itemid, Position number
However when i create transformation i don't see "Itemid" in the source side in the transformation mapping. Rest of the two key fields are present.
Please help.
-Anurag

Hi, Anurag.
I just posted a question to the forum, because we are implementing the same architecture, and we are wondering how deltas will work with this
architecture. Are you using deltas?
The text of my recent post is below.
We are loading from R/3 into DSO1, and then from DSO1 into DSO2. The R/3 extractor that loads DSO1 is
delta-enabled. We are not sure, however, if a delta mechanism governs the load from DSO1 into DSO2. The
DTP says its extraction mode is delta, but does that mean, if a row in DSO1 changes, it will negate the key figures
on the original row and send a new row the way R/3 does?
For example, suppose the R/3 extractor sends us Row 1.
Row 1 has a key figure with a value of $100.
Row 1 gets changed in R/3, and the new value is $125.
The R/3 delta mechanism takes care of this by negating the key figure on the appropriate row and sending us a correcting
row. For example,
the R/3 extractor will send us:
Row 1 $100
Row 1 -100
Row 1 $125
So... the net value is correct, i.e. 100 - 100 + 125 = 125.
When we load from DSO1 into DSO2, however, do you know what rows will load into DSO2? Is BW "smart" enough to do this
type of negation?
Thanks!

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.

Key Field not to be seen in report

Hi,
I have a DSO and in that I have 1 key field and 20 data fields.
I was able to load the data successfully in the DSO. And I am creating a report based on this DSO.
But when I create a report, I was unable to view the key field in the report.
I went to the query designer and checked, I could not see that particular key field also in my query designer, I could only see the data fields.
Could someone please guide me in this regard???
Would definitely assign points for the solution...
Thanks & Regards.

Hi,
I have checked the info object and it is BEx enabled.
I am not able to see another 2 characteristics as well in query designer while creating the query.
I can view two sections, i.e. Key Figures and Dimensions.
And I am creating a report on DSO not in a cube.

Key field not available in report

Hi,
I have a DSO and in that I have 1 key field and 20 data fields.
I was able to load the data successfully in the DSO. And I am creating a report based on this DSO.
But when I create a report, I was unable to view the key field in the report.
I went to the query designer and checked, I could not see that particular key field also in my query designer, I could only see the data fields.
Could someone please guide me in this regard???
Would definitely assign points for the solution...
Thanks & Regards.

Hi,
Please uncheck the Attribute only check box in the General tab of that Keyfield info Object.
If any info Object checked as Attribute only then those objects wont display in the Query Designer.
dont forget to give me the points..
thanks,
CK

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

Key Fields, Data Fields, Key Figures and Characteristis, Dimesions & Key Fi

Hi All,
Can any one please describe more about the below terms and with the Example....
Like when we identify which one is Key filelds and Data fileds, how to distingush creating new dimesions (Is it based on user reporting) Key figures in Dimestions...
DSO/ODS: Key fields, Data Fields
InfoCube: Dimensions, Key Figures
Infoobjects: Key figures, Characteritics
Regards,
Prem

Hi,
Search through SDN for more information on these concepts,
Re: ods data fields or key fields?
Re: Key Fields and Data Fields in ODS
defining Key -field and data fields
Regards,
Mani

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

0CALDAY as a key field

Similar Messages

Maybe you are looking for