Differences between High cardinality and line item dimension

Please Search the forum
Friends,
can any one tell me the differences between High Cardinality and Line item Dimension and their use.
Thanks in Advance.
Jose
Edited by: Pravender on May 13, 2010 5:34 PM

please search in SDN

Similar Messages

Difference between Transaction Figures and Line Items

Hi,
I gone through FI like FI-GL,FI-AR,FI-AP..there i find...
Line Items & Transaction figures as main...like
in FI we have
Line Items - 0FI_GL_4,0FI_AR_4,0FI_AP_4 etc...
Transaction Figures - 0FI_GL_6,0FI_AR_6,0FI_AP_6 etc...
Now Can some please explain...
what exactly Line Items are?
What exactly Transaction Figures are?
How data flows from end to end in FI? i.e where exactly GL,AR,AP comes into picture..how they are internally related?
Some one please explain me in detail (with expamles if possible) and quick reply is much appreciated...
Regards
Ramsunder

Hi
What exactly line items :
Line items are document items that were posted to a specific account. In contrast to a document item a line item only contains the information from the document that is relevant from the account view.
You can display the following line items:
Open items, Cleared items, Noted items, Parked items ,Items with special G/L transactions (in Accounts Receivable and Accounts Payable),Items with customer or vendor items (in Accounts Receivable and Accounts Payable)
You can display the line items for the following account types: Customer accounts,Vendor accounts,G/L accounts.
What exactly Transaction Figures are?
Transaction figures are the sums of line items on the debit or credit side. The balance is the difference between the debit and the credit transaction figure.
If you take General ledger
AP records all accounting transactions for dealings with suppliers(Vendors). Much of its data is obtained from procurement (Materials Management).
AR records all accounting transactions for dealings with customers. Much of its data is obtained from Sales and Distribution.
Asset Accounting records all accounting transactions relating to the management of assets.
Travel Management manages and calculates travel costs and supports travel planning and travel expenses.
Bank ledger supports the posting of cash flows.
Regards
Chandra Sekhar T

Difference between cumulative balance and line items total in FS10N

hi,
when I am executing FS10n, I observed that the cumulative balance amount is not equal to line items total . This is due to some amounts in previous years are varying from the line ltem totals in those periods of previous years.
This is not happening with QA server only Prdn server is facing this problem. Can anybody provide me a way to solve this..!?
Regards,
AJo
I have checked the master data for the GL and the check box for line item display is selected. It has not been changed for years.
Edited by: Anil Jonnalagadda on Oct 22, 2008 10:57 AM

Hi Anil,
The reason for the differences that you are viewing can be various. As the differences are found in the cummulative balance then it means that the differences might have occurred in previous fiscal years. The first stetp is to find when these differences were originated: You can run report SAPF190 (in se38) for previous fiscal years, and company code in question- This report should show the differences with message "Errors" in the log. If differences are found then you have to creeate a message and send it to SAP for further analysis and corrections.(only SAP experts can do this kind of corrections - component FI-GL-GL-X)
Also bear in mind that if you did archiving in previous fiscal years then this would not be an error:
If you already did archiving and secondary index deletion on this accounts with SAPF048I. So this explains why line items balance and GL summary balance differ ! There is no programm error.
See consulting note 81489 which describes this issue:
The balance of an account results from the balance of the open items. In
connection with an archiving that has been carried out, the line item
display - used with cleared items - must not therefore be interpreted as
a balance display. For the balance display, there are separate
correspond to the display balance of the open items from the line item
display.
Having archived and deleted secondary indexes ( with SAPF048I )
for an account you can not use line item drill down as a balance
display any more for a line item managed account.
( as not all line items are existing any more in table BSIS ! )
The transactions meant to display the binding balances are FS10N,
FK10N and FD10N.
They also give you the line items details, but only of those line
items not yet deleted ( by SAPF048I ).
kind regards,
Oscar Diaz

High cardinality and line dimenson

Hi
Are High cardinality and line dimenson both are dependent?
my understanding is that if the dimenson is more than 10% size of the fact table then we go for line dimenson. Highcardinality should be given only if the dimenson is more than 10% of fact table.By choosing line dimenson,fact table will be directly linked to sid table as there will be no dimenson table. Does it mean if I choose line dimenson, I can't go for high cardinality as there is no dimenson? Please let me know the relationship the between the two?
Thank you
Sriya

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.
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:
       1.      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: This 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.
For example a dimension having Sales Doc number and Sales Org can be set as High Cardinal as Sales Doc number will occur many times.
Hope this helps
Raja

Expert advice needed on Remodeling and line item Dimension

Hi All,
Scenario:
I have a cube 0FIAP_C03 for line Item. Now in this cube one of the dimensions u201CC036 -Document Detailsu201D is reaching the size of the Fact table. We are planning to use Re-Modelling and shift some of the characteristics like 0DOC_NUMBER - Sales Document, 0AC_DOC_NO - Accounting document number etc from this Dimension to another Dimension to reduce the size of this Dimension Table.
I have the following Questions:
1Will it be possible to add a new dimension and shift some characteristics from old Dimension to this new Dimension using remodeling( we donu2019t want to delete data from the cube)
2.what are the other feasible options to overcome the problem I have mentioned in my scenario( like Line Dimensions)
3.In case we can make this dimension as Line Dimension what other changes need to be made.
I am looking for a detailed explanation with all prou2019s and conu2019s, So kindly help me with your expert inputs.
Thanks,
Prafull.

Hi Prafulla,
Answers to your questions
1Will it be possible to add a new dimension and shift some characteristics from old Dimension to this new Dimension using remodeling( we donu2019t want to delete data from the cube)
No, remodelling wont work as per my understanding. ie You will have to delete and reload data
However, this also depends on the data in your dimension.....................................................
Consider the following example
Index(Dim-id).....Sales document............Sales Item............Accounting document
1......................1233456........................10.......................A123 .......end of record
2......................1233456........................20.......................A123.......end of record
3......................1233456........................30.......................A123.......end of record
Now suppose if you had to remodel the above dimension to move sales item to other dimension, then the dimension would appear as below................................................................................................
Index(Dim-id).....Sales document............Accounting document
1......................1233456.......................A123.......end of record
2......................1233456.......................A123.......end of record
3......................1233456.......................A123.......end of record
Now the problem is for the same combination of sales document and accounting document you should have had 1 row in the dimension, but you are having 3 rows(indexes) hence you are flouting the uniqueness for read and write operations to the dimension.. So logically this shouldnt be allowed...
However if your data in the dimensions is such that the uniquness of each row in the dimension is not disturbed, you could use remodelling.
You can try this in quality.
2.what are the other feasible options to overcome the problem I have mentioned in my scenario( like Line Dimensions)
I am not sure if I have understood your question. But I will still try to answer. If the dimension table has reached the size of the fact table then it is appropriate to consider remodelling.
Also you should consider embedding sales document and accounting document in the same dimension. Since there would be generally only one accounting document each sales document.
Use line item dimensioin as far as possible(restricted by number of characteristics). It reduces one step whie query since SIDs are directly present in fact table.. so you don't have to scan through dimension table.
Also have you considered archiving old dat not reported... It will reduce your dimension as well and improve performance...
3.In case we can make this dimension as Line Dimension what other changes need to be made.
-No other changes.
A safer option is to delete and reload data. Anyway remodelling also recommends a back up...
Its better to create a copy cube and use the copy cube/original cube for reporting until the other cube is getting processed to have minimal time of unreportable data.
Apologies .. Looks like the text in the post is loosing the format in which I typed hence the allignment is not correct..
Hope this helps,
Best regards,
Sunmit.

What is the difference between Personnel Administrator and Line Manager?

I understand that Personnel Administrator is responsible for all the master data in Personnel Administration. Who is Line Manager in Recruitment? While administering the vacancies, what is the difference between both of them in Recruitment.
Points assured.

Hi Nivedita,
A line manager may be a chief position in OM Structure.
A person who holds a managerial position in a company or department and who makes decisions in an area of responsibility.
Line managers can act as the first person responsible for applicant correspondence.
In the Recruitment workflow, tasks requiring a decision are sent to line managers.
Regards,
Kapil

Whats the difference between high-density and low-density ram?

I bought what I thought was supposed to be a cheap 256 mb chip (pc100 or 133) but the g4 400 read only 128mb, The fellow in the store that sold it flipped out when I told him I had a Mac and said something about high density and low-density.Another guy in the store described it as being one sided and two sided.
I don't know what my machine needs. I got my money back but he would'nt let me exchange the chip for another, me thinking it was simply mislabeled.

The QuickSilvers use PC-133 SDRAM and are compatible with high-density memory chips (256 Megabit), so that 16-chip 512 MB and 8-chip 256 MB non-ECC DIMMs are supported. A low density, 16-chip (128 Megabit) 256 MB DIMM is also supported.

Difference between Free goods and normal items

Where we have to create free of goods?.Is it in MM or pricing.
Is it necesssary to stock the free material.
If free goods also manufacturing in a same plant,how to handle in sales order.Because this item already created in MM

hi,
Instead of giving monetary benefits, the company prefers to give the free goods for the customer in the ratio of 1:1 occasionally.
in standard sap, normal pricing procedure will be assigned to ur sales area Doc. pricing procedure (A) Customer pricing procedure, where as free goods also will be assigning it to ur sales area,but the document pricing procdure will be as C- denotes free goods.
In sap, the free goods condition type is NA00, and even access seq. also will be Similar to condition type (it's ur wish to maintain like that), and the pricing procedure as NA0000.
the transaction code for freegoods is VBN1, where u can maintain ur condition records, here there will be a two option.
1. inclusive and 2. exclusive. maintain the records and save it.
kindly check the item category TANN, there pricing relevance should be B- free goods.
u have to maintain the free goods stock in ur plant. (its juz for transaction purpose).
i hope ur problem will be solved.
reward points if it is useful.
regards
KR

What is the difference between the "sent" and "sent items" folders?

My email is in the "sent" folder but not the "sent items" folder. How do I know my email has actually been sent?
Why are there two folders?
Can I just use one?
Thanks in advance for any help.

If anyone was interested I was able to find a relevant question here:
https://support.mozilla.org/en-US/questions/1015564
<blockquote >
Emails sent from Thunderbird go into the "Sent" folder. Emails from Android phone go into the "Sent Items" folder. MS Outlook sees both, but TB only sees "Sent"
</blockquote>
This webpage was helpful:
http://helpdesk.princeton.edu/kb/display.plx?ID=9430
<blockquote >
Sent vs. Sent Items <br>
In Thunderbird, the Sent folder (located on the IMAP mail server) retains a copy of each of your outgoing e-mail messages. This is a function that can be altered in the preferences, but is most often configured in this way on the Princeton campus. '''Outlook does not recognize that the Sent folder is any different from any other e-mail folder. Outlook's equivalent of the Sent folder is called Sent Items and is generally stored locally rather than on the central mail server.''' When you begin using Outlook, copies of your outgoing e-mail messages will be stored in the Sent Items folder. The Help Desk recommends that you create a rule to send copies of your Outgoing messages to your Sent folder on the IMAP server. See Solution 9202 for instruction.
</blockquote>
This one also:
http://office.microsoft.com/en-001/office-online-help/set-up-email-in-mozilla-thunderbird-8-0-HA102823188.aspx
<blockquote>
If you’re using an incoming POP3 server, you can only synchronize your Inbox folder. If you’re using IMAP4, you can choose the folders that you want Thunderbird to synchronize with the server. Remember that IMAP4 doesn’t support the synchronization of the Contacts and Calendar folders. '''Thunderbird uses a folder named Sent to store sent items. Exchange and Outlook Web App use a folder named Sent Items.''' You can synchronize the email items that you’ve sent in Thunderbird with the Sent Items folder on the Exchange server. To do this, follow these steps:
</blockquote>
This is about the “sent mail” rule:
http://www.ucl.ac.uk/isd/staff/mail/configure/thunderbird/sent_mail_rule

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

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 dimensions and cardinality?

hi all,
how to identify nor use the cardinality relationship as well as the line item dimension?
can anyone explain me about it. since i am trying to create an multi provider which enables to fetch data from 3 ods.
regds
Hari Chintu

Hi,
Below is some useful information on Line item dimension and high cardinality.
These concepts hold good for Cube design only, coming to ODS, these dont help you. As ODS is nothin but a flat structure, we do not have the facility of Star schema. Reporting on ODS can lead to performance issues, it is better to load data from ODS into Cube and then have a multiprovider on them instead of having it on ODS.
Hope this helps.
Regards,
Kalyan
Use
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:
       1.      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.
       2.      High cardinality: This 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.
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.
However, we recommend that you use ODS objects, where possible, instead of InfoCubes for line items. See Creating ODS Objects.
Activities
When creating dimensions in the InfoCube maintenance, flag the relevant dimension as a Line Item/ having High Cardinality.

Difference between sales order schedule line and item level data

Hi All,
Could you please let me know what is the difference between sales order schedule line and item level data?
Thanks,
Ramya

Hi Ramya,
Sales order schedule line contains del date, order qty, rounded qty, confirmed qty, delivery qty, schedule line category, purchase requisition etc., ie It contains the full details of sales order data with respect to the scheduled line of delivery. The total quantity of a sales order item can be subdivided into schedule lines that contain the various subsets with the corresponding delivering dates.
Sales order Item level data contains details of the item in the sales order like material code, net price, net value, UoM, PO details, reason for rejection if any, material group,billing date, plant etc., ie this
contains the full details of item irrespective of scheduled line.
Regards,
R. Senthil Mareeswaran.

G/L Balance and Line items difference

Dear Mates,
We have a Inventory-Spare Parts G/L account
When i see the FS10N g/l balances ,there is a figure appearing as 25,82,887/- in the period February and when i double click on the above said figure to see the line items whose total comes to 30,89,627/- with doc.type: WA.
Can please tell me ,what could be reason for the difference between Balance appearing on the initial screen and line items total.
Please treat it very urgent as auditors are sitting on my head.
Thanks
Subbu

Hi,
First let me know the SAP R/3 version and fiscal year.
In the mean time, you can also check any changes has been made to your GL account master data related to line item display.
all the best

Difference between Material type and Item category

What is the difference between Material type and Item category?
We can differentiate different kind of materails according to material type then why do we have Item category which is also more or less on the same lines.
Both can be considered as a terminology in SAP to group similar kind of materials.
Please let me know the exact difference between the two?

Dear Christino
We can list out so many differences.
When you create a material master record, the material type you choose determines:
- Whether the material is intended for a specific purpose, for example, as a configurable material or process material
- Whether the material number can be assigned internally or externally
- The number range from which the material number is taken
- Which screens appear and in what sequence
- Which departmental data you may enter
- What procurement type the material has; that is, whether it is manufactured in-house or procured externally, or both
Together with the plant, the material type determines the material's inventory management requirement; that is:
- Whether changes in quantity are updated in the material master record
- Whether changes in value are also updated in the stock accounts in financial accounting
In addition, the accounts affected by a material entering or leaving the warehouse depend on the material type.
-Most importantly, Users can be authorized to create materials of specific material types but not based on item category
- Item category will define whether the material should be valuated for stock or it should be considered as non-stock
- Pricing is carried out based on Item Category and not based on Material type
thanks
G. Lakshmipathi

Differences between High cardinality and line item dimension

Similar Messages

Maybe you are looking for