How can i decide candidates for line item dimension?

1Q): we have many infocubes out of all these infocubes, i have to decide which infocubes are the candidates for lineitem dimension? How to do it? Please tell me the technical specs how to do the analysis to find out the candidates for line item dimension?
2Q): if i have the small dimension can i combine all these dimension in to one dimension? what is the benefit of doing this? how to find out which dimensions are small?
Pizzaman i like to hear from you on this topic. Thanks to SDN Community. i appreciate your help. Again Thank you.

The process of figuring out what you might want to create as a line item dimension can vary a bit, it can depend a lot on your exisitng level of domain expertise (how well do you know the data in question). If you are familiar with the data, I would recommend you just take an initial guess at what you believe could be line item dimensions. If you are not familiar witht the data, you might want to examine the source more to understand the cardinality of different characteristics and identify any relationships between characteristics.
I really encourage people to just go ahead and model it and load some data and review, rather than agonizing over developing the theoretically perfect model on paper before they start. You learn a lot more that way.
Any of the SAP rules of thumb, are just that, general rules, not a pronouncement from God. There are always extenuating or unique circumstances that might warrant disregarding the rule, e.g. if the InfoCube will never become very large, maybe some of the concerns just are not worth your effort.
With every release of the Oracle (and the other DBs too)Oracle keeps getting better at data warehousing and star schemas. Oracle 10i is supposed to have made handling bitmap indices much more efficient, which is on of the factors influencing the decision to create a line item dimension.
There are other threads on SDN on line item dims that provide more technical detail and can help answer you first question
As far as 2Q - generally, it's better to have several small dimensions than one larger dimension. But having said that, combining a few very small dimensions into another slightly larger (but still small) dimension is a good idea. It keeps the number of table joins down which will improve query performance. You would do this with characterisitcs that have very few values, e.g. yes/no indicators.
e.g.
You have 8 characteristics that all of which have only two values. You put them in one dimension, and the max size of the dimension table is still only 2x2x2x2x2x2x2x2 or 256 rows. If you had these characteristics in other much larger dimensions, it's not hard to see it causing those dimensions to double, perhaps creating hundreds of thousands of dimension table rows to be created.
For more - read <a href="http://www.kimballgroup.com/html/designtipsPDF/DesignTips2003/KimballDT48DeClutter.pdf">Ralph Kimball Design Tip 48 - Junk Dimensions</a>

Similar Messages

How can I add a new line item for production order?

HI all,
How can I add a new line item for production order through BAPI/FM? Thanks in advance.

Hi Mil,
Unfortunetly SAP is not in front of me.
But if possible go to BAPI transaction , check for any production order's bapi for CHANGE purpose. Where you will be able to add your new line.
Reward if useful!

How can create and change PCA line items.

How can create and change PCA line items.
Please tell me the process and t.codes.

If you are in version < 4.7 ee then use 9KE0 tcode for passing profict center entries or trasnafer of balances from one profit center to another.
If you are in new GL regular FI entry like FB50 will hold good for account types "S"

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.

How to mention posting keys for line items in IDOCS for fb01 posting

Hi all ,
I am using IDOCS for fb01 posting with posting keys 15 and posting keys 40 for line items .The data is in legacy file . I am using IDOC ACC_GL_POSTING_01 for posting . Is there any way that I can mention the posting keys in the segment parameters of the IDOC.If there is anyone who have done fb01 posting with IDOCS,please help me with the code .Please treat the question as urgent .
Thanks in advance

Hi Arshad,
There is no fecility to enter Posting keys explicitly.. It is determined automaticall by the Credit/Debit amounts u enter in GL data in the segments E1BPACGL08 and E1BPACCR08 and also it depends on the Customer and Vendor no.
Sreedhar

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.

How can I settle just 1 line item using MRKO (consignment settlement)?

Hi All,
In consignment settlement, if for a given company code, say material document 41234552 has 3 unsettled line items, say 1 2 3.
Is there a way I settle just line item 1 and 3 and not settle line item 2 for the material document 41234552?
Regards,
Tejas

This is not possible. Have to clear the entire doc. Hence, closing this thread.
Tejas

How can i set image for any item in windows

i want to make button iconic in windows how can i do that in oracle 9i forms

First be aware that in forms .ico cannot be used for icons,
by default it is gif
so if you have an small gif file for your button you can alter the button properties in the property palette so that the button should be iconic (=> put to yes) and in the next filed iconname +put the name of the gif file without the extensoin (case sensitive)
Put this gif file in the icons/ path directory and your button will display the icon.
if you want more to know on the virtual path icons/ search this or the reports forum for virtual-path . you'll find plenty about it.
Hope it helps
erwin

Aggregates for master data & Line item Dimension

Hi i have question
1 Can we create Aggregate for Master Data?
2 Can we create Aggregate with Navigational Attributes?
3 Can we create Aggregate with Line Item Dimension?
4 How many dimension we can add with how many characteristics in it if we create a new Aggregate

1 Can we create Aggregate for Master Data? - No
2 Can we create Aggregate with Navigational Attributes? - No
3 Can we create Aggregate with Line Item Dimension? - No
4 How many dimension we can add with how many characteristics in it if we create a new Aggregate - You can create a maximum of 13 dimensions in the cube.You can add as many characteristics for an aggregate,adding many characteristics in the aggregate is as good as having the query fetch data from the Cube instead of the aggregates.
Aggregates are subsets infocubes derived from the main InfoCube to increase the query performance.You can create as many aggregates you want in an InfoCube.
For each aggregate,internally dimensions are created based on the selected characteristics.
Take a look at this link for detail information...
http://help.sap.com/saphelp_nw04/helpdata/en/7d/eb683cc5e8ca68e10000000a114084/content.htm

Need a scenario where we go for line item diemension?

can anyone explain the senario where we use the line item dimension ?
and how we know that size of dimension is more than fact tablw?

Hi
You need to roughly estimate that if you put two characteristics in one dimension means,
say plant and material
say there are 100 plants and 1000 materials...
then your dimension table will have 100 * 1000 = 100000 entries.so your fact table need to contain 100000 entries for these two chars...
.instead of putting these two into one dimension...if you put two dimensions...total entries in two dimensions are 100 + 1000= 1100...so your fact table contains 1100 entries...right???
so you need to think like this...if you feel that a characteristic may contains high cardinality then you have to go for line item dimension
run program
sap_infocube_designs
this will give the fact to dimension rations of all your cubes and indicate if the cube is balanced or not.
Hope it helps
Thanks
Teja
Message was edited by:
Teja badugu

Can anyone explain me line item dimension

Hi all
Can any one explain me line item dimension with real time exeamples.
thanxs a lot
hari

hi hari..
Line item dimension refers to single field. This is nothing but the SID of the field get stored in the fact table , and there will no extra dimension , hence improves performance while reporting as select need not go thru extra dimension table..
Line item dimension is used for those fields where the number of records is expected to be more..
You cant assign more than one characteristic to line item dimension.. But you can assign more than in normal dimension..
In modelling there are strong entities like customer, material which for dimensions. There are a few entities viz. "intersection entities" of the strong entities like "sales order no". Such intersection entities normally for line item dimensions.
n this example, if u want to have granularity level till the sales order no., you will have a real high no. of records in the sales order no dimension(if it was a regular dimension) as compared to the fact table(the ratio which u mentioned).
So we will treat this sales order no. as line item dimension.
Refer to the link below.
http://help.sap.com/saphelp_nw04/helpdata/en/a7/d50f395fc8cb7fe10000000a11402f/frameset.htm
This topic has been discussed on SDN earlier
Please refer to follwing SDN threads
Re: line item dimension,
Re: Line item dimension
Please go through this link from SAP help for line item dimension
http://help.sap.com/saphelp_nw04/helpdata/en/a7/d50f395fc8cb7fe10000000a11402f/content.htm
hope it helps...

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

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

Line Item dimension

Hi friends!
The auditor suggest us "flag the line item option in the dimensions with high cardinality, ie: document number, material number"
In my cubes have 0customer in dimension C toghether with other other characteristics, and 0material in dimension M together to other characteristics..
a) is the auditor suggest ok?
b) do I need mark this dimension as 'line item' in my cubes if the dimension M or C has more than one char?
c) do I need change the arquitecture in my cube and leave 0material alone in dimension M and in dim C only the char 0customer?
Thanks in advance!

Regarding High Cardinality :
If the values in the table are distinct - where the uniqueness of the values is high - a Bitmap index is preferred since the unique values are high...
As for Line item dimension - in a Line Item dimension - only one characteristic is allowed in a line item dimension and the SIDs will get stored directly in the Fact Table and the additional lookup of SIDs with the master data is avoided...
a) is the auditor suggest ok?
I would say that high cardinality is a better option as opposed to line item dimension . For Document Number - a Line item Dimension is preferred since Document number is typically used in reporting but not much on searches for the same ..
Also this is with the information you have given - it could also be that there is some more information to it that Line Item Dimensions were suggested ...
b) do I need mark this dimension as 'line item' in my cubes if the dimension M or C has more than one char?
You can mark a dimension as Line Item only if there is one characteristic
c) do I need change the arquitecture in my cube and leave 0material alone in dimension M and in dim C only the char 0customer?
Keep document number in line item - run the report to analyze the sizes of fact versus dimensions and then rearrange the characteristics to get better ratios instead of making Material and Customer as Line item Dimensions...
Also Material and Customer are usually viewed along with their Nav Attribtes - making them as Line Item will not give you much savings in terms of performance
Edited by: Arun Varadarajan on Mar 25, 2010 1:13 AM

How can i decide candidates for line item dimension?

Similar Messages

Maybe you are looking for