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.

Similar Messages

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>

Table for line items for parked documents

Hello all,
Do anyone know what is the table for line items for parked documents(fbv3)?
Because I check bseg and these doc. aren't there.
Thanks a lot!

Hi,
Please Check table "VBSEGS" you will get parked document ine items .please check below link it will clear...
Find tables for GLs on Parking Documents by FB60
Thanks in advance
Chakri

Table for line item in F-47 Display Document - Down Payment

Hi,
Can anyone please tell me from which table can I pick the values for line items. I'm developing a report in smartforms for down payment request. For header items I found out that the values are stored in table - BKPF.
Please help..
Regards,
Sriram

Hi,
Go to Logical database through SE36 and give KDF for vendor and DDF for customer. You will get the details of tables there.
Regards
shankar

Table for line items of budget document posted through FMBB transaction.

HI,
I am looking for Table of line items of budget document posted through FMBB transaction.
There is table FMBL but it is breaking the amount into 12 parts.
Thanks.

Hi
check the tables
FMBDA
FMBDP
FMBDT
FMBH
BPDK
Regards
Anji

MMBE table for line items

Hi experts,
I am currently developing a report same like MMBE.
Currently MMBE is showing only the current stock at the warehouse.
But i m sure there is line item behind this stock balance.
I need to develop a report to show the stock for a particular period which should map to the MMBE.
In this case i need the tables to show the line item and not the history table.
Thank you in advaced.

Hi,
Try MKPF & MSEG tables. or FM MB_READ_MATERIAL_STOCKS
Regards,
Amit

Table for line item relevancy for due list

Hi all
i have taken the list of orders from VF04 ,but is there any table where i can check which line item is relavant for Due list for each order?
Regars
Phani

hi Rhani,
that would be the billing index VKDFS.
Balazs

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

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

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

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.

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

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

InfoCube Design for Variable data - Use of Line Item Dimensions

I have an infoprovider based on billing conditions which we have extended the extractor structure for 2LIS13_VDKON and we now have a requirement to add Customer fields such as Customer Purchase Order Number and Contract Number. These fields are obviously highly variable. I have added to them to the reporting DSO and now need advice on what is the best way to add these types of fields as reportable dimensions to the infocube so as to not impact performance? I currently have 9 dimensions with multiple charachteristics and a time dimension. Should I just create a line item dimension for Purchase Order? Problem is I have 8 other line item dimensions to add which are customer specific reporting fields that we capture on the sales order and wish to report on. I know there is a limit of 16 dimensions and I am also concerned about performance.
Any advice is greatly appreciated
Lee Lewis

Hi,
To make sure that the infocube you have created should not have any performance issue: Please do the following
Go to RSRV > All elementary tests-> Database---> database information about infoprovider tables
Upon clicking on database information about infoprovider tables, on the right hand side, in the parameter enter your infocube name and execute and see the log: ( log will automatically popping up once you are done with execution )
There see the database infomation about infoprovider:
This log wil make you to understand how well you have designed your infocube and make sure that each (f ) table corresponding to each dimension will not exceed 20 % of the infocube size.
You create dimensions of infocubes in a such a way ( whether line item or normal dimension ) so that any of the dimensional F table will not exceed 20 % of the infocube size.
Actually this will give us the information of the size of the data of particular dimension and there by if any particular dimension is exceeding the 20 % of the infocube size, then you need to create line item dimension for the characteristics existing in that dimension .
After creating again, test it and see whether any of the dimension table exceeding 20% infocube size .
Repeat this process until you see all dim F tables less than 20 % of the info cube table size
This will negate any performance issues arise in reporting
Edited by: S Simran on Nov 6, 2009 10:11 AM

Table for line item dimensions

Similar Messages

Maybe you are looking for