Answer / kg

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.

Answer / murali

When dimension table size equals or exceeds the fact table
at that point time we need to use the line item dimension.

If we use Line item dimension our fact table contains SID
instead of dimension ID.

For maintaining L.I.D we have to create only one object in
dimension table.

Answer / gangadhar

If the volume of the masterdara of a dimension is growing
along with the transaction data then to improve the data
read performance of master data, we can create the
dimension as line item dimension.

when we create a dimension as line item dimension, the SID
of the characteristic will be joined directly with the fact
table without using dimID's.

Disadvantages : F4 help is not possible in data selection
screens for line item dimension.

Conditions : 1. The dimension should have only one
characteristic. 2. Master data of dimension >= 20% of
transaction data of infocube(interms of records).

Answer / kalyan

Line item dmension is a single chracteristic considered as
a dimension.When size of dimension table is greater then
10% of the size of fact table then we create line item
dimension

Answer / chavid

Hen the chracteristic value (#s) is one & is larger (say
like order no. During query this ill give performance
issue. So it is better to define such chars as line item
Dims. Only SId is generated & used by fact table. R O thumb
is hen the cardinality is > 10 then it is advisable to
define the IO as L I Dim. L I Dim uses b-tree index (
default is Bipmap).

Answer / karunesh mishra

Line item dimension can be created only on characteristic
not on key figure.
Reason why we create L.I.D is that, it increases the query
performence because it doesn't create the dimension table
and the SID is directly connected with the fact table.

Answer / balaji bathala

If you have a characteristic that can have a large no,of distinct values it is the likely the dimension which you include these char contains same no.of records. The path from Fact table to Dim Table and then to SID Table will become critical for performance. If you make this dimension as LineItem then the SAP BW will not create DIM Ids and it creates the Dimension Table and this table will act as a just view.

Directly the SID is connected to the Fact Table. Here the SID will act as the key in the Fact Table.

Limitations:-
We can include only one Characteristic in the Line Item Dimension because the Key in the Fact Table is SID. We can Create SID for each characteristic separately.

What is rowlevel security ? can u please explain with real time example?

0 Answers   Polaris,

What is sap bw/bi?

0 Answers  

what is infoset? what are the uses? in which case it suppose to be use? and difference in bi7.0/bw3.5?

3 Answers  

What is the diference between defining calculated key figure in info provider level vs query level?

2 Answers  

What is the format of LO data sources?

0 Answers  

What is 0record mode.

0 Answers  

which object based you created extended star schema?

0 Answers   Rockwell, TCS,

What is info provider documentation?

0 Answers  

How do you delete query objects (like workbooks, etc.,) in a single transaction?

1 Answers  

What are the LO extraction transaction?

3 Answers  

What is bw statistics and how it is used?

0 Answers  

What are the server related tuning?

0 Answers