Attribute dimension and webforms

hello,
is there a way of using the attribute dimension in a planning webform ?
I have created one but dont see the options when trying to select members based on that attribute.
thanks

Try this:
Attribute dimension in the planning Web form
Cheers..!!!

Similar Messages

  • Attribute Dimension and association with multi level base members

    I am trying to associate attribute dimension members with base members that can be at different levels (level 0 or level 1 or level 2 ).
    First question - Is that possible ? Second how do I do that.
    I am building the dimensions(base and attribute) members first and then trying to associate.
    I get the following error message :
    Base member (xxxxxxx) association level does not match base dimension association level
    The base dimension looks like
    Supplier
    |-----Supplier Group
    |---------Supplier ID (Associate this member to an attrbiute dimension)
    |---------------Invoice Number
    Sometimes the Supplier ID may not have a Supplier Group or an Invoice Number (hence it can be a level 0 or directly under the dimension name - Gen2)
    The Attrbute Dimension looks like
    Supplier Value
    |---High
    |---Medium
    |---Low
    Edited by: 816875 on 30-Nov-2010 07:01

    First to clarify, base mambers by definition would all be level 0 members, but to your question, attributres can only be associated to a single level within a dimension. your problem is sometimes the supplier is level 0 and other times level 1. This can't be done.

  • Attribute Dimensions and Excel Retrieves

    Dear All,<BR><BR>I have a cube that has a sparse dimension with attributes attached (all at the same level). When I retrieve using different attributes in the retrieve the results are not consistent i.e. some of the sparse members with the same attribute are left out of the result. It appears to happen when branches of the dimension in the same area are separated by a branch with an alternate attribute value (from the same attribute dimension). I have cured this by moving the affected branches next to each other, is this something that I need to watch out for on the design side i.e. to do with the way Essbase handles attribute dimensions? Any guidance would be appreciated.

    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.

  • Creating scenario dimension and loading data

    Hi all,
    We have two fact tables. The first one is sales that include quantity and subtotal columns. The other one is budget that include quantity and subtotal. We are working with hyperion essbase 9.3. First of all we are creating two model. For sales model we create 7 dimensions (product, chanell, time, company, currency, customer, account) and 3 attribute dimension and for budget model we create 4 dimensions (account,company,customer,product) in metaoutline. And we create 2 application for each metaoutline. We plan to report sales vs budget but we don't know how to join sales and budget data. Everybody recommends scenario dimension. we don't know how to create sceneraio dimension and in which application Essbase integration or Essbase administration services.
    thank you.

    I agree with Cameron. The best way is to put them into one cube. Since you are using a SQL source you can manulate it to have your budget load to the same time level as your actuals. For example suppose you load actuals daily and Budget is Monthly. for consistancy, you could load the budget data into the 15th day of the month. At the Monthly level where you would compare budget to actual, the numbers will be correct. Loading into dummy members for the dimensions that don't exist for budget is a common practice when trying to sync up data. If you really want to make it easy, you could union a view to make it look like you have a single fact table (based on the combo of budget and actual) and have a single metadata outline to load everything. I prefer having two because of different load requirements, but this is an option.
    If you don't want to go this way, the next option is to partition your budget data into the actuals cube. this would keep them seperate but allow you to see them togeter. Between the two option, I prefer the single cube approach better

  • 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 dimension build method

    Hi All,
    Please do let me know the process to build the attribute dimension using rules file. I tried it following the same way as any other normal dimension but donot get the property associated to the attribute dim. We want this process to be automated as we rebuilt the ourline each time during the load. Pleaes help.
    Thanks,
    Praveen

    Have a read of the section :- Building Attribute Dimensions and Associating Attributes
    http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/dotdimb.htm#dotdimb1060796
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • Why should we associate attribute dimension to base sparse dimension only

    hi experts,
    I have query, please suggest that.
    Why should we associate attribute dimension to base sparse dimension only ? any reason is there.
    thanks in advance

    Have a read of - why attribute dimension attached to sparse dimension and Attribute Dimension and association with multi level base members
    Cheers
    John
    http://john-goodwin.blogspot.com/

  • How to hide the Attribute dimension from Planning webform

    I am in Planning 9.3.1
    We are using members in row section of webform w.r.t Attribut dimension
    so when we are viewing the webform- it is displaying member name followed by Attribute dimension name .
    any way to hide that Attribute dimension member from the webform.
    KK

    In the Dimension Properties for that dimension, select "Enable custom attribute display" but dont pull the attribute from Available Dimensions to Selected Dimensions. I've given the name of the property from 11.1.1.3 version, so not sure if its the same in 9.3.1 but it'll be somewhat similar.
    Cheers

  • Line Item Dimension and Navigational attribute

    Hi Gurus,
    Can somebody tell me how line item Dimensions and navigational attributes works technically?
    What are the pros and cons for them?
    Regards
    Alex

    Hi Alex,
                You will use navigational attributes based on how you want to track and report history. Let me explain with an example.
    Customer Bubba is assigned Sales Group XYZ in Jan 2007. In July the Sales Group on the Customer Master record is changed to  ABC. Your are looking at the sales report.
    1). If you want to see all the sales made to Customer Bubba at the time of reporting (current) then you will use navigational attributes You will create 0SALESGRP as the navigational attribute of 0CUSTOMER .  Then all sales to the customer will show up under Sales Group ABC.
    2). If you want to see  all the sales made to the customer at the time the actual transaction occured then you will add Sales Group as a characteristic of the InfoCube. Then sales from Jan - June 2007 will show under Sales Group XYZ and from July - Present will show under Sales Group ABC.
    Performance issue occurs because navigational attribute is stored outside of the dimension table of the cube and is stored in separate master data tables. So query has to perform additional table read. So essentially there are advantages and disadvantages of usng navigational attributes. It is business requirement that will drive the use of navigational attribute.
    Hope this helps!!!. Please assign points.

  • Ees_japi.jar  and attribute dimensions

    We have a cube with a product dimension and several atribute dimensions. One of the attribute dimensions identify the product category. I need to execute a Java query that pulls back the level 0 of product dimension filtered down to the selected attribute (which is a category).Example Return if Category 1 is selected:Item 001 Category 1Item 014 Category 1Item 555 Category 1I believe it will be a variation of executeQuery method in the memberselection class. Any help on what to use to accomplish this is appreciated.Jim

    Disregard, I was not seeing the second style of executequery. Using the second version I was able to use the @WITHATTR() function and pull the needed information. Thanks anyway.Jim

  • 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

  • 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

  • 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

  • Creating a hierarchy in an attribute dimension using EIS

    we use EIS for our data/member loads.
    I have a couple of cubes with attribute dims and I had no problems using EIS to create those attribute dims as they did not have a hierarchy
    I have a new requirement to create an attribute dim with a hierarchy.
    I am not sure how can I do this in EIS. Please advice.
    I went through the chm file but could not really figure out anything about it.
    Thank you.

    Actually you can have hierarchies in your attribute dims in EIS, including text attributes. I have a number of models where we do this.
    It works the same as with regular dimensions. Assume you have a table with product codes and then a column for lev 0 attribute and lev 1 attribute.
    So code is XYZ
    Lev 0 attribute is Red
    Lev 1 attribute is Primary
    When you set up your attribute dim in EIS, set both attribute columns as attribute, then in the metaoutline model, drag lev1 attibute onto the outline, then drag lev0 attribute under it. You will get a warning that you can only associate the lev0 attribute with the base dimension, which is fine. Associate the lev0 attribute with the base dim as you normally would and build your outline.
    Your end result will be an attribute dim that looks like this
    Product Color
    --Primary
    ----Red

  • Performance problem with attribute dimensions - please help!

    Hi everybody,
    I run OBIEE reports on top of EssBase 9.3 ASO cube.
    My cube has 8 regular dimensions and 10 attribute dimensions.
    I am running a query based on:
    - 3 dimensions (TIME, BATCH, MODEL),
    - 2 attributes of BATCH ( SHIFT, SHIFT_STATUS )
    - and one measure.
    The query runs 3 minutes (!) and returns 190 rows.
    If I remove the attributes, the query runs 4 seconds for the same number of result rows.
    My MDX:
    With
    set [TIME6] as 'Filter([TIME].Generations(6).members,
    ([TIME].currentmember.MEMBER_ALIAS = "2009/01" OR [TIME].currentmember.MEMBER_Name = "2009/01"))'
    set [TIME7] as 'Generate([TIME6], Descendants([TIME].currentmember, [TIME].Generations(7), leaves))'
    set [BATCHES] as '[DIM_BATCH_HEADERS].Generations(5).members'
    set [SHIFT2] as '[SHIFT].Generations(2).members'
    set [SHIFT_STATUS2] as '[SHIFT_STATUS].Generations(2).members'
    set [MODEL2] as 'Filter([MODEL].Generations(2).members, ([MODEL].currentmember.MEMBER_ALIAS = "SNF_PCK" OR [MODEL].currentmember.MEMBER_Name = "SNF_PCK"))'
    select
    {[Accounts].[PROD_ACTUAL_QTY_KG]
    } on columns,
    NON EMPTY
    {crossjoin ({[TIME7]},
    crossjoin ({[BATCHES]},
    crossjoin ({[SHIFT2]},
    crossjoin ({[SHIFT_STATUS2]},{[MODEL2]}))))}
    properties ANCESTOR_NAMES, GEN_NUMBER on rows
    from [COP_MAAD.Cop_Maad]
    Thank you in advance,
    Alex
    Edited by: AM_1 on Feb 26, 2009 6:35 AM
    Edited by: AM_1 on Feb 26, 2009 7:03 AM

    Hi Glenn,
    I though that the reason might be the crossjoin with a very large set. The main dimension in this query has ~40000 members.
    Is there in EssBase MDX some analog for NONEMPTYCROSSJOIN() function that exists in MSAS?
    As these two attributes belong to the dimension that is used in the query, for every member of the dimension, there is one and only one member of each attribute. Therefore I though that Essbase should "know" how to behave.
    Thanks for an idea. I will try to increase the space for aggregation - hope this will help...
    Best Regards,
    Alex

Maybe you are looking for