Miximum no of fields in DSO

Hi All,
Can you please provide me info:
How many maximum KeyFields a DSO can have?
How many maximum datafileds a DSO Can have?
basically is there any restrictions on no of fields for DSO like Infocube?
Your information is greatly appreciated.
Regards,
Ravi

Hello,
Yes its there..
you can have maximum 16 keys for an oracle table therefore you can have only 16 keys for the DSO.
Also depending upon the maximum size of the data blocks the maximum number of data fields is 749.
check this thread.
http://help.sap.com/saphelp_nw04/helpdata/en/4a/e71f39488fee0ce10000000a114084/content.htm
Not sure if this has chnaged recently but should hold true.
Thanks
Ajeet

Similar Messages

Data fields in dso

Hi
If I need to calculate amount based on source and destination,and if these two source and destination fields char are there in data fields of dso and keyfigure amount is also in data fields of DSO can we get exact value if make report on this.
thx
rubane

Actually i need to build report where in rows there will be some char
like source plant and destination plant and in rows on the basis of source and destination the cummulated value of amount base on some other few restriction
now my question is :-
acc to my need I need to make genric extractor but one is already there which contains all my fields. now can i use the same extractor,but the worry is ;these all feilds are first going in dso and all are there in data fields coloumn
What I'm thinking is; it will suppress or accumulte records on the basis of key field's(as usual).
so can you pls let me know what to do in this scenario?
how to build a new report using existing extractor ;can i use existing one?
rubane

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

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

Adding fields into DSO in the Key Fields

Hello Experts,
I am using a Cube which loads data from DSO. Now, for some requirement I have to add one field into DSO in the key fields Part. But DSO already has 16 fields which I cannot remove.
So how can I add one more field into DSO in this case?
The cube I am using is 0FIGL_C10 and the DSO is 0FIGL_O10.
Regards,
Nirav Shah

You can create an Infoobject - acts as a custom key to concatenate multiple fields into one and make it a keyfield.
15 fields + custom key ( concatenate 2 fields ) = 16 Keyfields
Procedure - > Example
16th Key - > RVERS-Version-CHAR-3-0VERSION
17th Key - > RMVCT-TransactnType- CHAR-3-0MOVE_TYPE
1. Create one infoobject - ZKEY - Length = 6 ( add lenghts of the two objects)
2. Make ZKEY as a keyfield for the DSO.
3. Make 16th Key and 17th Key datafields.
Create a routine for ZKEY in the transformation or transfer rules to concatenate values coming from source into one.
TRFN Routine
Concatenate SOURCE_FIELDS-RVERS SOURCE_FIELDS-RMVCT into RESULT.
Or
Transfer Rules Routine
Concatenate COMM_STRUCTURE-RVERS COMM_STRUCTURE-RMVCT into RESULT.
This way nodata will be lost/overwritten due to less number of keyfields in the DSO.
We have as many as 21 Keyfields for GL Totals DSO.

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

Fields in DSO & Cube

Hi experts,
I have the field 0fiscyear in my dso and also in the cube. But
when creating transformation the field 0fiscyear is present in
the dso but not in the cube. So that i am unable to create
transformation for 0fiscyear.Anyone please explain me what
should i do to make the field visible in the cube.
And one more question. How can we select or hide the fields
of 0fi_ar_3.This data source is not visible in LBWE.
Full points will be assigned.
Thanks & Regards,
V N.

Hi VN,
Goto SBIW->Application Specific>Logistics>manage extract struvctures>initialization->appl specific setup of statistical dat -->select inventory mangement perform setup>
in the select materil movement/Setup: Invoice Verification, Revaluation as per your choice to load.
direct transaction OLI1BW for material movement
OLIZBW for invoice verification
once you gets into statistical setup give name of the run and termination time and date to setup then gofor excution
once setup tables start loading gotoRSA3 which is extrac chekor to chk u r datasource data
before all this make sure your data source as active.
i hope this is clear na
mahesh
Edited by: Mahesh Kumar on May 19, 2008 7:00 AM
Edited by: Mahesh Kumar on May 19, 2008 7:01 AM

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

Fields in DSO

hi experts,
I m new to BW,
i m facing a problem of aggrgating the fields in my DSO.
i have 2 fields in DSO1 with 100 records.
i have another 3 fields in DSO2 with 300 records.
Now i want to unite the records from these two dso into a new dso having 5 fields(2 from DSO1 + 3 from DSO2).

Hi,
You can unite 5 fields in your new DSO.
The 1st and 2nd DSO must have atleast 1 common field to combine the records from 1st DSO and 2nd DSO, so that you can get 300 records.
Else you will get 2 seperate records from 1st and 2nd DSO totally 400 records, in such case when the data loaded from 1st DSO to new DSO u will get blank fields(ie , you will get blank value in the 2nd DSO fields). when the data loaded from the 2nd DSO to new DSO u will get blank fields(ie, you will get blank value in the 1st DSO fields).
its upto your requirement... but mostly we must have common field to get single record from both DSO.

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

Read 0PROD_HIER to fill field in DSO

Hi Everyone,
I have a requirement where I need to populate a field (ZATTRBE1) of a DSO with PRODH4 of 0PROD_HIER. 0PROD_HIER is not coming from the source as the source to the DSO is 0material_text.
I have to read the hierarchy. I am aware of an FM 'RSNDI_SHIE_STRUCTURE_GET' but dont know how to use this to populate the field.
Kindly provide any information that you may have regarding this. A code would be very very helpful.
Regards,
Kshama.

Hi Kshama,
check also the following links:
/people/sap.user72/blog/2006/07/11/tracing-data-transformation-in-sap-bw-without-debugging
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0038ad7-a0c7-2c10-cdbc-dd674682c8e7?quicklink=index&overridelayout=true
I suggest you not to change the code but try to use a user break-point. Thanks to debug you can check the data in your internal table.
Hope it helps.
Best regards.
Simone.

Index creation on a field in DSO for performance improvement of a select st

Hi All,
We have one DSO in Production which has around 48 million records.
In a transformation of a cube, we have a select statement on the DSO with comparing 5 fields. And 4 of them are data fields in the DSO.before some time we change a structure of the DSO. We moved one info object from key field to data field which is being used in the select query.
After this change, we do a full load to the DSO and then everything is running fine. Except the load to cube is getting stuck at the select statement. It is running for ever.
Now I have the below doubts,
1. Can this happen as one of the field which we are using in the select statement does not have indexes?
2. If we want to create index on that field, then what would be the required steps?
Thank you,
Jaimin

Hi Jaimin,
Sorry ,i misunderstood the question.Request you to please explain the issue step by step once again.
Rgds
SVU123
Edited by: svu123 on Feb 25, 2011 11:52 AM
Edited by: svu123 on Feb 25, 2011 1:30 PM

How to map new field in DSO

I have added a new field to the dso and i have replicated the datasource as well which is showing the new field newly added in ecc. how can i map the new keyfigure in the transformation between the datasource and ods. its showin in the ds, can u pls tell me how to map now.

Ya but the problem is I have an infosource in between and its not showing in the transformation between the dso and infosource.....nor the infosource and the datasource. But its there in the first transformation on the dso side, not on the inforsource side..... but how to get that field in the infosource side...so that i can map the field between both the transformations....between infosoucre and dso and infosouce and ds.....You know what I mean. the zfield is showin in the dso field structure in the first level mapping between dso and infosouce....but where do i map it.
Edited by: Daniel on Nov 28, 2011 9:59 AM

Regarding Additive Field In DSO

Hi Guys,
I have one field as summation in DSO. I made it additive while creating the transformation. Can any one tell me how it will add a summation when i do a delta update.
Thanks

Hi,
Transformation
Aggregation type:
Use
You use the aggregation type to control how a key figure or data field is updated to the InfoProvider.
Features
For InfoCubes:
Depending on the aggregation type you specified in key figure maintenance for this key figure, you have the options Summation, or Maximum or Minimum. If you choose one of these options, new values are updated to the InfoCube.
The aggregation type (summation, minimum & maximum) specifies how key figures are updated if the primary keys are the same. For new values, either the total, the minimum, or the maximum for these values is formed.
For InfoObjects:
Only the Overwrite option is available. With this option, new values are updated to the InfoObject.
For DataStore Objects:
Depending on the type of data and the DataSource, you have the options Summation, Minimum, Maximum or Overwrite. When you choose one of these options, new values are updated to the DataStore object.
For numerical data fields, the system uses characteristic 0RECORDMODE to propose an update type. If only the after-image is delivered, the system proposes Overwrite. However, it may be useful to change this: For example, the counter data field u201C# Changesu201D is filled with a constant 1, but still has to be updated (using addition), even though an after-image only is delivered.
The characteristic 0RECORDMODE is used to pass DataSource indicators (from SAP systems) to the update.
If you are not loading delta requests to the DataStore object, or are only loading from file DataSources, you do not need the characteristic 0RECORDMODE.
Summation:
Summation is possible if the DataSource is enabled for an additive delta. Summation is not supported for data types CHAR, DAT, TIMS, CUKY or UNIT.
Overwrite:
Overwrite is possible if the DataSource is delta enabled.
When the system updates data, it does so in the chronological order of the data packages and requests. It is your responsibility to ensure the logical order of the update. This means, for example, that orders must be requested before deliveries, otherwise incorrect results may be produced when you overwrite the data. When you update, requests have to be serialized.
Regards
Santosh

Miximum no of fields in DSO

Similar Messages

Maybe you are looking for