This action might not be possible to undo. Are you sure you want to continue?
Search the Community
Solutions Industries Lines of Business
Services & Support Training & Education University Alliances
About SCN Partnership Events & Webinars
Downloads Developer Center Innovation
Activity Brow se Communications Actions
7 Replies Latest reply: Nov 18, 2008 10:27 PM by Ram Goswami
Ram Goswami Nov 17, 2008 10:28 PM
This question has been Answered. Guys, I understand designing dimensions in infocuve play an important role when it comes to performance both dataload and query sides. I read some interested tips on sdn etc. like the following: 1. small dimensions 2. few dimensions (less important than small dimensions) 3. only as many details as necessary 4. characteristics in the 'right' order (technical order >>> most selective first) 5. hierarchies only if necessary 6. time dependent structures only if necessary 7. avoid MIN, MAX aggregation for key figures in huge infocubes I have 20 chars and 8 keyfigures and I am asked to design an infocube. I know we are only limited to 13 dimensions. Each of which can have up to 248 chars and 233 keyfigures. How do I know which char to group with with another char and put them in one dimension and which one will go as a line item dimension? If I made every dimension as line item dimension, I won't have enough dimensions. Please help. Someone on SDN saif that 1:1 char should go into one dimension but I am having tough time understanding this. sample: Char1: Char2: Char3: Char4: Char5: Char6: Char7: Char8: Char9: Char10: Char11: Char12: Char13: Char14: Char15: Char16: Char17: Char18: Char19: Char20: When looking at 1:1 relationship. What 2 chars am I comparing this 1:1....Char1:Char2 ??? Char1:Char3??? and so on Thank you, RG
Thanks Ajeet Helpful Answer by Ajeet Kumar Singh 532 View s Average User Rating (0 ratings) Ajeet Kumar Singh Nov 18.e.the one for which the dimesion is showing in red are badly built.sales org.. and generate huge dimension table. then modify them accordingly.customer sales.. After creating and data loadings of the cube you can check the dimensions behaviour in RSRV well. bill to party should go together. Or try to put those char in the dimension which belong to each other. Try to avoid those characteristics in the same dimension which generates more number of combination. .. Different kind of customer objects e. 2008 5:13 AM (in response to Ram Gosw ami) Re: Dimension issue Hi.. The characteristics in the dimension are chosen wisely. try to analyze the source records before creating the cube.. Genrally company codes sales org division distribution channel are commmon and should be put together. 2008 9:40 PM HI Ram. The same rule applies with all the 20 chars..item lenght etc. shipt to party. You know better about the source system and should be aware of the kind of data you get.if you put customer and material together then the size of dimension will be beyond imagination.g..company code.. Go for line item only for those objects which are huge in number like billing doc.. payer. each item will have one category asscociated with it.material doc. you should go by functional knowledge as well as bit experience.etc.This will give you a fair amount of idea. You will put all the company lebel information in same dimension like... material. etc..material plant( material compounded with plant). So you will put them together in one dimension along with all those char which are related to items. You can use the program SAP_INFOCUBE_DESIGNS to see the existing cubes which are loaded into production and try to see what is the ratio for the dimensions for which combinations of characteristics . For example Sales document item category and item number have 1:1 relation i.sales doc.after 2 or 3 takes I think you should have an idea...This will reduce the size of dimension..Here also you can see the dimension percentage of the cubes. You will have to group all of them logically. I generally put all the dates together all the document numbers as line item...which are always unique.. item description...e. etc.all sold to party. Another example You have different kind of material objects ..customer partner.g.eg.Correct Answer by Ajeet Kumar Singh on Nov 18. customer. they are only made line item so that they do not combine with other objects and create many record for every one records of material..You will put all the material objects in the same dimension.all the customer objects in the same dimension. Since the value of material and customer is always the same in different infoobjects...
.Before grouping characters in a dimension... 2008 6:12 PM (in response to Ram Gosw ami) Helpful Answer Re: Dimension issue Hi. For above example when you load the data from R/3 . . Thanks Ajeet Like (0) Debjani Das Nov 18.e.... I hope it explains. Sales document category and item number are keys......all the customer objects in the same dimension"Thanks...Hope it explains.but if customer address is put in a dimension with customer then we will get only one record per customer. Thanks for your reply. like the example you gave "Sales document item category and item number have 1:1 relation i... RG Like (0) Ajeet Kumar Singh Nov 18.... But if you try to put a customer address with material it will create lot of combination as one customer can have many material sold to it and therefore per customer many records. I think you are saying that I need to find KEYS in my chars..You will put all the material objects in the same dimension..this all if put together in same dimension will not result in more then one combination and therefore only on record in the dimension table...You will put all the material objects in the same dimension.. Always try to keep the the size of the dimension table as small as posiible.. . each item will have one category asscociated with it..".you can put different infoobjects which contains same kind of values like cusomer sales..all the customer objects in the same dimension" By this I meant.. 2008 7:01 PM (in response to Ram Gosw ami) Re: Dimension issue Hi Ram. For your understanding you can take it as keys........always keep this thing in mind..customer compounded with comapny codes.. Bascially its just a concept to keep the size of the dimension table as small as possible. Thanks Ajeet Like (0) Ram Goswami Nov 18. 2008 5:41 PM (in response to Ram Gosw ami) Re: Dimension issue Ajeet... "Since the value of material and customer is always the same in different infoobjects..for a particular record in the cube all these fields will generally contain the same value so when put together in the dimension table will not create many combinations. And as I have written depends mainly on how the data is coming from R/3 data source.. Did I understand you correctly? Also what do you mean when you say "Since the value of material and customer is always the same in different infoobjects.......
then modify them accordingly. What do I do when I am dealing with 20 or more chars? Thanks a lot again RG Like (0) Ajeet Kumar Singh Nov 18.000 reads of the number range table and 1............ However..the one for which the dimesion is showing in red are badly built... the examples you guys provided will only suite if I were to have 2 chars..... try to analyze the source records before creating the cube...000 * 1.. Two charcteristics with no correlation Char A and Char B.after 2 or 3 takes I think you should have an idea.......what will be the size of the dimension table....... Like (0) Ram Goswami Nov 18..000 reads ) to get the next Dim ID number. I am much more clear than before.. shipt to party... .000. Thanks a lot for your valuable information. Thanks Ajeet .000 new values of Char A and 1.. Genrally company codes sales org division distribution channel are commmon and should be put together....... 2008 9:01 PM (in response to Ram Gosw ami) Re: Dimension issue Guys... you potentially could have a combination of characteristics where every value for Char A......For an example.. then the load process only has to read the number range tables for each of the dimensions 1.....Here also you can see the dimension percentage of the cubes. The load process then has to insert 1...000 new values of Char B. Regards. Now what happens if you put both Chars in the same diemsnion...000 inserts to the Dimension table... bill to party should go together. you have every possible value of Char B .. Since they are unrelated.just imagine the size of the table.000 times ( total of 2..So if u do permutation combination...000 records into each of the dimension tables ( total of 2... Assume that every day when the transactions are loaded to the InfoCube........ I generally put all the dates together all the document numbers as line item.000 combinations of values. But if u put Material number and material description in one dimension...... If each Char is in a separate dimension.For one material there will be only one description..... payer...... 2008 9:40 PM (in response to Ram Gosw ami) Correct Answer Re: Dimension issue HI Ram..Suppose if u put Customer and material in a single dimension.. That would translate to 1... Debjani..000 writes )....This will give you a fair amount of idea.....So there lies the problem.... The same rule applies with all the 20 chars..........or 1.number of characteristics in a dimension is directly proportional to the overload in load time....one customer can take different materials.. You can use the program SAP_INFOCUBE_DESIGNS to see the existing cubes which are loaded into production and try to see what is the ratio for the dimensions for which combinations of characteristics ................. After creating and data loadings of the cube you can check the dimensions behaviour in RSRV well...then its ok. there are 1.... You know better about the source system and should be aware of the kind of data you get.000. You will have to group all of them logically.....all sold to party...
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.