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

Similar Messages

28.Which is a possible member of anchoring dimension (largest dense dim or smallest sparse dim or largest sparse dim...

Higreetings to you all.can anyone tell me "Which is a possible member of anchoringdimension (largest dense dim or smallest sparse dim or largestsparse dim etc.,)"?

There is a good explanation in the DataBase Administrator's Guide. The DBAG is always a good first stop for technical issues, and in many cases does a great job. One word of caution is that while the body text is rarely technically wrong, the same is not true for examples (throughout the documentation). Short answer (from memory, so it may be somewhat flawed): A sparse dimension is either a bitmap dimension or an anchor dimension. The bitmaps are used to optimize the calc order of the members, so it's basically a checklist of which ones are finished and which need to be done. Multiple bitmaps are needed for multiple calc conditions (like one member rolling up to more than one parent). The anchor dimensions are essentially 'outside' of this optimization technique, and thus the fewer, the better. Hence the DBAG reference to having a "single dimension, multiple bitmap" calc as being the most optimum. HTH

Why should we associate attribute dimension to base sparse dimension only

hi experts,
I have query, please suggest that.
Why should we associate attribute dimension to base sparse dimension only ? any reason is there.
thanks in advance

Have a read of - why attribute dimension attached to sparse dimension and Attribute Dimension and association with multi level base members
Cheers
John
http://john-goodwin.blogspot.com/

Aggregate only portion of sparse dimension

System 9 BI+(9.3) - Here's my problem.
I need to aggregate only a portion of a sparse dimension.
All members are stored data. Dimension looks like this:
Total Europe
-Western Europe
--France
--Germany
--United Kingdom
--Iberia
---Spain
---Portugal
-Central Europe
-Eastern Europe
I tried
FIX(May, 2009, @IDESCENDANT("Iberia"))
agg(Products,Channel)
ENDFIX
but all it does is aggregate Spain and Portugal, but not Iberia.
I also tried
FIX(May, 2009, @IDESCENDANT("Western Europe"))
agg(Products,Channel)
ENDFIX
but again all it does is aggregate France, Germany, Spain, Portugal, bit not Iberia or Western Europe.
Any ideas/assiatnce appreciated.

The comment on Network54 (sorry, I forgot who posted it) is on the money -- you are not aggregating Region/Geography/whatever your dimension is called.
Assuming your dimension order is:
Region
Products
Channel
I would write a script like:
FIX(@LEVMBRS("Products", 0), @LEVMBRS("Channel", 0))
@IDESCENDANTS("Iberia") ;
ENDFIX
FIX(@IDESCENDANTS("Iberia"))
AGG("Products", "Channel") ;
ENDFIX
You will have to rearrange this a little bit if your dimension order is different. As an example, if your dimension order is Products, Region, Channel, your code might look like:
FIX(@RELATIVE("Iberia", 0), @LEVMBRS("Channel"))
AGG("Products") ;
ENDFIX
FIX(@IDESCENDANTS("Products"), @LEVMBRS("Channel"))
@IDESCENDANTS("Iberia") ;
ENDFIX
FIX(@IDESCENDANTS("Products"), @IDESCENANTS("Iberia"))
AGG("Channel") ;
ENDFIX
This may look painful, but you may find a significant performance increase.
Take a look at my blog post, ignore all the Planning stuff, and jump to the bit where I explain how a BSO db consolidates. The concept is identicial to the one I outline above. Here's the link: http://camerons-blog-for-essbase-hackers.blogspot.com/2009/06/why-i-hate-and-love-business-rules-part_17.html
Regards,
Cameron Lackpour

FIX STATEMENT AND LARGE SPARSE DIMENSIONS

Hello all,
We have the following Essbase BSO db;
Account (Dense) (285 Members) (Aggregating Dimension)
Period (Dense) (65 Members) (Aggregating Dimension)
D1 (Sparse) (3700 Members)
(Aggregating Dimension)
D2 (Sparse) (8900 Members)
(Aggregating Dimension)
D3 (Sparse) (15000 Members)
(Aggregating Dimension)
Version (Sparse) (3 Members) (NON-Aggregating Dimension)
Scenario (Sparse) (5 Members) (NON-Aggregating Dimension)
Year (Sparse) (3 Members) (NON-Aggregating Dimension)
Currency (Sparse) (11 Members) (NON-Aggregating Dimension)
D4 (Sparse) (20 Members) (NON-Aggregating Dimension)
Block Size = ~150KM
Index Cache = 4GB
Data Cache = 8GB
CPUs = 8
MEMORY FREE = 26GB
NOTE:
We are executing the database with data loaded for "JUST" 10 BLOCKS,
SO
VERY VERY SMALL VOLUME OF DATA!!!
We have come across a rather irritating and strange issue while executing
the following calc;
CASE 1: With LEVEL-0 OF RELEVANT
SPARSE DIMENSIONS IN FIX STATEMENT
//ESS_LOCALE English_UnitedStates.Latin1@Binary
SET MSG ERROR;
SET CACHE HIGH;
SET UPDATECALC OFF;
SET LOCKBLOCK HIGH;
SET AGGMISSG OFF;
SET CALCPARALLEL 4;
SET CREATENONMISSINGBLK OFF;
FIX(ACTUAL,"2013",@LEVMBRS(D1,0),@LEVMBRS(D2,0),@LEVMBRS(D3,0),@LEVMBRS(D4,0),
@RELATIVE("EBITDA",0))
DATACOPY ARS->CURRENCY_VERSION TO ARS->WORKING;
DATACOPY CAD->CURRENCY_VERSION TO CAD->WORKING;
DATACOPY CHF->CURRENCY_VERSION TO CHF->WORKING;
DATACOPY COP->CURRENCY_VERSION TO COP->WORKING;
DATACOPY EUR->CURRENCY_VERSION TO EUR->WORKING;
DATACOPY GBP->CURRENCY_VERSION TO GBP->WORKING;
DATACOPY MXN->CURRENCY_VERSION TO MXN->WORKING;
DATACOPY CNY->CURRENCY_VERSION TO CNY->WORKING;
ENDFIX
$$$$$$NOTE1: The above FIX STATEMENT
works just fine and executes in 1 sec as its just a DATACOPY. ESSENTIALLY I
HAVE CREATED THE BLOCKS I WANT TO PERFORM THE BELOW SPARSE CALCULATION$$$$$$
FIX(ACTUAL,"2013",@LEVMBRS(D1,0),@LEVMBRS(D2,0),@LEVMBRS(D3,0),@LEVMBRS(D4,0),
@RELATIVE("EBITDA",0))
ARS = ARS->CURRENCY_VERSION *
"ARS_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
CAD = ARS->CURRENCY_VERSION *
"CAD_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
CHF = ARS->CURRENCY_VERSION *
"CHF_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
COP = ARS->CURRENCY_VERSION *
"COP_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
EUR = ARS->CURRENCY_VERSION *
"EUR_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
GBP = ARS->CURRENCY_VERSION *
"COP_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
MXN = ARS->CURRENCY_VERSION *
"MXN_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
CNY = ARS->CURRENCY_VERSION *
"CNY_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
ENDFIX
$$$$$$NOTE2: The above FIX STATEMENT
is where we have a problem, THE CALC JUST HANGS AND DOES NOT CALCULATE$$$$$$
CASE 2: With “specific” members of
RELEVANT SPARSE DIMENSIONS IN FIX STATEMENT
//ESS_LOCALE English_UnitedStates.Latin1@Binary
SET MSG ERROR;
SET CACHE HIGH;
SET UPDATECALC OFF;
SET LOCKBLOCK HIGH;
SET AGGMISSG OFF;
SET CALCPARALLEL 4;
SET CREATENONMISSINGBLK OFF;
FIX(ACTUAL,"2013",W1,"2251026",MORSCREJWHITE,MORSCREJWHITE_S,KG,TRADESALES)
DATACOPY ARS->CURRENCY_VERSION TO ARS->WORKING;
DATACOPY CAD->CURRENCY_VERSION TO CAD->WORKING;
DATACOPY CHF->CURRENCY_VERSION TO CHF->WORKING;
DATACOPY COP->CURRENCY_VERSION TO COP->WORKING;
DATACOPY EUR->CURRENCY_VERSION TO EUR->WORKING;
DATACOPY GBP->CURRENCY_VERSION TO GBP->WORKING;
DATACOPY MXN->CURRENCY_VERSION TO MXN->WORKING;
DATACOPY CNY->CURRENCY_VERSION TO CNY->WORKING;
ENDFIX
$$$$$$NOTE3: The above FIX STATEMENT
works just fine and executes in 1 sec as its just a DATACOPY. ESSENTIALLY I
HAVE CREATED THE BLOCKS I WANT TO PERFORM THE BELOW SPARSE CALCULATION$$$$$$
FIX(ACTUAL,"2013","2251026",MORSCREJWHITE,MORSCREJWHITE_S,KG,WORKING)
ARS = ARS->CURRENCY_VERSION *
"ARS_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
CAD = CAD->CURRENCY_VERSION *
"CAD_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
CHF = CHF->CURRENCY_VERSION *
"CHF_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
COP = COP->CURRENCY_VERSION *
"COP_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
EUR = EUR->CURRENCY_VERSION *
"EUR_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
GBP = GBP->CURRENCY_VERSION *
"GBP_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
MXN = MXN->CURRENCY_VERSION * "MXN_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
CNY = CNY->CURRENCY_VERSION *
"CNY_RATE"->"NO_CURRENCY"->"C_NONE"->"L_NONE"->"S_NONE"->"U_NONE"->WORKING;
ENDFIX
$$$$$$NOTE4: The above FIX
STATEMENT works just fine, as I am fixing on just ONE member from relevant
dimensions in the FIX STATEMENT$$$$$$
Please note the only difference between NOTE 2
and NOTE 4 is the FIX statements. I.e., Fixing all required lev-0 members from
required dimensions as opposed to Fixing on just single lev-0 members from
required dimensions.
Also please note that NOTE 1 FIX statement works
just fine! So, there is no problem with the FIX statement itself but rather
with the combination of Sparse Calculations and with Fixing all LEV-0 members
from required dimension in the FIX. Probably because the Sparse dimensions are
VERY LARGE.
Could anyone shed some light on what might be wrong here?
We are on Essbase standalone V11.1.2.
Your inputs are very much appreciated!
Thanks

Hi,
One minor thing I notice - your NOTE 2 problem script does not fix on your Working version, whereas the NOTE 4 script does.
With your small number of blocks, this should not be the problem, but it's probably worth quickly testing and eliminating before delving deeper.
Your script could be invoking member formulae from the Account dimension - does your outline validate ok..?
I cannot tell from your NOTE 4 script which member relates to the Account dimension - is it 2251026?
Whichever it is, it is worth expanding NOTE 4 script up to @RELATIVE("EBITDA",0)....
- if it runs, you know the problem is with your sparse member selections (ie number of blocks being calculated).
- If it doesn't run, then you know there is a problem in calculating one or more of the Accounts under EBITDA. In which case, gradually narrow the range of Accounts to locate the Account or Accounts that trigger the issue. Chances are there's a problem with the member formula

Value based hierarchies and Period dimension should only contain 2 monthl

Hi,
Can anyone tell me what is value based hierarchies. And also can anyone let me know to filter the records in AWm because in Period dimension should only contain 2 monthly values (Oct. 2008 ( 200810) and Sep. 2008 ( 200809)) it is urgent.
Thanks
vel

The following definition of a value hierarchy comes from the OLAP Developers guide
"A hierarchy defined only by the parent-child relationships among dimension members. The dimension members at a particular distance from the base level do not form a meaningful group for analysis, so the levels are not named. For example, an employee dimension might have a parent-child relation that identifies each employee's supervisor. However, levels that group together first-, second-, and third-level supervisors and so forth may not be meaningful for analysis."
Typically this means that the source table has two columns, VALUE and PARENT, where PARENT has a (logical) foreign key relationship to VALUE. An example may be EMPLOYEE, MANAGER, where MANAGERs are also EMPLOYEEs.
The simplest way to restrict the values loaded into the AW is to define a SQL view over the source table with an appropriate WHERE condition. You then use AWM to map the dimension to your new view. E.g.
CREATE OR REPLACE VIEW RESTRICTED_TIME AS
SELECT *
FROM TIME
WHERE MONTH IN (200810, 200809)

Set ZATTR_PROD may only be changed in the original system

Please,
Iu2019ve enhancement the PRODUCT_CUSTOMER2 BADI to change product attribute type when Iu2019m replicating products from ECC to CRM.
When I try to replicate the material from ECC to CRM thereu2019s the follow error:
"Set ZATTR_PROD may only be changed in the original system"
How can I solve it?
Thanks in advance
Edited by: Ronaldo Alvarenga on Oct 25, 2010 11:17 PM

Hello,
Maintain an entry for Z* settype in below path:
SPRO>IMG>CRM>Master Data>Products>Enhancements>Allow Changes to Product Data.
Hope this helps!
Best Regards,
Shanthala Kudva.

Sparse Dimension

Hello,
Recently Added 2 alternate heirarchies to a sparse dimension. I have made all the parents of alternate Heirarchies dynamic while all the lev0 are shared. while the parents and Lev0 for main heirarchy are stored.
1) Is it a good practise to have parents of alternate Heirarchy Dynamic? since its a sparse dimension.
2) My .pag size has increased ? why would adding shared members increase the .pag size?
3) also my Calc time has gone up... simple Agg which is fixed for single month and year which initially used to take 6 mins is taking 15 mins... Any advice on improving the calc time?
Thank You for your help.

1) This is usually not a good practice, as dynamic calcs on sparse dimensions can cause a lot of I/O during a retrieval. This can have an adverse affect on retrieve performance. Sometimes you can get away with it if
there aren't a lot of members under the dynamic member though.
2) I recently had a similar question on Network54. In my case, the answer was likely fragmentation. Does your .pag size go down after a dense restructure?
3) What happens if you say *@IDESC(Stored Parent Name);* instead of AGG (Dimension);. Any difference?
Hope this helps,
- Jake

[svn:osmf:] 9829: Extending ILayoutContext with an ' updateIntrinsicDimensions' method, that the ILayoutRender uses to inform the context that context' s intrinsical dimensions may have changed because its children got layed-out .

Revision: 9829
Author:   [email protected]
Date:     2009-08-31 06:38:08 -0700 (Mon, 31 Aug 2009)
Log Message:
Extending ILayoutContext with an 'updateIntrinsicDimensions' method, that the ILayoutRender uses to inform the context that context's intrinsical dimensions may have changed because its children got layed-out. Adding implementing code to LayoutContextSprite and LayoutRendererBase.
Modified Paths:
    osmf/trunk/framework/MediaFramework/org/openvideoplayer/layout/ILayoutContext.as
    osmf/trunk/framework/MediaFramework/org/openvideoplayer/layout/LayoutContextSprite.as
    osmf/trunk/framework/MediaFramework/org/openvideoplayer/layout/LayoutRendererBase.as

A slow boot time can be caused by login items.
User Login Items:
    Flux
    NoSleep
    ClipMenu
    Canon IJ Network Scanner Selector2
    BetterTouchTool
    USBOverdriveHelper
    TotalFinder
    Gmail Notifr
Open System Preferences > Users & Groups > Login Items
Remove one login item noted above then restart your Mac to test. It may be one or multiple items causing the slow boot.

Re-Order the Sparse Dimensions

Hi,
We have a typical scenario where in we need to change the order of sparse dimensions in the outline.The cube is already in use,however,as we got rid of few members in one of the sparse dimension and we want to change the order of sparse dimensions in the outline to enhance the performance.
My question here is,
1.How to change the order of the sparse dimensions in the outline?
2.What would be the impact?
Any quick response on this is highly appreciated !!
Thanks,
RNG

1) We can improve calculation performance by changing the order of standard (not attribute) sparse dimensions in the database outline. We can Order standard sparse dimensions by the number of members they contain, placing the dimension that contains the fewest members first.
This arrangement provides a number of possible improvements, depending on the site:
●The calculator cache functions more effectively, providing approximately a 10% performance improvement if you have a database outline with a very large dimension (for example, a dimension containing 1000 members).
●Parallel calculation, if enabled, is more likely to be used if the standard sparse dimension with the most members is the last standard sparse dimension in the outline.
2) I think there would not be an any impact...
JSA

Sparse Dimension calc order

Hi,I have some sparse dimension with different number of members.Which is the correct order in the outline to maximize the calc time ?Thank you.

You may achieve improvement in calculation performance by changing the order of the sparse dimensions in the database outline. Order the sparse dimensions by their number of members, starting with the dimension that contains the fewest members. (Ref :Database Admin guide)

Sparse dimension problem (2)

This message is for Jade Cole and Farid Rashid:I'm working on Hyperion Essbase 5.0.2 patch 11 and when you assign a constant to a member in a sparse dimension, Essbase DOESN'T create data blocks for sparse dimension member combinations!!! It must be a bug!!! I have replicated the situation on Hyperion Essbase 6.0 and works fine.Thank you,Lucas.

You need to restrict the CLEARDATA further, as it seems to be deleting the entire block. Hence, the Account = 1 is failing.There are a few ways to remedy the problem - one way would be to use DATACOPY to create the Enterprise1 and Enterprise2 blocks, but you would need a source member that had numbers.The other thing you could do is re-arrange the formula so that a sparse member appears on the left hand side of the equation, rather than a dense member. This will create the blocks and populate the values, but you should be careful, as it may create more blocks than you want.Hope that helps.Regards,Jade-------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

I am having the problem when trying to take a panorama picture. It may only take the first frame or doesn't even start at all when I press the shutter button. even though when i hold the phone straight up and down, so that camera is at the top

I am having the problem when trying to take a panorama picture.
It may only take the first frame or doesn't even start at all when I press the shutter button.
even though when i hold the phone straight up and down, so that camera is at the top on the back and the home button is on the bottom on the front.
This problem is irritating me....?

To take panorama
- ensure that the panorama option is on
- press the shutter button once
- you will see a line with an arrow
- move around in a circle ( I keep the camera steady and turn myself around in a circle)
- as you do this you will see the arrow moving across the screen as it captures pictures
- at the end of the capture, you will be able to see your panorama picture
I hope that this helps, do report back.

Problem while adding a new dimension in a existing cube with data in BW3.5

Hi,
We are trying to create a new dimension with new characteristics in a existing cube. But while activating we are getting error that "InfoCube contains data; intentional changes not permitted". Can we add a new dimension in a existing cube with data in BW3.5? If it is not possible then we can take the backup and delete the data from cube and then change the cube. But my question is that, when we will transport the cube with changes to quality then will it transport successfully or same procedure needs to be done there as well.
Regards,
Saikat

hi,
Adding new infoobject /dimension to the cube containing data in 3.5 is not possible.
easier solution is create a new cube similar to old and add the new dimension and proceed.
else you have to drop data and transport.
Ramesh

Error for output tax code:Tax code I4 may only contain one assignment line.

Hi
While posting customer invoice with output tax code, I am getting following error.
Tax code I4 may only contain one assignment line.
Please help me resolve.
Regards
Rekha

There are quite some answered questions in this forum for this issue.
Here is one.
Error in Sample document (Message no. FF731)
Also, please search the forum with the following search key words.
Tax AND code AND may AND only AND contain AND one AND assignment AND line
Make sure you select all posts, not just the past 90 days (the default option), and you will see quite some hits.

Attribute dimensions may only be added to sparse dimensions

Similar Messages

Maybe you are looking for