Is it possible to create an Attribute Dimension in an ASO Database?

When I create the initial attribute parent and attempt to save the outline, it gives me an error that I need to associate the attribute dimension with the base dimension. So I go to my L0 member, but the associations tab is greyed out. Any ideas if this is possible to create? Thanks!

OK, Are you doing this.
1. create the attribute dimension
2. click on the base dimesnion
3. right click on the DIMENSION NAME and selet edit properties
4. Click on the tab called Attributes. You should see the list of attribute dimensions
5. Once the dimension is associated with the base dimension, you can assign attributes to the members

Similar Messages

  • How to create an attribute dimension in Essbase Studio?

    I cannot figure out how to create an attribute dimension using Essbase Studio. The online help states that I need to "Find the Attribute settings grouping in the center" of the member properties dialog box. I suspect that I'm having a problem figuring this out because I don't have the attribute dimension properly defined in the relational data source or in the mini-schema. I've tried creating a table with no key relationship to the other tables and with no logical joins defined, but that doesn't seem to help. Any ideas?

    so in the 11.1.1 version you would click on the member name in the hierarchy you added to the Essbase model and in the center pane of the general tab should be the attributes settings section.
    If I had a dimension called stores wth two groupings unser it region and store_type, I would click on store_type and add the attribute info

  • Is it possible to create a new table in the master database with SSMS ?

    Hello ,
    I have problems with this thread :
    http://social.msdn.microsoft.com/Forums/en-US/sqlexpress/thread/5153c43b-7844-41c4-a414-d14730abe435/
    If no user database has been created , in SSMS , we can see only the 5 system databases ( master, msdb , tempdb... ).
    Logically , the user should connect automatically on the Master database ( if the user is the same as this used to install a new SQL Server instance, this user should be sysadmin that's to say he/she has all possible permissions and especially dbcreator ).
    Is it true that it is impossible to create a new table on the master database ?
    I have done many researches about this possibility , all I have found is the advice : don't touch to the master database. This database is used to store critical information about the instance and its user databases. Even in the last book of Kalen Delaney
    about SQL Server 2012 Internals , I have found nothing clear about the creation of tables in this database ( and what about the other system databases ? I am excluding tempdb ).
    If someone has an idea about this thread and my questions , I would be thankful for a reply on this thread or on the related thread in the SQL Server Express Forum ( with my poor written English , I am not sure to have poster in a correct and understandable
    way ).
    If you think that this thread is not in the good forum , a moderator of this forum can move this related thread ( I have not done the move as I am not sure which is the good forum Database Engine or Transact-SQL ... )
    Thanks beforehand and have a nice day.
    Mark Post as helpful if it provides any help.Otherwise,leave it as it is.

    >>Logically , the user should connect automatically on the Master database ( if the user is the same as this used
    to >>install a new SQL Server instance, this user should be sysadmin that's to say he/she has all possible permissions and >>especially dbcreator ).
    If you add the current user during the installation you can have it as system admin , or you can add him/her later on
    in SQL Server. BTW regarding dbcreator I have wrote some blog , need to read... :-)
    http://sqlblog.com/blogs/uri_dimant/archive/2010/09/02/be-careful-to-grant-dbcreator-server-role-to-the-user.aspx
    You can (if you have needed permissions) to create objects in master database, usually I create objects for instance maintenance (like rebuild indexes...) 
    Best Regards,Uri Dimant SQL Server MVP,
    http://sqlblog.com/blogs/uri_dimant/
    MS SQL optimization: MS SQL Development and Optimization
    MS SQL Consulting:
    Large scale of database and data cleansing
    Remote DBA Services:
    Improves MS SQL Database Performance
    SQL Server Integration Services:
    Business Intelligence

  • 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

  • Attribute Dimensions with Integration Services

    Good evening, I'm creating an ASO Essbase model through Integration Services v9.3.1 and I am having difficulties with creating an Attribute dimension that contains a hierarchy.
    We have a list of stock codes which are grouped by vendor in a dimension, each stock code has an attribute assigned to it for the buyer responsible.
    The business requirement is to start from the top level of the attribute dimension, drill in to categories, then to drill in to teams, and finally to the buyer... so we effectively require 3 levels within the attribute dimension.
    I have successfully created both the vendor (physical) and buyer (attribute) dimensions through EIS without problems, but when I load to Essbase all of the buyers are added at the top level of the dimension and I can't seem to specify that there should be a parent/child hierarchy to build the attribute dimension from.
    Is this possible, and if so any advice you can give as to how I achieve this would be greatly appreciated.
    Thanks in advance,
    Graham

    Graham,
    This is definitely a supported feature in EIS/9.3.1/ASO. I have many models with this type of structure. How you set it up can vary. Usually my Attribute Hierarchies are not that deep, only two to three levels, maybe four in a rare case, so I don't usually use a parent child table to set up the hierarchy (I'm not saying that it won't work, it might, I haven't tried, but same steps should apply). In a typical model I will have my stock table which has a buyer field. Then in another table I will have my attribute structure which will have columns for buyer, teams, and categories.
    In EIS OLAP model, you add your attribute hierarchy table and use a join to link it to the main stock table, joining on the buyer field (you are now going from a "star" schema to a "snowflake". Go into the properties and make sure you define all the columns as "Attributes".
    Then in Metadata model, drag your categories attribute onto the outline, then drag the teams and set it as a child of categories and finally drag buyer and set as child of teams. You only set the attribute association for the buyer back to the base dimension.
    When you run your dim build it will set up your attribute dimension correctly.
    Some things to keep in mind, make sure you have a process that ensures for every stock code you have in the main table, you have a matching one in your attribute dim table.
    Sometimes, depending on how much manipulation I need to do, instead of joining the tables in EIS I will go back to relational source and create a view that joins the two tables together, then in my OLAP model, I have one table that has three attribute columns, one column for the buyer and then the other two for team and category, from that point setting up in metadata model is the same.
    Good luck, let me know if you run into trouble.

  • Attributes Dimension

    I am having trouble understanding Attributes dimension. Can someone give a clear example and explain this concept to me? Also tell me how to view the Attributes in the Excel add-in.You can respond here or email me directly at [email protected] Lal

    The best way to explain attributes are to go by example. Say you have an essbase database that tracks sales of products over time. So you have a Time dimension, a Measures dimension and a Product dimension.A requirement comes along where the business needs to analyze product profitability by package size - the size of the container each product is shipped in. In older versions of Essbase, there were 2 ways to do this:1) New dimension for package type2) Shared rollups in the product dimensionThese approaches work, but they add size and complexity to the database, which increases calc time. Also, the shared rollup idea starts to get cumbersome when you introduce more things - say product color. Now you have products shipped in different packages and in different colors. You can still create shared rollups for the colors, but now the business wants to compare sales of a package/color combination with a different package/color combination. You need even more shared rollups for the comparisons.Adding a new dimension creates all of the possible combinations of product, package type and color, but if you assume that these new properties are product specific, it adds sparsity to the database.In Essbase 6, you can create an attribute dimension - it looks sort of like a real dimension, but it works by piggybacking an existing dimension. You attach package type and color tags to each product, and you can then use the attribute dimensions to slice and dice the data as you would with real dimensions.By default, Essbase will sum all of the like attributes together to give you a total - sales for all red products for example. However, you can choose from Sum, Count, Min, Max and Average, all applied dynamically.Attribute dimensions do not show up in a default Excel retrieval. You can add them to the sheet by typing them into a cell manually or using Member Select. You can then use them as you would normal dimensions.Hope that helps a bit.Regards,Jade----------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

  • How to design Flat file for loading attribute dimension in a planning application

    Dear Gurus,
    I have a requirement to extract attribute dimensions from an essbase application and load it to another planning application. I have a dimension called Program and two attribute dimensions Sales Manager, Accounts manager associated with Program dimension in Essbase application. I will Extract these dimensions using Essbase outline extractor. After Extracting the attribute dimensions I have to load these dimensions to planning applications using outline load utility. Kindly guide me how to design the flat file for loading attribute dimensions in planning application.
    Thanks and Regards
    SC

    You could dig through the docs and try to figure out the file format manually, or you could do this the easy way.  Simply use the Outline Load Utility to export your attribute dimension from Planning.  The export file format is the same as the import file format.  You might have to manually add a couple of test members to your attribute dimension so that your export file has some content.  Then simply update the file you exported, and import it.
    (I am assuming you have already manually created the Attribute dimension in Planning, and that you simply need to add members to it.)
    Hope this helps,
    - Jake

  • Loading Attribute Dimension - Hyperion Planning

    Hello Everyone,
    I appreciated a lot informations that I found here. I red the http://john-goodwin.blogspot.com/2008/11/odi-series-loading-essbase-metadata.html
    about loading attribute dimension on Essbase, but when I try to execute the same steps using Hyperion Planning Adapter in ODI, I cannot see the option inside the model to reverse also all dimension attribute, hence I cannot load members on my dimension attribute. Do you know how can I develop the attribute dimension load on Hyperion Planning?
    Regards,
    Wallace Galvão
    Brazil

    Hi,
    You first need to create the attribute dimension in planning, ODI does not create dimensions.
    Once you have created your attribute dimension you can reverse the planning application again and the attribute dimension should be created as a DataStore
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Essbase's attribute dimensions in OBI 10.3.4.1

    Hello everybody:
    As far as I know, it is possible to use Essbase attribute dimensions in OBI 10.3.4.1. But, in your opinion, is there any problem when integrating them or they work in OBI as standard dimensions?. Have somebody had any issue with this integration?
    Thank you in advance
    Regards,
    Javier

    Hello:
    I have read this article before writing this post. But it refers to Essbase 9.3.1 (I refer to 11.1.1.3) and OBI 10.1.3.3.2 (I refer to 10.3.4.1). One of the goals of my questions is knowing if something has changed since that article was written, because it implies some manual changes in the rpd.
    Thank you
    Regards
    Javier
    Edited by: Javi M on 28-feb-2011 4:51

  • Import varying attribute dimension (with a load rule)

    How do I maintain varying attribute dimensions in a model with a large base dimension? It does not make sense to manually maintain all those members in the outline.
    Is it possible to import varying attribute dimensions (with a load rule)?

    That is true for regular attribute dimensions. Nowhere, I have found instructions how to do this for varying attribute dimensions (aka slowly changing dimensions) that change over time.

  • Attribute dimensions may only be added to sparse dimensions

    Hello everyone,
    I got this error several times. It wouldn't be so surprising for me if my Account dimension would be set as dense. But it is set to be sparse...
    Could anyone help me with this?
    Maybe some details will be helpfull:
    I have created an attribute dimension with only one member - "Yes". Then, I have created flat file for Account dimension with 6 custom properties, every property associated with the attribute dimension. Account dim is set as sparse, not dense. Importing flat file results ok, with no errors and warnings. Validating the application is ok.

    Hi Andy,
    I'm using only Plan1 and account dimension is set as sparse in this plan type.
    What do you mean with "refreshing"? I'm doing redeploy of the whole application from EPMA. Or should I try refreshing the database from the application? I think the first step may be the redeploy. Or am I wrong?
    Thanks,
    Vlado

  • Attribute Dimension association

    Hello guys,
    Is there a way to associate just attribute members with the standard dimension using a rule file. Actually I have a lot of members which I need to associate with attributes & I cannot perform this manually through EAS. So can I create a rule to associate attributes to these members?
    Note: I don't have to build the dimension, I just need to associate attributes to the standard dimension members.
    Thanks in advance.

    Yes this is correct. You need to go into the dimension build setting dialog and on the dimensions tab make sure you double click on the dimension you are building to (you can tell if it work if the dimension name appears at the top of the list). In the attributes area, check the box for allow attribute changes and do not check the other box. the scroll down and set the build type (or whatever it says) to use levels.
    I'm making the assumption that you created the attribute dimension in advance and associated with the base dimension

  • Linking 2 attribute dimensions

    Dear all,I have an application that contains, among others, an "Entity" dimension and a "Territory" dimension, both of them are sparse.I have created an attribute dimension on each.The problem starts now: each entity has a natural territory where selling directly to customers is allowed (the French entity or subsidiary is allowed to sell in France); however, sales to other territories other than its own must be done through the corresponding entity or subsidiary.I have started tagging the entities with the attributes: "France"... but Essbase does not allow me to tag the territories with exactly the same attributes: I cannot use "France" for a territory.1) what is my best option for the outline2) how can I easily check in a script (in a FIX) that for the Entities in their natural territories some calculations must be done; and different calculations for the rest of the territoriesThank you very much for your help

    Yes, you can. You just cannot assign 2 attributes from the same attribute dimension to the same member.

  • Error While Building Attribute Dimension in ASO Cube

    Hi all,
    Cuurently I'm trying to bulit an ASO application in Oracle EPM 11.1.1.3
    When I'm building an attribute dimension "QSize" in ASO cube ,I'm Getting some Warnings
    I'm using Flat file as my source AND MY RULE FILE IS
    GEN2,QSIZE, ALIAS2,QSIZE
    1, ">100"
    2, "100-249"
    3, "250-499"
    4, "500-1000"
    5, "<1000"
    I VALIDATED THE RULE FILES,
    when i try to load the data into the essbase,Its giving me a warning stating that
    Record #1 - Incorrect Syntax For Member <100 (3305)
    *1 "<100"*
    and i don't see the alias name for member 1
    I came know that Essbase doesn't allow ">" character at the beginning of Dimension Or Member Name
    Please let me know if there is Any other way,where I can Assign the alias "<100"
    Thx in Advance
    Regards,
    RSG
    Edited by: SG on Jan 22, 2011 3:03 PM
    Edited by: SG on Jan 22, 2011 3:04 PM
    Edited by: SG on Jan 22, 2011 3:06 PM

    Could you get away with an underscore? I think that works. You will have _<100 which is not ideal but might be worth a try.
    Failing that, go with GT and LT. <--This is incredibly lame, but sometimes users go for the "computer is too stupid" answer. Which in this case, is sort of true.
    Regards,
    Cameron Lackpour

  • Outline will not restructure after adding another attribute dimension

    I have a large ASO outline - 9 dimensions with 30 attribute dimensions. When I add another attribute dimension - top level - and then add a single child, the outline will no longer save and restructure itself. If I clear all the data in the cube and load the new attribute, it will save and restructure. I can then add all of the data back in and actually add or remove attribute members and the cube will save and restructure itself. I have tried to up the memory setting on the application - in various increments - up to 1.5GB with no difference in performance. While I can (may have to) live with the fact that I can load the attributes in during the nightly rebuild cycle by placing them in the correct build order in the MaXL scripts, I can no longer run an update for that attribute in EAS console on demand. Has anyone else had this problem with a large number of attribute dimensions in their ASO cube and if so, how have you gotten around it. As a side note, I cannot compress the outline even after clearing the data and aggregations. The "Compact Outline" routine hangs and I have to kill EAS to stop the process. Thanks,

    Have you taken the new RAM stick out yet?
    Powerbooks can pretty picky when it comes to RAM.
    Joe

Maybe you are looking for