Checking Line Item Dimension

Hi
Does anyone know a quicker way to do a mass check on whether 'line item dimension' has been defined in InfoCubes?
Please share if you do.
Many thanks,
Anthony

Hi Anthony,
You can look up table RSDDIMEV (field LINITFL).
Hope this helps...

Similar Messages

What is line item dimension and cardinality in BI 7.0

Can u plz suggest me what is line item dimension and cardinality in BI 7.0..
Thanks in advance.
Venkat

Hi Babu
Line item: This means the dimension contains precisely one characteristic. This means that the system does not create a dimension table. Instead, the SID table of the characteristic takes on the role of dimension table. Removing the dimension table has the following advantages:
¡ When loading transaction data, no IDs are generated for the entries in the dimension table. This number range operation can compromise performance precisely in the case where a degenerated dimension is involved.
¡ A table- having a very large cardinality- is removed from the star schema. As a result, the SQL-based queries are simpler. In many cases, the database optimizer can choose better execution plans.
Nevertheless, it also has a disadvantage: A dimension marked as a line item cannot subsequently include additional characteristics. This is only possible with normal dimensions.
Note: In SAP BW 3.0, the term line item dimension from SAP BW 2.0 must a) have precisely one characteristic and b) this characteristic must have a high cardinality. Before, the term line item dimension was often only associated with a). Hence the inclusion of this property in the above. Be aware that a line item dimension has a different meaning now than in SAP BW2.0.
SAP recommends that you use ODS objects, where possible, instead of InfoCubes for line items.
Hope this helps.
Plz check these links:
SAP Help:
http://help.sap.com/saphelp_nw04s/helpdata/en/a7/d50f395fc8cb7fe10000000a11402f/frameset.htm
Thanks & Regards
Reward if helped
Edited by: Noor Ahmed khan on Aug 5, 2008 2:36 PM

Line item dimension wont insert sid values in infoobject sid table

Hi all,
I have a strange problem, whenever I load data into a cube which has a line item dimension on 0customer without first loading the master data I am getting inconsistency in RSRV saying that no corresponding DIMid exists in sid table.
So there are Dimids in the fact table but the dimension table, which is same as the sid table in the the case of line item dimension, doesnt have them.
Can someone explain me why is this happening? I thought if a characteristic value doesnt exist in the master data but comes in through the transaction data it inserts the same in the sid table.
Is there a different rule for line item dimensions? Can someone point me to some OSS or documentation?
thanks

Thanks all..
To clear up a few questions:
1. What I mean by <i>"So there are Dimids in the fact table but the dimension table, which is same as the sid table in the the case of line item dimension, doesnt have them"</i> is:
the line item dimension table /bic/D<cubename>9 which is really a view on the sid table for characteristic /bic/s<ch. name> does have all the sid values (or all the dim values) as the fact table.
So fact table has more entries for that dimension than the sid table.
2. Yes we are facing reporting errors where we cannot drill down by that infoobject and LISTCUBE doesnt show us any cube data when that characteristic is chosen for display.
3. I have checked notes where it seems to be a RSRV bug but in our case it doesnt seem to be as observed in the actual table mentioned in #1
Now it is apparent that I am right both from help.sap.com link and what I am observing that for line item dimensions master data HAS TO BE LOADED FIRST for the characteristics used as a line item.

Line item dimensions

hi..
wat is line item dimensions nd cardinal heights???
regards
deepa

Hi Deepa,
Line Item Dimension:
When your dimension table becomes large (>10% of the fact table) then you can make the dimension a "line-item" dimension. The constraint is that the dimension should have only 1 characteristic. By making the dimension as line item the SID values are directly used instead of the Dim ids and the query performance is better.
The disadvantage is that once you make the dimension line -item you cannot add another characteristic to that dimension and you cannot remove the line -item checkmark without deleting the cube data.
http://help.sap.com/saphelp_nw04/helpdata/en/a7/d50f395fc8cb7fe10000000a11402f/frameset.htm
Multi Dimensional modelling will include fact table in center with Dimension tables around it. Overall system performance is greatly affected and dependent on the size of these dimension tables in respect to the fact table. SAP recommends that size of dimension table should be 20% of the size of fact table. In case if this size is more than 40% dimension should be defined high cardinal ( should be supported by database) If dimension tables are more than 40% the dimension should be defined as line item. When dimension is defined as line item, Dim ID in the fact table is replaced with the SID ID, Only one characteristic will be defined in that dimension. This results in improved performace.
Here is how it will work
Fact table
Dim ID1 DIM ID2 DIM ID3 AMOUNT QTY
Dimension Table 1
Sid1 DimID1
Dimension Table 2
Sid 4 Dim ID 2
Dimension Table 3
Sid6 Dim ID 3
Cosidering that Dim1 is too big, We can define Sid 1 in Line Item Dimension and Dim ID 1 is replaced by Sid 1 so fact table will look like this
Sid 1 Dim2 Dim3 Amount Qty
Compounding Attribute is superior object to define characteristic, for example
Plant A manufactures TV
Plant B manufacture TV
The only way to differentiate product can be TV and Plant A
Also,
Cost center 100 can be in Controlling Area A and
Controlling Area B can also have cost center 200,
So Cost center is compounded with CO Area to uniquely identify that line.
Just check this thread line item dimension
Cardinality defines the numeric relationships between occurrences of the entities on either end of the relationship line.
Check this link:
http://www.datamodel.org/DataModelCardinality.html
For cubes -> High Cardinality means that this dimension contains a large number of characteristic values. This information is used in accordance with the individual database platform in order to optimize performance. For example, an index type other than the standard may be used. Generally a dimension is perceived to have high cardinality when the dimension is at least 20% the size of the fact tables in terms of the number of entries each contain. Avoid marking a dimension as having high cardinality if you are in any doubt.
Also refer the below link for Line Item Dim and High Cardinality.
http://help.sap.com/saphelp_nw04/helpdata/en/a7/d50f395fc8cb7fe10000000a11402f/frameset.htm
Check this explanation by pizzman:
Re: High cardinality (CARDHeight) vs Line item
Refer these links on line-item and cardinality:
Line Item Dimension
Re: Line Item Dimension
Cardinality
Re: High Cardinality Flag
****Assign Points If Helpful****
Regards,
Ravikanth

How to know what were line item dimensions

Dear SDN,
How to know what were made line item dimensions.
Thankyou.

Rahul,
Go to the edit mode of your info cube and then check out your dimensions, there if the line item dimension check box is checked then it means that, that particular dimension is a Line item dimension.
Regards,
Gattu

Usage of line item dimension - design or run time?

Hi,
Can anyone please tell me at which stage a line item dimension is considered - at design time or after data load, once queries are run and performance degenerates?
I have read many posts and blogs about line item dimension and high cardinality, but I would require more information on when a line item dimension comes into play.
If we can decide at design time, then how is it done without data being loaded?
At which instances will the dimension table size exceed the fact table's size?
Please explain the above 2 points with a clear example, including the DIM ID and SID table access, and the ratio calculation for line item dimension consideration.
Thanks in advance.

Hello Aparajitha,
I agree with Suhas on point of consideration of LID . It would be good enough to consider a Dimension as LID in the Cube during design, it will be fruitful for the performance point of view. There is no point in saving the LID for future purpose if you have less than 13 Dimension in the Cube. It is going to save a extra join in connecting the relevant data.
If the total Dimension exceeds 13 or more (during design) , then you no option but include the related Char IO together in a one dimension.Here you cannot make a LID .
During the run phase, if the Dim table is more than 20 % of Fact Table, then for the sake of performance you have to go for the LID.In that case you will have the overhead of managing data (backup, delete & restore) .
On your specific questions :
"If we can decide at design time, then how is it done without data being loaded "
Technically same as you do during run-- Goto Dimension -- Right click --Properties -- and Check LID.
Logically -- Depending upon the Business meaning, which char has max unique values you can go with as LID.
"At which instances will the dimension table size exceed the fact table's size "
Frankly I haven't come across that.. ... Fact table is the center table and always will be the huge table in comparison to Dim table . Dim table cannot exceed the Fact Table ....!
Yes if the size of Dim Table is more than 20% of Fact table ( ratio of Dim Table to Fact Table) , then we have to select between the LID or High Cardanility.
Gurus..Please correct if anything is wrong ..!
Regards
YN

How Line Item Dimensions

Hi..
I found some dimensions need to be conveted into line items. but when checked with cube that dimension has more than 1 characteristics. In that case what i have to do..and how can i convert it into line items

Hi Rajini...
1. When you anticipate high growth in the dimension tables of an entity.
2. Usually you decide whether a char is to in a line item dimension or not.
3. SAP recommends to have ODS for line items rather than cube; cube should have summarised data.
Also, see this link:
http://help.sap.com/saphelp_nw70/helpdata/en/a7/d50f395fc8cb7fe10000000a11402f/frameset.htm
Using Line Item Dimension
remodeling :
http://help.sap.com/saphelp_nw70/helpdata/en/58/85e5414f070640e10000000a1550b0/content.htm
regards,
supriya

Regarding Line item dimensions

Hi all,
In our project for one of the cube 3 line item dimensions are maintained already , But still we have to create one more line item dimension for that infocube because the percentage for the one of the dimension and fact table is reached to 90%.So is it preferable to have more line item dimensions? If not please provide the alternative suggestion.
we maintained relative infoobects in dimensions.
Thanks & Regards,
Swarna.P

Hi,
If there is no other alternative to swap the Chars in between Dimensions, then go for Line Item Dimension. It won't be a problem if you have more then 2 or 3 Line Item Dimensions. I Used 4 Line Item Diemsions becasue the Ratio is crossing 90%. So Line Item is solution for my problem, first check the Chars in Dimensions and re-arrange it then check the Ratio, if it doesn't work then go for Line Item Dimension.
Thanks
Reddy

Table for line item dimensions

Hello SDN,
Any table gives info about what all line item dimensions are used in Cubes.
Goodday.

hi,
there is no table which contains info. about what are the line item dimensuins in a cube.
use LISTSCHEMA t-code to know the tables in a cube.
or got SE11, give Dim table name ie /BIC/D<cube name><dim no>
serach the keyfield.
or check directly in infocube edit.

Infocube line item dimension and performance optimization

Hi,
I remodelled an infocube and line item dimension contains only one characteristics set as line item dimension.
previously the dimension as one characteristics but it wasn't set as line item dimension.
and when I checked the SAP_INFOCUBE_DESIGNS from SE38 it looks ok.
/SAP/CUBE /SAP/CUBE3 rows: 8663 ratio: 3 %
After setting it as line item the rows is now minus but it is showing red which means that there is problem with the dimension
/SAP/CUBE /SAP/CUBE3 rows: 1- ratio: 0 %
Its this a performance problem since it is showing red.
thanks

hi,
No,its not performance issue.
for a dimension to be line item dimension...the dimension size shouldn't be more than 20% size of the fact table size.
when a dimension is set as line item dimension,the regarding SID will be placed in Fact Table,but not the DIM ID.
may be that is the reason when your dimension is not line item dimension,it shows the number of rows and when it is made line item dimension,its not showing any rows and the ratio also null.
hope this is clear for you.
Regards
Ramsunder

Regarding line item dimension

Hi all,
what are the necessary prerequisities will u take regarding line item dimension.
for eg., for sd cubes we r using sales doc no., i.obj as a line item dimension? why can't the other i.obj?
plz explain me clearly?
Thanks & Regards,
V.Vijay.

HI,
Line Item and High Cardinality
When compared to a fact table, dimensions ideally have a small cardinality. However, there is an exception to this rule. For example, there are InfoCubes in which a characteristic document is used, in which case almost every entry in the fact table is assigned to a different document. This means that the dimension (or the associated dimension table) has almost as many entries as the fact table itself. We refer here to a degenerated dimension. In BW 2.0, this was also known as a line item dimension, in which case the characteristic responsible for the high cardinality was seen as a line item. Generally, relational and multi-dimensional database systems have problems to efficiently process such dimensions. You can use the indicators line item and high cardinality to execute the following optimizations:
Line Item Dimensions
Line item: This means the dimension contains precisely one characteristic. This means that the system does not create a dimension table. Instead, the SID table of the characteristic takes on the role of dimension table. Removing the dimension table has the following advantages:
¡ When loading transaction data, no IDs are generated for the entries in the dimension table. This number range operation can compromise performance precisely in the case where a degenerated dimension is involved.
¡ A table- having a very large cardinality- is removed from the star schema. As a result, the SQL-based queries are simpler. In many cases, the database optimizer can choose better execution plans.
Nevertheless, it also has a disadvantage: A dimension marked as a line item cannot subsequently include additional characteristics. This is only possible with normal dimensions.
High Cardinality
If your dim table size exceeds the 20% of your fact table then you can say it as high cardinality, for ex: your fact table contains 100 records and your customer dimension contains 25 records means this dim is with high cardinality. you can check with your client for the expected records for those dimensions or for the info objects which you define in one dimension. to know the sizes of the dimension tables and fact tables you can runa a program in SE37 SAP_INFOCUBE_DESIGNS, it displays all your info cubes fact and dimension tables with sizes, if any dimension exceeds the more than 10% to 20% it will be in RED.
It means that the dimension is to have a large number of instances (that is, a high cardinality). This information is used to carry out optimizations on a physical level in depending on the database platform. Different index types are used than is normally the case. A general rule is that a dimension has a high cardinality when the number of dimension entries is at least 20% of the fact table entries. If you are unsure, do not select a dimension having high cardinality.
http://help.sap.com/saphelp_nw04/helpdata/en/b2/fbb859c64611d295dd00a0c929b3c3/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/en/a7/d50f395fc8cb7fe10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5c/d14d3c306f090ae10000000a11405a/frameset.htm
Note: In SAP BW 3.0, the term line item dimension from SAP BW 2.0 must a) have precisely one characteristic and b) this characteristic must have a high cardinality. Before, the term line item dimension was often only associated with a). Hence the inclusion of this property in the above. Be aware that a line item dimension has a different meaning now than in SAP BW2.0.
SAP recommends that you use ODS objects, where possible, instead of InfoCubes for line items.
Tarak

13 line item dimension cube into BWA?

I have heard earlier that BWA does not support line item dimensions due to swap of data between blades. not sure this is still an issue.
My cube has 13 line item dimensions. For performane reasons, we created 13 line item dimensions as cube storing 240 million records and user want to analuse all this data.
I want to push this line item cube to BWA for better performance and like to know the impact.
thanks for advance replies.
Thanks

texas_user wrote:
My assumption for BWA has no limitations. That's why we spent so much for BWA right?
Rewording Mark Victor Hansen: "Only in imagination, there's no limitation".
Best cases for BWA performance are documented; unfortunately the only link I have on hand is to BIExpert article [Tips and Techniques for Optimal Query Performance with SAP NetWeaver BI Accelerator|http://www.bw-biexpertonline.com/article.cfm?id=3665].
> It should support all navigation included single record reading to whole set of data.
> I have 300 million of records in cube. We don't know what kind of adhoc analysis user planning to do.
> We put all 14 fields from base cubes in query allowing user to do anything with data to make better decisions.
> My question is making 13 line item dimension in cube and putting 300 millions records in BWA improve performance or not?
> Space or cost is not concern here. Do we able to do it?
> Does Web intelligence query come back? Or die?
So far there is nothing worrisome in your description. 300M recs is not mind-blowing. The areas of watch-out:
1/ There used to be performance implications with line-item dimensions in the past, when number of records in dimension was higher than number of records in fact table. But it was 2-3 years ago...
2/ Once you put something on top of BW, like BO in your case - you need to check where time is spent, because in the past communication between BI tool and BW used to have impact as well. Make sure you have latest patches there.
Cheers,
-Vitaliy

How to consider an object as Line Item Dimension?

Can I have the formula for Line Item Dimension? I know basic idea like If the LID is more than 20% of the fact table then we consider as LID but how can we say that the object having more than 20% than Fact table?

Hi sanjeev kumar--
I hope thru that program you will get the ratio between different dimesion tables and the facttable.
In doing so if the size of the dimesion table is too high then we have to trace out the offending charecteristic in that dimension and have to assign that char as a line item dimension.
Generally it can be created on single char infoobjects. After creating it directly links to the MD . i mean to say there won't be a dimension for this..
You can check this under the Tcde listschema .
Hope this Helps,
Regards,
Vishwa.

Removing line item dimension

Dear All,
I have encountered a problem after I removed line item dimension flag from the dimension properties and added new characteristics to that dimension.
When I checked the data in the cube, I was surprising to find the old characteristic (that was the only char. in the dimension previously) having irrelevant values.
Now I can understand that there was no dimension table before removing the flag. And the new dimension table leaded to wrong matching between fact table and SID table.
Can you suggest any solution to make the correct matching between the fact table and SID table ?
thanks in advance..
regards,
berna

Try performing the RSRV Tests.
Go to tcode: RSRV and perform the following tests:
All Combined Tests --> Transaction Data --> Foreign Key Relationship Between Dimension(s) and SID Tables for the Associated Characteristics
All Combined Tests --> Transaction Data --> Fact and Dimension Tables of an InfoCube
Cheers,
Neel.

Line Item Dimension has been reset / cancelled after upgrade to 7.0

Hello,
we upgraded to Netweaver BI 7.0 SP 17 and now I receive the message that the line item flag in the dimension has been reset / cancelled.
Can I set the line item flag again also in the new BI 7.0 Multicube?
Does anyone know where to set the flag ?
Thanks and regards,
Ilona

Hi llona,
U need to set the flag at the dimention screen of the Multiprovider..
When u enter the Dimention screen there u can find all the dimentions of the Multiprovider, right side to those dimension u can check the Line Item Dimention flag..
Make sure that u will assign only one char to the line item dimension.. then only u can treat a dimension as Line Item..
Thanks
Do these things in D and move it to the further landscapes..
thanks
Assign points if this helps

Checking Line Item Dimension

Similar Messages

Maybe you are looking for