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.

Similar Messages

  • Calculation issue on attribute dimension

    The issue that I'm facing with is as below. I have two pass calc on some of the measures in the outline. Since I'm not doing any calculation on the attribute dimension, when I drill down using this dimension it pops up an error message
    "Two-pass calc skipped on member [X] in attribute calc"
    Please advise on how to resolve this.
    Thr formula has @CURRMBR. The DBAG says that If a member formula contains a run-time dependent function associated with an attribute member name, and the member with the formula is tagged as two-pass, calculation skips the member and issues a warning message.
    It also says that Two-pass calculation member property is unavailable for attribute dimensions.
    So does it mean that every two pass calc member is skipped?
    I'm a bit confused.. how does it work?
    Is there a resolution for my issue? Please confirm if there is a way to get this two pass calc done for the formula with @CURRMBR.
    Thanks.
    null
    .

    Hello,
    I will give it a try:
    << I assume you have the two-pass calc member on the accounts dimension and the associated dimension of the attribute dimension is not the accounts dimension either. >>
    Attribute dimensios are calculated dynamically. They provide a different view on the members of the associated dimension which they belong to. There are 5 different calculation functions in the rollup of the members on the base dimension (sum, min, max, count, average).
    So this is within the associated dimension (sparse) which is linked to the attribute dimension (virtual).
    The accounts dimension is always involved in displaying figures. The attribute calculation e.g. sum is done last. So the dynamic calculations have to be done first. This message is likely a warning message that the value displayed is not the result of the two-pass calculation, but from the attribute calculation.
    You might review the storage setting of the member. Often the @currmbr is also not necessary in the formula when considering the calculation order of the members.
    Hope this helps a bit.
    Regards,
    Philip Hulsebosch
    www.trexco.nl

  • Load hierarchical attribute dimensions with Integration Services?

    Hi everybody,
    I need to load product dimension which is organized in a relational table like this:
    Product (parent_code, member_code, member_alias, brand, consolidation, formula)
    Every product has a brand and I need to load brand as attribute dimension. The thing is Brand is not flat but it has it's own hierarchy. For Brand I have another relational table where data is organized parent-child like this:
    Brand (brand_parent_code, brand_child_code, brand_child_alias).
    I have used in the past Integration Services but with flat attribute dimensions.
    Can I load hierarchical attribute dimensions with Integration Services? If yes, how do I do it, how do I specify the hierarchy?
    Thank you,
    Daniela

    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.

  • 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.

  • 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.

  • Associating attribute dimensions with the standard dimension in EIS

    Hi... we need to bring 2 attribute dimensions in to the Metaoutline of EIS.These 2 attribute dimensions must be associated with lev 0 member of the standard dimension.how to achieve in EIS?
    The current status: we did the olap model by mapping all the dimensional tables with the fact table and we are struck up how to bring the 2 attribute dimensions in to the model screen and association with standard dimesnion.
    The table structure for the standard dimension is
    column1/Gen-1     column2/Gen-2-Alis     consolidation     col3(Attr)     colu 4(Attri)
    Reason-1     Reason-1-extension               
    Reason-2     Reason-2-extension               
    Reason-3     Reason-3-extension          
    col3 and col4 are attributes to be associated with column2.
    Pls guide us the approach to be done in EIS..

    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.

  • Epm11 attribute dimensions sum

    In outline, there are 13 dimensions:
    -YearTotal (Time Dimension)- Dense
    -Accounts - Dense
    -Scenario - Dense
    -Costing -Dense
    -Cumulative- Dense
    -Currency -Sparse
    -Company -Sparse
    -Doctype -Sparse
    -Years -Sparse
    -Sales Dep -Sparse
    -Geographics -Sparse
    -Customer -Sparse
    -Product -Sparse,
    and 6 attribute dimensions:
    -Standart
    -Anme
    -Hardness
    -Coat Type
    -Product Type
    -Logistics.
    Scenario dimension children : Actual and PYear (Previous Year value : Formula =@SHIFT ("Actual",-1,@LEVMBRS("Years",0)); ).
    For a material that was sold in 2009 and not sold in 2010:
    -if we dont use the Product Type attribute dimension, 2010->Pyear value is coming.
    Material Year Scenario Subtotal
    A 2010 Actual missing
    A 2010 Pyear 15000
    A 2009 Actual 15000
    -if we use the Product Type attribute dimension, 2010->Pyear is missing but it is not true.
    Material        Product Type_ Year Scenario Subtotal_
    A PT 2010 Actual missing
    A PT 2010 Pyear missing
    A PT 2009 Actual 15000
    I guess the reason is that there is no block for this material and year combination (A->2010) . What can I do ,can you give a suggesstion ?
    Thanks a lot.

    Yes they can.Basically, attributes are linked through to your base dimension anyway.You can either @withattr or @attribute in your filter.eg.WRITE/READ @attribute("bottle")where "bottle" is a member of your "pkg type" dimension say

  • 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

  • Maximum number of Attribute dimensions Possible in BSO Cube

    hi,
    i have two simple queries :
    1 - What are the maximum number of Attribute dimensions Possible in a BSO Cube.
    2- How many attribute dimension can be associated with one base Dimension.
    hope to get reply soon.
    thanks in advance.
    Regards
    Anubhav

    No Limits are defined as such:
    How many Maximum number of Dimensions can create ?
    Even in the Dbag, it says "many":
    A base dimension member can have many attributes, but only one attribute from each attribute dimension.Cheers..
    Rahul S.

  • Web Analysis data layout does not reflect newly added attribute dimension

    Hi,
    We newly added one new attribute dimension. If any new report creation in Web Analysis reflect that dimension. However, the reports which are old(created before the addition of new dimension), does not show the newly added dimension.
    Please advice.
    Thanks,
    Meenakshi

    Thanks for this.
    I have tried assigning the new DB connection. However, still it did not work. Does the data layout displays dimensions according to reports. I mean, can we restrict the visibility of dimension at report level? Please advice.
    Thanks,
    Meenakshi

  • 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

  • HOW TO cache user clicks on links with attributes such as "_blank" ?

    HOW TO cache user clicks on links with attributes such as "_blank" in Adobe AIR with JS or MXML or AS3 for creating new costume browser window (AIR) ?

    >This feature is indeed new to 8.5.
    Can you explain a bit more on what is possible in version 8.5? How easy it is to attach events to different sections of the 3D model? How easy it is to handle such events? I assume the events will fire even if the user rotates the 3D model via the camera control, right? Any limitations on the 3D model or what types of events are supported? If you have LV documentation describing this feature then that would be *very* helpful!
    Thanks for your reply
    MZ2

  • 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