Moving Member in Entity Hierarchy

Hi Guys,
I have just been given the task of moving a member in our entity hierarchy.
I know how to move the member, but do I have to re-consolidate the data after the move, and how far back do I re-consolidate?
Thanks

Thanks for that, Just a Q on the journal entries.
What "Special" way do they have to be treated?
I dont think there are any journlas processed on this entity but I will check.
Any other advice/considerations to take into account when moving an entity?

Similar Messages

Adding additional entity hierarchy.

When trying to add a fourth entity hierarchy in BPC v7 I get the following message:
"Errors in the metadata manager. The process type specified for the entity dimension is not valid since it is not processed".
This message is received while trying to process the entity dimension. It stops at step 4 of 5 of the processing. Prior to this attempt I was getting an error message saying that I exceeded the 8060 byte per row limit of SQL so eliminated some property members. I am not sure how the 8060 is calculated.
Thanks for the help.

Hi,
When you are creating dimensions for your application set you should be aware of the following maximums for any one dimension.
u2022 The maximum number of fields in a table (a dimension = 1 table) is 1024.
u2022 The maximum record size is 8064 bytes (a record = 1 row in a table)
The two maximums above relate to the underlying SQL database in which BPC information and data is stored. They need further explanation as to how they relate to a BPC dimension. In BPC a field equals a property. So you can have up to 1024 properties in a dimension. One other factor that has an impact on the actual number of properties you can have in a dimension is the number of levels you have defined.
SQL Server creates a set of properties for each level within the dimension. For example, you have 10 properties and three levels in your dimension, your total number of fields is 30. The second limiting factor is the size of the record. To determine record size you have to figure out the number of bytes (a byte equals a character) in each level. Since levels are repeated you only need to figure out the number of bytes in the first level and then multiply that number by the number of levels. To come up with the total number of bytes for a level you simply add up the field size for each field and multiply it by 2.
Hope this helps you.

I have account member ACC15015.for intersection of N0_version,No_Scenario,No_Entity I WNAT TO CAOP THIS aCC15015 DATA TO EACH SCENARIO,EACH VERSION AND LEV 0 MEMBER OF ENTITY.PLZ HELP ME

i have account member ACC15015.for intersection of N0_version,No_Scenario I,No_Entity I have some data for this intersectionNOW I WANT TO CYOP THIS aCC15015 DATA TO EACH SCENARIO,EACH VERSION AND LEV 0 MEMBER OF ENTITY.
WHAT IS THE SSCRIPT FOR THIS
PLZ HELP ME

I guess my first question is why? One of the beauties of Essbase is the efficient way it stores the data. If you are using this for a calculation, you can just reference the intersection where the data exists. Bloating your database by creating blocks for all of these intersections is counter-productive.

Setting default member of attribute hierarchy in MDX script. Default member not taken into account while using user defined hierarchy

Hi all
I have a date dimension that (type time) with attributes
- [FiscalYear] (type years)
- [FiscalMonth] (type months)
- [FiscalWeek] (type weeks)
In addition to the attributes used in the natural hierarchy, I have an attribute [PerType] containing one member comming from the relational table 'WTD' which corresponds to 'Current Date'. All other members of this attribute hierarchy are calculated members (defined in the MDX script). Examples:
--Last year
CREATE MEMBER CURRENTCUBE.[Date].[PerType].[LY] AS NULL,
VISIBLE = 1;
SCOPE([Date].[PerType].[LY]);
SCOPE(DESCENDANTS([Date].[Fiscal].[All], [Date].[Fiscal].[Year], SELF_AND_AFTER));
THIS = ([Measures].CurrentMember, [Date].[PerType].[WTD], ParallelPeriod([Date].[Fiscal].[Year], 1));
END SCOPE;
END SCOPE;
--Month to date
CREATE MEMBER CURRENTCUBE.[Date].[PerType].[MTD] AS NULL,
VISIBLE = 1;
SCOPE([Date].[PerType].[MTD]);
SCOPE(DESCENDANTS([Date].[Fiscal].[All], [Date].[Fiscal].[Week], SELF_AND_AFTER));
THIS = Aggregate(CrossJoin({[Date].[PerType].[WTD]}, MTD([Date].[Fiscal].CurrentMember)));
END SCOPE;
END SCOPE;
--Year to date
CREATE MEMBER CURRENTCUBE.[Date].[PerType].[YTD] AS NULL,
VISIBLE = 1;
SCOPE([Date].[PerType].[YTD]);
SCOPE(DESCENDANTS([Date].[Fiscal].[All], [Date].[Fiscal].[Period], SELF_AND_AFTER));
THIS = Aggregate(CrossJoin({[Date].[PerType].[WTD]}, YTD([Date].[Fiscal].CurrentMember)));
END SCOPE;
END SCOPE;
The defalut member of FiscalWeek attribute hierarchy is set dynamically in the MDX script:
ALTER CUBE CURRENTCUBE UPDATE DIMENSION [Date].[FiscalWeek], DEFAULT_MEMBER =
Filter(
[Date].[FiscalWeek].Members,
[Date].[FiscalWeek].Properties( "FiscalWeekStartDate", TYPED) <= DateAdd("d", -2, CDate(CStr(Month(Now())) + "/" + CStr(Day(Now())) + "/" + CStr(Year(Now()))))
AND
[Date].[FiscalWeek].Properties( "FiscalWeekEndDate", TYPED) >= DateAdd("d", -2, CDate(CStr(Month(Now())) + "/" + CStr(Day(Now())) + "/" + CStr(Year(Now()))))
)(0).PrevMember;
If I run the following query:
with member
measures.x as [Date].[Fiscal].DefaultMember.Name
measures.y as [Date].[FiscalWeek].DefaultMember.Name
select
measures.x,
measures.y
} on axis(0)
from [GLWeekly]
it gives me back correctly the default member set over the MDX script.
I order the statements in the MDX Script so that the default period (week) is set at the beginning of the script (just after the calculate).
I do not understand why creating the following calculated member I am obliged to specify [Date].[Fiscal].CurrentMember in the tuple to have correct results:
MEMBER [Account].[CoA].[Standard Engagement Revenue (MTD)] AS ([Account].[CoA].[Standard Engagement Revenue], [Date].[PerType].[MTD], [Date].[Fiscal].CurrentMember)
I would expect that:
([Account].[CoA].[Standard Engagement Revenue], [Date].[PerType].[MTD])
is sufficient.
If the default week is specified in the slicer using a member of the natural hierachy (=> [Date].[Fiscal].x) it works.
Why can't SSAS use the default member if it is must defined in the MDX script?
Can someone explains me this. Thanks a lot in advance.

Hi Ina,
have you thought about adding a dynamic statement inside the MDX script? You could define the default member like this:
... DEFAULT_MEMBER = iif( Day( Now() ) = 3, <expression for previous month>, <expression for current month> );
This way you don't need to change it everytime by running a script.
By the way, what do you mean it doesn't update the default member? When you execute this MDX what does it says?
with member measures.x as [Dimension].[HierarchyName].DefaultMember.Name
select { measures.x } on 0 from Cubename
If this returns the correct name, then the problem is somewhere else. I believe it should return you the correct name. Look here, test this on Adventure Works, statement by statement and see what happens.
ALTER
CUBE [Adventure Works]
UPDATE
DIMENSION [Product].[Product Categories],
DEFAULT_MEMBER = [Product].[Product Categories].[Category].&[1]
with
member measures.x
as [Product].[Product Categories].DefaultMember.Name
select measures.x on 0
from [Adventure Works]
ALTER
CUBE [Adventure Works]
UPDATE
DIMENSION [Product].[Product Categories],
DEFAULT_MEMBER = [Product].[Product Categories].[All Products]
with
member measures.x
as [Product].[Product Categories].DefaultMember.Name
select measures.x on 0
from [Adventure Works]
I think you can see which members are default (on related hierarchies) using
MDX Studio. This should help you detect which attributes have not moved accordingly and hence cause problems in your report. The usual suspects are those attributes used in your last month reports. If that's too much for you, just copy paste the definition
of the measure x and use .CurrentMember instead .DefaultMember. And so for all related hierarchies of your dimension. You can run it as one query, just put enough measures (x1, x2, ...), one for each hierarchy, ok?
Here's a test for Day():
with
member measures.y
as
iif( Day(Now()) = 28, 'Yes', 'No' )
select
measures.y on 0
from [Adventure Works]
Today this returns Yes, tomorrow it will be No.
Ups, I just checked one more thing. When you run the script, it sets the default member only for that session. If you execute the first two of the four statements that I've sent you, it will set the default member on Bikes and show you that.
But, if you open another query windows and execute that select statement (only), you'll see All member instead. So, it has set it to Bikes only for the currect session. Consequence? You reports are not aware of it. So, better use dynamic statement in
your MDX script.
Regards,
Tomislav Piasevoli
Business Intelligence Specialist
www.softpro.hr

Rejecting a moving member when using interface tables

Hi,
I'm using the interface tables to update some of my dimensions in EPMA.
My problem is that I want the process to reject members when they are moved, and I can't do that.
Let me explain a little bit more: if I have a product A under a parent X, and that in the next load, A is specified under Y, then I want the process to fail with a message like this: "the member cannot be created because it already exists under another parent".
Right now what it does is that it create the new A under Y and the A under X as shared member. I've tried to change the settings of my profile: I change Merge as Primary for 'replace' but that's not what I want. I tried 'Move' but it's not what I want. I tried to set my IsPrimary column as blank string, doesn't change anything.
Does anyone know how to do that ? Basically, we want to make sure that no product are moved by mistake. Any movement should be performed manually by the admin in the dimension library before interfacing.
Thanks for your help.
Cyril

I used only IM_Dimension & HS_Account_Hierarchy table to load data and that worked.
But now, if I want to give option to user to select the Load_Id while importing, IM_Load_Info needs to be populated.
The problem arises at the time when you try to insert data in IM_Load_Info. Even if we clear data from the table it generates next sequential Load_ID from previously deleted record. For eg. Load_Id in IM_Dimension & hierarchy table is 1, then for the same record in IM_Load_Info can have Load_id as 14.
Now user can select 14 while importing but cannot import any data since all records are having Load_Id as 1.
I am still not able to resolve/handle this problem

Need to create a dimension member formula refering hierarchy.

Hello Experts ,
System : BPC 10 NW SP 11
Dimension : BOOK – entity type
Dimension : ACCOUNT - Account type
Scenario : create a ACCOUNT dim member formula effecting only members exists in Entity dimension PARENTH3, with property MGMT_CALC = Calc.
I tried below syntax : but none of them working.
IIF([BOOK.PARENTH3].CURRENTMEMBER.PROPERTIES("MGMT_CALC")="CALC", (IIF ([PNC_REV]=0,0,[ACCOUNT].[PNC_UUND_TOT]/[ACCOUNT].[PNC_REV])),NULL); SOLVE_ORDER=10
IIF([BOOK].[PARENTH3].CURRENTMEMBER.PROPERTIES("MGMT_CALC")="CALC", (IIF ([PNC_REV]=0,0,[ACCOUNT].[PNC_UUND_TOT]/[ACCOUNT].[PNC_REV])),NULL); SOLVE_ORDER=10
IIF([BOOK.H3].CURRENTMEMBER.PROPERTIES("MGMT_CALC")="CALC", (IIF ([PNC_REV]=0,0,[ACCOUNT].[PNC_UUND_TOT]/[ACCOUNT].[PNC_REV])),NULL); SOLVE_ORDER=10
In case I am not reading hierarchy as in below syntax, it works fine.
IIF([BOOK].CURRENTMEMBER.PROPERTIES("MGMT_CALC")="Calc", (IIF ([PNC_REV]=0,0,[ACCOUNT].[PNC_UUND_TOT]/[ACCOUNT].[PNC_REV])),NULL); SOLVE_ORDER=10
The requirement is to read PARENTH3 members with specific property value.
Thanks in advance
Pavan

Hi Pavan,
I believe there is a similar thread to which I have responded.
Your formula is based on a condition with a property. A property value is applicable to the member irrespective of which hierarchy it belongs to. So, why do you need to consider the hierarchy for your formula?
Hope this helps.

Toplink Unmapped class member in Entity

I am using Oracle Toplink
I would like to add an unmapped property (class member) to my entity, meaning I just want an entity class member that is not tied to the database. Doing so, toplink automatically defaults the mapping and throws an exception stating that no database column exists. I just want a simple class member that does not exist in the database.
Is it possible to tell toplink to ignore this class member so that it will not look for it in the database?
What are the alternatives?
Thanks for the help
Suzanne

You need to mark the field as transient using the JPA @Transient annotation.
<p>---
<br>James Sutherland
<br>Oracle TopLink, EclipseLink
<br>Wiki: Java Persistence, EclipseLink

Can ODI journalising help to identify if any member deletes from hierarchy

Hi
I am applying journalizing to identify if there is any change in hierarchy.
I extract dimension hierarchy into a DB table on which journalizing is already applied.
If there is insert in the DB table (new member added), the ODI identifies it, any updates my target from this journalizing table.
Now, if i delete a member from my dimension and then extract this dimension members into DB table, it just enters data into table(overwriting the existing rows).It does not identify if any member has been deleted coz that member still exist in the DB table & does not get deleted from the table.
In this case how can we check if any member has been deleted from the hierarchy or not. Is there any other option to achieve this

I just looked at all the ddls' i have the following syntax for all MV's
CREATE MATERIALIZED VIEW WIS.SNAP_MAX_ENTITY
TABLESPACE WIS_CDS_DATA01
PCTUSED    0
PCTFREE    10
INITRANS   2
MAXTRANS   255
STORAGE    (
            INITIAL          80K
            MINEXTENTS       1
            MAXEXTENTS       UNLIMITED
            PCTINCREASE      0
            BUFFER_POOL      DEFAULT
NOCACHE
LOGGING
NOCOMPRESS
NOPARALLEL
BUILD IMMEDIATE
USING INDEX
            TABLESPACE WIS_DATA01
            PCTFREE    10
            INITRANS   2
            MAXTRANS   255
            STORAGE    (
                        INITIAL          80K
                        NEXT             80K
                        MINEXTENTS       1
                        MAXEXTENTS       UNLIMITED
                        PCTINCREASE      0
                        FREELISTS        1
                        FREELIST GROUPS 1
                        BUFFER_POOL      DEFAULT
REFRESH FORCE ON DEMAND
WITH PRIMARY KEYEdited by: vijayp on Aug 7, 2012 6:44 PM
Edited by: vijayp on Aug 7, 2012 7:02 PM

Moving member servers without DC

Hi
I have recently been asked to move some server's (running windows server 200 and windows server 2003 r2) to a new site as the old site is being decommisioned, the DC's will be decomm'd, as the legacy data will only be required for reference purposes and
the business is closing down, as the company is being closed down.
The DC's run DNS, DHCP and ADDS.
The servers that will be moved are purely application servers, I was wondering what would happen when the DC's are powered off? Will the member servers still function and communicate, also the time server is one of the DC's, how will this affect the retrieval
of data from the member servers.
Thanks
Gin

The servers that will be moved are purely application servers, I was wondering what would happen
when the DC's are powered off?
If I understand well, the DCs will be decommissioned and the domain will no longer exist. If this is the case then you will need to disjoin these servers from the domain to avoid false positive alerts in the logs and so that you can do the things in the
correct way.
About the impacts on your application servers, you need to know their dependencies and relation with AD. If you have an AD based application then it will no longer work. You need to check each of these applications and do the assessment of the impacts. A
test environment would help and contacting the application developers / support would be helpful too.
Will the member servers still function and communicate, also the time server is one of the DC's,
how will this affect the retrieval of data from the member servers.
About which data are you speaking? You need to check the requirements for your applications.
As for the time sync, you need to think about hosting an internal NTP server that is in sync with external ones or simply make all your servers point to external NTP servers for time sync as you will no longer have DCs.
The servers will hold data and the legacy application, without the DC's will the servers boot up
and be able to talk to each other, also what happens with the time synchronisation when there's no DC available.
They will be able to boot and use the cached credentials for authentication. For the time sync, it will no longer work as your DCs will be no longer available.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

All member for Time hierarchy shows measures as NULL

Hi!
I've encountered the following problem.
I have a simple Time hierarchy in my cube (Date -> Month -> Quarter -> Year) and when I try to filter data by inserting the filter into nested FROM I get NULL for ALL element. For example:
SELECT NON EMPTY [DIM DATE].[DIM DATE].[All] on columns
FROM (SELECT ({[DIM DATE].[DIM DATE].[Year].&[2015]}) on columns from [CUBE])
WHERE ([Measures].[Measure1])
At the same time this query returns me normal value:
SELECT [Measures].[Measure1] on columns
FROM [CUBE]
WHERE ( [DIM DATE].[DIM DATE].[Year].&[2015])
Is there anything wrong with hierarchy? What should I check at the first place?
Many thanks in advance!

Hi, Simon!
Thank you for your reply!
The problem is that I can't actually change those queries as they are generated by Excel 2010 while my cube is being browsed. Here is what I do in Excel 2010:
1.Dim Date hierarchy is in Rows section and Measure in Measures.
2.Dim Date is filtered - only 1 year is chosen.
3. In my cube Total is empty, and here it is not.
4. Here is what I get in MDX :
SELECT NON EMPTY [DIM DATE].[DIM DATE].[All] on columns
FROM (SELECT ({[DIM DATE].[DIM DATE].[Year].&[2015]}) on columns from [CUBE])
WHERE ([Measures].[Measure1])
Here is screenshot of Step-by-Step Sample cube, with an example for this situation:
And the second query is for this simple situation:
1.Dim Date is moved to Filters section and the same year is chosen there.
2.Measure 1 is selected in the Measure section.
3.Measure is not empty.
4.I get this MDX:
SELECT [Measures].[Measure1] on columns
FROM [CUBE]
WHERE ( [DIM DATE].[DIM DATE].[Year].&[2015])
Here is a screenshot of Step-by-Step cube with same query. In my cube the situation in this case is the same:
When I try doing this in MS Sample cubes - it works fine, totals are shown in both cases.
Thank you in advance!

Showing member in different hierarchy level

hi all!
i have requirement to show data which on different level hierarchy.
my xml hierarchy : AsetHeader,AsetHdrDesc (lev1)
L Aset Number(lev0)
L Aset activation date(lev0)
i want to show all in format like this (all in same level):
AsetHeader|AsetHdrDesc|AsetNumber|AsetActivation
AsetHeader|AsetHdrDesc|AsetNumber|AsetActivation
fyi, aset number can be NULL value.
any help will be appreciated,
thx
Edited by: user13655637 on Apr 25, 2011 10:57 PM

Hi ganesh,
for this same as normal procedure.. but in BEX analyser.. in the query designer window properties.. I mean select ur hierarchy and right click and > select Ristrict-> and there you can select particular level of nodes only...
so, there you can select all fourth level nodes..and drag and drop it into right side window... and save it.. and execute the query..
so, now you can get only Fourth level nodes only in the reporting level...
i think this will helpfull to u..if it's ok ... Reward me points..
Thanks
@jay

Moving CCG from Alternate Hierarchy

Dear All,
How can i move a cost center group from Alternate hierarchy to standard hierarchy ? I have tried OKEON in standard hierarchy however it gives me an error saying that the cost center group is already present. Should I delete the CCG in alternate hierarchy. Pls advice.
best regds
Subha

Hi,
Delete the cost center group from KSH2 and add create it from OKEON.
Your problem will solve.
Regards,
Ravi

Shared Members on interface changes of Entity or account hierarchy

Hello,
Is there any scripted way to remove 'Shared Members' from the Account and Entity hierarchy, or if not, is there any means of finding them on mass, as we have set up a database interface to maintain account and entities, but the problem is after accounts or entity change parent they leave a 'Shared Member' on the original parent, which is not desired functionality as it throws totals out on forms / reports.
thanks for your input, no blogs please as our security prohibits me seeing them.
Robert.

Thanks John, can I ask you a follow on also...
If a member had never share as its property and you used the hierarchy interface to assign it to a new would would it; -
a. Prevent update of its parent hierarchy via the interface
b. Move it to whatever new parent you deemed and remove it from its original
thanks for your input,
Robert.

Data not rolling up of a dynamic calc member for a particular entity

Hi,
In my planning application data is not rolling up of a dynamic calc member for a particular entity whereas it is working fine for other entity.
Please find below the sample Smartview Retrieve
----------------Member_ALL---Member_None---Member Top---Member_ALL---Member_None---Member Top
----------------Entity 1----------Entity 1------------Entity 1----------Entity 2----------Entity 2------------Entity 2
Acc1------------100----------------#--------------------#---------------122---------------#-------------------122
NOTE: # denotes missing
Member_ALL and Member_None are children of Member_Top. Both Member_ALL and Member_Top are Dynamic Calc whereas Member_None is Store.
As shown above data is rolling upto Member Top for entity 2 while it is not getting rolled up for Entity 1.
Request you to please help in finding the error.
Thanks in Advance'
Joseph

Hi Joseph,
Is Acct 1 Dynamic Calc? In that case will it NOT calculate the combination MemberTop->Entity1 as Member_ALL->Entity1 + Member_None->Entity1.
I beleive it'll calculate the Acct1 member again for Member Top based on the dynamic formula (whatever the logic). If you make it Acct1 Stored, then the aggregation will be correct by first calculating and storing the Acct1 member and then AGG the Member dimension.
Cheers,
Abhishek

"Zoom out" on shared member defaults to different hierarchy??

Hi Guys,
I've created a shared member Cost Centre hierarchy in my outline. When I "zoom in" to the shared member hierarchy to level 0, then try zoom back out, level 1 is no longer the shared members level 1 as I've defined in my new shared member hierarchy.
Instead, level 1 (from zooming out of the level 0 shared member) defaults to the rollup associated with the member that the shared member points to?? Is there a way to make the zoom out of a shared member from level 0, zoom to the level 1 in the shared members hierarchy and not the associated member that the shared member point to?
I really hope that makes sense to you guru's :-)
Thanks
Dermott.

user1113036 wrote:
That's the way Essbase has worked from time immemorial. Annoying, isn't it?You think it's annoying in the UI? It is really annoying in the API.. A standard way to walk a tree structure is the 'preorder walk algorithm' which essentially walks down the children of the tree, the next sibling(s), then back to the parent, etc until eventually the original root node is encountered signaling that all nodes have been visited. With the behavior of Essbase described in this thread, a preorder walk actually goes into an endless loop when the 'parent' is the 'real' parent of a member and not the shared member 'parent'.
Tim Tow
Applied OLAP, Inc
Edited by: timtow on Aug 24, 2008 5:37 PM

Moving Member in Entity Hierarchy

Similar Messages

Maybe you are looking for