Regarding line-item-dimention

hi,
plz clarify my doubt regarding line-item-dimention.
When line-item Dimensions are used without containing the line-item characteristic in the aggregate, which aggregate should be built?
thanks,
Neelima.

Hi Nl .G
Aggregates can be built out of other aggregates to reduce the amount of data to be read and, hence, to improve the roll-up performance Aggregate hierarchy is determined automatically.
In order to use an aggregate in the first place, it must be defined activated and filled. When you activate it, the required tables are created in the database from the aggregate definition. Technically speaking, an aggregate is actually a separate BasicCube with its own fact table and dimension tables. Dimension tables that agree with the InfoCube are used together. Upon creation, every aggregate is given a six-digit number that starts with the figure1.
am sure using basic aggreate will solve this issue..Try and let me know..
any furthur info you can read from the given link..
[Aggregates|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cbd2d390-0201-0010-8eab-a8a9269a23c2]
Edited by: Prasanna Kumar Perla on Aug 4, 2008 1:52 PM

Similar Messages

Removing line item dimention from info cube

Hi All Experts,
Early watch report has suggested us to remove line item dimention and high cardinality from some cubes.
bur our cubes are having data , and when I tried to chekc this in our Dev server, Line Item dimention is disabled when it is filled with data.
but when I delete data from Cube, Line item diemention check box gets enabled.
so does it mean that we can not flag or remove line item dimention form cube if contains data,
and in mine case I have to delete all data from cube and then trensport it to PRD after deleting data from Cube and reload after transport.
Am I correct.
Please advice If I am wrong.

Hi,
yes, you are correct. You have to delete the content of the cube before you can change a line item dim. to a 'normal' dimension. As a workaround you might use a copy of the cube, create and/or copy all update rules to the new cube, and create a new update rule from the old to the new cube. Transport everything to prod, then load you new cube from the old cube and do all the other load as before. Move/copy your queries from the old cube to the new cube as well.
regards
Siggi

Line item dimention

hi experts,
what is line item dimention. when it is used.what is the importence of it in creating cube
puli

Hi Sridhar,
It is very often possible in the data model to assign only one characteristic to a dimension.This will probably occur with specific reporting requirements or if for example you have the document line item in your model.
In these situations a dimension table means only overhead. BI allows you to define this kind of dimension as a line item dimension (Check box dimension definition). In doing this no dimension table will be generated for this dimension. As dimension table will serve the SID table of this characteristic. The key in the fact table will be the SID of the SID Table.
The fact table is created during InfoCube activation. The structure of the fact table in the BI data model is the same as it is in the normal Star schema. The keys of the dimension tables (i.e. the DIM-IDs) or the SIDs of line item dimensions are the foreign keys in the fact table.
If all dependent attributes of a characteristic are navigational or display attributes in the characteristics master data table or nodes of an external hierarchy, then remember you have the option to define this characteristic as a line item dimension.
USE OF LINE ITEM DIMENSION:
As the BI schema does not enforce that you put a parent attribute into the same dimension table as its child attribute, it is often worth thinking about locating parent attributes in their own dimension table (e.g. with 100,000 article and 2,000 article groups why not put the article group in its own dimension table if queries are
often reported at article group level?)
Hope this helps.
Thanks,Ramoji.

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

Line Item Dimention Vs Hig Cardinality

HI ALL
           I have a problem with a cube and the below are the challenges...
                   1) can we use High cardinality / line item dimension if we already used one of these(High cardinality / line item dimension)?
                   2) while loading 4lakh records in to cube, i tried optimizing the cube by segregating characteristics into different dimension and i am successful in bringing down the percentage levels but all dimension levels are almost near to 30%. I Have only 1 key figure , will it cause any problem....
         please let me know the concept....
Thanks
vijay

Hi Vijay,
High Cardinality Purpose: If data volume stored in a table is very huge, it's difficult to retrieve particular record or sets of records. For fast retrieval purpose system creates Indexes on various columns, by default SAP BW creates 'Bitmap' index on each dimension.
If dimension doesn't contains large number of distinct values 'Bit Map Indexes' are fine, but in case distinct values are high and the dimension table is at least 20% of the size of the fact table, SAP recommends checking the 'High Cardinality' check box to create 'B-Tree' indexes. When compared to Bitmap indexes B-Tree indexes data retrial is fast, this is recommended on Oracle Data base.
Line Item Dimension: By checking this the relational path of Fact Table -> Dim_ID -> SID will be reduced to Fact -> SID, so you must create a dimension which doesn't create more relations between included characteristics in dimension.
So you can check Line Item dimension to make the system aware of not creating the Dim_ID path and you can check the High Cardinality to make the system to generate B-Tree indexes.
Hope this helps.
Regards
-Sunil

Regarding Line Items posting in LSMW

Hi
Can You let me know the procedure that how we can post the data realted to the line items using LSMW technique.
Regards,
kumar

LSMW cannot be used for data involving table control. U need to go in for a BDC session method for better performance .

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

Regarding Line Item Selection and product category

Hi Experts,
We are having a requirement in Line Item Selection in Oppurtunity.The requirement is that we need to display only the product categories belonging to that particular company(for eg Product Categories belonging to Company X) by restricting the display of product IDs.Please provide me some pointers on this as this is a high priority requirement.
Requirement:Line item selection of an opportunity will be at a 'X' category from the product hierarchy level.

Hi Amar,
You have to retrieve all you rproduct ids based on your criteria before the execution of the below step in your method.
result = qs->get_query_result( ).
Once you have all your product Id's then default your search criteria with your product id's using the below code.
ls_selection-attr_name = 'PRODUCT_ID'.
      ls_selection-sign = 'I'.
      ls_selection-option = 'EQ'.
      LOOP AT it_product INTO v_productid WHERE comt_product_id CP ls_search_criteria-low.
        CLEAR ls_selection-low.
        ls_selection-low = v_productid.
        CALL METHOD qs->add_selection_param
          EXPORTING
            iv_attr_name = ls_selection-attr_name
            iv_sign      = ls_selection-sign
            iv_option    = ls_selection-option
            iv_low       = ls_selection-low.
        CLEAR: v_productid,wa_result.
      ENDLOOP.
this code should be included in your event handler before calling get_query_result( ).
Hope this helps.
Regards,
Lakshmi.Y
Edited by: Lakshmi Soujanya on Jul 11, 2011 11:55 AM

Regarding Line items printing

Hello Experts,
                           I am developing a purchase requisition in that i am printing line items like
material no, material code, quantity. while looping the item table, below every material code i need to
display material text from a standard text object, text id like
10       material description       10000
          jkdhfjkdfghjkd
          jkxgdhvjkdhvjdkv
          nskdhvkldhvidskvkl
20      material description       10000
           jsdgcjkdsgc
           sbdjkcbdsjcd
but this material text has to extend till the end of the line,but it is not extending because i created a
text node under material description
suggest any alternate method pls

Hi,
Create table with more than 3 or 4 lines ans for main window you have to use two lines. One is for item details and other one is for material text (This line should not have any coloumns). Then it should print till the end.
Thanks,
Pranav

Regarding line item in bdc

Hi,
     I tried bdc for transaction mfbf.
     After entering all values and entering into post   with correction the line item exists.
     Here using counter in bdc the batches are entered.
      say,
           (01),
           (02),
           (15).
     But after pressing page down.
     The line item changes to (02). and values are get
     stored in (02) of first page.
    Here i am facing some difficulty.
   Is there any possibility to rectify these.
   If there please send me...

Hello Shiba,
Try to do the recording again, but if you need to insert a new record in the table click the botton to add a new row, it will be always adding the data in the firts row, and the others will scrool down automatacally,
Hope this helps,
Gabriel. P

Regarding Line item

Hi Friends,
line item dimension improves the preformence i know that but can i use 13 dimensions as line line items?
or is there any limitation....please let me know friends.
---venkat

Hello Venkat,
Line item dimension improves performance; yes, but if you look into it, how it improves? you will know the answer for your question. Say you have 13 charac and you are going to have 13 different dimensions, this may not be the optimal design. having all 13 charc in a single dimension, even this may not be the optiomal design. the optimal design would be to group related characteristics with smaller crdinality into single dimension ad making the charac with very high cardinality as line item dimension and finally even grouping non-related characs with smaller dimension into a single dimension.
the reason for having a line item dimension is, say document number is a charac and it is grouped with 0country. the values for doc no will be in millions nd combining this with country (say ur proj have 4 countries) will make these milions * 4, which will be a huge set in the dimension table to perform a search during querying.
rgds,
Hari

Regarding line item details in SCRIPT

Hi Gurus,
when I am debugging my driver program all the values are coming into the internal table and i am passing that internal table to the Script form ,every thing is ok.But the item details are not printing in my form.
I checked all the sizes of the fields in my item.Every thing is ok.
I have to print the item details.How to do...?
Any help can be appreciated highly.
Regards,
Sidram

hi,
are you passing the internal table directly..??
try this way..
Loop at t_data in wa.
call write_form
endloop
in the form
texteditor,
display the item details in this way
/E element
&wa-col1&..&wa-col2&.. etc
hope this helps...
thanks
Sharath

Regarding Line item of MIRO

Hi all,
I am preparing "ENTRY TAX" report. In that report , for one of the columns i have to fetch "POTEXT" field in MIRO transaction. I am not getting in which table that value will get stored. I did SQL trace too.
If anyone could help me, i shall be thankful to them.
Thx & regards,
Ravi

Rbkp & rseg use these tables..
If not found in above tables than check in tcode SE75
here u can take help of abaper..

Regarding Line Items

Hi
I want to display customer wise open items in a report. In that I want to merge all the items by adding amounts and display it under document no. I used collect statement for this. Is there any other alternative to add the amounts and display them?
plz give me the suggestion ASAP.
Thanks in advance
venkat

Hi Venkata,
If you use
SORT <INTERNAL TABLE> BY <column name>
AT NEW 'column name'.
ENDAT.
but make sure that the 'Column name' should be at the first position other wise all data will display.... . AT NEW will not work.

Regarding sap smartforms line items

hi,
this is regarding line items in sap smartforms
when i am executing single line item i am getting out put
when i am executing with 2 line items i am getting error like bellow
You tried to switch to the next table column, but no other column exists. The current column is 9. The line type IT_GEN contains only 9 columns.
plz explain clearly

Hi,
if you are using template and the line type is for 1 to 2 lines in the template... make sure that column position you mention is equal to the number of cells in the line type... if the data is displayed in the second row the row position should start from 2 and and column position should lie between 1 and 9.
Just a suggestion ... its better to go with table node instead of going with template...
regards
padma

Regarding line-item-dimention

Similar Messages

Maybe you are looking for