Hi
am having a problem trying to allocate some data iin cubes, what i want to do is really simple to understand:
I have a dimension called acounts ( acoun1,acoun2, acoun3...) verstions( ver1,ver2,ver3) and months.
so i have the following cubes:
cube1( acount, months, version) and cube2( groups, months, version) with the groups consolidating the proper acount.
something like:
acoun1
acoun2 group1
acoun3
acoun3
acoun4 group2
acoun5
etc, but the thing is the client needs to maintain this so he wants a "table" so he can input and change the destination of the acount, it needs to change. acoun1 can be in the future, part of the group 2.
if you guys have any experience with allocation tables ( Planning) and making it on tm1, pls let me know, it would be appreciated.
Thanks
Kazêh
Allocation table tm1
-
- MVP
- Posts: 2836
- Joined: Tue Feb 16, 2010 2:39 pm
- OLAP Product: TM1, Palo
- Version: Beginning of time thru 10.2
- Excel Version: 2003-2007-2010-2013
- Location: Atlanta, GA
- Contact:
Re: Allocation table tm1
There may be other options, but the best way I can think of to accomplish this is going to be to add the Account dimension to your second cube and then write a rule like:
Don't forget the feeders you'll need to write in Cube1.
Code: Select all
[] = N:IF(!Group@=DB('LookupTable',!Account,!Months,!Version,'GroupCode'),DB(Cube1,!Account,!Months,!Version),0);
-
- Posts: 44
- Joined: Fri Apr 19, 2013 12:59 pm
- OLAP Product: TM1
- Version: 10.1
- Excel Version: 2007
Re: Allocation table tm1
Thanks tomok, i used that line with a little changes and now is working perfectly, thank you man 

-
- Posts: 44
- Joined: Fri Apr 19, 2013 12:59 pm
- OLAP Product: TM1
- Version: 10.1
- Excel Version: 2007
Re: Allocation table tm1
Hi again guys, i have another doubt about this allocation.
in the end i came up with another solution cause the input cube for the client was too big, so he wants something more simple.
so i was thinking on this:
1: "origen" cube. with the acounts, versions, and months
2: "destino" cube. with groups, verssions and months
3: "updatedacountscube" with acounts and a new dimension "agrupador" and this one has a picklist with the groups
the updateacountcube is the cube that the client is going to eddit for changing the acounts.
http://postimg.org/image/3psu7kis7/ those are my cubes , the litle one is the updateacountscube
also i have a ti process that update the dimension acounts with a view from this cube, so if he wants to change the acounts from a diferent cube, he select the new group (11,12,13) , and this value is updated as an atribute for acounts dimension.
what i want to achieve now is to implement a rule that can take the atribute from acounts dimension and compared with the name of the groups and somehow consolidate only the acounts with the right atribute.. did i explain that well? xD
the real request is to make more simple the input table for the client so he can changes the acounts in diferentes groups, but he WANTS to see a table like that.
sorry for asking this again, but im still learning how to use tm1. Any help would be great.
Thanks
Kazêh
in the end i came up with another solution cause the input cube for the client was too big, so he wants something more simple.
so i was thinking on this:
1: "origen" cube. with the acounts, versions, and months
2: "destino" cube. with groups, verssions and months
3: "updatedacountscube" with acounts and a new dimension "agrupador" and this one has a picklist with the groups
the updateacountcube is the cube that the client is going to eddit for changing the acounts.
http://postimg.org/image/3psu7kis7/ those are my cubes , the litle one is the updateacountscube
also i have a ti process that update the dimension acounts with a view from this cube, so if he wants to change the acounts from a diferent cube, he select the new group (11,12,13) , and this value is updated as an atribute for acounts dimension.
what i want to achieve now is to implement a rule that can take the atribute from acounts dimension and compared with the name of the groups and somehow consolidate only the acounts with the right atribute.. did i explain that well? xD
the real request is to make more simple the input table for the client so he can changes the acounts in diferentes groups, but he WANTS to see a table like that.
sorry for asking this again, but im still learning how to use tm1. Any help would be great.
Thanks
Kazêh