Problem adding attribute dimension

Version: 9.2
Cube: ASO
I feel like I am dropping the ball. I am trying to add an attribute to my ASO cube at the bottom of my outline. Everything I try to edit the member properties I get an "Attribute Calculations dimension can not be created". I don't have any calculations/consolidations.
When I click the database properties-->Attribute settings-->Calucation dimension names-->(try entering a name) all I get is "NULL value for member name string".
When I use ASOsamp(or any app) I can create/tag an attribute dimension though.

Hi There,
I guess you might've added a Gen1, member, i.e. a dimension, at the end of the outline & intended it to be an Attribute dimension. Correct?
If yes, after adding the member at the end,
- Before opening the dialog for member properties, tag the dimension as "Attribute" by clicking on the appropriate icon, right on the outline page.
- Associate this attr. dim to one of your sparse dims.
- Add a member to the Attribute dim. & associate it with one of the members of sparse dim.
- Now, it should let you save the outline.
Good luck!
- Natesh

Similar Messages

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

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

Problems adding attribute via OID Self-Service Console

I have added a new attribute via the Oracle Directory Manager tool, but when I map it to the Self-Service Console and select the Predefined List from the User Interface Type, and add the values to the list, only the last value will show up as many times as entries are in the list. For example, the list has the values Y N R, and when updating the value in the Console, the attributes list values are R R R.
I have not found anything on Metalink indicating a bug. Has anybody have any experience with this problem?
any help will be appreciated.
thanks

Please open a SR on this issue or open a bug.
regards,
--Olaf

Building Attribute Dimensions in VB

I am writing a VB program to update an attribute dimension. I have followed the documented approach to populate the ESB_MBRINFO_T structure but continue to get errors 8 - ESB_OUTERROR2_ILLEGALDATATYPE and 64 = ESB_OUTERROR2_ATTRDIMNOTASSOCIATED.
The code is
Public Function esbMoveOrAddMember(rsChild As String, _
rsParent As String, _
rsAlias As String) As Integer
Dim sts As Long
Dim stsInfo As Long
Dim hChild As Long
Dim hCurrentParent As Long
Dim hParent As Long
Dim uNewMemInfo As ESB_MBRINFO_T
Dim szAlias As String * ESB_MBRNAMELEN
esbMoveOrAddMember = 0
If esbFindMember(rsParent, hParent) Then 'Find Parent
If esbFindMember(rsChild, hChild) Then 'Find member
' Found parent and child so see if a move is needed
' Get the current parent handle
stsInfo = EsbOtlGetParent(mhOutline, hChild, hCurrentParent)
If hParent <> hCurrentParent Then
sts = EsbOtlMoveMember(mhOutline, hChild, hParent, ESB_NULL)
If sts <> 0 Then
esbMoveOrAddMember = 1
Call essGetAndDisplayMessage(sts)
End If
End If
Else
'Good Parent, new member so add it
Call SetupAttributeMemberForAdd(rsChild, uNewMemInfo)
sts = EsbOtlAddMember(mhOutline, uNewMemInfo, ESB_NULL, hParent, hChild)
If sts <> 0 Then
esbMoveOrAddMember = 2
Call essGetAndDisplayMessage(sts)
End If
End If
Else
esbMoveOrAddMember = 3
sts = 5
End If
'* Set the alias of the child member
If sts = 0 And hChild <> 0 And Len(rsAlias) > 0 Then
szAlias = rsAlias
sts = EsbOtlSetMemberAlias(mhOutline, hChild, "", szAlias)
If sts <> 0 And sts <> 1060023 Then
esbMoveOrAddMember = 4
Call essGetAndDisplayMessage(sts)
End If
End If
End Function
Sub SetupAttributeMemberForAdd(rsChild As String, uMemInfo As ESB_MBRINFO_T)
With uMemInfo
.szMember = rsChild
.usConsolidation = ESB_UCALC_NOOP
.fTwoPass = ESB_FALSE
.fExpense = ESB_FALSE
.usConversion = ESB_CONV_NONE
.usTimeBalance = ESB_TIMEBAL_NONE
.usSkip = ESB_SKIP_NONE
.usShare = ESB_SHARE_DYNCALCNOSTORE
.usStorage = ESB_DIMTYPE_SPARSE
.usCategory = ESB_CAT_ATTRIBUTE
.usStorageCategory = ESB_STORECAT_ATTRIBUTE
.Attribute = ESB_ATTRMBRDT_NONE
End With
End Sub
Any help will be appreciated as Oracle support is none so far.

Hi,
Your error "ESB_OUTERROR2_ILLEGALDATATYPE and 64 = ESB_OUTERROR2_ATTRDIMNOTASSOCIATED." indicates problem with attribute dimension association
kindly check is there any duplicate member in attribute dimension.
or same attribute dimension is associated with some other dimensions

Outline will not restructure after adding another attribute dimension

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

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

Problems with multiple Attribute Dimensions

Hello Guys,
when i try to get data from an Essbase database using the Grid API with more then one Attribute Dimension,
the server needs a very long time to response or doesn't response at all.
I encounter the same behaviour when i perform a query using the Excel Query Designer.
Here is a sample query log output:
<subquery>
<cluster size="1">
<dim size="1"><member>MEASURE</member></dim>
<dim size="1"><member>PERIOD</member></dim>
<dim size="1"><member>YEAR</member></dim>
<dim size="1"><member>CATEGORY</member></dim>
<dim size="1"><member>CURRENCY</member></dim>
<dim size="1"><member>CUSTOMER</member></dim>
<dim size="1"><member>PRODUCT</member></dim>
<dim size="1"><member>Business</member></dim>
<dim size="1"><member>black</member></dim>
<dim size="1"><member>Attribute Calculations</member></dim>
</cluster>
</subquery>
<elapsedtime>94.217 seconds
Any help would be appreciated.
Regards,
Martin Brandl

Thanks for the swift response. Always ideas are useful.
As of now , Middleware cannot split the file.
Thing is SAP is creating two Idocs with different message types. Problem is First IDoc contains ORDERS message type but also DELIVERY segments as well. Second IDoc with DELIVERY message tyoe but ORDERS segments as well... This is the problem... I think we are missing some field activation in file for EDIDC record.
As far as I know file port supports the number of IDocs in one file.. Hope TRFC port also supports that

Attribute dimensions may only be added to sparse dimensions

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

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

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

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.

Error when Refresh Planning after adding attribute V9.2.1

Has anyone encountered this and what is the solution:
Added new attribute dimension in planning web and added attribute members. When I try to do incremental or full refresh, receive error message:
Errors detected (AssocAttrDimension, 1060057) Could not associate attribute with member (attribute,member) Decanatura, Career -2147218881
Career is the dimension and Decanatura is the attribute added
Using 9.2.1
Thanks
Jeff

Hi Jeff,
please find some findings from planning DBAG which may be useful to resolve your issue:
You can assign attributes only to sparse dimensions.
You cannot assign attributes to label-only members.
After you create attributes and attribute values, you can assign attribute values to each member of the dimension.
You must assign attribute values to dimension members at the same member level within a dimension.
You can define attribute values for Entity, user-defined custom dimensions, and Account
members if the Account dimension is designated as a sparse dimension in all plan types. You
can then assign attribute values to members of a dimension.
Attribute values for an attribute must be assigned to the same-level sparse dimension members.
Assigning an attribute value to another level causes an error during the application refresh.
hope this helps.
www.dornakal.blogspot.com
Edited by: Dornakal on May 28, 2009 5:55 AM

ODI Planning Attribute Dimension

I have an existing Product dimension that was created via ODI 10.1.5.6 to Planning 11.1.1.3.03 -- the Product Dim loads fine. Then I attached an attribute dimension called "Product Line" to it using custom attributes. I added four attributes to attach to products. Then re-reversed the Planning application in ODI Planning Model. I can see "Product Line" attribute load dimension (to load new attributes) in the Dimension hierarchy in ODI. However I cannot see a new Column for "Product Line" under the "Product" dimension in ODI. Am I missing something??

So adding the manual dimension seemed like it would work. However it gave me an error as it didn't recognize it when I executed the integration. In any event, deleted the planning model, recreated it and reversed it and the field showed up. Fun stuff! Thanks again.

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

Setting up Dynamic Attribute dimension.

Hi,I have a dimension for my clients and a measure dimension for sales. I want to set up an attribute dimension called Band for my Client dimension. This should be set to "Band=Large" when the sales total for the client is more than 20000 USD in the previous year (2001) or it should be set to "band=Small" if the total sales for the previous year is less than 5000 USD or else "Band=Mid" if the total sales in the previous year is between 5000 to 20000 USD. Currently, I use excel sheet from the essbase database extrace the total sales for each range and use the same as input to set the attribute dimension. Is there a easy way to do this using calc script.regardssuja.

No, there isn't. Since attributes are member based, there is no way (at least in Essbase) to dynamically assign an attribute to a member based on a data point.However, there are ways around the problem, but I can see one dilema. What if sales for a client is "large" for a member of one dimension but "small" for another? Members are not intersection based, so a client cannot be tagged as "Large" for one intersection and "Small" for another.If you want to go the attribute route, there may be a way to automate the process you described in your post - perhaps running an extract from Essbase similar to your Excel report and having a script assign the attribute value according to the sales figures.If you want to use a calc script, you could create a "BAND" member in your accounts dimension and assign it a 1 (Small) 2(Medium) or 3 (Large) depending on the sales figures.Hope that helps.Regards,Jade-------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

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.

Problem adding attribute dimension

Similar Messages

Maybe you are looking for