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"

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

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.

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

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

Attribute Dimension Essbase

Dears,
I would like to know how Attribute Dimension Essbase working in OBIEE,
I'm Using ASO & i import Time Dimension and Attribute Dimension for Time (Sun, Mon, etc).
I want to know how its working in Report.
I want to See the Time dimension with This Day name ?
Is it possible ?
Thanks in advance.

Any Help please ?

Deploying Essbase Text-Attribute Dimensions

Hello,
we have an Essbase-cube with a text-attribute dimension. All associations are fine, also the validation. The deployment fails with the error:
"Level zero members defined as dynamic calc must have a formula assigned to them"
As it is an attribute dimension, there is something wrong.
Any help apreciated!
Michael

Are you sure you don't have an Account or some other dimension's member that has been tagged as dynamic calc and yet does not have a formula?
That's the message you'll get when that happens.
The Planning refresh should (hopefully) show you which member is that way. Failing that you can go into Essbase and try doing outline validations -- I suspect the error will not have gone across but it may be worth a try. If the latter is the case, you are going to have to compare the two -- Planning and Essbase to find that dynamically calculated member without a formula.
Regards,
Cameron Lackpour
P.S. The message sort of makes sense, sort of -- attribute dimensions are dynamic, but I've never personally seen this error.

Essbase Attribute Dimension

When we retrieve totals on base dimension without specifing the attributes the numbers turn out right. HOWEVER when we retrieve specifying the attributes the totals consolidate everything inspite of having tilde on some of the members.

You are correct, when you retrieve and include an attribute dimension, then it will add everything regardless of the sign. eg. profit = revenue less expenses, however, throw an attribute in there and then suddenly, profit will be revenue plus expenses. Wrong.This is because attributes are always dynamically calced and they will only sum, count, min, max or avg. This means that you can't have attributes associated to dimensions that roll up with anything other than pluses(+). To make it more complicated, if you do have attributes against a standard roll-up dimension and the other dimensions have a dynamic calc member then the dynamic calcs will be a sum again regardless of the sign. So the other dimensions have to be stored values.

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

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

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.

Business Rule - Can you fix on children in attribute dimension?

HI,
Base Dimension: Service
Attribute Dimension: Service_Code
If I have the following hierarchy in an attribute dimension, how can I fix on all members of the Service dimension that have the attributes Model A, Model B and Model C attached them without listing them individually? Is there a way to fix on children of 'IMH Models' somehow?
Service_Code
   IMH Models
      Model A
      Model B
      Model C
   CAD Models
      Model D
      Model E

Hi
in the FIX use the @ATTRIBUTE("IMH Models"). By default it will fix on all base members associated with the children of the attribute parent you have specified. See below text from Tech Ref
Description
When @ATTRIBUTE is used with a non-level 0 member of an attribute dimension,
Essbase returns all base members that are associated with the children of the
attribute member. For example, in the Sample Basic database,
@ATTRIBUTE(Large) returns all base members that fall into one of
the population ranges for the attribute parent Large.
Thanks
Anthony

Attribute dimension hierarchy

what is use of hierarchy in Attribute dimension. Any one can give example when to have it.

The essbase documentation has a good section on understanding attributes - http://docs.oracle.com/cd/E17236_01/epm.1112/esb_dbag/dattrib.html#dattrib497341
Cheers
John
http://john-goodwin.blogspot.com/

Space is attribute Dimension in Essbase

Similar Messages

Maybe you are looking for