Attributes in dimension

Hi there,
This is more of a question around dimension modelling.
Should we be adding attributes of a master data info-object as part of the dimension even if the master data info-object is already part of the same dimension? e.g. if material group is an attribute and material is already part of Product dimension, is it wise to add matgrp in the dimension?
I think it increases the size of the dim.table by generating more no. of SID combinations.
How does this approach work performance wise vs.
1. Not adding attributes at all if Master data info obj. is already part of the dimension and adding them as and when required in the query designer.
2. Marking the attribute as navigational.
Suffice it to say, that the attributes in the dimension would have extensive analysis, i.e. a lot of queries would be based on these attributes.
Thanks.
Ashu.

Ashutosh,
The decision to model an attribute as a part of a dimension or as a navigational attribute is decided by how changes to the attribute value are to be handled.
For e.g. If Mat1 belongs to Grp1 today and it changes to Grp2 say a month down the line how is the data to be reported.
if it is to be reported as per the group that it was in when the transaction was created, then it should be modeled as a part of the dimension.
If the data is to be reported as per the latest value, even for data that was created when it was actually in GRP1, then it has to be modeled as a navigational attrobute.
Assuming that you want scenario 1, then it should be modeled in the same dimension as the material. As every material belongs to only one material group, the number of entries in the dimension table will not increase. The number of SID combinations should not increase.
Cheers
Aneesh

Similar Messages

  • Adding attribute to dimension in a mapping

    Hi,
    I am working on a mapping for type 2 slowly changing dimension, just like it is described in a OTN document. There it is said that we have to add an attribute "matching" to the final dimension target. When i try to do that in a mapping I see that buttons for adding and removing attributes from dimensions are disabled. Is there a way to enable those buttons, or do I have to add that attribute outside the mapping through "edit dimension" option.
    I am using OWB 9.04

    Hi,
    If I'm correct the document you refer to is using an table object and not a dimension as a target.
    Technically it will work because you don't need the dimension information. But there are some steps you have to do to get it working.
    1. Create an Unbounded table which is exactly the same as the dimension. (You can use the dimension as a source and delete it afterwards.)
    2. Now you can create the MATCHING column.
    3. In the properties set the bound name of the table to the dimension.
    4. In the properties of the MATCHING column set the bound name to the primary key of the dimension.
    In this way the Slowly Dimension Type 2 mapping will work.
    With kind regards,
    Bas Roelands

  • Metanet -  own MetaStar doesn't accept Attributs of Dimension

    Hi,
    I'm creating a form displaying Personal Infotype Datas instead of Payroll Datas.
    For displaying Datas of Infotype 13 Social Insurance Germany (01) I created a new MetaStar ZSOCIAL_INS_DE Containing the Dimension SI_KEY_DE.
    As I am reading Infotype 0013 I had to copy the Function Module HRF_DE_READ_SIKEY and changed the type of ms_data to P0013.
    The Dimension SI_KEY_DE contains Keys and Attirbuts. In the Originanl MetaStar SOCIAL_INS_DE and a copied MetaStar the Attributs of Dimension SI_KEY_DE can be found under RegisterCard MetaFields.
    As Soon as I create a new MetaStar the Attributs of Dimension SI_KEY_DE are not inserted in REgisterCard MetaFields. Therefore when generating the Print-Programm of the Form the Attributs (Ex. AVKEY_OFFICIAL) are not in the importing Parameter at Call Function even they are defined under Export in SE37.
    At the moment I helped myself with copying Dimension SI_KEY_DE to a z-Dimension and changed all Attributs to Keys.
    Does anybody knows how to insert an Attribut of a Dimension into RegisterCard MetaFields of a MetaStar?
    Thanks
    Petra Käß

    Hi,
    I'm creating a form displaying Personal Infotype Datas instead of Payroll Datas.
    For displaying Datas of Infotype 13 Social Insurance Germany (01) I created a new MetaStar ZSOCIAL_INS_DE Containing the Dimension SI_KEY_DE.
    As I am reading Infotype 0013 I had to copy the Function Module HRF_DE_READ_SIKEY and changed the type of ms_data to P0013.
    The Dimension SI_KEY_DE contains Keys and Attirbuts. In the Originanl MetaStar SOCIAL_INS_DE and a copied MetaStar the Attributs of Dimension SI_KEY_DE can be found under RegisterCard MetaFields.
    As Soon as I create a new MetaStar the Attributs of Dimension SI_KEY_DE are not inserted in REgisterCard MetaFields. Therefore when generating the Print-Programm of the Form the Attributs (Ex. AVKEY_OFFICIAL) are not in the importing Parameter at Call Function even they are defined under Export in SE37.
    At the moment I helped myself with copying Dimension SI_KEY_DE to a z-Dimension and changed all Attributs to Keys.
    Does anybody knows how to insert an Attribut of a Dimension into RegisterCard MetaFields of a MetaStar?
    Thanks
    Petra Käß

  • Attribute calculations dimension is absent while refreshing database in planning app

    Dear All,
    I have loaded two attribute dimensions and a custom dimension called "Program" in my planning application. These attributes has to be associated with the "Program" dimension members". After loading these dimensions I tried to refresh the planning application. But it throws me the following error.
    "Attribute calculations dimension is absent"
    Kindly guide me to overcome this issue.
    SC

    I take that you are using EPMA (the fact that you were able to create an attribute dimension without associating it with a base dimension).
    You'll have to create an association, to attach the attribute to a sparse dimension.
    Creating Dimension Associations
    You can create a property for each attribute (I usually call it as <name of the attribute>_Prop)
    Regards
    Celvin

  • OBIEE Plug-in for AWM error: Missing spread attribute for dimension\

    Hi,
    While trying to export a cube to OBIEE administrator using the AWM plugin for OBIEE we get the following error for a lot of dimensions.
    AWM version is 11.1.0.7.0B on a 11.1.0.7 DB
    ERROR: Missing spread attribute for dimension DAY_FLG at level ALL_FLAGS
    ERROR: Missing spread attribute for dimension DAY_FLG at level FLAG
    ERROR: Validation problems found for dimension DAY_FLG
    Dimension DAY_FLG will not have UDML generated
    As suggested in other forums I have created a long_desc attribute and selected the "created level attribute in views" option for all the dimensions in the cube, still the error persists.
    Please help.
    Regards,
    Abhishek
    Edited by: 866977 on Jun 20, 2011 3:30 AM

    Thanks for you response David. But I'm afraid this does not solve the problem. I did it to all the dimensions and the error on day_flg persists. I noticed that an error on one of the other dimensions thougfh has changed. Detailed error below:
    ERROR: Missing spread attribute for dimension DAY_FLG at level ALL_FLAGS
    To Fix error: In AWM on the attribute panel for the long description attribute of each applicable dimension -
    select the check box 'Create level attribute columns in views'
    ERROR: Missing spread attribute for dimension DAY_FLG at level FLAG
    ERROR: Validation problems found for dimension DAY_FLG
    Dimension DAY_FLG will not have UDML generated
    ERROR: Missing spread attribute for dimension HOUR at level ALL_HRS
    ERROR: Spread Attribute HR_LONG_DESC found but is not visible for level HR
    The dimension HOUR will be marked invalid and no UDML will be generated for this dimension or any cube dimensioned by this dimension.
    ERROR: Validation problems found for dimension HOUR
    Please help

  • Attribute as dimension

    Hi gurus,
    1.can we use attribute as dimension in any case.

    HI,
    1. No a dimension HOLDS characteristic(s). Attributes can be characteristics, but a dimension is something different. It's how you group your characteristics in your info provider. (max 13 + 3 SAP defined).
    Kind regards
    /martin

  • Force OBIEE to display attribute as dimension property and not separate dimension

    Hello,
    I have following question - in my project which utilizes Essbase and OBIEE I am interested in display of attribute as a characteristic of dimension and not as separate dimension.
    OBIEE generates following mdx statement:
    With
      set [_Prod.Manufacturer2]  as '[Prod.Manufacturer].Generations(2).members'
      set [_Product6]  as 'Filter(Descendants([Product], 8), (([Product].CurrentMember.MEMBER_Name = "P3336" OR [Product].CurrentMember.MEMBER_ALIAS = "P3336")))'
    select
      { [Measure].[Volume] } on columns,
      NON EMPTY {crossjoin({[_Prod.Manufacturer2]},{[_Product6]})} properties MEMBER_NAME, GEN_NUMBER, [Prod.Manufacturer].[MEMBER_UNIQUE_NAME], [Prod.Manufacturer].[Memnor], [Product].[MEMBER_UNIQUE_NAME], [Product].[Memnor], [Product].[Alias_table_1] on rows
    from [APP.DB]
    while I am interested in achieving following - where attribute Prod.Manufacturer is displayed as property of Product dimension and not as separate attribute
    With
      set [_Axis1Set] as '{Filter(Descendants([Product], 8), (([Product].CurrentMember.MEMBER_Name = "P3336" OR [Product].CurrentMember.MEMBER_ALIAS = "P3336")))}'
       select
      {[Measure].[Volume]} on columns, {[_Axis1Set]} properties [Product].[Prod.Manufacturer],MEMBER_NAME, GEN_NUMBER, [Product].[Memnor], [Product].[Alias_table_1]  on rows
    from [APP.DB]
    OBIEE generates expected syntax for Alias tables, is same possible with attributes?
    How ?
    thx
    Tomek

    Thanks heaps for your answer, Vladim!
    That's funny, huh? As mentioned, in respect to the Workstatus control, SAP made that functionality available for the Owner property of the Entity dimension (i.e. more than one user can be declared as an owner of a e.g. Cost Center and could hence change a particular Work Status).
    Any ideas for a workaround ?
    Have a good weekend...
    Claus

  • All values showing up when selecting attributes from dimension

    I have two dimensions:
    DimCustomer - CustomerID, name, etc
    DimProduct - ProductID, price etc
    FactOrderDetail - CustomerID, OrderID, OrderDetailID, ProductID
    When i drag CustomerName onto the pivot table, it shows ALL customers.
    When I then drag ProductName on to the pivot table, it does a cross join, links all Customers to All Products.
    I expected id only get a list of customers linked the products they bought, due to the relationship through the fact table. What am i doing wrong here?

    You need to add a measure in the pivot to make the relationship effective.
    Something simple like this should work:
    RowCount:= COUNTROWS(FactOrderDetail)
    That works, thanks!
    How come a measure such as TotalValue:=SUMX(product,product[Cost]) doesnt work?

  • Oracle DB 10g and BI Discoverer for OLAP - Dimension Attributes

    Hi,
    We are using Oracle Database 10g release 1 with partitioning, data mining and OLAP options and Analytic Workspace Manager 10.2.0.1.0A to create the multidimensional objects. For the user dimensions created using AWM we have custom attributes like HireDate, StartDate, Sales Personnel Role etc., For reporting purposes we are using Discoverer for OLAP. In this Discoverer version, I don't see an explicit provision to drag these attributes onto the worksheet. We are only able to filter based on these attributes and capture the measures...
    Can someone throw light on this? Also, if there is a possibility to drag these attributes onto the worksheet can that be expounded?
    Thanks in advance!

    Again this depends on what you are trying to achieve. If you define an attribute against a dimension it takes very little space as it is not directly connected to a cube and so no data is stored against that attribute.
    If, however, you have a 4D revenue cube (product, geography, channel, time) with products attributes COLOR and PACK SIZE and you want to view revenue additionally borken-out by COLOR and PACK SIZE as well as the other four dimensions then your schema will require additional storage space. However, 10g compressed cubes and sparsity options do help to manage the explosion of data points as the number of dimensions increases. This should allow you to easily add attributes as dimensions into your cube.
    One thing to remember is that most users start to struggle when confronted with more than 9 dimensions. So although Oracle OLAP can create extremely large dimensional models, users prefer their cubes to have 9 or fewer dimensions.
    Hope this helps,
    Keith
    Oracle Business Intelligence Product Management
    BI on Oracle: http://www.oracle.com/bi/
    BI on OTN: http://www.oracle.com/technology/products/bi/
    BI Beans http://www.oracle.com/technology/products/bib/index.html
    Discoverer: http://www.oracle.com/technology/products/discoverer/
    BI Software: http://www.oracle.com/technology/software/products/ias/devuse.html
    Documentation: http://www.oracle.com/technology/documentation/appserver1012.html
    BI Samples: http://www.oracle.com/technology/products/bi/samples/
    Blog: http://oraclebi.blogspot.com/

  • ODI Planning Attribute Dimension

    I have an existing Product dimension that was created via ODI 10.1.5.6 to Planning 11.1.1.3.03 -- the Product Dim loads fine. Then I attached an attribute dimension called "Product Line" to it using custom attributes. I added four attributes to attach to products. Then re-reversed the Planning application in ODI Planning Model. I can see "Product Line" attribute load dimension (to load new attributes) in the Dimension hierarchy in ODI. However I cannot see a new Column for "Product Line" under the "Product" dimension in ODI. Am I missing something??

    So adding the manual dimension seemed like it would work. However it gave me an error as it didn't recognize it when I executed the integration. In any event, deleted the planning model, recreated it and reversed it and the field showed up. Fun stuff! Thanks again.

  • Create Attribute Dimension by rule file

    Hi,
    How can we create an attribute dimension and associtae members of sparse dimension with members of attribute dimension by using a rule file?
    There is no option of 'Attribute' under dimension type in dimension propertites.
    Plz help on it.
    Atul K

    First you have to create a standard dimension and made the storage setting sparse.
    Then, you can create another dimension of type Attribute and associate it with the standard sparse dimension.
    Then you can write rule files for attributes.
    If you are assigning the attribute dimension MKT_TYPE to the standard dimension MARKET and the generation 4 is the last.
    The typical rule file is like this:
    Gen4, MARKET MKT_TYPE 4, MARKET
    New york Big Market
    Washington Small Market

  • Problem adding attribute dimension

    Version: 9.2
    Cube: ASO
    I feel like I am dropping the ball. I am trying to add an attribute to my ASO cube at the bottom of my outline. Everything I try to edit the member properties I get an "Attribute Calculations dimension can not be created". I don't have any calculations/consolidations.
    When I click the database properties-->Attribute settings-->Calucation dimension names-->(try entering a name) all I get is "NULL value for member name string".
    When I use ASOsamp(or any app) I can create/tag an attribute dimension though.

    Hi There,
    I guess you might've added a Gen1, member, i.e. a dimension, at the end of the outline & intended it to be an Attribute dimension. Correct?
    If yes, after adding the member at the end,
    - Before opening the dialog for member properties, tag the dimension as "Attribute" by clicking on the appropriate icon, right on the outline page.
    - Associate this attr. dim to one of your sparse dims.
    - Add a member to the Attribute dim. & associate it with one of the members of sparse dim.
    - Now, it should let you save the outline.
    Good luck!
    - Natesh

  • Attribute dimensions (11.1.2.2)

    Is it so that you cannot use attribute dimensions (retrieving data) in Excel when logged in using a Planning connections? Works fine using an Essbase connection to the same Essbase cube. Doesn´t work at all when logged in using a Planning connection.
    As Planning is used for input I can sort of see a logical reason for it, but on the other hand I wouldn´t be surprised if it is supported either... Anyone?

    You can use attribute when using Planning connection.
    Peform adhoc-analysis and then you can type in the attribute member/dimension name
    Regards
    Celvin
    http://www.orahyplabs.com
    Please mark the responses as helpful/correct if applicable

  • Load fact table with null dimension keys

    Dear All,
    We have OWB 10g R2 and ROLAP star schema. In our source system some rows don’t have all attributes populated with values (null value), and this empty attributes are dimension (business) keys in star schema. Is it possible to load fact table with such rows (some dimension keys are null) in the OWB mappings? We use cube operator in mappings.
    Thanks And Regards
    Miran

    The dimension should have a row indicating UNKNOWN, this will have a business key outside of the normal range e.g. -999999.
    In the mapping the missing business keys can then be NVL'd to -999999.
    Cheers
    Si

  • Error while adding attribute

    Hi All,
    I have a BSO cube with 9 dimensions and want to add attribute dimension to generate report based on the managers responsible for different locations. When I created a dimension a new dimesion and changed its dimesion type to "Attribute" dimension I'm getting error which says "Attribute Calculations dimension/member name already used" but that name is nowhere else used in the dimension. Any idea what could be the cause of this error?
    Using version 11.1.1.3.

    Thanks Tim,
    There are names such as headcount, Avg_rate etc in some of the dimensions but it is not possible to change those names in the outline. You had mentioned that we can change the name in the "Attribute Calculations Dimension", how do we do that? because the document says this is a hidden dimesnion which gets created when we create first Attribute dimension.
    "You will either have to change the name in the 'Attribute Calculations Dimension' or in the existing outline."

Maybe you are looking for