Hierarchical attribute dimension with Essbase Studio

Hi everybody,
I need to load product dimension which is organized in a relational parent-child table like this:
(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 its own hierarchy. For Brand I have another relational table where data is organized parent-child like this:
(brand_parent, brand_child, brand_alias).
I need to do this load with Essbase Studio but I do not known how to create the Product hierarchy in cube schema in order to load the hierarchical parent-child attributes. Documentation and tutorials only show examples for flat attributes. I thought of these two ways but not sure if will work:
case 1) Product hierarchy like this:
Parent_code
Member_code
Brand_parent
Brand_child
Member_code
case 2) Product hierarchy like this:
Parent_code
Member_code
Brand_parent
Brand
Member_code
Has anyone had to this? How did you do it?
Any help will be very appreciate.
Thank you,
Daniela

I've not tried it, but you should be able to build the attribute hierarchy within the product hierarchy. sort of like
Parent Code
---member Code
Brand Parent
---Brand Code
-----Member Code.
A couple of things
1. Remember to create the self join between Parent_code and Member code
2. IF this does not work, I suggest creating either a user defined table or a view that just gives you distinct brand parent and Brand Code. Join the Brand Code to the product table on brand_code = brand code and use that table to build that hierarchy.

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

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

  • Unable to create attribute dimension in Essbase Studio

    Hi All,
    As per the process,I am create an Attribute for an dimension as below
    Hierarchy
    Family(gen1)
    SKU(gen2)
    Attribute1(gen1)
    SKU(gen2)
    Attribute2(gen2)
    SKU(gen3)
    Here the issue i am unable to create an 2nd attribute parallel to first on i mean attributes are not creating as sliblings.
    Please advise
    Thanks,
    SatyaB

    I think I understand what you are asking. I think your example is something like
    Products
    ---Colas
    -----Coke
    -----Diet coke
    Bottle (attribute)
    ---Coke
    Can (attribute)
    ---Diet coke
    This is not the way attributes work, you would have a column in your soruce perhaps called container_type that has the relationship
    Container_type
    Sku
    So the rows would look like
    Sku----Family-----container_type----other properties
    coke...Colas........Bottle............XXXXXX
    Diet Code..Colas...Can.............XXXXXXX
    This could be in your primary table or a joined table

  • Need Help with Essbase Studio TBC cube deployment errors

    Hello Everyone,
    I am trying my hands on Essbase studio. I am using TBC example which comes with Essbase Studio installation. I am getting the following errors.
    How can I troubleshoot these errors. Since it comes with Essbase studio I supposed the data to be clean.
    In the essbase studio i defined the TIME dimension, but it stills give me that error.
    Please click the Details button for more information
    The error file is located on the server at: C:\temp\TBC.TBC_08-04-10_15-54-09.err
    Failed to deploy Essbase cube Caused by: Cannot end incremental build. Analytic Server Error(1007151): Wrong incremental dimension build sequence
    \\Record #3 - Error adding Label Only Attribute to member Inventory (3320)
    \\Record #3 - No time dimension defined
    \\Record #3 - Shared member cannot have a formula
    Measures ~ O Inventory ~ O
    \\Record #14 - Error adding Label Only Attribute to member Ratios (3320)
    \\Record #14 - Shared member cannot have a formula
    Measures ~ O Ratios ~ O
    \\Outline verification errors:
    \\When a single child member {Measures} is Dynamic Calc or Dynamic Calc and Store, the parent must also be Dynamic Calc or Dynamic Calc and Store

    Hi,
    Were you able to resolve that error with TBC db?
    I am running in to the exact same error...
    thanks

  • Error in access with Essbase Studio Console

    We get error to connect with Essbase Studio Console.
    "children for Root. Reason: Unknown package name 'drillthrough'.Line = 1."
    It is a new installation.
    EPM 11.1.2.2

    Hi,
    During the installation of Essbase Studio only, ess_es_server.jar and ess_japi.jar are missing. If you install both Essbase and Studio, they are not missing.
    This is due to unpublished bug 14232814 - DURING THE INSTALLATION ONLY STUDIO SOME .JAR FILES NOT INSTALLED
    Try the following:
    Stop Essbase Studio
    copy files into EPMSystem11R1\common\EssbaseJavaAPI\11.1.2.0\lib
    ess_es_server.jar
    ess_japi.jar
    If folder does not exist create it.
    1. Stop essbase Studio.
    2. Drop tables from relational database
    3. Recreate tables.
    4. Start Essbase Studio.
    Scripts for dropping & recreating catalog located under
    oracle\middleware\EPMSystem11R1\products\Essbase\EssbaseStudio\Server\database\common\db_name
    Hope it helps....
    KosuruS
    PS: If the above information is helpful, mark it :)

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

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

  • Help with Essbase studio

    Hi All,
    I wanted some help/ advice with building cubes using essbase studio. I had posted the similar question earlier but this is bit different. Actually we have data in the following format:
    Employee ,     Region,     Product,    Version,    Activity,   Dates
    ABC,          CA,            Prod1,           1,           Intro_date,       01/10/11
    PQR,          CA,            Prod1,           1,           Offer_Date,       03/10/11
    PQR,          CA,            Prod1,           1,           End_Date,       04/10/11
    Now we want to build the cube using studio. Where measures should have Intro_date, Offer_date and End_date and dates should be loaded in them. This can be achieved using rules files but we want to do it using studio because there are other studio features which we want to use.
    Kindly advice.

    Kindly advice if this is possible ? all my data sources are in this format.

  • Space is attribute Dimension in Essbase

    Hi -
    I had a similar problem for data in the past. I created a thread and then I ended up using MAXL.
    Now I have similar situation. I have an Essbase Dimension Employee which has Attribute Employee Status. When I try to extract Metadata out of essbase with its attributes the process failing because of the space in the field Employee Status. Has anyone faced this issue. Whats the work around for this issue

    I am answering my own question.
    I am able to fix the issue by using double quote in the name. Syntax is Employee."Employee Status"

  • Drill Through Report With Essbase Studio

    I have built a new minischema, cube / essbase model, and deployed to Essbase using Hyperion Studio 11.1.2.1. I created a drill-though report and was able to use the "test" feature to verify that the report returned data. The drill-through report type is relational and the association has been mode to my new cube. Restarted and confirmed the studio services were running correctly on the Essbase server. I have tried to drill-though using SmartView and AddIn, but recieve the message "No Drill Through Report at this Location". Cell styles are enabled and its not picking up my drill-through styles.
    Pray tell what I should consider as my next move to troubleshoot?

    Did not have the proper APS server connection selected during my testing. :D Once I connected SmartView to the proper APS server the application translated the drill-through report correctly.

  • Essbase Studio Error(1021001): Failed to Establish Connection With SQL Data

    Hi.
    I have trying to deploy a cube with Essbase Studio but I get the error: "*Error(1021001): Failed to Establish Connection With SQL Database Server*"
    My environment is Linux 5, Oracle 11g and EPM 11.1.1.2. Oracle database and Essbase was installed with diferent users. In the .bash_profile of hypadmin user (that install Essbase) I have set the following variables
    ORACLE_BASE=/u01/app/oracledb/product/11.1.0
    ORACLE_HOME=$ORACLE_BASE/db_1
    LD_LIBRARY_PATH=/usr/X11R6/lib:$ORACLE_HOME/lib:$LD_LIBRARY_PATH
    ORACLE_HOSTNAME=devbi.sigfe2
    PATH=$ORACLE_HOME/bin:$ORACLE_HOME/jdk/bin:$ORACLE_HOME/bin:/sbin:$ORACLE_HOME/opmn/bin:$PATH
    ORACLE_SID=orcl
    JAVA_HOME=/u01/app/installfiles/jdk1.5.0_19
    In my pc (windows xp) I can open Essbase Studio console, do the connection to Oracle database, get tables and create minischema, mesures and hierarchies (I can see the preview of hierarchies). Also I can create cubes with EAS and can connect with MAXSHELL to essbase.
    When I try to deploy the cube from Essbaes Studio y get the error "Error(1021001): Failed to Establish Connection With SQL Database Server".
    The Essbase Studio Log File say:
    +12:40:16 07/24/09 (admin-1) INFO Start creating outline in database "5.4.0.41:1423.POC_ESS.POC_ESS1"...+
    +12:40:16 07/24/09 (admin-1) FINA Sign on Essbase by CSS token "5.4.0.41:1423" successfully...+
    +12:40:16 07/24/09 (admin-1) INFO Start building dimension "DM_CIUDADES" ...+
    +12:40:16 07/24/09 (admin-1) MÁS FINA Start creating rule file ...+
    +12:40:16 07/24/09 (admin-1) INFO SQL statement has been created and put into rule file "/home/hypadmin/hyperion/products/Essbase/EssbaseStudio/Server/./ess_japihome/data/DM_CIU.rul"+
    +12:40:16 07/24/09 (admin-1) INFO The query is "SELECT (CONCAT('reg_',CAST(cp_105."ID_REGIONPADRE" AS VARCHAR2(1000)))) as "REGION_PADRE", (CONCAT('reg_',CAST(cp_105."ID_REGION" AS VARCHAR2(1000)))) as "REGION_HIJO", cp_105."DE_REGION" as "REGION_HIJO.Default" FROM "POC"."DM_REGIONES_ESS3" cp_105 ORDER BY cp_105."DE_NIVEL" ASC, cp_105."ID_REGIONPADRE" ASC, cp_105."ID_REGION" ASC"+
    +12:40:16 07/24/09 (admin-1) INFO Rule file has been created and saved as "/home/hypadmin/hyperion/products/Essbase/EssbaseStudio/Server/./ess_japihome/data/DM_CIU.rul"+
    +12:40:16 07/24/09 (admin-1) FINA Essbase starts to add members to DM_CIUDADES dimensioin based on the rules file.+
    +12:40:16 07/24/09 (admin-1) ADVERTENCIA (1021001): Error al establecer conexión con el servidor de bases de datos SQL. Consulte el registro para obtener más información.+
    +12:40:16 07/24/09 (admin-1) ADVERTENCIA essbaseDriver.FailedToBuildDimensionException+
    +12:40:16 07/24/09 (admin-1) GRAVE Unexpected exception in EssbaseExport prevented cube from being deployed+
    -------------- Exception --------------
    com.hyperion.cp.datasources.export.essbase.EssbaseDriverException: Failed to deploy Essbase cube
    Thanks in advance to all that have any idea to help me to solve this issue.
    A.S.

    Hi,
    If you type database SID in lowercase, try to reenter iot in uppercase. Strange, but I and my colleagues encounter this behaviour many times.

  • Unable to create Measures dimension in proper relationshipin Essbase Studio

    I am planning to build measure hierarchy in Essbase studio with TBCSample(SQL Server 2005) which is came by default with Essbase Studio installation
    I built the hierarchy with parent child relationship.
    However the hierarchies is not coming in the proper order
    Generally Sales,COGS should come under “Margin ” and it should be under “Profit”
    Eg:      Profit
         Margin
              Sales
              COGS
    However it is showing differently in “Preview” mode.
    Profit
    Margin
    Margin
    Sales
    COGS
    When I deployed the cube I got the below errors because of the duplicate members
    The error file is located on the server at: E:\Hyperion\products\Essbase\EssbaseStudio\Server\.\ess_japihome\data\TBCSampl.TBCSampl_03-29-11_23-16-00.err
    \\Record #6 - Member name (Measures) already used
    Measures Inventory
    \\Record #7 - Member name (Measures) already used
    Measures Profit
    \\Record #8 - Member name (Measures) already used
    Measures Ratios
    \\Record #9 - Member name (Margin) already used
    Profit Margin
    \\Record #14 - Member name (Total Expenses) already used
    Total Expenses Marketing
    \\Record #15 - Member name (Total Expenses) already used
    Total Expenses Misc
    \\Record #16 - Member name (Total Expenses) already used
    Total Expenses Payroll
    Please let me know how to resolve this issue
    Database: SQL Server 2005
    EPM Version : 11.1.1.3
    Thanks,
    SatyaB

    open the minischema and in the graphic go to your measures table. highlight either the parent or child member and right click. select create join. In the screen that comes up, selet the other column from the same table. It will create the join. You wnat an inner join. You can also click on the member and drag and drop the join line to the child member to create the join

  • Essbase Studio: Failed to deploy Essbase cube

    Hi
    I have started working with Essbase studio sometime back and I am able to deploy BSO cube with success using the TBCSample Database which comes along with Essbase. Now I wanted to deploy ASO cube, as no sample database is available I thought to create one, I extracted ASOSamp using ODI to CSV files. Then I bulk inserted the csv extracts into MSSQL 2003 server which created 11 tables (Age, Geography, IncomeLevel, Measures, PaymentType, Product, Stores, Time TransactionType, Year). The above mentioned table does not have any keys(Primary, Foreign) as it is an Essbase export.
    I then successful created ASO Cube Schema using the newly created sample database in MSSQL, validated cube schema without any errors.
    Essbase Property Setting:
    Measures Hierarchy is tagged as Dynamic Compression at dimension level
    Time, Product and Year Hierarchy is tagged as Multiple Hierarchies Enabled, Year does not have multiple hierarchies but it has formulas for Variance and Variance % member. Is there a way to tag Year as Dynamic hierarchy?
    But when I try to deploy the cube to Essbase I receive following errors:
    Failed to deploy Essbase cube
    Caused By: Cannot end incremental build. Essbase Error(1060053): Outline has errors
    \\Record #1 - Member name (Time) already used
    + S Time + S
    \\Record #6 - Member name (1st Half) already used
    MTD + S 1st Half + S
    \\Record #7 - Member name (2nd Half) already used
    MTD + S 2nd Half + S
    \\Record #21 - Member name (Qtr1) already used
    Qtr1 + S Feb + S
    \\Record #22 - Member name (Qtr1) already used
    Qtr1 + S Jan + S
    \\Record #23 - Member name (Qtr1) already used
    Qtr1 + S Mar + S
    \\Record #24 - Member name (Qtr2) already used
    Qtr2 + S Apr + S
    \\Record #25 - Member name (Qtr2) already used
    Qtr2 + S Jun + S
    \\Record #26 - Member name (Qtr2) already used
    Qtr2 + S May + S
    \\Record #27 - Member name (Qtr3) already used
    Qtr3 + S Aug + S
    \\Record #28 - Member name (Qtr3) already used
    Qtr3 + S Jul + S
    \\Record #29 - Member name (Qtr3) already used
    Qtr3 + S Sep + S
    \\Record #30 - Member name (Qtr4) already used
    Qtr4 + S Dec + S
    \\Record #31 - Member name (Qtr4) already used
    Qtr4 + S Nov + S
    \\Record #32 - Member name (Qtr4) already used
    Qtr4 + S Oct + S
    \\Record #33 - Member name (Time) already used
    Time + S MTD + S
    \\Record #34 - Member name (Time) already used
    Time ~ S QTD ~ S
    \\Record #35 - Member name (Time) already used
    Time ~ S YTD ~ S
    \\Record #9 - Error adding Attribute to member QTD(Jan) (3320)
    \\Record #9 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD + S QTD(Jan) + S [Jan]
    \\Record #10 - Error adding Attribute to member QTD(Apr) (3320)
    \\Record #10 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Apr) ~ S [Apr]
    \\Record #11 - Error adding Attribute to member QTD(Aug) (3320)
    \\Record #11 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Aug) ~ S [Jul]+[Aug]
    \\Record #12 - Error adding Attribute to member QTD(Dec) (3320)
    \\Record #12 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Dec) ~ S [Oct]+[Nov]+[Dec]
    \\Record #13 - Error adding Attribute to member QTD(Feb) (3320)
    \\Record #13 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Feb) ~ S [Jan]+[Feb]
    \\Record #14 - Error adding Attribute to member QTD(Jul) (3320)
    \\Record #14 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Jul) ~ S [Jul]
    \\Record #15 - Error adding Attribute to member QTD(Jun) (3320)
    \\Record #15 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Jun) ~ S [Apr]+[May]+[Jun]
    \\Record #16 - Error adding Attribute to member QTD(Mar) (3320)
    \\Record #16 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Mar) ~ S [Jan]+[Feb]+[Mar]
    \\Record #17 - Error adding Attribute to member QTD(May) (3320)
    \\Record #17 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(May) ~ S [Apr]+[May]
    \\Record #18 - Error adding Attribute to member QTD(Nov) (3320)
    \\Record #18 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Nov) ~ S [Oct]+[Nov]
    \\Record #19 - Error adding Attribute to member QTD(Oct) (3320)
    \\Record #19 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Oct) ~ S [Oct]
    \\Record #20 - Error adding Attribute to member QTD(Sep) (3320)
    \\Record #20 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    QTD ~ S QTD(Sep) ~ S [Jul]+[Aug]+[Sep]
    \\Record #36 - Error adding Attribute to member YTD(Jan) (3320)
    \\Record #36 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD + S YTD(Jan) + S [Jan]
    \\Record #37 - Error adding Attribute to member YTD(Apr) (3320)
    \\Record #37 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Apr) ~ S [Qtr1]+[Apr]
    \\Record #38 - Error adding Attribute to member YTD(Aug) (3320)
    \\Record #38 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Aug) ~ S [1st Half]+[Jul]+[Aug]
    \\Record #39 - Error adding Attribute to member YTD(Dec) (3320)
    \\Record #39 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Dec) ~ S [1st Half]+[Qtr3]+[Qtr4]
    \\Record #40 - Error adding Attribute to member YTD(Feb) (3320)
    \\Record #40 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Feb) ~ S [Jan]+[Feb]
    \\Record #41 - Error adding Attribute to member YTD(Jul) (3320)
    \\Record #41 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Jul) ~ S [1st Half]+[Jul]
    \\Record #42 - Error adding Attribute to member YTD(Jun) (3320)
    \\Record #42 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Jun) ~ S [1st Half]
    \\Record #43 - Error adding Attribute to member YTD(Mar) (3320)
    \\Record #43 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Mar) ~ S [Qtr1]
    \\Record #44 - Error adding Attribute to member YTD(May) (3320)
    \\Record #44 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(May) ~ S [Qtr1]+[Apr]+[May]
    \\Record #45 - Error adding Attribute to member YTD(Nov) (3320)
    \\Record #45 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Nov) ~ S [1st Half]+[Qtr3]+[Oct]+[Nov]
    \\Record #46 - Error adding Attribute to member YTD(Oct) (3320)
    \\Record #46 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Oct) ~ S [1st Half]+[Qtr3]+[Oct]
    \\Record #47 - Error adding Attribute to member YTD(Sep) (3320)
    \\Record #47 - Aggregate storage outlines only allow formulas in compression dimension or dynamic hierarchies.
    YTD ~ S YTD(Sep) ~ S [1st Half]+[Qtr3]
    \\Record #2 - Incorrect Dimension [Year] For Member [ParentName] (3308)
    ParentName Consolidation DataStorage MemberName Consolidation DataStorage Formula
    \\Record #1 - Member name (Promotions) already used
    S Promotions S
    \\Record #2 - Incorrect Dimension [Promotions] For Member [ParentName] (3308)
    ParentName DataStorage MemberName DataStorage
    \\Record #3 - Member name (Promotions) already used
    Promotions S Coupon S
    \\Record #4 - Member name (Promotions) already used
    Promotions S Newspaper Ad S
    \\Record #5 - Member name (Promotions) already used
    Promotions S No Promotion S
    \\Record #6 - Member name (Promotions) already used
    Promotions S Temporary Price Reduction S
    \\Record #7 - Member name (Promotions) already used
    Promotions S Year End Sale S
    \\Record #2 - Incorrect Dimension [Payment Type] For Member [ParentName] (3308)
    ParentName DataStorage MemberName DataStorage
    \\Record #2 - Incorrect Dimension [Transation Type] For Member [ParentName] (3308)
    ParentName DataStorage MemberName DataStorage
    \\Record #22 - Member name (Home Entertainment) already used
    Home Entertainment + S Home Audio/Video + S
    \\Record #23 - Member name (Home Entertainment) already used
    Home Entertainment + S Televisions + S
    \\Record #24 - Member name (Other) already used
    Other + S Computers and Peripherals + S
    \\Record #25 - Incorrect Dimension [Product] For Member [ParentName] (3308)
    ParentName Consolidation DataStorage MemberName Consolidation DataStorage
    \\Record #26 - Member name (Personal Electronics) already used
    Personal Electronics + S Digital Cameras/Camcorders + S
    \\Record #27 - Member name (Personal Electronics) already used
    Personal Electronics + S Handhelds/PDAs + S
    \\Record #28 - Member name (Personal Electronics) already used
    Personal Electronics + S Portable Audio + S
    \\Record #31 - Member name (All Merchandise) already used
    Products + S All Merchandise + S
    \\Record #32 - Member name (High End Merchandise) already used
    Products ~ S High End Merchandise ~ S
    \\Record #33 - Member name (Systems) already used
    Systems + S Desktops + S
    \\Record #34 - Member name (Systems) already used
    Systems + S Notebooks + S
    \\Record #18 - Error adding Attribute to member Digital Recorders (3320)
    Home Audio/Video + S Digital Recorders + S
    \\Record #36 - Error adding Attribute to member Flat Panel (3320)
    Televisions + S Flat Panel + S
    \\Record #37 - Error adding Attribute to member HDTV (3320)
    Televisions + S HDTV + S
    \\Record #8 - Incorrect Dimension [Income Level] For Member [ParentName] (3308)
    ParentName DataStorage MemberName DataStorage
    \\Record #1 - Member name (Geography) already used
    S Geography S
    \\Record #2 - Error adding member 27425 (3317)
    \\Record #2 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    A M F GREENSBORO - NC S 27425 S 336
    \\Record #3 - Error adding member 36310 (3317)
    \\Record #3 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABBEVILLE - AL S 36310 S 334
    \\Record #4 - Error adding member 29620 (3317)
    \\Record #4 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABBEVILLE - SC S 29620 S 864
    \\Record #5 - Error adding member 67510 (3317)
    \\Record #5 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABBYVILLE - KS S 67510 S 316
    \\Record #6 - Error adding member 58001 (3317)
    \\Record #6 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABERCROMBIE - ND S 58001 S 701
    \\Record #7 - Error adding member 42201 (3317)
    \\Record #7 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABERDEEN - KY S 42201 S 502
    \\Record #8 - Error adding member 21001 (3317)
    \\Record #8 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABERDEEN - MD S 21001 S 410
    \\Record #9 - Error adding member 39730 (3317)
    \\Record #9 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABERDEEN - MS S 39730 S 601
    \\Record #10 - Error adding member 28315 (3317)
    \\Record #10 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABERDEEN - NC S 28315 S 910
    \\Record #11 - Error adding member 79311 (3317)
    \\Record #11 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABERNATHY - TX S 79311 S 806
    \\Record #12 - Error adding member 79601 (3317)
    \\Record #12 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABILENE - TX S 79601 S 915
    \\Record #13 - Error adding member 79608 (3317)
    \\Record #13 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    ABILENE - TX S 79608 S 915
    \\Record #14 - Error adding member 79698 (3317)
    \\Record #14 - Aggregate storage outlines only allow any shared member once in a stored hierarchy, including prototype.
    Are these errors due to data source, if yes what could be possible work around?
    Is there any problem with Essbase properties which I have set if so then when I validate cube schema why I dn't get any errors?
    Please help me, I am stuck here not able to deploy ASO Cube.
    Thanks in advance

    Hii
    I have the same problem , you have.
    did you manage to solve it ??
    Thanks in advance

Maybe you are looking for