TM1 Forum

I am trying to create a TM1 approval hierarchy but whenever I go to put my hierarchy in place, I get two errors. One stating that the hierarchy has more than ope top level member, and the other stating that the hierarchy includes consolidated members but excludes their children. Problem is that within the hierarchy neither is true, but when I go to preview what the hierarchy looks like contributor has shifted the top level element down a level. Does anybody know why this is happening, does contributor not support uneven work flow hierarchies?

Hi

The requirements for Approval Hierarchies are very restrictive. Are you sure that there are no alternate hierarchies in the dimension, ie no element with more than one parent? One way to check is to list out all the elements in Excel and use an ELPARN alongside.

Are you sure that all the elements join up to a single top level element? One way to check is to do a show all on the dimension, past the elements in to Excel, then select the top level element and do an expand all below and past in to Excel - both lists should be the same length.

Check that the subset includes all elements - using a dynamic subset with an expand all is a good way to be sure of that.

Personally I haven't really understood the point of Contributor yet. Our users still prefer a more customised Excel interface that the View based interfaces that Contributor can offer.

Regards


Paul Simon

If your approval hierarchy dimension contains more than one top level rollup then you need to use a dynamic subset drilling down children as your approval hierarchy. This is the only way that contributor can tell which top level parent is the top of your approval hierarchy. This is most likely the cause of your error.

I see, I have created a hierarchy that has a top level BS hierarchy so that there is a single hierarchy in the dimension. I did not however know that each element could only have one parent. That is probably the issue.

Hi guys,
Im having a similar issue with TM1 Contributor,
We are implanting a budget application at a client and by the time we were doing the contributor part, we used a dimension's subset with just one hierarchy and it worked perfectly.
After a while, there were needed a second hierarchy at the same dimension but, as in contributor we only use subsets for approval hierarchies, there should be no problem inserting this new one.
The problem is that now its returning the very same error that "cdhodge2002" has, it says that the hierarchy has more than one top level member, but when I go to TM1 Client, the subset has just one top level
Another weird thing happening, is that when we look at the hierarchy that is being created by contributor, it looks like it shows the structure by the order the items were inputed when dimension was created, and not a logical hierarchy.

Maybe that is happening because of the new hierarchy, but if contributor uses a subset and not a dimension, that shouldnt be happening.

Has it ever happened to any of you??
Many Tks
Renato de Araujo Santos

Just in case, maybe you may try creating your subset with the following expression to avoid multiple top nodes by logic:

Hi mce
Unfortunately it did not work
maybe its a problem on contributor
thank you very much
Renato de Araujo Santos

Hi again everyone,
I've deleted the second hierarchy's leaves and the contributor worked again, wich points that the whole lalalá about using a subset instead a dimension for a workflow approval is not true. That is why, in the "botton line", i cant have two hierarchies.
Also ive had to keep the totals because i use then for some rules in other cubes, by then, the rights were the chosen ones to stop working propperly.
Eventually, when I use the top level item, a test user starts to have access to the hierarchy, but when i choose any other item it returns the error "java.long.ArrayIndexOutOfBonds", which I suppose that is because of these totals, as ive tested some other applications without more than one hierarchy and they worked perfectely.
Do you guys have any clue about it?

Regards
Renato de Araujo Santos

Hi all,

I know this is a really old post but I'm hoping someone can help me.

I am working with Contributor 9.5.2 and am creating an application for the first time.

I have created a subset for the hierarchy approval - the method that I used to to this was create a new Top Level element in Dim editor, copy and paste all other elements (both Consolidations and n level elements) into it. In subset editor I then selected the new top level element and expanded all elements under it and saved as a new subset.

I know that all elements only has one parent (I can see this visually and have carried out the ELPARN test in excel). And I know that there is only 1 top level element.

When I copy the approval hierarchy subset into the design pane of contributor I get the following message "The hierarchy has more than one top level member". When I view the subset in the contributor design pane it looks like the direct children of the Top level are correct (they roll up to the top level), but the next level of consolidation elements and the N levels below this (the dim has 4 levels) all look like top level elements - hence the error message. Yet in perspectives the hierarchy looks like I want it to.

I have made the subset dynamic using " {TM1DRILLDOWNMEMBER( {[PAAR_AFE].[Tullow]},ALL, RECURSIVE ) } " in the expression window of the subset editor. The resulting hierarchy in perspectives again looks like I want it to, but again in Contributor it has the same results as before.

I tried creating a new Dim from scratch (I only added 20 or so elements over a couple of levels) to test - this worked fine. However, I don't want to have to create a new dim and re-create all of the cubes with this dim just for the contributor to work - I would much rather the existing dim subset worked!

Any advice would be much appreciate.

Cheers

What about the IBM Technotes 1568864, 1497495 or 1449599 ?


https://www-304.ibm.com/support/docview ... wg21568864
Tm1 Contributor - Workflow page is blank

Cause
Approval Hierarchy Dimension Subset is dynamic. It is not possible to use an MDX with TM1DrilldownMember


https://www-304.ibm.com/support/docview ... wg21497495
Unable to define an Approval Hierarchy in TM1 Contributor/Cognos Express Planner: The hierarchy has more than one top level member


https://www-304.ibm.com/support/docview ... wg21449599
TM1 Contributor approval hierarchy errors adding a subset