Attribute dimension member limits?

Are there any limits to how many members can be assigned to a specific attribute?
For example, if I have 80000 members, and I need 40000 of them to be assigned to one attribute option and 40000 to another (just pulling random numbers out of the air), is that allowed or are there limits to how many members can be assigned to one attibute option?

If there is a limit, it's a practical one rather than a technical one, or at least in the millions (meaning the practical limit will supercede the technical one).
That said, you are painting a performance nightmare -- but if it works, it works. :)

Similar Messages

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

Excel Addin - Attribute dimension values

Hi all, I have an excel report which pulls data for our departments. Eachdepartment has a manager and the manager for the department istagged using attribute dimension. Now I want to get data for alldepartments and in second column along with it the name of themanager (i.e. the attribute dimension member name). I somehowcannot figure out a way to do this again. Any inputs into how this can be done? 

Robert, Thanks for the suggestion.Our analysts already have the report templates setup which theyuse for retrival. I am not sure if they want to do something likethat. Sometimes there might not be data in the department forthat period and then that department would be suppressed but it isneeded in the report at times.I am guessing that I might have to do some VBA stuff in thereport to allow the analysts to have this. I was just hoping to seeif someone else has found a better way to do this. I say bettersince I was looking for some that the analysts might be able to doeasily but themselves.

How to tag attribute member with standard dimension member in EIS

hi,
would any one please help me how to tag attribute member with standard dimension member in EIS
THANK U IN ADVANCE

In your OLAP model, view columns for the base dimension table. Go into the column properties and for the columns that have Attribute values highlight them and click the Attribute button.
Go into Metadata Model and those fields will be available to drag into your outline as attribute members.
Once in the outline, go into the properties of the attribute and assign the level of the base dimension they associate with.

ORA-35563: Multiple values exist for an attribute of this dimension member

After following the tutorial Building OLAP Cubes I was trying to make a cube with aggregation down to the day instead of down to the month.
I created a times table pretty similar to the one used in the tutorial:
CREATE TABLE EVENT_TIMES (
        HOUR_KEY        DATE NOT NULL,
        DAY_ID          VARCHAR2(10),
        DAY_NAME        VARCHAR2(10),
        DAY_END_DATE    DATE,
        DAY_TIME_SPAN   NUMBER,
        MONTH_ID        VARCHAR2(30) NOT NULL,
        MONTH_NAME      VARCHAR2(40),
        MONTH_END_DATE DATE,
        MONTH_TIME_SPAN NUMBER,
        YEAR_ID         VARCHAR2(30) NOT NULL,
        YEAR_NAME       VARCHAR2(40),
        YEAR_END_DATE   DATE,
        YEAR_TIME_SPAN NUMBER
As you can see, instead of a DAY_KEY like in the tutorial, I now use an HOUR_KEY.
This is a sample of the data I inserted in this table:
select to_char(hour_key,'YYYYMMDDHH24MISS'),DAY_ID,DAY_NAME,DAY_END_DATE,DAY_TIME_SPAN,MONTH_ID,MONTH_NAME,MONTH_END_DATE,MONTH_TIME_SPAN,YEAR_ID,YEAR_NAME,YEAR_END_DATE,YEAR_TIME_SPAN from event_times;
TO_CHAR(HOUR_KEY,'YYYYMMDDHH24MISS') DAY_ID     DAY_NAME   DAY_END_DATE DAY_TIME_SPAN MONTH_ID                       MONTH_NAME                               MONTH_END_DATE MONTH_TIME_SPAN YEAR_ID                        YEAR_NAME                                YEAR_END_DATE YEAR_TIME_SPAN
20140104050000                       Y2014M1D4 Y2014M1D4 04-JAN-14                1 Y2014M1                        Y2014M1                                  31-JAN-14                   31 Y2014                          Y2014                                    31-DEC-14                365
20140104060000                       Y2014M1D4 Y2014M1D4 04-JAN-14                1 Y2014M1                        Y2014M1                                  31-JAN-14                   31 Y2014                          Y2014                                    31-DEC-14                365
I then created my TIME dimension with DAY as the lowest level.
When I try the maintain cube option it fails at the 'LOAD NO SYNCH' step with the rejected records having an error message that says:
ORA-35563: (XSRWLD17) Multiple values exist for an attribute of this dimension member.
To me, this is a very cryptic message and the only explanation I find online is:
Cause
Multiple source table rows containing different values for a dimension attribute were found. Only the first of the multiple rows has been loaded.
Action
Fix the mapping or remove the rows with conflicting attribute values..
This confuses me. In the tutorial the lowest level was day and the TIMES table contained 1 record for each day.
In my example, the lowest level is hour and the TIMES table contains 1 record for each hour.
Which attribute has multiple values? And which values?
The rejected records (101) are not very clear:
ALIAS_1 = 'MONTH_Y2014M1' AND ALIAS_3 = to_date('31JAN14') AND ALIAS_4 = 31 AND ALIAS_5 = 'Y2014M1' AND ALIAS_6 = 'Y2014M1' AND ALIAS_7 = 'YEAR_Y2014'
If anyone can help point me in the right direction, it would be greatly appreciated.

I have seen this recently. The issue is with the dimension load itself. You have a hour level record table but the rules relating to hierarchy/attribute values etc are checked/reinforced during the load and this error comes up sometimes.
I would guess that the issue seems to be with your month level information present in the higher level month columns. There are many records corresponding to a single month in ur case, month of Y2014M1. Information relating to Month level member Jan 2014 or member MONTH_Y2014M1 is present in these records: 31 (days) *24 (hours) = 744 records. The data in these 744 records for columns - MONTH_ID, MONTH_NAME, MONTH_END_DATE, MONTH_TIME_SPAN need to be exactly the same in order for the single member MONTH_Y2014M1 to have month attributes loaded with valid values.
For e.g: if records #1 to #743 contain month_timespan=31 but for some unknown reason record #744 contains month_timespan=30 then this error will come up. OLAP does not know which value to load (31 or 30), and only 1 value can be loaded onto the month level member corresponding to month Y2014M1.
A quick check of the data should give you the answer. Typically there may be some mistake/invalid assumptions made with the boundary records (in your case, check for values for records corresponding to hour=0 or hour=23/24) which is causing the issue.
HTH
Shankar

EPMA/Planning custom dimension member attributes question

I have a custom dimension associated to an attribute dimension that I am setting via dataloader. Can I query on members with missing values of an attribute?
For example,
Dimension: Product
Attribute: Color Members: Red, Green, Blue, Yellow
Should it also include a Color member “Other” and require that every Product member have the Attribute Color set to one of the members?
Thanks for your help -

Hi,
If you are requiring to do analysis on other areas then it is probably best practice to create another attribute which will store this information, as you mentioned you could just create a member called "Other"
Cheers
John

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.

How to get the ID of a dimension member in script logic?

Hi everybody,
I am working in some logic scripts and I wonder if exists any option to get the current member ID of a dimension in order to concatenate a string using the member referred and an additional set of caracters such as: MEMBER_ID&"_ccccc".
Moreover, I would like to use this ID dimension member in order to filter members of another dimension whose attribute is equal to the ID of the desired member. Is it feasible?
In conclusion, is it possible to get a variable which is referred to a member ID of a dimension, and using it in order to filtering other dimensions?
Many thanks in advance,
Antonio

Hi Antonio,
You ask if it is possible compare a dimension id with a property value.. yes it is posible , for doing that you will have to do something like this,
*FOR %ACC1%=ThisA,ThisB,ThisC
      *WHEN DIMENSION.PROPERTY=%ACC1%
              *REC(............)
       *ENDWHEN
*NEXT
if you want to concatenate using a filter theres a posibility, like this example using the time dimension.
*xdim_memberset time=%year%.jan -
>2011.jan
hope it helps

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

Error selecting a dimension member in BPC EPM report - The given key was not present in the dictionary

Hi,
We are currently running SAP BPC 10.1 NW on Hana
Version:
CPMBPC 810 SP 4
SAP_BW 740 SP 9
HANABPC 810 SP 4
EPM Excel Add-in 10 SP 21 .NET 4 build 9094.
On my embedded model. I have a BEX query on a aggregation level which I access in a report using the EPM Add-in Excel .
When I edit my report in EPM Add-in Excel , and I try to select the dimension members for a selected dimension member, I get the following error.
"The given key was not present in the dictionary"
Any assistance to help resolve the problem will be appreciated.
Regards
Gavin

Hi Shrikant,
I had a look at MBR_SEQ , it is a attribute on the dimension member in BW , this relates to a past version of BPC 7.5. We are currently on BPC 10.1 Embedded model , and the MBR_SEQ does not exist on any of the characteristics I have in my info cube.
When I create a web report I am able to access the dimension members using the select dimensions options, the problem seems to be on the EPM Add-in Excel client only.
Thanks
Gavin

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

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

Is it possible to create an Attribute Dimension in an ASO Database?

When I create the initial attribute parent and attempt to save the outline, it gives me an error that I need to associate the attribute dimension with the base dimension. So I go to my L0 member, but the associations tab is greyed out. Any ideas if this is possible to create? Thanks!

OK, Are you doing this.
1. create the attribute dimension
2. click on the base dimesnion
3. right click on the DIMENSION NAME and selet edit properties
4. Click on the tab called Attributes. You should see the list of attribute dimensions
5. Once the dimension is associated with the base dimension, you can assign attributes to the members

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.

Attribute dimension member limits?

Similar Messages

Maybe you are looking for